View previous topic :: View next topic |
Author |
Message |
kernelOfTruth Watchman
Joined: 20 Dec 2005 Posts: 6111 Location: Vienna, Austria; Germany; hello world :)
|
|
Back to top |
|
|
Ant P. Watchman
Joined: 18 Apr 2009 Posts: 6920
|
Posted: Thu Aug 26, 2010 7:36 pm Post subject: |
|
|
I dunno, the vibe I get from those posts isn't that Gentoo needs more people, it's that some other devs screw up over and over and nobody puts them in their place. I'd say it needs LESS people. |
|
Back to top |
|
|
dE_logics Advocate
Joined: 02 Jan 2009 Posts: 2253 Location: $TERM
|
Posted: Tue Sep 07, 2010 4:25 pm Post subject: |
|
|
^
That's an issue. We have 4 package managers already (including entropy). _________________ My blog |
|
Back to top |
|
|
smartass Apprentice
Joined: 04 Jul 2011 Posts: 189 Location: right behind you ... (you did turn around, didn't you?)
|
Posted: Mon Apr 16, 2012 11:19 am Post subject: |
|
|
dE_logics' thoughts made me think about this:
Perhaps "developer hierarchy levels" should be introduced. We already have a council anyways.
What I'm getting at is that some devs concentrate more on portage, some more on ebuilds, etc.
Not everyone has the necessary skills/experience to do certain things, so I believe devs should be more restricted to certain types of task that they are best at. Also, based on their experience (which could be quantified by the number/size of their commits, elapsed time of being a dev, how often they commit, etc.) they could be granted different permissions (commit access) and privileges.
Benefits:
- unprivileged devs lacking skills couldn't screw up things they should't be playing with anyways
- for low-level dev positions the entry effort could be a bit lower which could lure in more people
- devs would have a better understanding of who's working on what and therefore they could concentrate on their own tasks without being interrupted by other people asking them to do something beyond their expertise
- this system would make sure that somebody isn't assigned too many tasks which he wouldn't have time to work on and these tasks that would otherwise just collect dust could be assigned to someone else
There already projects resembling this, like the sunrise overlay, proxy-maintaner project, maintainer assignments, liveDVD "one-man-teams", gentoo council, herds, etc.
However, these efforts aren't fully integrated, do not constitute a clear hierarchy and don't always cooperate or even work on similar stuff, duplicating functionality. This is what I'm getting at.
I believe making clearer who's responsible for what and what are his privileges would be beneficial both for devs as well as for users.
P.S.: I'm not a dev (yet, would like to become one in the next few moths) and therefore my suggestions have no real significance, however, I have a lot of experience with working in teams and I believe these principles are essential. |
|
Back to top |
|
|
Etal Veteran
Joined: 15 Jul 2005 Posts: 1931
|
|
Back to top |
|
|
|
|
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum
|
|