Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Development/maintenance status #79

Open
sotte opened this issue Nov 15, 2016 · 44 comments
Open

Development/maintenance status #79

sotte opened this issue Nov 15, 2016 · 44 comments

Comments

@sotte
Copy link

sotte commented Nov 15, 2016

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
Copy link

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
Copy link
Contributor

zoofood commented Nov 19, 2016

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
Copy link
Author

sotte commented Nov 19, 2016

Nice to hear that!

Maybe you can integrate @Kriskras99 changes.

@Kriskras99
Copy link

Kriskras99 commented Nov 19, 2016

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

@Kriskras99
Copy link

@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
Copy link

dgentry commented Dec 13, 2016

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
Copy link
Contributor

zoofood commented Dec 28, 2016

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
Copy link

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

@WhyNotHugo
Copy link

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
Copy link

@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
Copy link

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

@jhermann
Copy link

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

@ofek
Copy link
Contributor

ofek commented Feb 26, 2020

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

@pradyunsg
Copy link

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

@McSinyx
Copy link

McSinyx commented Mar 12, 2020

@pradyunsg: I think it's not that the @ActiveState team cannot maintain this, but they are like completely off the grid (sure @zoofood does not seem to visit GitHub very regularly, but there should be at least another team member with write access, or even just some minimal communication). It was really sad to see @ofek pinging for almost two weeks straight. I'll not be surprised to see you dropping the same message next year and still be entirely ignored.

@zoofood
Copy link
Contributor

zoofood commented Mar 30, 2020

Hi Gang,

I appreciate everyone's anxiousness/frustration/concern here. I originally took on maintenance as Trent and Srid had moved on and it needed a home and we were rebuilding our team at ActiveState. It has sadly languished at the bottom of my todo list in the last while. It is not any issue with ActiveState per se, we have plenty of community initiatives spread across many language ecosystems (Python/Perl/Go/Tcl) that we are putting time/money into and not the least of which we are building a platform by which the community can put together their own Python runtimes and dependencies, all built from source.

I always planned to get back to this project as I quite enjoy it and want to give back where possible. With that in mind, I am going to work internally at ActiveState to find some resources to get this project back in shape. If we can't put a meaningful effort into this project and get releases out we will hand it off by the end of April.

I have had several offers of help and many good options, thanks to everyone that has reached out.

Thanks.

-JR

@ofek
Copy link
Contributor

ofek commented May 5, 2020

@zoofood Any update?

@zoofood
Copy link
Contributor

zoofood commented May 6, 2020

Hi @ofek, thanks for checking in. Had some hurdles to get it on PyPI, will be resolved this week and the first of several updates will go out to get us current.

@pradyunsg
Copy link

goes to https://pypi.org/project/appdirs/

appdirs 1.4.4

Released: May 11, 2020

Hurray! 🎉

@ofek
Copy link
Contributor

ofek commented Jun 1, 2020

@zoofood Are we still considering donating the project?

I see a release happened, which is great! However, the only other development has been merging a shebang line removal and 2 PRs removing names of people who no longer maintain this...

@pradyunsg
Copy link

pradyunsg commented Jun 1, 2020

I'm up for picking up the maintenance of this package (my earlier offer to co-maintain still stands) and I'm still interested. I'll also echo the suggestion of making this a part of jazzband to ease the development overhead.

I also recognise that the world is... uhm... going through unprecedented times and making releases of OSS software falling lower in the priority list is OK. It'll still be helpful to know what the state of affairs is.

@eukreign
Copy link

eukreign commented Jun 1, 2020

I just joined jazzband (in anticipation of this project being moved over there) and thus also support moving this project there.

I have a PR pending on this repo that's been there for a week (and I see dozens others for way longer): #147

I work on a product which has been using appdirs (https://github.com/lbryio/lbry-sdk) for at least 4 years, so am very invested in continuing to maintain this project, ideally jazzband can adopt it, otherwise I'll have to fork it and contribute to the existing 70 forks (i'd rather not do that).

I can take the lead on this or support someone else here who's been pushing for this before me.

Let's just do something.

@ofek
Copy link
Contributor

ofek commented Jun 9, 2020

Any update?

@ofek
Copy link
Contributor

ofek commented Jul 1, 2020

I guess not?

@gaborbernat
Copy link

I always planned to get back to this project as I quite enjoy it and want to give back where possible. With that in mind, I am going to work internally at ActiveState to find some resources to get this project back in shape. If we can't put a meaningful effort into this project and get releases out we will hand it off by the end of April.

I understand that resource availability is an issue. However, considering this I think everyone would benefit if you'd bless 2 more people to maintain besides yourself. 17 pull requests open does not feel like a good place to be. Thanks for your efforts until now but consider offloading some of the work when you get busy with other things.

@ofek
Copy link
Contributor

ofek commented Aug 26, 2020

@zoofood Any progress on this?

@gaborbernat
Copy link

Feel free to open discussions at https://github.com/platformdirs/platformdirs

@WhyNotHugo
Copy link

Looks like issues for that repository are disabled.

@ofek
Copy link
Contributor

ofek commented Jul 10, 2021

I've just enabled them, try now.

jugmac00 added a commit to jugmac00/craft-cli that referenced this issue Nov 10, 2021
@elenakrittik
Copy link

☠️

@pradyunsg
Copy link

On a different note, we can close this out on the basis that 8734277 has happened.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests