DiffSK/configobj

Move this project to Jazzband?

Opened this issue · 10 comments

Cf. #160 – last release is from 2014.

See their FAQ, the "about" page, and guidelines.

ping @robdennis & @EliAndrewC

tjbp commented

Can we consider nearly 10 months to be sufficient time for the input of @robdennis and @EliAndrewC to be unnecessary?

As I’m sure you can appreciate, this has been a weird year.

I can follow up with Eli, but this project is in somewhat of a weird spot where we offered to help update something owned by Michael Foord (http://www.voidspace.org.uk/) And it’s not obvious if we should get his blessing.

Eli has been the only one of us paying attention to this for the last few years, so I think the next step is to figure out with him what we want to do.

For now a new release with the fix that moves _version.py into a relative package import rather than clobbering the global PYTHONPATH namespace would be great. Since that seems to be the main motivation for moving the project anywhere (and is the reason @tjbp is here).

Ref: https://bugs.archlinux.org/task/68893

Whoops, yeah speaking for myself it's been a weird year, and I don't see myself having time to support this project in the near future, and I don't want to stand in the way of others who DO have that time to provide that support. I also don't object to having my name taken off the list of active owners/maintainers since it's been a couple of years at this point since that accurately described my role in this project.

FWIW, moving this project to Jazzband seems fine with me, under the general principle of "the people putting in the work should be making those decisions" :)

I confess I don't recall what access we've already given or whether I'm blocking anyone by e.g. not having shared access to the PyPI project at https://pypi.org/project/configobj/ so please let me know what if anything is needed for me to not be standing in the way.

I'm already maintainer on PyPI, but I'd need Owner status for the project to be manageable at a new home.

If I only have to handle final release management and others handle PRs etc, this is doable. and the main JazzBand requirement would be fulfilled. If building a core contributor team actually works, the hope is more people being able to fully manage the project would emerge over time.

So we need either of you to extend the PyPI owner group, and also transfer the project here between orgs (because that needs GitHub owner rights).

I believe I have just now made you an owner on pypi. That’s what I’m able to do for the moment.

Thanks for that. You'd also need to do that for https://pypi.org/project/validate/

Jazzband or equivalent does seem like a good long-term option, but I don't feel up to figuring it out myself before 5.1.0 release.

I'd need someone who wants to own that I think