Skip to content
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

Project Lead: django-configurations #379

Open
uhurusurfa opened this issue Nov 9, 2024 · 8 comments
Open

Project Lead: django-configurations #379

uhurusurfa opened this issue Nov 9, 2024 · 8 comments
Labels

Comments

@uhurusurfa
Copy link

Project lead request.

Although usser pauloxnet was supposed to have project lead status, he remains unable to do anything significant. Additionally he has stated that he is very busy and suggezsred I apply to be included on the team so that there is more than 1 person to manage the project

@jezdez
Copy link
Member

jezdez commented Nov 13, 2024

From looking at the contribution history of @uhurusurfa (https://github.com/jazzband/django-configurations/pulls?q=sort%3Aupdated-desc+is%3Apr+author%3Auhurusurfa+is%3Aclosed+), I don't see much to indicate that you have a proven track record to maintain the project and this request doesn't contain other references to convince me otherwise.

I would suggest for you to provide more PRs for review. Because project leads can essentially release new versions unsupervised, the bar is higher than for usual Jazzband members (who already have a wide range of permissions). So my vote at the moment is a no.

@pauloxnet @blueyed What do you think?

@uhurusurfa
Copy link
Author

@jezdez - more than 2 weeks have passed and still no response from any team leads.
This project needs people who are actively using it and are interested in its upkeep.

Please let me know if you have a planb for this project or if you are willing to add me so we can get this project fully updated and keep contributors interested so that they continue to contribute by actually reviewing and processing theior PR's

@pauloxnet
Copy link
Member

I would suggest for you to provide more PRs for review. Because project leads can essentially release new versions unsupervised, the bar is higher than for usual Jazzband members (who already have a wide range of permissions). So my vote at the moment is a no.

@pauloxnet @blueyed What do you think?

I agree with you Jannis.

Building an history of contributions it's not difficult, I did the same. Not all contributions require a maintainer role to be merged as in the coverage related PRs.

@uhurusurfa
Copy link
Author

@pauloxnet - clearly you guys believe you are super experienced and know more than others who have been in the industry a lot longer time.
Sadly I completely disagree with your approach.
I will just fork the project and maintain my own version.

Good luck.

@uhurusurfa
Copy link
Author

uhurusurfa commented Nov 26, 2024

... and anyone trying to build up successful PR's will never get there because nobody is maintaining the django-configurations project.
It is quite short sighted to believe that a project maintainer must make a history of commits to the project they want to help ACTIVELY maintain. There is a lot more to having the skill to run a project than simply having made many little PR's to a single very very small project.

@webknjaz
Copy link
Member

@uhurusurfa xz-utils is still fresh is people's memory. That malicious actor also really wanted to help actively maintain the project, right until they stuffed a backdoor into a few releases.

@uhurusurfa
Copy link
Author

Clearly with 40 years in the industry I am a malicious actor.

@uhurusurfa
Copy link
Author

Note that IF there are actually other trusted project leads on the project and they actually were doing their job as project leads and reviewing PR's then it should not matter if there is a malicious actor.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants