My $0.02 and no offence !
Best so far. Unfortunatelly I'm not in position to offer much but I'm a
Mandrake user ( fan ). My $0.02, this, as all the projects, would need a
champion / dictator willing to work 24h / day AND say what is included
and what is not, what is ready and what is not, etc.
Again, at current situation I just don't have time for anything else but
to give some ideas ( mostly useless ) but 30+ years on big projects, and
Mandrake is a big project, only the real successful have been where you
have one and only one person taking the full responsibility - think Linux !
On other hand, I would like to see something fixed on current developement
level I can install and test - home ! In work I just don't have time for
testing - everything has to work out of the box or I will problems with
management ( mostly MS fans ).
have a nice day.
On Sunday 28 September 2003 12:34, Buchan Milne wrote:
> On Sun, 28 Sep 2003, Warly wrote:
> > It may be a good idea, before cooker opens again, to take these days to
> > have some brainstorm.
> >
> > May you give your opinion on :
> >
> > - What was wrong in 9.2 development process?
>
> I think compared to previous releases, there wasn't as much
> feature-planning (as in 9.0 and 9.1). This may just be my perception since
> I was involved in some planning for features in 9.0 ...
>
> > - We though a bit late in the 9.2 developement process to split cooker
> > ml, we should do it now.
>
> Please, this *must* be done. Why? Most people interested in the server
> development work will have production servers, and may not run cooker
> themeselves. Having the >95% of the traffic that is related to GUI stuff
> discourages people interested in improving server-side stuff from
> subscribing to cooker. I don't think Mandrake will be taken seriously on
> the server (though there is no reason why it shouldn't) unless you can get
> those running Mandrake servers in production involved in the development.
>
> Some have said that this will not be effective, but please tell me why a
> user will send a mail to a cooker-kde list for breakage in cyrus-imapd or
> apache or openldap.
>
> I think there should be a general list, that applies to Mandrake-specific
> software (DrakX, urpmi, drakxtools) and generic cooker issues. Then there
> should be lists for:
> -server software
> -KDE and KDE/Qt-based apps
> -GNOME and GTK-based apps
> -Other desktop software (OpenOffice.org, Mozilla etc)
> -Hardware (/kernel here too?)
>
> > - What could we do to improve 9.3/10.0 development.
>
> One big issue is that users sometimes don't know if an issue that
> irritates them is a bug or a feature. The reason for this is that there is
> no documentation on the design of features. Also, since there is no
> documentation on the design of features, bug reports/suggestions/criticism
> can only be given when significant time has been invested in it. The
> aspect that is going to be used for many problems is going to be used
> again here: drakconnect. Some fundamentals are wrong, and by the time
> people used it/filed bugs on it, it was too late.
>
> > - What should we do to improve the Wiki.
>
> Make it more visible on Mandrake web sites. Do more "concept design" work
> on the wiki.
>
> > - Should we have cooker snapshot ISOs?
>
> IMHO, no. I believe there should be a mini ISO specifically for hardware
> testing that any user can run without a large download or any risk of
> messing up any installation. Boot it, see if your hardware works for
> installation purposes, and some basic tools for reporting hardware
> problems.
>
> > - What could we do, as a community, to increase the acceptance of
> > mandrakelinux?
>
> There it too little press on the community aspects of Mandrake. Redhat
> hasn't got a development community, but probably most non-Mandrake users
> would think they do.
>
> > - How to have more contributors?
>
> We need clear documentation/instructions on how to contribute. At present,
> contributor status seems random (he who bugs Lenny the most gets an
> account). There are a number of contributors who don't have accounts yet
> (IMHO Luca Olivetti at least should have one), but no process for becoming
> a contributor. Also, some contributors aren't subscribed to the lists they
> should be (even though they have aksed to be subscribed).
>
> One thing that oculd be done would be to make more of the inrastructure of
> thow accounts etc work public, and possibly appoint community members who
> can add accounts or fix some things (yes, I know this could be a problem
> for Mandrakesoft, but you trust me not to trojan samba, so why would you
> not trust me to add accounts).
>
> Part of this may be due to ad-hoc setups for authentication etc, and I
> think Mandrake needs to sort these issues out using the tools that are
> provided in the distro (ie get single-sign-on across all mandrake
> websites, using ssl where appropriate, including logins on development
> machines).
>
> More official devel
