Django-guardian: Django-guardian welcomes your support

[ad-m]

In recent months, the project did not have new releases. This was due to the lack of time on the part of the current project maintainer. Even I myself do not have time, and I do not even use django-guardian in any actively developed project.

This situation is not good for the project. It is necessary to devote some time for:

• reviewing outstanding issues to resolve them,
• helping people who make pull requests to the project to bring these changes to be consistent with the whole project,
• answering questions on Stackoverflow, because they appear there.
• dropping old-versions
• etc.

Who has a certain amount of time to carry out these tasks and lead the project further?

[kiran-capoor94]

Hi, I’m new here. Let me know how I can help.

[johnthagen]

Might be worth pinning this issue for more visibility.

[brianmay]

@johnthagen I didn't know you could do that. Thanks. Now done.

@kiran-capoor94 I noted that nobody replied to your request, at least not here. If you are still interested in helping, please see the list in the first message.

In particular, there are 16 pull requests open at present. Help reviewing these and fixing them up to a acceptable standard appreciated.

[DavisRayM]

Hey 👋 , I would like to help around where I can too. Picking up a few issues and contributing code for now.

[kiran-capoor94]

@johnthagen I didn't know you could do that. Thanks. Now done.

@kiran-capoor94 I noted that nobody replied to your request, at least not here. If you are still interested in helping, please see the list in the first message.

In particular, there are 16 pull requests open at present. Help reviewing these and fixing them up to a acceptable standard appreciated.

Thanks, will review.

[megaleunam]

I would like to help with some problems. i am currently using django-guardian on a project

[ad-m]

@melvyn-sopacua , there are 13 pull requests open at present. Help reviewing these and fixing them up to a acceptable standard appreciated. Notes that you don't see problems are also support. There are also open development issues, e.g. #694. Everybody can take it and provide pull requests to solve it.

[RainshawGao]

@ad-m Maybe you can consider jazzband.co. they are almost a django community.

[thclark]

@ad-m would you like to add me as a maintainer? Maybe give me pypi access too... I could at least triage some of the issue backlog, merge a few PRs and help get a new release out supporting django 3.2?

[ad-m]

Thanks for reporting. I am glad that you want to support the project. I don't remember you, apart from the last review unfortunately.

I propose to start in small steps with PR reviews. In the case of GitHub, anyone can publish reviews. After a certain period of cooperation, we will be able to grant special powers.

[RainshawGao]

Yes, but we may need an active maintainer who is familiar with django. Join jazzband.co is really easy for this.

[thclark]

Thanks for reporting. I am glad that you want to support the project. I don't remember you, apart from the last review unfortunately.

Been around since 2018 and had a lot of use of guardian with various use cases.

I propose to start in small steps with PR reviews. In the case of GitHub, anyone can publish reviews. After a certain period of cooperation, we will be able to grant special powers.

I think I'd second @RainshawGao - joining jazzband will take a lot of effort off your shoulders, ensure that experienced people are able to help with maintenance tasks, and save vetting people yourself (which I understand why you feel the need).

Also: it's worth noting that we can't review PRs unless we're maintainers. The best we can do is chuck in a few comments into the PR conversation which is helpful but not an actual review.

[michael-k]

The best we can do is chuck in a few comments into the PR conversation which is helpful but not an actual review.

Of course it is. The only difference is that if a maintainer adds a LGTM, everybody thinks that (s)he properly reviewed the code. Whereas a LGTM from a random person doesn't tell the maintainers anything. (Was the code properly review? Does the person just want this feature?)

There's no difference between a review from a maintainer or anybody else if it contains proper feedback instead of just a LGTM.