I think even tho I haven't documented all efforts into one doc yet,
it would be good to summarize the past two weeks.
Project status week 22
Initials
In week 22 we have talked about any texts written with newbies in mind and the need for a tutorial like this. Unfortunately there where none. In short this tutorial would need to be:
I. written for newbies: that is with a suitable tone of voice, explain Linux/GNU's basics, the ways of doing things, and not assume a lot(?) of knowledge, "Make it simple, just not too simple" (q: busbarn).
II. clear: a logical setup they will be able to understand and work with (docs are referred to for "advanced" topics),
III. as vendor-neutral as possible, don't presume any setup and be as neutral to it, so SOHO or laptop should make no difference.
//(any critical points to add?)
Timeline
Ihere is an example of how we could proceed:
here, but didn't put in a "hard" timeline.
Issues (aprox, not all)
We talked about how much knowledge we are supposed to assume a newbie should have, the need for explaining "basics" while doc submissions where still pouring in. Notably spikes are translations, GUI vs CLI, physical security.
An approximation for a "fundamentals" list is:
here to which where no objections.
Forecasting week 23:
- discussion more focussed and add some structure.
- draft up the framework, divide, conquer before next weekend
Group questions
Should we build our doc starting with the highest priority items? Or try to be complementary to their install process? Other ways?
Project status week 23
Current member list in no particular order
Tcaptain, Manthram, Bastard23, Jharris, Busbarn
Jonr, Fancypiper, DavidPhillips, Markus1982, Kroenecker
Twilli227, Tangle, Jeremy, AXO, Brian Hatch, Peter_robb, Grim Reaper.
Issues (aprox, not all)
We started off discussing my list of fundamentals (come to think of it, no one else put up his/hers?!!#)
and somehow wen't back to CLI tool usage...
Group questions
At this point I think using a mailinglist will be better for "concentration".
Would any of you object to taking this discussion to a mailinglist?
(No answers yet)
Forecasting week 24:
- draft project outline, the stuff we should keep focussed on or the projects' Raisin d'etre (or cumquat),
- draft framework and "fundamentals" list,
- finalize discussion on what to include,
Final notes
- Anyone is free to join. Willingness to collaborate preferred over expert knowledge. Just tell us what you're willing to contribute, only proofreading and testing the tutorial for instance would be cool too. Please read the *whole* thread carefully first before posting.
- If anyone strongly disagrees with anything said, I invite you to speak up. This is an open discussion and constructive, positive criticism is welcome, just make sure to explain your issues clearly.
- Please keep this thread bookmarked and visit it preferably daily. As a group we need to get and stay focussed.
- Please answer any group questions, because as a group we decide where to got to.