On Sat, Jun 11, 2016 at 10:49 AM, Leo Famulari <l...@famulari.name> wrote:

> On Sat, Jun 11, 2016 at 06:43:21AM -0700, yoo...@gmail.com wrote:
> > Upon further reflection.. The Guix manual might not be an appropriate
> place
> > for such a guide. If the Guix manual isn't a good place for such a set of
> > instructions, do you have any suggestions for a location (blog, etc)?
>
> There is this useful wiki managed by Raymond Nicholson:
> https://gitlab.com/rain1/guix-wiki/wikis/home
>
> Although, I'd like to echo Ludovic's question, and also say that the
> goal of the manual is to be completely sufficient for first-timers and
> experienced users alike.
>
> I find the phenomenon of 3rd party wikis giving instructions on how to
> use some piece of software to be a dismaying "antipattern". And, the
> situation only gets worse as people send documentation to the 3rd party
> wiki instead of to the software project in questoin.
>

I agree on the 3rd party wikis point as well, hence my willing to pick up
some Texinfo and attempt submitting a patch :)


>
> So, please tell us of any specific shortcomings! It seems that you would
> prefer "System Installation" to begin with an outline?
>

Now that you mention it.. Merging what I've done in to the "System
Installation" section would make more sense location-wise but..

After reading the feedback here and spending some more time in IRC (which
really drives home the feedback about translations and colloquialisms,
thanks John) I would like to do the following:
- Add a contiguous set of examples to the existing "System Installation"
section (such that if you follow the examples you will almost certainly end
up with a working system, even if you don't read much of anything else)
- Add at least one more sub-section to "System Installation" that
introduces users to extending/customizing the initial system's .scm file
-- Something like a "Where to go from here? Customizing your installation."
-- A chance to tease users in to Scheme programming

Sound better?

-- 

   .:Justin:.

Reply via email to