Hi Russ

I understand that Alex is busy doing other things now. But he is the owner of 
the django-taggit repo. If someone is searching for django-taggit it's his repo 
that shows up. 

What you are suggesting, creating my own fork and fixing my issues there is not 
the solution. It would only lead to even more fragmentation. And I'm sure some 
of the 114 forkers already fixed a lot. That's why they've sent out pull 
requests.

I believe that if you publish a repo and you are the main contributor then it 
is your responsibility to maintain it. If you don't have time, then hand it 
over to someone else  or just give someone else the rights to push into your 
repo. I'm not asking Alex to fix all bugs himself, because most of the bugs 
have already been fixed by other people. He or someone with the rights to his 
repo just has to review the code and merge the pull requests, or deny them and 
guide the helper to a better solution. That would not take too long.

True, it's easy for me to just complain here without helping out. But there are 
others that are fare more involved in the project than me. I have several repos 
myself that I'm maintaining.

The approach of 'I just fix it myself' is maybe not the right one. If there are 
that many people working on one project it's probably better to just talk to 
each other first and coordinate the efforts.

Regards
Simon


Am 29.05.2012 um 01:27 schrieb Russell Keith-Magee:

> Hi Simon,
> 
> 
> So - if you're not happy with the state of django-taggit, then it's up
> to *you* -- not anybody else -- to fix the problem. Roll up your
> sleeves and get involved. Start addressing some of the tickets.
> Generate a private branch that merges all the pull requests. You say
> the hcarvalhoalves fork is the most maintained? Start submitting pull
> requests to them, instead of Alex. If they don't respond, start
> publicising your own fork. And when you've put in enough effort to
> show that you're serious, consider contacting Alex directly and see if
> he's interested in sharing ownership of the project, or passing the
> project off to you completely.
> 

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to