IRC, freenode, #hurd, 2011-07-25

[failed GNU/Hurd project]
< antrik> gnu_srs1: I wouldn't say he was on track. just one of the many
  many people who insist on picking a hard task; realizing that indeed it's
  hard; and going into hiding
< antrik> we see that happen every couple of months
< cluck> maybe we need a "hurd 101" 
< cluck> getting a teacher and setting up a regularly held "class" for hurd
  noobs
< Tekk_> cluck: what would that include?
< cluck> explaining core concepts, giving out "homework" (small tasks), etc

Anatomy of a Hurd system.

< cluck> that way "the big guys" could focus on the hard stuff and have an
  army of code monkeys at their disposal to write speced stuff
< cluck> (then again this idea would heavily depend on available "teachers"
  and "students", which, going by gsoc numbers, may not be all that
  helpful)
< Tekk_> cluck: gsoc isn't an accurate indicator
< Tekk_> cluck: I'm not allowed to participate in gsoc but I'd join :P
< antrik> cluck: we don't need code monkeys... we need hackers
< Tekk_`> antrik: code monkeys involve into hackers
< Tekk_`> under the right conditions
< cluck> antrik: jokes aside some sort of triage system/training ground for
  newcomers could be helpful

IRC, freenode, #hurd, 2013-01-20

<zacts> so once I have written my first translators, and really understand
  that, what kinds of projects would you recommend to an operating
  systems/hurd newbie.
<zacts> I am reading the minix book now as I have it, but I'm waiting on
  getting the modern operating systems book by the same author.
<zacts> I was initially going to start working on minix, but their focus
  seems to be on embedded, and I want to work on a system that is more
  general purpose, and I like the philosophy of freedom surrounding the
  hurd.
<zacts> I like how the hurd design allows more freedom for users of the
  operating system, but I would also like to incorporate ideas from minix
  on the hurd. mainly, rebootless updates of servers/translators.
<neal> then you should study how translators work
<neal> how ipc works
<neal> and understand exactly what state is stored where
<zacts> ok