[Gnoppix-devel] Re: GNOPPIX maintenance

[Sven Herzberg]

Am Sa, den 01.11.2003 schrieb cyberdune um 16:48:
> Thats fine.. I am trying to write a new installer,

  Well, and I already started to. If you and amu would please start
using cvs like cvs is used in almost any non-trivial free software
project. There are two installers in CVS, the one currently being used
and the one i'm working on. I'm just going to switch the language of
implementation from C to ruby the week after the next one.

> >> try to make  it more easy for other people  to commit stuff to
> >> gnoppix (simply  changing things from the  image is note really  a way
> >> that's acceptable -- even if your opinion differs from mine)
> 
> Explain me exactly what you mean, please. As we have webCVS, I think,
> we are rather more open to the community than Knoppix!

cool, webcvs rocks if cvs is not used. please guys, create cvs modules
for gnoppix-related stuff and create debian packages from that.

> I am working on that. I wrote three scripts to automate the process.

And where are they? in cvs? to be seen via webcvs?

> Know I am working out the way to write a prog out from that.
> You all (members) will get that at FIRST!! (in a few days)

Guys, please start thinking in the community way. Release early, release
often. (and release PUBLICALLY)

> > Then we  will have  an efficient project  management.  Please  take this
> > advice into consideration, try to merge  and share your work with others
> > because you  know that  when an  OSS project is  not well  managed, some
> > people take your work and fork a new project.
> 
> JA, that's the reason we need have to have an INTERN-mailing-list to 
> discuss and share.

guys, intern is the wrong way to go, we cannot exclude the rest of the
world from gnoppix' development. gnoppix is free software and gnoppix
should be maintained transparently for everyone to see how decisions are
made.

> 3. USE an INTERN-mailing-list!!!!!!!!!!!!!!!!!1
>      to trace the work on Gnoppix to share the knowledge, to gain 
> improvements,

why should the knowlegde be shared just between intern-people. Other
people can contribute more easily if the know what's going on and how
things are working.

>      to establish an corporate identity, to avoid mistakes .. etc ..

>      b. Follow the ROADMAP on Gnoppix (I will suggest this one in an 
> Intern-mailing-list)

Why suggesting an internal roadmap, why not let the publicity take part
in decisions? ATM I know 5 people who joined morphix because they
"couldn't figure out how to take part".

>      c. If s.b. is NOT able to complete his task because of a lack of 
> knowledge,
>      thats not a problem as long as he tries to solve it on the 
> Intern-mailing-list then.
>      And if s.b. is not able to couple the heavy work overload he should 
> stop signing tasks
>      and assign his one to another member (On the INTERN-mailing-list).

Why exclude the public here again? Give me (and the public) reasons!

Regards,
  Sven
-- 
Sven Herzberg <address@hidden> · Jabber: address@hidden
GNOME Deutschland                  · http://www.gnome-de.org/
GNOPPIX                            · http://www.gnoppix.org/

signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil