[PROPOSAL] Better organization of the devel team
Hi there, At the last crux IRC meeting we discussed the distribution of resposibilities, and I'd like to pick up that idea a even go a bit futher and suggest a reorganization of our team, to better assign and distribute responsibilities. Rational -------- Ever since we've taken over the whole project from Per, there are a number of jobs which aren't clearly assigned, and no one really feels responsible for. Because of that, some jobs are neglected, or not done right, since no one feels responsible to do them. One typical problem was the server outage of crux.nu recently. Another problem I personally face it the lack of focus, since I'm involved in several jobs (many of which I'm just doing because no one else does...); introducing these teams would hopefully allow everyone to focus on their primary duties, and therefore allow us to make our jobs better, and most important, make it more fun: often when posting ideas to crux-devel, the feedback was rather limited (e.g. Simone's setup, Matt's ISO changes); this is probably because the majority of the readers doesn't really care, which is perfectly fine, but frustrating for those putting the work into something. With the team hierarchy, such posts could be discussed in the 'core' group only, meaning that there's real feedback, and giving back the motivation to those doing the work. Idea ---- Introduce team for 'ports', 'infrastructure' (website, mailing lists, crux.nu, all the cronjobs) and 'core development' (utilitites, setup, releases), with a leader each (this means that if there's a problem, there's a defined person to talk to) and clearly assigned tasks and responsibilities. These teams could also recruit independently, so we can fetch someone into the infrastructure team even if he can't create ports, as long as he's fit for the job. Procedure --------- If this proposal is accepted, I'd suggest to define the responsibilities of the teams, and look for team leaders. Problems -------- Finding leaders could be one, as well as finding enough people for the infrastructure team, although I'd hope that the more focused recruiting should help there. As always with such proposals, every crux developer can vote, so I'd appreciate hearing from you :-). Best regards, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
On 08/06/06 13:04 Johannes Winkelmann wrote: Hi,
Idea ---- Introduce team for 'ports', 'infrastructure' (website, mailing lists, crux.nu, all the cronjobs) and 'core development' (utilitites, setup, releases), with a leader each (this means that if there's a problem, there's a defined person to talk to) and clearly assigned tasks and responsibilities.
+1 vote for the proposal. It would also be nice to keep track of such categorized tasks & ideas under our current bugtracker. I take the chance of writing about a couple of related things I think we need to address shortly: 1. Next IRC meeting: discussion about teams (if the proposal get approved), next release(s) timeframe, etc. 2. crux.nu updates. the current setup is quite outdated; I don't dare to touch anything since we've a bunch of different services configured by different people. Besides of updates, a cleaner (documented?) setup would be great. This is a potential job for the infrastructure team. Regards, Simone -- Simone Rota Bergamo, Italy - http://www.varlock.com
On Sun, Aug 06, 2006 at 01:04:34PM +0200, Johannes Winkelmann wrote:
Idea ---- Introduce team for 'ports', 'infrastructure' (website, mailing lists, crux.nu, all the cronjobs) and 'core development' (utilitites, setup, releases), with a leader each (this means that if there's a problem, there's a defined person to talk to) and clearly assigned tasks and responsibilities.
These teams could also recruit independently, so we can fetch someone into the infrastructure team even if he can't create ports, as long as he's fit for the job.
my vote: +1 I'll go on holiday the next 2 weeks. So, if there's anything to decide, decide well ;-) regards Juergen -- Juergen Daubert | mailto:jue@jue.li Korb, Germany | http://jue.li/crux
On Sun, Aug 06, 2006 at 01:04:34PM +0200, Johannes Winkelmann wrote:
Idea ---- Introduce team for 'ports', 'infrastructure' (website, mailing lists, crux.nu, all the cronjobs) and 'core development' (utilitites, setup, releases), with a leader each (this means that if there's a problem, there's a defined person to talk to) and clearly assigned tasks and responsibilities.
These teams could also recruit independently, so we can fetch someone into the infrastructure team even if he can't create ports, as long as he's fit for the job. Sounds like a good idea. In fact I have nearly the same opinion about responsibilities but I have to admit that I am no exception her. The job of the maintainer for the portdb was assigned to myself (on my wish) but I haven't managed to get involved in it yet.
Procedure --------- If this proposal is accepted, I'd suggest to define the responsibilities of the teams, and look for team leaders. Of course I like this proposal and therefore accept it.
I myself could imagine to work/be in the ports team. Working as the maintainer for the portdb or testing/verifying ports would be fine. Regards Viper
Hi, By the end of August I will no longer be able to actively maintain my ports--this Fall is going to be the hardest semester of university yet. ;-) I'm not sure what my formal responsibilities could be called. KDE maintainer--certainly--plus desktop-related stuff, multimedia, and things that I think are really useful like shorewall, rsnapshot, ntp, etc. 112 ports is a lot to just move to the attic over the weekend, so I'd like this email to be a sort of advance notice and a request to start adopting my ports. I'll also stop serving my personal httpup repository, so if anyone feels like checking any of them into opt (cabextract or buffer come to mind...maybe digikam), please do so soon. I will continue to provide a tarball of the repository on my web site, and Younès <ycrux@club-internet.fr> has expressed a willingness to adopt these ports, so none of this repository will be lost. What I feel is the more pressing issue is that I don't really have the time to package and test KDE anymore, nor have I found someone to inherit the responsibility of doing so for both the latest, and future releases. Ideally I think that it would be nice if someone would maintain the official parts of KDE in opt, and then publish anything KDE-related as a kde-extra.httpup repository. I don't think that it really matters if all of my other ports become fragmented among multiple maintainers, but it makes sense for bulk of the KDE stuff to be handled by one or two people. I will transfer all of my convenience scripts, sources for update information, KDE packager email list, pre-release tarball downloading procedures, etc. to whoever we find (assuming he or she might want any of these). `hope you will know of someone who might be interested in adopting our KDE implementation (I haven't asked him yet, but possibly Younès?), Nick
On 08/12/06 12:18 Nick Steeves wrote:
Hi,
Hi Nick,
By the end of August I will no longer be able to actively maintain my ports--this Fall is going to be the hardest semester of university yet. ;-)
Sorry to hear that, thank you very much for your work so far, and good luck with the hot semester :) If real life happens to slow down a bit (I've heard sometimes it does), it'll be grate to benefit from your contribution again. Best regards, Simone Simone Rota Bergamo, Italy - http://www.varlock.com
Hi Nick, On Mon, Aug 14, 2006 at 18:54:08 +0200, Simone Rota wrote:
On 08/12/06 12:18 Nick Steeves wrote:
Hi,
Hi Nick,
By the end of August I will no longer be able to actively maintain my ports--this Fall is going to be the hardest semester of university yet. ;-)
Sorry to hear that, thank you very much for your work so far, and good luck with the hot semester :) I can only join Simone here, thank you for the work you put into CRUX and also wish you all the best for your studies.
Best wishes, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
Nick Steeves [2006-08-12 04:18]: Hi Nick,
By the end of August I will no longer be able to actively maintain my ports--this Fall is going to be the hardest semester of university yet. ;-) I'm not sure what my formal responsibilities could be called. KDE maintainer--certainly--plus desktop-related stuff, multimedia, and things that I think are really useful like shorewall, rsnapshot, ntp, etc. 112 ports is a lot to just move to the attic over the weekend, so I'd like this email to be a sort of advance notice and a request to start adopting my ports.
I'll look through the list, I think there's a few ports of yours that I use regularly... Good luck with your studies, Tilman -- A: Because it messes up the order in which people normally read text. Q: Why is top-posting such a bad thing? A: Top-posting. Q: What is the most annoying thing on usenet and in e-mail?
Johannes Winkelmann wrote:
Idea ---- Introduce team for 'ports', 'infrastructure' (website, mailing lists, crux.nu, all the cronjobs) and 'core development' (utilitites, setup, releases), with a leader each (this means that if there's a problem, there's a defined person to talk to) and clearly assigned tasks and responsibilities.
These teams could also recruit independently, so we can fetch someone into the infrastructure team even if he can't create ports, as long as he's fit for the job.
my vote: +1 The amount of my spare time will increase in the end of September (finally, i hope). So i really look forward dedicating more time to CRUX in general (i haven't even updated to 2.2 - shame on me).
Procedure --------- If this proposal is accepted, I'd suggest to define the responsibilities of the teams, and look for team leaders.
I'd like to volunteer for the 'infrastructure' team. Website, server maintenance, portdb and so on. Regards Till -- http://www.tbmnet.de ___________________________________________________________ Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: http://mail.yahoo.de
Hi Till, On Tue, Aug 15, 2006 at 08:56:25 +0200, Till Biedermann wrote:
Johannes Winkelmann wrote:
Idea ---- Introduce team for 'ports', 'infrastructure' (website, mailing lists, crux.nu, all the cronjobs) and 'core development' (utilitites, setup, releases),
[...]
my vote: +1
The amount of my spare time will increase in the end of September (finally, i hope). So i really look forward dedicating more time to CRUX in general (i haven't even updated to 2.2 - shame on me). That's great to hear.
Procedure --------- If this proposal is accepted, I'd suggest to define the responsibilities of the teams, and look for team leaders.
I'd like to volunteer for the 'infrastructure' team. Website, server maintenance, portdb and so on. Cool, thanks. There were also volunteers to help with the contrib
collection, and Falk who will work on the wiki, so that's starting to look good.
Regards, Johannes -- Johannes Winkelmann mailto:jw@smts.ch Zurich, Switzerland http://jw.smts.ch
participants (7)
-
Johannes Winkelmann -
Juergen Daubert -
Nick Steeves -
Simon Gloßner -
Simone Rota -
Till Biedermann -
Tilman Sauerbeck