[Linuxjunior-devel] EOW Review 6/11/2010

[Matt <mva...@gm...>]

Greetings everyone,

I would first like to announce a new format on updating everyone about 
the progress of Linux Junior.  Every Monday, I will be sending out a 
Milestone email, which will contain goals for the upcoming week.  I 
realize that it is going to take some time to get use to the format, but 
I am hoping to be able to break task into weekly manageable jobs that 
can GET DONE!  Every Sunday I will be sending out an email containing 
Milestone reviews.  These reviews will simply restate the milestone 
goals and progress made on them.  The time of the milestone reviews will 
also be a great time to share any of your thoughts on what should be put 
onto the next weeks milestone goals.  Both these emails will be sent out 
in Volume/Issue format, with new volumes cycling each calendar year.  
Every Friday I will send an EOW review, such as this email, which I 
intend to be a bit lighter on the technical side and just update 
everyone with the overall status, and any concerns that have arisen 
during the week.  Again, the EOW review will be designed to illicit 
feedback from everyone, and to help adjust where to go.

This new mailing format isn't to stop everyone from sharing their own 
thoughts at their own time, but sort of open up an mailing "open forum" 
to encourage feedback from those who are generally sitting at the 
sidelines not knowing where and when they can chime in.

Current Project Status
I know I promised earlier in the week the release of the files, but, 
after doing some work, I discovered for some odd reason the gcc compiler 
is broken, and I have been having a heck of a time retracing my steps to 
fix it without having to fix it.  Another thing currently on the list  
is the kernel not recognizing the network interface, I may have to spend 
some time recompiling the kernel this week again! D'oh!  I'm also 
working on some basic legal cleanup before I dump the files for everyone 
to work on.  Stay tuned...

Recent Thoughts
I'm beginning to think the project name was a mistake, as Linux is a 
trademarked name, and I can only assume that one is not allowed to use a 
trademarked name within another name, and I haven't even begun to look 
into it, but I'm sure Junior is already trademarked.  Any ideas?

Being a subscriber to Google's blogs, I was recently delighted and 
surprised to see the issue of technology and children come up, seeing 
even Google has a web page devoted to this .  Wouldn't it be great if 
they partnered up with us in the future... I think I'm getting way to 
ahead of myself.

If anybody is interested in having real time chat discussions on the 
work being done for Linux Junior, let me know, and we can arrange for 
times and a channel to meet up on.

My final thoughts I'll share today is LSB (Linux Standards Base) 
compliance.  If you don't know, LSB is a work group created by the Linux 
Foundation designed for created compatibility for executable and 
software across different Linux distributions.  It would be nice to 
comply to the LSB certifications, however, their definitely is a lost of 
freedom to chose on how the system runs and how unique it is for kids.  
I will be looking into the issue throughout the next week, and perhaps 
even start a wiki page discussing my interpretation of the pros and cons.

That's it for today,  hope you all have a great weekend.  Just a 
reminder that the new format of email updates will not start until next 
week, since it would be kind of senseless to post a milestone review on 
Sunday with nothing to review!

Thanks,
Matt