Re: [Cooker] How Debians do it
Damian Gatabria [EMAIL PROTECTED] writes: I would certainly do more than troll the list and file bug reports if there was something that told me what needed to be done. If I could scroll through a ToDo list and volunteer for specific tasks that my skill set would allow me to do well, I would be able to contribute a lot more to the project. I've been following these threads with much interest, and i must say i feel eager to contribute in whatever way i can. A ToDo list and the ability to volunteer for specific jobs sounds very good IMO. :o) If I find some time next week I will try to put in place a first version of a page with such features. However in a first time bugzilla bugs are more or less a TODO, just browsing and see if you could fix some of them is a very interesting first step. -- Warly
[Cooker] How Debians do it
For anyone who doesn't know, I looked into how Debian organizes their development community: 1. They have documents clearly outlining their goals and standards. http://www.debian.org/social_contract#guidelines http://www.debian.org/social_contract 2. They generally communicate through mailing lists: http://www.debian.org/MailingLists/ low volume: debian-devel-announce, debian-news high volume: debian-devel, debian-project, debian-mentors, etc. This is probably more developer friendly than my wiki suggestion. I still think we should have some sort of web-interfaced list of developers, contact info, and stuff they're currently working on, but yeah, mailing lists are much nicer for communicaiton. There is a cool website for new joiners: http://www.debian.org/devel/join/newmaint And their developer's reference is a bit more complete than our RPM-how-to: http://www.debian.org/doc/packaging-manuals/developers-reference/ 3. They have a clear list of what packaging needs to be done: http://www.debian.org/devel/wnpp/ 4. They have guides for writing documentation, website maintenance, translation, publicity, and quality assurance. These are all things that are underrated. Especially documentation and quality assurance. We should make sure that anyone who wants to help with these types of things feels invited and gets full credit where due. http://www.debian.org/devel/website/ http://qa.debian.org/ While debian still sucks in many ways (hehe), I think we could learn a lot from their community model, and get more done in less time, and attract a lot more help. Austin -- Austin Acton Hon.B.Sc. Synthetic Organic Chemist, Teaching Assistant Department of Chemistry, York University, Toronto MandrakeClub Volunteer (www.mandrakeclub.com) homepage: www.groundstate.ca
RE: [Cooker] How Debians do it
While debian still sucks in many ways (hehe), I think we could learn a lot from their community model, and get more done in less time, and attract a lot more help. I would certainly do more than troll the list and file bug reports if there was something that told me what needed to be done. If I could scroll through a ToDo list and volunteer for specific tasks that my skill set would allow me to do well, I would be able to contribute a lot more to the project. Gregory K. Meyer ___ Join Excite! - http://www.excite.com The most personalized portal on the Web!
Re: [Cooker] How Debians do it
On Thursday 06 February 2003 22:01, Austin Acton wrote: For anyone who doesn't know, I looked into how Debian organizes their development community: 1. They have documents clearly outlining their goals and standards. http://www.debian.org/social_contract#guidelines http://www.debian.org/social_contract 2. They generally communicate through mailing lists: http://www.debian.org/MailingLists/ low volume: debian-devel-announce, debian-news high volume: debian-devel, debian-project, debian-mentors, etc. This is probably more developer friendly than my wiki suggestion. I still think we should have some sort of web-interfaced list of developers, contact info, and stuff they're currently working on, but yeah, mailing lists are much nicer for communicaiton. Yeah this is an absolutly need. Current one-fits-all is not a solution. The different mailinglists of debian sounds like the way to go. There is a cool website for new joiners: http://www.debian.org/devel/join/newmaint Sounds nice too And their developer's reference is a bit more complete than our RPM-how-to: http://www.debian.org/doc/packaging-manuals/developers-reference/ Yeah documantation of the ways 3. They have a clear list of what packaging needs to be done: http://www.debian.org/devel/wnpp/ 4. They have guides for writing documentation, website maintenance, translation, publicity, and quality assurance. These are all things that are underrated. Especially documentation and quality assurance. We should make sure that anyone who wants to help with these types of things feels invited and gets full credit where due. http://www.debian.org/devel/website/ http://qa.debian.org/ While debian still sucks in many ways (hehe), I think we could learn a lot from their community model, and get more done in less time, and attract a lot more help. Austin Yes I'm impressed by the organisation. Every little detail that get on my nerves currently with mandrake is solved there. We need organisation !! -- Regards Steffen counter.li.org : #296567. machine: 181800 vdr-box : 87 Please dont CC me, since if I have replied I'll watch the tread. Both mails will be filtered to the ML-folder. Thanks
RE: [Cooker] How Debians do it
--- On Thu 02/06, Austin Acton [EMAIL PROTECTED] wrote: From: Austin Acton [mailto: [EMAIL PROTECTED]] To: [EMAIL PROTECTED] Date: 06 Feb 2003 18:57:25 -0500 Subject: RE: [Cooker] How Debians do it On Thu, 2003-02-06 at 17:07, Gregory K. Meyer wrote: I would certainly do more than troll the list and file bug reports if there was something that told me what needed to be done. If I could scroll through a ToDo list and volunteer for specific tasks that my skill set would allow me to do well, I would be able to contribute a lot more to the project. I think you just proved my point. I was trying to. Gregory K. Meyer ___ Join Excite! - http://www.excite.com The most personalized portal on the Web!
Re: [Cooker] How Debians do it
I would certainly do more than troll the list and file bug reports if there was something that told me what needed to be done. If I could scroll through a ToDo list and volunteer for specific tasks that my skill set would allow me to do well, I would be able to contribute a lot more to the project. I've been following these threads with much interest, and i must say i feel eager to contribute in whatever way i can. A ToDo list and the ability to volunteer for specific jobs sounds very good IMO. :o) Damian -- -- I don't want Windows to be only for the 31173. Yes, we've come a long way from all those security holes, virii, and cryptic commands like Edit textfile.txt (what in the hell is that supposed to mean?)
