-
-
Notifications
You must be signed in to change notification settings - Fork 217
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
Implement Jazzband guidelines for django-dbbackup #417
Comments
@jonathan-s @ZuluPro Can you add me on as a maintainer within Read The Docs? |
Current roadblocks
|
Codecov doesn't need to be reconfigured, on the next test run it should just work. It's also not needed to be project lead to do any of that.
Not you personally should be assigned a RTD maintainer, but the jazzband-bot account. |
This isn't what the TODO above says, @jonathan-s @ZuluPro please add the jazzband-bot account. |
Regarding the project leads: The jazzband/help#262 proposal said that @Archmonger and @johnthagen want to become project leads. The problem is that @Archmonger doesn't have any commits in the project that would make it clear that they can make decisions for the project. That's a no-go I'm afraid since project leads are supposed to be able to review releases when they are made by contributors. A lack of prior experience with project means that's not going to work. @johnthagen Can you specify someone else? (also please join Jazzband on https://jazzband.co/ so I can add you as project lead) |
@jezdez The reality is that both @Archmonger and I are very new to this project but we volunteered to get it off the ground and compatible with Django 4.0. Given @Archmonger's other public Python/Django record and initiative/willingness to help I still believe he's the prime candidate for a project lead of this project. If we don't qualify for JazzBand, I understand. My main priority was to make sure |
Correct. We both only came on board to this project within the last ~20 days. The previous maintainers shifted the project onto us to pull into Jazzband due to lack of time commitment indefinitely. If I don't make the cut for not committing within that 20 day period that's fine. It was a busy EOY for me, but at least the repo is now maintainable within Jazzband. |
Wasn't certain if the bot would retroactively add maintainers, so I figured it'd be simpler from someone on the Jazzband side (myself/John) to add the bot to RTD. Currently, both John and I do not have RTD permissions. |
This comment has been minimized.
This comment has been minimized.
@jezdez Still need @johnthagen added as a project lead as well. |
@Archmonger Done adding @johnthagen as project lead. @johnthagen apologies for the long delay. |
@jezdez No problem. Thanks! |
This issue tracks the implementation of the Jazzband guidelines for the project django-dbbackup
It was initiated by @Archmonger 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/django-dbbackup/collaboration/)jazzband-bot
as maintainer to the Read the Docs project (e.g. URL: https://readthedocs.org/dashboard/django-dbbackup/users/)Project details
The text was updated successfully, but these errors were encountered: