Gentoo Logo
Gentoo Spaceship




Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-desktop-research
Navigation:
Lists: gentoo-desktop-research: < Prev By Thread Next > < Prev By Date Next >
Headers:
To: gentoo-desktop-research@g.o
From: Paul de Vrieze <pauldv@g.o>
Subject: Re: test
Date: Thu, 9 Oct 2003 10:27:23 +0200
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Thursday 09 October 2003 01:08, Luca Barbato wrote:
>
> I suggest to think about the problems first, see how the other distro
> solved them and then find a solution that takes in account what the
> other did but also what they fail to accomplish.
>
> so Research fields should be, IMHO, problems&solution from the others,
>

I do not think that we should focus on what other distro's do. We should focus 
on identifying problems that are there. After such a problem is identified we 
should try to determine whether we think this problem needs to be solved by 
gentoo (keeping the gentoo and desktop-research goals in mind). After that we 
need to look at the solution to the problem. At this stage comes looking at 
solutions by other distros.

This solving process has a number of stages. The first one being the 
identification of possible solutions, and their costs (how much work are 
they, and how "beautiful" are they etc.). Then we choose one solution to 
implement and test. This involves trying to get approval by the people from 
the projects that will be involved when it is actually put into gentoo. After 
the test is successful, we are going to put it into the main tree, and put it 
into action. Putting it into action involves making sure that our solution 
will be maintained, if necessary by creating a team to do that maintenance.

However before we can think of finding problems, we first need to have a 
policy on the following points:
- - Which problems do we handle? We only handle desktop problems, but when does
  a problem qualify as being desktop.
- - How do we handle problems? Basically, do we follow the process described
  above, or some other process.
- - What are the conditions for a solution to be acceptable.
- - Will we have a seperate cvs testing tree (overlay)?
- - How are we going to make sure that the solutions get out of the testing
  tree, and in to the main distribution? Will we use GLEP's?

Paul

ps. I know it is nicer to think of solutions than of problems, and nicer to 
think of problems than of procedures, but first things should go first. And 
procedure comes first.

- -- 
Paul de Vrieze
Gentoo Developer
Mail: pauldv@g.o
Homepage: http://www.devrieze.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)

iD8DBQE/hRv7bKx5DBjWFdsRAlt0AJ497K4aJ0OsqeDCkZ5WyU3Y2RWj0QCgl6y+
/z0FjWITQ519n12vLFBPyCw=
=3UH4
-----END PGP SIGNATURE-----


--
gentoo-desktop-research@g.o mailing list

Replies:
Re: test
-- dams
References:
test
-- Paul de Vrieze
Re: test
-- Gerald J. Normandin Jr.
Re: test
-- Luca Barbato
Navigation:
Lists: gentoo-desktop-research: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
Re: test
Next by thread:
Re: test
Previous by date:
Re: test
Next by date:
One research problem we could research


Updated Jun 17, 2009

Summary: Archive of the gentoo-desktop-research mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.