[[!meta copyright="Copyright © 2011 Free Software Foundation, Inc."]] [[!meta license="""[[!toggle id="license" text="GFDL 1.2+"]][[!toggleable id="license" text="Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled [[GNU Free Documentation License|/fdl]]."]]"""]] [[!tag open_issue_documentation]] [[!toc]] # IRC, freenode, #hurd, 2011-10-12 we have a mission statement: http://hurd.gnu.org yes but it's quite wishy washy considering all the elegant capability Hurd potentially has to offer Gorodish: it's true that the mission statement is very abstract... but then, it's hard to put anything more specific into 35 words not with some practice I notice programers tend to speak and write in terms of what something does not what it is the "What is Hurd" is a good example there's a lot of interesting information there but the way it's ordered is odd a mission statement is not primarily a PR instrument; but rather a guide that allows separating things that benefit the common goal from things that don't... I agree that some actual marketing material in addition would be nice :-) yes the modesty of Developers that work on FOSS projects never ceases to amaze me I agree that the informational, factual, results oriented documentation is the primary objective of documenting # IRC, freenode, #hurd, 2011-11-25 heh, nice: http://telepathy.freedesktop.org/wiki/Rationale most of this could be read as a rationale for the Hurd just as well ;-)