Maintain django-eav?

[dorey]

If you would like to maintain this project, please post here. I think I'm now the only person that looks at these PRs, but I don't use this app myself.

Alternatively, we could ask github to point to a different fork as the root node, if someone else is keeping it up-to-date with django updates, etc. (E.g. SideStudios/django-eav and @drewisme)

Pinging the most recent contributors-- @Michael-Spirit @novoxudonoser @jpwhite3 @Torjas

Thanks

[ghost]

@dorey I might help a little bit as I need it these days...

[jpwhite3]

@dorey I'm interested. I use a heavily modified version for my needs today.

[tiuma]

Hello, this app is still mainteined? Are there some fork running under python 3 and Django 1.10?
Thanks in advance!

[dorey]

Alright, @Sahloul and @jpwhite3 , I have added you as contributors. Sorry for the delay, but if anyone else wants commit rights then please post here.

I think a good policy is to follow the github-flow model for changing the repo (no commits to master, all changes come in the form of a pull request from a branch or a fork).

[jpwhite3]

Open question: Should support of this be limited to the most current Django LTS release, so 1.8 onward until the next LTS this spring?

[ghost]

I guess it is fair enough to do so..

[IwoHerka]

Hey, I'm pinging this thread to let you guys know about this issue I've opened: #56 (which may be of interest)

[madEng84]

Hi guys, @ghost seems to be a deleted user.
Is this project currently mantained?
What about Compatibility with django LTS version 1.11 and python3?

Thanks a lot

[madEng84]

@IwoHerka thank you, I'll take a look at it ;D

Guys, what do you think of deprecating this package if not mantained?

[sshishov]

What package we should use? django-eav or django-eav2?