> I won't presume to speak for the core devs, but who wouldn't answer > "yes" to the question of need for more committers! :-) Then we need the "process of becoming committer". I don't want a worthless discussion on this question, like one month ago. Please, only core devs, and only "Yes, I admit", "No, I strongly resist". Even bazaar have to be organized in some specific way to be successful. Open source development process should not be equal to anarchy, when "everyone can do what they want, and we will commit/change only that we want." Sorry for being harsh.
> However, I don't know if I would necessarily agree with all your > points here. Given the recent Django sprint, much progress was made > in closing tickets and applying patches. Also, I wouldn't be fooled > by the total ticket count. There is a lot in there that will likely > be killed in one swipe by either the Queryset refactor or made > obsolete by newforms-admin being merged to trunk. For me, the process of developing Queryset refactoring totally went out of control. And everyone says that "all will be outdated after queryset refactoring release so we won't do anything now." Problems are also with development of newforms-admin branch, that trunk is not working for half week now (without patch appeared later and discussed in django-dev). Also, please, core devs, your answer on this situation. How do you see it? What do you do to improve it? > And like all open source projects, the way to gain commit access is to > have a proven record of good work on the project. Recent changes to > Django's Trac setup allow users to register and do work as the same > registered user, which will make it easier for core devs to recognize > consistently good work and promote a coder to commit access. Yes, but your ticket will stay uncommitted for months, even if you will put the patch! Moreover, the patch will become outdated after some time or some number of commits! I tried to add patches, but it's worthless now. It seems that changes happen only when you manage to get any of core devs interested in your ticket. Please, core devs. Your actions. One more comment. I'm asking not about "Should we(you) or not?". I'm asking about "How will you? And when?". It's project management question, actually. And a bit political one. Sorry for being offensive, again. I want to contribute stuff and see it working, but getting tired of bad management and bad workflow :( And BDFLs can't be in all places all time like they are trying to do now. IMO, the most important duties for them are to control the process (unless anyone else is doing this) and give responsibilities and rights to others. We can't run sprints each month (or can we?). -- Best regards, Yuri V. Baburov, ICQ# 99934676, Skype: yuri.baburov, MSN: [EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-developers@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-developers?hl=en -~----------~----~----~----~------~----~------~--~---
