-
-
Notifications
You must be signed in to change notification settings - Fork 595
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
Need for 2nd maintainer #329
Comments
Other option: transfer project to https://jazzband.co/ |
I've now applied some patches to my fork: https://github.com/claudep/tablib |
@claudep are releasing your fork on PyPI as well, or only keeping a github fork around? |
I'm still reluctant to go forward with the fork, as I find it so weird that an eminent developer like Kenneth is not even able to say a word about this package maintenance. If someone reading this knows him personally, please take the time to talk to him! |
I've reached out to Kenneth through a Twitter DM, that's my best bet to get in touch. Other than that, I'd be willing to step up to maintain this, I think it must be possible to set some time aside on a Friday afternoon at $dayjob to get things sorted out. |
Kenneth has replied through Twitter - so we're making progress here. I'm totally okay with taking up maintenance, but also don't want to be 'snapping' away this, so if anyone else wants to step up, maybe it wouldn't be bad to have multiple people added with write permissions on github and PyPI. |
I think everyone will welcome any responsive maintainer, so feel free to continue what you started. |
@sergei-maertens go for it. Thanks for contacting Kenneth. How about the other projects (records, etc.). They are quite interdependent and some long-term issues were blocking progress in other projects. To me it seems like a fleet of ships, which shall be somehow coordinated and would benefit with spare commander when the captain is busy with other stuff. |
I'm not familiar with the other projects (well, except for requests, as a user), so I'd limit myself only to tablib. I'm fine with keeping other projects in mind when working on tablib - as long as I can be properly informed, but I'm sure that will work out. As for the other projects - I had success reaching out via Twitter, but I'm also hesitant to say 'just DM him there' for obvious reasons. Maybe on my next contact I should just ask to review the call-for-maintainers issues on the other projects? Is there any other project than records that needs more maintainers? |
@sergei-maertens Any progress on this? |
Unfortunately not
…On Fri, Aug 10, 2018, 20:21 Claude Paroz ***@***.***> wrote:
@sergei-maertens <https://github.com/sergei-maertens> Any progress on
this?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/kennethreitz/tablib/issues/329#issuecomment-412165424>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFQ01o0Dm4SxXbDQ2W9oVc0mwlSEsi-Aks5uPc80gaJpZM4TVm2W>
.
|
@sergei-maertens I see that you approved this one: https://github.com/kennethreitz/tablib/pull/325, is the maintainer issue solved? @claudep are you still maintaining your fork? we would like to avoid having a fork just for https://github.com/kennethreitz/tablib/pull/325 |
It is not - I haven't heard back from Kenneth
…On Wed, Sep 12, 2018, 11:22 Manel Clos ***@***.***> wrote:
@sergei-maertens <https://github.com/sergei-maertens> I see that you
approved this one: #325 <https://github.com/kennethreitz/tablib/pull/325>,
is the maintainer issue solved?
@claudep <https://github.com/claudep> are you still maintaining your
fork? we would like to avoid having a fork just for #325
<https://github.com/kennethreitz/tablib/pull/325>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<https://github.com/kennethreitz/tablib/issues/329#issuecomment-420576199>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFQ01r127xUEY4WPES6JfOx4sKdhQkZFks5uaNJrgaJpZM4TVm2W>
.
|
Sergei, would you suggest a way forward? Should we create some sort of official unofficial common fork 😬 |
Oh, @iurisilvio, do you plan to be (regularly) active again? What's your take about this issue? |
Interested to hear what @iurisilvio has to say about it, otherwise I would indeed go forward with an 'official' unofficial fork and hope that the changes can then be merged back upstream at some point. The main issue right now is that we can't release new versions on PyPI. @iurisilvio - can you add maintainers on PyPI, or is that something only Kenneth can do? |
Without response or assistance from @kennethreitz or @iurisilvio I can't see an alternative to forking. |
I’m not opposed to it |
Great news! it would be awesome to transfer the repository to the Jazzband organisation (https://jazzband.co/). @kennethreitz would you agree? |
I'd strongly vote for jazzband. curious how this continues.... |
@kenneth-reitz , now that you have put efforts in the past to make that library, that you have users using it, contributors willing to contribute and people willing to maintain it, and that you understandably have no time nor interest to take care of it anymore, acknowledging the latter fact and making a move to pass on the responsibility would be a very nice move to let the project continue it's life. People here on in an organization like jazzband are willing to do that work. Independent forking of the project could move the project forward, but would have to regain the user base, which is quite close to letting the project die like it is now the case. Both case would be quite a shame, and would not make honor to all the work done until now. I really liked the API and was using it at work, but because of a small bug that was just waiting for a maintainer to merge the fix for months, we had to reinvent the wheel and recreate a subset of the API, and then moved to using pandas, which is absurd for the use that we have of it. I'm relatively new to open source, and I can't understand how the creator of a project can possibly prefer it's project to die than letting it live it's life in the hands of other people. |
Thanks to all of you for reaching out. It seems like we all want the same thing. We'll try to get things running again here. If anyone wants to help out as a maintainer / contributor for tablib, please reach out to us at: not-kennethreitz/team#17 Or have a chat at our discord: https://discord.gg/sps3Fj |
I guess the ticket could be closed now, thanks @timofurrer for taking the lead! Don't hesitate to reach to me if you need help. |
Could someone update this issue on how the ownership moved to @vinayak-mehta (just so that we understand what happened)? Was there not any support for moving the project to Jazzband? |
Kenneth decided to find a new home for all his repos, and Vinayak kindly volunteered for tablib. not-kennethreitz/team#21 (comment) +1 to Jazzband, it'd would be a good home, a lead developer (or developers) are still needed, and Jazzband can help provide some support for everyday admin/maintenance/release/infra stuff. This has also been proposed for other repos in not-kennethreitz/team#21. |
Transfering to Vinayak did not improve the situation at all. |
Sorry I haven't been able to spend time here. I can transfer ownership to Jazzband. Or should we perhaps move it to PSF where some of the other projects went? |
I see only requests went to PSF. Jazzband might be a good home, albeit having mostly Django-specific projects. What do @iurisilvio and @timofurrer think? |
I would also like to suggest camelot-dev as a possible alternative. I volunteered to maintain tablib was because of its alignment with camelot. We can possibly change the org name to something else and build a home for projects that deal with tabular data (maybe other types of data too). We can add more maintainers to the org, right now there's only @dimitern and me. |
The benefit of Jazzband is there's more backup in case people are too busy. They can especially help with things like releases (and partially automating releases). |
I'm no longer maintaining here nor do I feel responsible. |
Thanks for your thoughts! I've initiated a transfer of tablib to Jazzband :) |
Not quite yet, bear with me 😅 Should we create a tablib team at Jazzband who will have write access to master? (considering tablib is used by a lot of other projects) Right now, every member will be able to push to master. I think we'll have to ask Kenneth to add |
As for me, I'm trusting Jazzband members. If anyone tries to abuse the system by not respecting the code of conduct, he'll probably be excluded and any commit can be reverted anytime. |
Cool, I guess that makes sense since we haven't heard cases of people not respecting the Jazzband code of conduct. |
Simply protect master, should do. |
I did the transfer by not selecting any of the boxes just to check if that'll work and it did 😅 Can everyone still write to master? I guess those check boxes were for repository settings, because I can't see them now. |
@timofurrer, we need you to add jazzband account to PyPI project as maintainer role. |
done 👍 🎉 |
As @hugovk mentioned in PR #310, we have a maintainer issue with tablib (similarly with
records
).Facts:
0.12.1
released on Sep 1, 2017To summarize:
tablib
from users as well as from contributors.Proposal for next actions:
The text was updated successfully, but these errors were encountered: