Development/maintenance status

[sotte]

What is the development status of this project? The last commit was on Jul 23, 2015, but there seem to be some interest in this project (issues as well as PRs).

Maybe it's possible to find a new maintainer for this project you guys don't want to keep maintaining it.

[Kriskras99]

I would love to take over this project.
In my fork I have implemented new tests and merged the current PRs. And in the dev branch I have added support for xdg-user-dirs and replaced CSDIL with KNOWNFOLDERID.

[zoofood]

Hi Guys,

I've discussed with the team here at ActiveState and we'll ramp up maintenance again on this shortly. Sorry for the delay.

Cheers,

-JR

[sotte]

Nice to hear that!

Maybe you can integrate @Kriskras99 changes.

[Kriskras99]

I will open a pull request when the other pull requests are merged or closed, because I depend on some of them.

[Kriskras99]

@zoofood could you start merging the already open pull requests (Especially #53, #56 and #64)? Then I could open a pull request for a new test framework, and give a more "correct" replacement for CSIDL.

[dgentry]

Hi @zoofood,

Do you know when "shortly" is? If it's going to be more than another week (just over a month since you last posted), maybe you could just add @Kriskras99's as a repo maintainer? If not, maybe we should all consider his stable fork to be the canonical one now. At my company, TwoPoreGuys, we would immediately use #64 and #81.

Thanks,
Dennis

[zoofood]

My apologies. The team was very busy, I'm moving things through here myself, kicking it off over the holidays here, but will take a bit of ramp up.

[Kriskras99]

Nice to hear, as soon as the pull requests are merged, I will squash my commits and open a pull request.

[WhyNotHugo]

TBH, since development has stagnated before (and picking this up again is also going a bit slow), maybe you ought to consider taking up a co-maintainer, so we're sure this doesn't happen again (it also increases trust by users/other devs).

[pradyunsg]

@zoofood Please do consider adding someone as a co-maintainer -- it would help reduce the bus factor here and improve the health of the project as a whole.

[pradyunsg]

@zoofood I'll be happy to be a co-maintainer for this project, if you're willing to add one. :)

[jhermann]

https://jazzband.co/ would be another option. 27 commits since the last release that could be published…

[ofek]

I agree that https://github.com/jazzband seems like the logical home

[pradyunsg]

Dropping in to say that I'm still interested in picking up maintenance for this package.