diff options
Diffstat (limited to 'community/gsoc/project_ideas.mdwn')
| -rw-r--r-- | community/gsoc/project_ideas.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/community/gsoc/project_ideas.mdwn b/community/gsoc/project_ideas.mdwn index 2ec9d58d..6299428b 100644 --- a/community/gsoc/project_ideas.mdwn +++ b/community/gsoc/project_ideas.mdwn @@ -680,3 +680,15 @@ The task is to create easy to use Hurd bindings for a language of the student's choice, and some example servers to prove that it works well in practice. This project will require gaining a very good understanding of the various Hurd interfaces. Skills in designing nice programming interfaces are a must. + +* A release creation framework + +One of the points which keep people from using the HURD is that it never looks like it is in a working state. To get attention from people (and the press, etc.) the HURD needs releases, and doing a release should be as simple as submitting a changelog and release notes and tagging the code, ideally done with only one simple command. + +A framework for creating HURD releases could give the HURD far more visibility and thus make it more interesting to developers. + +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. + +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. |