-
Notifications
You must be signed in to change notification settings - Fork 12
Make it easier to create new commitfests #25
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
Comments
Hi @JelteF , I have been meaning to start my open source contributions and thought this might be a good issue to begin with. I have good grasp on Python and related frameworks. Can I take up this issue and try to resolve it? |
Sounds great. Feel free to ask questions in the #commitfest-dev channel in the "PostgreSQL Hackers Mentoring" discord: https://discord.gg/XZy2DXj7Wz |
Sure! Thanks for letting me know. I will check it out. |
Updated commitfest\admin.py to ease the starting and ending action on a commitfest via a drop-down list.
Updated commitfest\admin.py to ease the starting and ending action on a commitfest via a drop-down list.
My plan for this is to have a python script that knows the workflow schedule, looks the current date and the collection of open CFs, and determines whether it is in a new month AND the set of CFs represents the prior month. If that is the case it can perform the few actions (create new and status change) needed to change the overall workflow state from the prior month to the current one. If that isn't the case it does nothing. Schedule it to run via cron on the first of the month. Optionally, run it daily since its behavior should be idempotent. |
Specifically, I can already use the calendar I posted on Discord to derive these 2025 month changes:
|
Currently new commitfests need to be created from the admin panel, and dates need to be filled in manually. I think the easiest would probably be to have a "start commitfest" button that does:
Then there could also be an "end commitfest" button that does:
Obviously these buttons should only be pressable by some type of administrator role.
The text was updated successfully, but these errors were encountered: