Closed jazzband-bot closed 1 year ago
ping @mattseymour @scuerda @adamchainz @ParthS007 @dcwatson
Hello guys! Is there anything I can help with? If so, just let me know. I would love to lend a hand here.
@jacobian Hey there, would you mind adding the jazzband
to the PyPI project as co-maintainer so we can set up semi-automatic releases via GitHub?
Ah, well done @jezdez i was just about to ping @jacobian in relation to this. Seems like your are 7 hours in front of me 😉
Ah, well done @jezdez i was just about to ping @jacobian in relation to this. Seems like your are 7 hours in front of me 😉
Barely!
I added a issue for following the code contributing guidelines in the coming PRs but I couldn't assign myself.
Now that @jacobian has added jazzband to the PyPI project, it would be worth thinking about project leads for this, so we can speed up resolving https://github.com/jazzband/help/issues/292. In case anyone feels like they would be willing to be responsible for reviewing releases (docs: https://jazzband.co/about/releases), please let me know.
@jezdez I put a ticket in a little while ago jazzband/help#278 to put my name forwards on this project if it works for you.
@mattseymour If it's okay, I can join with you. I am taking it as a learning opportunity on handling releases and I already contributed a couple of pull requests. If it counts as experience, I have been maintaining my personal projects on pypi for sometime now. If it doesn't makes sense to have two project leads for this project, I want to be part of release process and any improvement/reviews in future anyways if possible. 😃
@jezdez I put a ticket in a little while ago jazzband/help#278 to put my name forwards on this project if it works for you.
Oh, I missed this one, thanks for pointing that out. I've added you and also added the needed release key to the repo for the automated release process, which stil needs the release GitHub Action workflow, that I can work on in the next few days.
@mattseymour If it's okay, I can join with you. I am taking it as a learning opportunity on handling releases and I already contributed a couple of pull requests. If it counts as experience, I have been maintaining my personal projects on pypi for sometime now. If it doesn't makes sense to have two project leads for this project, I want to be part of release process and any improvement/reviews in future anyways if possible. 😃
I'll let @mattseymour and @jacobian decide on this, since Jacob had already vouched for Matt in https://github.com/jazzband/help/issues/278 I think it's reasonable for them to make a call here, too.
In the meantime, feel free to join the project as a regular team member on https://jazzband.co/projects/dj-database-url.
@ParthS007 as mentioned by @jezdez feel free to join the project and lets see where things lead. 😄
Marking issue as closed. There is no other requirements from this issue for the time being.
This issue tracks the implementation of the Jazzband guidelines for the project dj-database-url
It was initiated by @jacobian who was automatically assigned in addition to the Jazzband roadies.
See the TODO list below for the generally required tasks, but feel free to update it in case the project requires it.
Feel free to ping a Jazzband roadie if you have any question.
TODOs
README
fileCONTRIBUTING.md
orCONTRIBUTING.rst
filejazzband
account to PyPI project as maintainer role (e.g. URL: https://pypi.org/manage/project/dj-database-url/collaboration/)jazzband-bot
as maintainer to the Read the Docs project (e.g. URL: https://readthedocs.org/dashboard/dj-database-url/users/)Project details