diff options
| author | TWikiGuest <web-hurd@gnu.org> | 2005-07-28 13:18:35 +0000 |
|---|---|---|
| committer | TWikiGuest <web-hurd@gnu.org> | 2005-07-28 13:18:35 +0000 |
| commit | 9eee68b606a925c7381003c26e3db7fb48153e29 (patch) | |
| tree | 5593335136480dfc0fdd8acf46fabdd256b73d64 /Distrib | |
| parent | 815525b284fb2a6ec296bd4cc34a3c9c9bcd8e96 (diff) | |
none
Diffstat (limited to 'Distrib')
| -rw-r--r-- | Distrib/GnuOS.mdwn | 8 |
1 files changed, 6 insertions, 2 deletions
diff --git a/Distrib/GnuOS.mdwn b/Distrib/GnuOS.mdwn index 5764a2c6..68b07490 100644 --- a/Distrib/GnuOS.mdwn +++ b/Distrib/GnuOS.mdwn @@ -28,7 +28,9 @@ These are just some quick notes I am making late at night. Lets clean this up. * 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 - * I disagree, GSD is small and splitting the traffic into 2 lists is just silly at this point. -andrew + * I disagree, GSD is small and splitting the traffic into 2 lists is just silly at this point. -andrew + * It's not about traffic but about intimidating. Some people/topics/opinions just do not fit the "official" channel, and shouldn't get voiced down by the "officials" + * But well, maybe IRC is enough for the less formal stuff... * IRC channel? * As this is closely related to the Hurd, probably we shoud just use the established #hug and ##hurd * Bug / Issue tracking @@ -54,8 +56,10 @@ These are just some quick notes I am making late at night. Lets clean this up. ## <a name="Moving_forward_"> Moving forward? </a> 1. AMS had made a GNU release. We can try it and test it to good use. We can fix broken things in it, and enhance it. + * The snapshot is very old. Probably better to build something from current stuff, even if it means more work 2. GNU is all about freedom AND ease of use. So, given installers are by nature quite complex, how should we install GNU on users's computers? I think ams's GNU System Creator comes into play here, maybe ams or sdschulze could (re-)write specifications of GSC. 3. Until we have an installer ready, we could go the Gentoo-like route, and have every part manually installed. A good installation documentation may help. Our next milestone may be just this (in case ams hasn't already done it): * have a good installation document out, with all the required packages hosted at gnu.org or savannah.org * get stowfs working -4. Move on, start coding, documenting, packaging. +4. Maybe try to use hacked Debian packages until we get native ones? +5. Move on, start coding, documenting, packaging. |