Merge branch 'master' of flubber:~hurd-web/hurd-web

2 files changed, 93 insertions, 9 deletions

diff --git a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn
index 6f0af07e..5febe7b6 100644
--- a/community/weblogs/ArneBab/niches_for_the_hurd.mdwn
+++ b/community/weblogs/ArneBab/niches_for_the_hurd.mdwn
@@ -131,7 +131,9 @@ that's KDEs fabled network transparency on the filesystem / shell level (where i
 
 * add temporary filesystems anywhere via `settrans -a NODE /hurd/ext2fs`
 
-* make everything temporarily writeable without really changing it via [[hurd/translator/unionfs]].
+* On-demand mounted filesystems via a passive translator which unmounts the filesystem when it isn’t used for some time. 
+
+* make everything temporarily writeable without really changing it via [[hurd/translator/unionfs]]. Store the changes on an external device. 
 
 * Read tar archives and mbox files via `ls foo.tar.gz,,tarfs` and `ls foo.mbox,,mboxfs`, respectively → [[hurd/translator/nsmux]]. 
 
@@ -157,7 +159,7 @@ aren't possible.
 	* elegantly mount iso images and similar as unprivileged user. 
 
 - Other useful stuff: 
-	* Install deb-packages from an ftp server via 'dpkg -iO ftp://foo/bar/*.deb'
+	* Install deb-packages from an ftp server via 'dpkg -iO ftp://foo/bar/package.deb'
 	* remount a filesystem readonly as regular user: fsysopts /foo -r
 	* give a process additional group and user permissions at runtime:  
 	  $ groups  
@@ -195,10 +197,6 @@ aren't possible.
 	  # once the subhurd closes.  
 	  $ subdo --no-lasting-changes ./virus
 
-- Running parts of the Hurd on different computers, maybe even with shared servers on 
-dedicated hardware (Cloud Computing when the servers can be made to migrate from 
-between computers). Maybe this should be placed in "need a lot of coding". 
-
 - subhurds for quickly adapting the whole system without bothering others. 
 
 - Define your personal environment via translators, so you can easily take it with 
@@ -230,8 +228,6 @@ traditional systems in this reagard, but in fact surpass them.
 
 - The possibility to create more efficient and powerful desktop environments. 
 
-- Multicore systems (need to fixup Mach for SMP)
-
 - Currently to offer CPU time to some project (like the World Community Grid), it is 
 necessary to install a program from them, and they can then do only what that proram 
 allows them to - which leads to reinventing a processing environment instead of just 
@@ -248,6 +244,12 @@ level. Programs only have to display the given files and quickly update the
 state of their own files, so the programs stay very easy. The translator could 
 notify the program when something changes.
 
+- Multicore systems (need to fixup Mach for SMP)
+
+- Running parts of the Hurd on different computers, maybe even with shared servers on 
+dedicated hardware (Cloud Computing when the servers can be made to migrate from 
+between computers). Maybe this should be placed in "need a lot of coding". 
+
 
 
 ### Unfeasible ideas
@@ -328,13 +330,32 @@ Each participant:
 ("must", because in a community people can do what they perceive as important, and 
 telling someone to stop what he's doing is no option (in my opinion))
 
+**Result: We talk about the niches we can already fulfill :)**
+
 
 Things to do
 ------------
 
 todo-item -> niches for which it is useful. 
 
+*This might be useful for the next GSoC.*
+
 ### Easy
 
-- Port debian packages to the Hurd -> mainly tinkerers, but also any other niche. 
+- Port debian packages to the Hurd -> currently mainly tinkerers, but also any other niche. In the long run this is necessary for every user. Easy start for devs. 
+- Document easier access to low-level functions via translators, one function at a time. -> tinkerers. 
+- get nsmux ready for regular users by setting it up in the LiveCDs by default. -> show tinkerers what it can do.
+
+### Complex
 
+- A filesystem-based package manager: Unionmounting packages. With filterfs from nsmux packages any user should be able to selectively disable any package without affecting the system of others. Simple active translators can add packages. -> clean design and more freedom for tinkerers to setup test environments: “Does this also work with XY disabled?”
+- Enable subhurds for regular users via a subdo command: A framework for confining individual applications. -> tinkerers for testing their work.
+- Define your personal environment via translators, so you can easily take it with 
+you ⇒ system on a USB stick. Would work great with a filesystem based package manager. -> ?
+
+### Huge
+
+- Get Hurd/GNU Mach ready for efficient multicore usage. -> multicore
+- Running parts of the Hurd on different computers, maybe even with shared servers on 
+dedicated hardware (Cloud Computing when the servers can be made to migrate from 
+between computers). -> multicore on steroids :)
diff --git a/community/weblogs/ArneBab/tasks-for-the-hurd.mdwn b/community/weblogs/ArneBab/tasks-for-the-hurd.mdwn
new file mode 100644
index 00000000..bf6224b2
--- /dev/null
+++ b/community/weblogs/ArneBab/tasks-for-the-hurd.mdwn
@@ -0,0 +1,63 @@
+Tasks for the Hurd
+==================
+
+*These tasks are compiled from the
+ [[community/weblogs/ArneBab/niches_of_the_hurd]] and
+ [[community/weblogs/ArneBab/what_we_need]]. The first asked “where
+ can the Hurd find niches where it is the biggest fish in the pond,
+ and how?” while the second asked “what do we still need to make the
+ Hurd usable for most of its developers as system for their day-to-day
+ tasks?”.*
+
+*This might be useful for the next GSoC. Please feel free to edit
+ and/or migrate it mercilessly :)*
+
+### Easy
+
+- Port debian packages to the Hurd -> currently mainly tinkerers, but
+  also any other niche. In the long run this is necessary for every
+  user. Easy start for devs.
+- Document easier access to low-level functions via translators, one
+  function at a time. -> tinkerers.
+- get nsmux ready for regular users by setting it up in the LiveCDs by
+  default. -> show tinkerers what it can do.
+- Test on modern machines. If it doesn’t work, file a bug:
+  [info](http://www.mail-archive.com/bug-hurd@gnu.org/msg19105.html).
+
+
+### Complex
+
+- A filesystem-based package manager: Unionmounting packages. With
+  filterfs from nsmux packages any user should be able to selectively
+  disable any package without affecting the system of others. Simple
+  active translators can add packages. -> clean design and more
+  freedom for tinkerers to quickly setup test environments: “Does this
+  also work with XY disabled?” ⇒ rapid testing for different base
+  systems.
+- Enable subhurds for regular users via a subdo command: A framework
+  for confining individual applications. -> tinkerers for testing
+  their work.
+- Define your personal environment via translators, so you can easily
+  take it with you ⇒ system on a USB stick. Would work great with a
+  filesystem based package manager -> use the capabilities of a system
+  and all its installed packages without having to give up your own
+  custom environment.
+
+- Implement USB support, maybe using DDE or DDEkit -> prerequisite to system on USB.
+- Add Wireless support, maybe via DDE. 
+- Add sound support via a sound translator. 
+- Add SATA support. 
+- Stabilize Xorg, so it can run fast for days. 
+- Add PPPoE capablilities. 
+- Debug NFS for climm, w3m and git. 
+- Port a full-featured browser (i.e. Firefox).
+- (Graphical Desktop and switching between console and X) or full
+  featured high-resultion console which doesn’t need X (and emacs :)
+  ).
+
+### Huge
+
+- Get Hurd/GNU Mach ready for efficient multicore usage. -> multicore
+- Running parts of the Hurd on different computers, maybe even with
+  shared servers on dedicated hardware (Cloud Computing when the servers
+  can migrate between computers). -> multicore on steroids :)