Re: [Cooker] the end is inevitable
On Thursday 06 February 2003 12:02, Warly wrote: > Ben Reser <[EMAIL PROTECTED]> writes: > > My opinion had been changed by Fracios but given recent events. I've > > changed my opinion back. Unfortunately, Mandrakesoft has sat on these > > recent events. As usual, Mandrakesoft sits on the truth of the events > > that swirl around. We ultimately don't get the details. > > > > I suspect we are all wasting our time anymore. I suspect the end is > > inevitable. > > I agree, it is time to change. > > Difference between Mandrake employees or not is nonsense, it should only > exist one community, like debian one. That sounds good to me. > > I propose to create and contruct MandrakeLinux development on this > community, with strict rules on who is doing what, and the affected > tasks for each, and where anyone which is part of the developers > community have certain power to commit changes. > Sounds very good > The difference must be who is a mandrake developer and who is not, and > forget who is mandrakesoft employee and who is not. > ACK. At the moment I feel like confusion when I read cooker. No seperation, some things get lost, a lack of communication and so on. It seems to me you have to rant to get heared. Thats inacceptable, frustating and does not make things better. For the coming release I guess the things don't get better. (Much more traffic on cooker). -- 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] the end is inevitable
On Thu, 2003-02-06 at 06:02, Warly wrote: > I agree, it is time to change. > Difference between Mandrake employees or not is nonsense, it should only > exist one community, like debian one. That is the best idea I have heard in a LONG time. It may be hard to change from the current system to a developer-community based system, but I think everything would work a lot better after the change. > I propose to create and contruct MandrakeLinux development on this > community, with strict rules on who is doing what, and the affected > tasks for each, and where anyone which is part of the developers > community have certain power to commit changes. This is also good. Often I find I'm working on the same thing as one or two other people when I could be doing something new and more productive. > The difference must be who is a mandrake developer and who is not, and > forget who is mandrakesoft employee and who is not. Well right now, volunteers and employees have different attitudes, different responsibilities, and different resources. Right now it's like a four tier system: Employee-Developer Volunteer-Developer Volunteer-Helper (you know, bug reports, beta-testing, cooker trolling) User We should stive to create a TWO tier system Developer User The developers should be divided up based solely on TASK. What are you working on? What resources do you need? How can we let everyone else know that you are in charge of that task and there are a LOT of other tasks available to be worked on? As you said, it works well for Debian. They don't have 'volunteers', they have developers. And it's not because they're not a company. It's because from the main decision makers down to the guy who contributes one .deb file or one piece of documentation, they are all treated equally and they feel like one team of developers. > We can also discuss if we need to change the name, as Mandrake is > likely to have some trouble again because of this copyright on > Mandrake the magician (NewDrakeLinux? DrakeLinux?) Well, although I like the name Mandrake, it would make a media splash if the name was changed. And if people heard about a debian-like distro, highly community based, with a corporate back-end, it might attract a lot of new developers. It might also make some skeptics more likely to contribute without fear that the corporation will go under and their work will be lost somehow. Let's keep talking about this. 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] the end is inevitable
- Original Message - From: "Warly" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Ben Reser" <[EMAIL PROTECTED]> Sent: Thursday, February 06, 2003 12:02 PM Subject: [Cooker] the end is inevitable > Ben Reser <[EMAIL PROTECTED]> writes: > > > On Tue, Jan 28, 2003 at 06:37:57PM +0200, Buchan Milne wrote: > >> The hope was that it would be implemented per-urpmi-source, so that for > >> example if I was maintaining a bunch of desktops with 3rd-party > >> software, I could associate a company key with the company urpmi source, > >> and packages would be updated automatically (if I run urpmi --update > >> from cron). > >> > >> PLF would also gain from this? > > > > I have the code for this partly done. I haven't been working on it or > > for that matter anything else related to Mandrake because I have little > > time to sit around and argue to get contributions in. So I've found > > other things to do with my time. What I do still do is the stuff I > > actually need and post to my own tree. > > > > My opinion had been changed by Fracios but given recent events. I've > > changed my opinion back. Unfortunately, Mandrakesoft has sat on these > > recent events. As usual, Mandrakesoft sits on the truth of the events > > that swirl around. We ultimately don't get the details. > > > > I suspect we are all wasting our time anymore. I suspect the end is > > inevitable. > > I agree, it is time to change. > > Difference between Mandrake employees or not is nonsense, it should only > exist one community, like debian one. > > I propose to create and contruct MandrakeLinux development on this > community, with strict rules on who is doing what, and the affected > tasks for each, and where anyone which is part of the developers > community have certain power to commit changes. > > The difference must be who is a mandrake developer and who is not, and > forget who is mandrakesoft employee and who is not. > > We can also discuss if we need to change the name, as Mandrake is > likely to have some trouble again because of this copyright on > Mandrake the magician (NewDrakeLinux? DrakeLinux?) > > -- > Warly > Was'nt this what Gael Duval talked about in an interview for a few weeks ago? About "Mandrake Foundation" or something?
