I am intending to document all the components (from kernel up) that comprise the 6.0 release which we now have (thanks) and how they fit together and are managed by e-smith. I would find such a document useful (that's why I'm doing it). In fact I think it's the most useful way I can contribute at this point. I'll share.
The incentive to get me off my arse is Mitel's recent move. Not such a bad thing I don't think. I can read and write and I can cut code. If anyone has any text they think may be useful in this regard I'd be greatfull. I dissagree with you on this point though. Most (read substantial) "free" projects actually work because of the spin off business to their "owners". That was you guys and you WERE "boss". Someone has to decide on release contents and commit to it (and manage bug lists and ...). Try hearding cats sometime. If we (this group) don't move in a unified manner (same as you guys did) the "free" e-smith will most surely die. I'm going to try to prevent that (it's geat shit). Peter Lambert -----Original Message----- From: Charlie Brady [mailto:[EMAIL PROTECTED] Sent: Friday, 12 December 2003 11:26 AM To: Peter Lambert Cc: e-smith-devinfo Subject: Not enough Indians (Re: [e-smith-devinfo] Boss) On Tue, 9 Dec 2003, Peter Lambert wrote: > I also think we need to get a chain of command in place. Some hard > decisions are always needed. > > A lot of the names on the "volunteers" list are very familiar to anyone whos > been on devinfo list. I'm sure most of us could point the finger at people > who we'd respect enough to work for (as in take instruction, err guidance, > from). I disagree completely. Free software projects don't work that way. It's said that managing software developers is like herding cats; surely it's more so when the developers are volunteer and unpaid. Free software developers essentially work for themselves, and have to be self motivated. There aren't 437 device drivers in the 2.6 linux kernel because Linus directed a bunch of people to write them - they're there because a whole bunch of people had hardware that they wanted to get working. Co-ordination is definitely useful, but only if there is something to co-ordinate. There's lots of people out there with ideas, but they all count for nothing unless someone makes the ideas concrete. If you want to contribute, don't wait for "a boss" to tell you to do so. Find something that you'd like to see happen and make it happen, or at least start it happening. Work on the FAQ, for instance. Or document something. Have a poke around and understand how something works, and write down what you learn. Chances are that'll be useful to someone. -- Charlie Brady [EMAIL PROTECTED] Mitel Networks Corporation http://www.mitel.com/ Phone: +1 (613) 592 5660 or 592 2122 Fax: +1 (613) 592 1175 A: Because we read from top to bottom, left to right. Q: Why should i start my reply below the quoted text? -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Searchable archive at http://www.mail-archive.com/devinfo%40lists.e-smith.org
