Stefan van der Eijk [EMAIL PROTECTED] writes:
PS: Some friends have always argued that the debian way is the only
sustainable way to go. If mdk is going to do it just like debian, why not fold
and move the idea's and effort into making debian a better distro instead of
duplicating the effort?
On Thu, 2003-02-06 at 22:06, Pixel wrote:
Stefan van der Eijk [EMAIL PROTECTED] writes:
PS: Some friends have always argued that the debian way is the only
sustainable way to go. If mdk is going to do it just like debian, why not fold
and move the idea's and effort into making debian a
Adam Williamson [EMAIL PROTECTED] writes:
Pixel, if you're going to start distro wars, it's probably at least a
good idea to USE the other distro first. someone told me isn't really
good enough...
Pixel or me have been using debian for ages before MandrakeSoft *Grin*
On Thursday 06 February 2003 05:06 pm, Pixel wrote:
Stefan van der Eijk [EMAIL PROTECTED] writes:
PS: Some friends have always argued that the debian way is the only
sustainable way to go. If mdk is going to do it just like debian, why not
fold and move the idea's and effort into making
On Mon, 2003-02-10 at 15:06, tarvid wrote:
On Thursday 06 February 2003 05:06 pm, Pixel wrote:
Stefan van der Eijk [EMAIL PROTECTED] writes:
PS: Some friends have always argued that the debian way is the only
sustainable way to go. If mdk is going to do it just like debian, why not
- Original Message -
From: Adam Williamson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Monday, February 10, 2003 4:34 PM
Subject: Re: [Cooker] Creation of a community ( was : the end is inevitable )
On Mon, 2003-02-10 at 15:06, tarvid wrote:
On Thursday 06 February 2003 05:06 pm
On Mon, 2003-02-10 at 13:34, Adam Williamson wrote:
On Mon, 2003-02-10 at 15:06, tarvid wrote:
On Thursday 06 February 2003 05:06 pm, Pixel wrote:
Stefan van der Eijk [EMAIL PROTECTED] writes:
PS: Some friends have always argued that the debian way is the only
sustainable way to go.
On 7 Feb 2003, Gustavo Franco wrote:
In one months or two you're doing: apt-get update; apt-get -uy
upgrade.I can see :P
We have 'urpmi.update -a; urpmi --auto-select --auto' (I have this in
cron), and it gives me more than Debain does, unless Debian has XFS+ACL
support in the default kernel
Le Samedi 8 Février 2003 01:13, Gustavo Franco a écrit :
But, I don't think we need to be a carbon copie of Debian.
Debian is not the only volunteers OS project, everybody seems to forget
FreeBSD, and other, or even some smalls os, such as AtheOs, OpenBeOS, and
others, who don't work in
Le Samedi 8 Février 2003 10:47, Michael Scherer a écrit :
OpenBSD team release CDs each 6 month, as said before. They maintain the
four last release.
Well, a small mistake, they maintain two previous release.
ie, actually, 3.1 and 3.2.
--
Michaël Scherer
On Sat, 2003-02-08 at 08:49, Buchan Milne wrote:
On 7 Feb 2003, Gustavo Franco wrote:
In one months or two you're doing: apt-get update; apt-get -uy
upgrade.I can see :P
We have 'urpmi.update -a; urpmi --auto-select --auto' (I have this in
cron), and it gives me more than Debain does,
On Sat, 2003-02-08 at 07:47, Michael Scherer wrote:
Le Samedi 8 Février 2003 01:13, Gustavo Franco a écrit :
But, I don't think we need to be a carbon copie of Debian.
Debian is not the only volunteers OS project, everybody seems to forget
FreeBSD, and other, or even some smalls os,
But can you run Mandrake on more than ten architectures?
Well, if it was the main reason to use a Debian instead of another distro, we
should all be using NetBSD...
--
Michaël Scherer
Read the documentation, here:
http://www.openbsd.org/porting.html
Well, I just missed this one.
That is the problem to work when there is too much people in a small room.
Mandrake as a new project inside Debian.But it was refused here, many feels
involved.But if you change the original
On Sat, 2003-02-08 at 17:39, Michael Scherer wrote:
[...]
Mandrake as a new project inside Debian.But it was refused here, many feels
involved.But if you change the original idea, try debian-project ML.The
Debian-Mandrake can receive financial support of SPI as described by
Goerzen, more
If it was accepted, can you explain what we would do ?
We've two scenarios here:
1) Mandrake as a new subproject:
If accepted, you can contact Debian developers through two MLs:
debian-project and debian-devel.To discuss about a internal merge
with Desktop subproject or not and others
On Sat, 2003-02-08 at 18:49, Michael Scherer wrote:
If it was accepted, can you explain what we would do ?
We've two scenarios here:
1) Mandrake as a new subproject:
If accepted, you can contact Debian developers through two MLs:
debian-project and debian-devel.To discuss about a
So , merging the differences would not be interesting, for all the works
it represent.
Yes, but we can share our experiences.
Well, of course, I agree at 100 % .
But I really hope that nobody has waited this discussion to do so.
--
Michaël Scherer
Le Vendredi 7 Février 2003 00:50, Austin Acton a écrit :
On Thu, 2003-02-06 at 17:38, Michael Scherer wrote:
We also need to support equaly contribs and main, don't you think ?
Well, the problem is Mandrake says publicly we fully support the
packages in main, but not in contribs so they do
Michael Scherer [EMAIL PROTECTED] writes:
The difference must be who is a mandrake developer and who is not, and
forget who is mandrakesoft employee and who is not.
We should stive to create a TWO tier system
Developer
User
This sounds great, so , now, what is the definition of a
Austin Acton [EMAIL PROTECTED] writes:
I mean now, people are divided into categories like: contribs, club,
installation, documentation, printing, Mandrake employee, paying club
member, club VIP memeber, etc. etc. That bugs me.
Somehow everyone who's contributing tangible work to the distro
Stefan van der Eijk [EMAIL PROTECTED] writes:
Q: when can we do that? And who will make it happen... There are a lot
of bright people on the list that can help to make it happen. How do
we first define an architecture for this. Produce a document first?
We should progress step by step, the
Austin Acton [EMAIL PROTECTED] writes:
On Thu, 2003-02-06 at 16:06, Stefan van der Eijk wrote:
Q: when can we do that? And who will make it happen... There are a lot
of bright people on the list that can help to make it happen. How do we
first define an architecture for this. Produce a
Le Vendredi 7 Février 2003 01:16, Austin Acton a écrit :
1. Is there any hope of MandrakeSoft adopting a plan like this?
Since the beginning of the thread was Warly's post, I hope MandrakeSoft will
adopt this plan. After all, nobody talk about this after Ben Reser's post on
Slashdot (
Michael Scherer [EMAIL PROTECTED] wrote:
The problem is that if some people, ie Mandrake employees, have full control
of main, this would means that we are not fully equal.
That's not a problem, thats a fact of life ;)
Ever heard of Damocles sword? :)
Just take a look at the discussion
On Thu, 2003-02-06 at 20:28, Michael Scherer wrote:
But demand high quality for what they deliver. Otherwise, send it back.
Well, of course.
Peer reviews, but this would say tht some developpers hav more power than
others.
All developers should be treated as equals, but, some of them
On Fri, 2003-02-07 at 08:21, Warly wrote:
Stefan van der Eijk [EMAIL PROTECTED] writes:
[..]
Mandrake is a distribution focused on user, aimed to ease linux access
to everybody, and which is very reactive and on the cutting edge.
Debian is more developper oriented and with a timeframe which
Le Vendredi 7 Février 2003 12:35, Han Boetes a écrit :
Michael Scherer [EMAIL PROTECTED] wrote:
Just take a look at the discussion for Maildir in /etc/skel, which
involves changes in main. If there is a distinction between developers,
because some of them have control on main, and the
Le Vendredi 7 Février 2003 18:04, Gustavo Franco a écrit :
On Thu, 2003-02-06 at 20:28, Michael Scherer wrote:
Well, we could try something like morethan one developper per package.
Actually, in Debian, only the packager can change something.
If you take a look to the changelog of any of
On Fri, 7 Feb 2003 10:39:19 +0100
Michael Scherer [EMAIL PROTECTED] wrote:
The problem is that if some people, ie Mandrake employees, have full control
of main, this would means that we are not fully equal.
Maybe it's time then that non-emplyees/contributors get write access to main.
I
On Fri, 2003-02-07 at 18:17, Michael Scherer wrote:
Le Vendredi 7 Février 2003 18:04, Gustavo Franco a écrit :
On Thu, 2003-02-06 at 20:28, Michael Scherer wrote:
Well, we could try something like morethan one developper per package.
Actually, in Debian, only the packager can change
The difference must be who is a mandrake developer and who is not, and
forget who is mandrakesoft employee and who is not.
We should stive to create a TWO tier system
Developer
User
This sounds great, so , now, what is the definition of a developer ?
I propose ( as a draft ) someone
On Thu, 2003-02-06 at 15:17, Michael Scherer wrote:
This sounds great, so , now, what is the definition of a developer ?
One who contributes tangible material to the distro. Software,
documentation, detailed bug-reports, graphics.
I propose ( as a draft ) someone having write access to some
I propose ( as a draft ) someone having write access to some part of the
distribution, this will include website developers, documentation writers,
and packagers.
I don't agree, necessarily. A leading distro has to have tight
standards. It's hard to get people to closely follow these
This sounds great, so , now, what is the definition of a developer ?
One who contributes tangible material to the distro. Software,
documentation, detailed bug-reports, graphics.
I propose ( as a draft ) someone having write access to some part of the
distribution, this will include
But demand high quality for what they deliver. Otherwise, send it back.
Well, of course.
Peer reviews, but this would say tht some developpers hav more power than
others.
All developers should be treated as equals, but, some of them should be team
chief , or something like that...
How do
On Thu, 2003-02-06 at 17:28, Michael Scherer wrote:
Produce a document first?
Right.
First a name for the document :-)
Well:
a Code of Conduct would be required, outlining how people are to act,
how they are to make decisions, who makes what decisions, etc.
a Code of Standards also: RPM
On Thu, 2003-02-06 at 17:38, Michael Scherer wrote:
We also need to support equaly contribs and main, don't you think ?
Well, the problem is Mandrake says publicly we fully support the
packages in main, but not in contribs so they do need to have tight
control over main.
Maybe a fair solution
On Thu, 2003-02-06 at 16:06, Stefan van der Eijk wrote:
Q: when can we do that? And who will make it happen... There are a lot
of bright people on the list that can help to make it happen. How do we
first define an architecture for this. Produce a document first?
Well preliminary questions
39 matches
Mail list logo
