BTS 2011 - Ideas

I had some ideas for the BTS 2011 discussions:

For the wiki:
- an overview page of all features currently in ltsp
- each feature has its own page, explaining it in more detail (each
wiki page has a discussion page in which a feature can be discussed)
- distro overview page, mapping all features to support in each distro
- current links to distro specific manual (they are mostly hosted on
distro specific sites)
- collect all ltsp-generic manual stuff, tips & tricks currently
hosted on distro specific sites to ltsp wiki
  these pages should explain how ltsp is supposed to work (regardless of distro)
- specific developer pages, stating guidelines for development on ltsp
(for instance the IntegratingLtsp page)
- architecture pages, showing all components of a working ltsp
configuration, also compare to ltsp-cluster


Related to plugins discussion I had earlier with alkisg and vagrantc:
- The commands with distro specific options (ltsp-build-client,
ltsp-update-image, ltsp-info) should work with the same plugin system:
  + for distro maintainers easier to work with one system
  + common plugin code (which is now only used in ltsp-build-client
can be shared with plugin/functions
  + for man-pages, a common after-build man page generator would be
easier to implement across the different commands
  + I can work on ltsp-update-image implementation on Gentoo,
currently depends on Debian/Ubuntu packages

- This regardless of how the plugin system is implemented.
  I agree with alkisg that the configure phase is redundant and could
take place centrally
  however, different distro use different steps, this should be facilitated


ltsp-info improvements
- should help debugging, ideally a ltsp-info --debug, which checks
your configuration
- common questions and answers should find their way in ltsp-info so a
user can help himself with simple things
- relate ltsp-info checks to applicable wiki pages, so users are
pointed to the right documentation, we want more knowledgeable users
- not only debug, but also status information
  in a test branch, I made a plugin which shows currently logged in clients
  http://bazaar.launchpad.net/~wimmuskee/ltsp/ltsp-info-dev/view/head:/server/plugins/ltsp-info/common/60-active-clients

to all devs/users attending, good luck and have fun,
Wim

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_____________________________________________________________________
Ltsp-developer mailing list.   To un-subscribe, or change prefs, goto:
      https://lists.sourceforge.net/lists/listinfo/ltsp-developer
For additional LTSP help,   try #ltsp channel on irc.freenode.net