summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas.mdwn
diff options
context:
space:
mode:
authorGNU Hurd wiki engine <web-hurd@gnu.org>2008-03-14 08:59:20 +0000
committerGNU Hurd wiki engine <web-hurd@gnu.org>2008-03-14 08:59:20 +0000
commit56ecdf45b5460f73f5d1e3597833c3290dd81b4c (patch)
tree2f34dcabfb06d4373f223ea9d61ca70d45b9942b /community/gsoc/project_ideas.mdwn
parent6d34b18f293540a9e643d071d026911d363817fc (diff)
web commit by http://arnebab.livejournal.com/
Diffstat (limited to 'community/gsoc/project_ideas.mdwn')
-rw-r--r--community/gsoc/project_ideas.mdwn6
1 files changed, 5 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn
index 6299428b..c72302f7 100644
--- a/community/gsoc/project_ideas.mdwn
+++ b/community/gsoc/project_ideas.mdwn
@@ -689,6 +689,10 @@ A framework for creating HURD releases could give the HURD far more visibility a
It should include automatic publishing of the press release to selected weblogs and newssites, as well as preparing and uploading the release to visible servers and creating images of the HURD to be used in free virtualization software and livecds ( an example livecd: http://people.debian.org/~neal/hurd-live-cd/ ), so people can test the features at once.
+Also it should update a status page with the current release (with date), state and features of the HURD.
+
+It could automatically update packages for different distributions, too.
+
The press releases should also by default include pointers to all necessary information to dive into using the HURD, as well as to begin coding at once.
-And naturally the framework should be easily adaptable to changes inside the HURD project, and if possible to other projects as well.
+And naturally the framework should be easily adaptable to changes inside the HURD project and, if possible, to other projects as well.