diff options
author | TWikiGuest <web-hurd@gnu.org> | 2005-07-27 16:32:45 +0000 |
---|---|---|
committer | TWikiGuest <web-hurd@gnu.org> | 2005-07-27 16:32:45 +0000 |
commit | 52f26c412d7e8a1844bce361a1eb0ad8137ef1e8 (patch) | |
tree | 23cb0f4f8035f3efe27a420beed361902b3a50e4 /Distrib | |
parent | e7156424967589110af36857f550aaa93bfee6f4 (diff) |
none
Diffstat (limited to 'Distrib')
-rw-r--r-- | Distrib/GnuOS.mdwn | 20 |
1 files changed, 14 insertions, 6 deletions
diff --git a/Distrib/GnuOS.mdwn b/Distrib/GnuOS.mdwn index 15972b92..e809d227 100644 --- a/Distrib/GnuOS.mdwn +++ b/Distrib/GnuOS.mdwn @@ -18,19 +18,27 @@ These are just some quick notes I am making late at night. Lets clean this up. 1. Lets establish some ground rules. 2. We need a name: - * "GnuOS = GNU Now Unified" has been suggested by Anders and I like it but we are open to suggestion. - * GNU should be the name of the system. Any other name would represent a fork of the GNU project. Atleast, that is how I see it. -Andrew + * Just GNU is confusing, because it means too many different things to people (project for creating free software, set of tools, philosophy, license etc.). We need a distinctive name for the GNU distribution + * "GnuOS = GNU Now Unified" has been suggested by Anders + * "GNU System" is already somewhat established and quite descriptive; but we need some more handy short form, like GNUsys or GnuSys or something 3. We need infrastructure * Wiki for community communication * Repository for packages - * Mailing lists? Can gnu-system-discuss not be used for this purpose? -Andrew + * Probably we can host it on the GNU servers + * Mailing lists? + * gnu-system-discuss is already there and should be used for most technical stuff + * We might want some less formal channel for community stuff etc. in addition * IRC channel? - * Bug tracking system - * Issue tracking? Should we set up a Savannah project? - * Would we fork Mach? + * As this is closely related to the Hurd, probably we shoud just use the established #hug and ##hurd + * Bug / Issue tracking + * Probably we should set up a Savannah project + * How to handle experimental patches to the core packages (Hurd, Mach, libc etc.) that are not in official CVS yet? 4. We need a community vision and direction. * Lets work together for a common goal * Lets establish goals and priorities and get resources on them. (More later) + * Major goal to create a system making full use of Hurd features? + * We should never hesitate to throw away existing stuff whenever it hinders us to make good use of Hurd features + * However, we should try to reuse existing stuff (from Debian for example) as long as it doesn't limit our possibilities or impose considerable overhead * Lets have fun. It's GNU and it's important but let's enjoy ourselves. ## <a name="What_are_we_missing_"> What are we missing? </a> |