> > I'm opposed to this. Firstly, unless I've missed something whoever > gets the position, would definitionally get it before they've done > anything! This is completely antithetical to the spirit of open > source, meritocracy. Why should design be treated any different from > other changes to Django? Changes to the design of the admin should be > handled in the same way as any changes, for a large change someone > writes up a proposal, starts work, asks for review, finalizes, and it > gets committed. That being said there is no reason a designer > couldn't have a commit bit, Wilson certainly does, but they'd have to > earn it the same way anyone else does. We don't need a formalized > process to get input from designers we trust, I ask for review from > tons of people who have no formal standing in the Django community > when I have questions that pertain to their area of expertise. > > In conclusion, there is 0 reason design needs to be treated different > from a procedural perspective. > > Alex >
First off, there are designers who have contributed great amounts of stuff to the Django community. Nathan Borror has his Basic Apps (which interestingly is a designer contributing code, because that's what he can contribute easily). The Grapelli team has that project which represents a large amount of open source code in the design realm around the project. There are countless others that have put in the time, and helped out around here. It's not like we're going to take in some random designer, these are people that we know and trust. I agree that this should be treated in the same way as development, is that not what we're proposing? We have the same role for a designer on the core team as for a developer. This seems like we are doing the same thing? It's not like the Czar/Core designer person will be able to just make commits to the code base whenever they want with no oversight. They will be just like a normal committer, people will be able to veto things and everything else. It just means that we have people who really know what they are talking about with design to make those decisions. A similar idea is when Simon asked for feedback on the security issues with Django's signing infrastructure. We don't have experts on the team to make those calls, so we need to bring in people who are knowledge in that area. If there was someone in the community who has contributed a lot, and knew a ton about security, it would seem like a no brainer to make them a committer, with a Czar-like power over security issues. I am merely proposing we do the same thing with design. Cheers, Eric -- You received this message because you are subscribed to the Google Groups "Django developers" group. To post to this group, send email to django-develop...@googlegroups.com. To unsubscribe from this group, send email to django-developers+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/django-developers?hl=en.
