FOSS Lab Manual Part 1 Draft Release
Vijay Kumar
A draft version of the FOSS Lab Manual Part 1 (first four chapters)
alone is available for review from the download section. Please review
it and send in your feedback. We will incorporate the feedback and
make the final release by today or tomorrow.
http://foss-lab-manual.googlecode.com/files/foss-lab-manual-p1-1.0-rc1.pdf
Regards,
Vijay
Shrinivasan T
Looks nice.
Hope we can say about ILUGC in the last page.
--
Regards,
T.Shrinivasan
My Life with GNU/Linux : http://goinggnu.wordpress.com
Free/Open Source Jobs : http://fossjobs.in
Get CollabNet Subversion Edge : http://www.collab.net/svnedge
Shakthi Kannan
--- On Wed, Jun 29, 2011 at 12:39 PM, Vijay Kumar
<vijay...@bravegnu.org> wrote:
| A draft version of the FOSS Lab Manual Part 1 (first four chapters)
| alone is available for review from the download section. Please review
| it and send in your feedback. We will incorporate the feedback and
| make the final release by today or tomorrow.
\--
#001 The .pdf must have a link to the source of the project.
Otherwise, people may not know whom to contact for suggestions,
feedback.
#002 It will be good to start a chapter in a new page. Chapter II for example.
#003 What is the use of "Required Reading"? Do the students read them
before proceeding? Ideally, you will want all documentation in place,
so students don't need an Internet connection.
#004 I am not sure why the syllabus mandates Perl, PHP, Python et. al.
It is best for students to pick one programming paradigm and a
language, learn and understand all the concepts well before trying
another programming paradigm.
SK
--
Shakthi Kannan
http://www.shakthimaan.com
Vijay Kumar
> #001 The .pdf must have a link to the source of the project.
> Otherwise, people may not know whom to contact for suggestions,
> feedback.
Point taken.
> #002 It will be good to start a chapter in a new page. Chapter II for example.
Hmmm... We do start chapters in a new page ... I am missing something here?
> #003 What is the use of "Required Reading"? Do the students read them
> before proceeding? Ideally, you will want all documentation in place,
> so students don't need an Internet connection.
True. That is on the cards. But this is the fallback, till we get the
"Study Material" ready.
Regards,
Vijay
Shakthi Kannan
--- On Wed, Jun 29, 2011 at 1:40 PM, Vijay Kumar
<vijay...@bravegnu.org> wrote:
| We do start chapters in a new page ... I am missing something here?
\--
"2. Getting Started Lab II" on page 4. I assume that 2 stands for
chapter 2, but, it is in chapter 1. Or, it should be called 1.2.
---
| True. That is on the cards. But this is the fallback, till we get the
| "Study Material" ready.
\--
Instead of writing everything from scratch, it might be a good idea to
just get the available (good) documentation, and cross-reference the
file in the .pdf, or simply create a static HTML page, that links to
all the documents (relative).
For C, you already have:
http://publications.gbdirect.co.uk/c_book/
For Python (for example):
'A Byte of Python' http://www.swaroopch.com/notes/Python
This is already being used in universities:
http://www.swaroopch.com/notes/Python#Academic_Courses
Write documentation only when there are no other good alternatives
available. Include whatever is available. This way, you can let
upstream maintain their documentation, and it will be less re-work for
all of you.
Just some suggestions,
Vijay Kumar
> Hi,
>
> --- On Wed, Jun 29, 2011 at 1:40 PM, Vijay Kumar
> <vijay...@bravegnu.org> wrote:
> | We do start chapters in a new page ... I am missing something here?
> \--
>
> "2. Getting Started Lab II" on page 4. I assume that 2 stands for
> chapter 2, but, it is in chapter 1. Or, it should be called 1.2.
They are sections in a chapter ... And the numbering style comes
from Docbook stylesheets. I don't think we would want to mess with
that for now.
> Instead of writing everything from scratch, it might be a good idea to
> just get the available (good) documentation, and cross-reference the
> file in the .pdf, or simply create a static HTML page, that links to
> all the documents (relative).
Well, I didn't suggest that we write everything from scratch. But if
we have to combine these docs from various sources, into something
cohesive, it would require a good amount of time and effort. I guess
that will be done after we finish the lab manual.
Regards,
Vijay
Shakthi Kannan
--- On Wed, Jun 29, 2011 at 2:04 PM, Vijay Kumar
<vijay...@bravegnu.org> wrote:
| They are sections in a chapter ... And the numbering style comes
| from Docbook stylesheets. I don't think we would want to mess with
| that for now.
\--
The "Linux System Administration" from GBDirect has the indexing as I
had mentioned. Atleast aim to be consistent across all documents.
---
| Well, I didn't suggest that we write everything from scratch. But if
| we have to combine these docs from various sources, into something
| cohesive, it would require a good amount of time and effort.
\--
It wouldn't because you are only linking them together. Taking
(selected) snippets from various sources, checking whether there is a
flow to the content, is lot of work!
What would be beneficial is to localize the context used in the above
documentation, so people can relate to in some way. For example,
instead of Alice and Bob, you can use Anita and Balu.
Forgot to add for Perl:
http://www.perl.org/books/beginning-perl/
Arun SAG
>A draft version of the FOSS Lab Manual Part 1 (first four chapters)
>alone is available for review from the download section.
Kernel compilation, virtualization, compiling from source and introduction to package management system.
Are we going to change the order?
--
Arun S.A.G
http://zer0c00l.in/
Vijay Kumar
> Kernel compilation, virtualization, compiling from source and
> introduction to package management system.
>
> Are we going to change the order?
Yes. That's what we initially planned. Starting out with Kernel
Compilation, in the first lab, sure isn't the right way. And
guess changing the order wouldn't be problem as long as we
stick to the syllabus.
Regards,
Vijay