[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lnst-developers
Subject:    [lnst trac] #31: quick guides
From:       trac () fedorahosted ! org (lnst)
Date:       2012-12-21 12:33:43
Message-ID: 063.9b6cf336bd428625bccdbf8913c2b992 () fedorahosted ! org
[Download RAW message or body]

#31: quick guides
---------------------+------------------------------------------------
  Reporter:  jtluka  |      Owner:  somebody
      Type:  task    |     Status:  new
  Priority:  major   |  Milestone:  Push LNST as a package into Fedora
 Component:  wiki    |    Version:
Resolution:          |   Keywords:
Blocked By:          |   Blocking:
---------------------+------------------------------------------------

Comment (by rpazdera):

 Replying to [comment:3 jtluka]:
 > Replying to [comment:2 rpazdera]:
 > > We now have three quick guides. I was thinking do we want more of
 them? Are there any more topics that could be explained effectively in
 this practical form?
 > >
 > > Maybe we could do one for each command class, but I am not sure it
 would be appropriate to demonstrate system_config with a whole recipe,
 that is practically unrelated to it ...
 >
 > The initial idea behind the quick guides was to have a sample recipe in
 the guide that's ready to use without any modification or with a minor
 changes.
 >
 > For the command classes - I think this is better to have in separate
 documentation. I'm also thinking that we should create some FAQ section,
 answering can-lnst-do-this-and-that? with limitations, advices and so on.

 Ok, in that case, 3 are maybe enough - at first you try one or two quick
 guides and then you can refer to the standard docs. We can put up links to
 them to the intro so the newcomers can get to them right away.

 The FAQ section is a great idea! I'll setup a dummy link on the home page
 for it.

-- 
Ticket URL: <https://fedorahosted.org/lnst/ticket/31#comment:4>
lnst <https://fedorahosted.org/lnst/>
Linux Network Stack Test

[prev in list] [next in list] [prev in thread] [next in thread]