Netlabs News: Difference between revisions
| Line 11: | Line 11: | ||
=== 4. June - 10. June ===  | === 4. June - 10. June ===  | ||
* netlabs.org webmaster  | |||
** Adrian Gschwend is back from his Southeast-Asia trip and will try to catch up with work @ netlabs.org as soon as possible :-)  | |||
* DWS 2007  | * DWS 2007  | ||
** List of presentations for Developers Workshop 2007  | ** List of presentations for Developers Workshop 2007  | ||
Revision as of 22:30, 13 June 2007
This page will be used to gather news about netlabs.org and it's projects.
If you are looking for the bi-weekly newsletter, please go here: Netlabs_bi_weekly_newsletter
11. June - 17. June
- SVN & TRAC at netlabs.org
- imported the sbliveos2 CVS repository to SVN and comited it to http://svn.netlabs.org/uniaud/browser/sbliveos2
 - imported the dwindows CVS repository to SVN for Mark Hessling (one of the REXX masters) and comited it to to http://svn.netlabs.org/dwindows
 
 
4. June - 10. June
- netlabs.org webmaster
- Adrian Gschwend is back from his Southeast-Asia trip and will try to catch up with work @ netlabs.org as soon as possible :-)
 
 - DWS 2007
- List of presentations for Developers Workshop 2007
- The following presentations are already scheduled for this years Developers Workshop, stay tuned for updates!
 - Introduction to NOM (Chris Wohlgemuth)
 - Utilizing Multi-Core Processors (Keith Merrington)
 - The Voyager Project: Where are we now? (Adrian Gschwend)
 - A freely programmable USB-Interface for eCS - Focussing on the DLP-USB245M (Uwe Hinz)
 - How to create popular software products for eComStation (Eugene Gorbunoff)
 - eComStation User Interface (Eugene Gorbunoff)
 - Managing Program Resources (Christian Langanke)
 - VirtualBox (Adrian Gschwend)
 
 
 - List of presentations for Developers Workshop 2007
 - FM/2
- Various fixes and updates
 - See: http://svn.netlabs.org/fm2/timeline
 
 - kBuild
- Good progress again
 - See: http://svn.netlabs.org/kbuild/timeline
 
 - kLibC
- Load of updates and corrections again
 - See: http://svn.netlabs.org/libc/timeline
 
 - NewView
- Quite some fixes
 - See: http://svn.netlabs.org/newview/timeline
 
 - UniAud
- Very good progress, although not always visible in a release yet. But keep an eye on it!
 - See: http://svn.netlabs.org/uniaud/timeline
 
 
Developers Workshop 2007
- Amsterdam, here we come... don't miss it!
 - July 7 and 8
 - http://wiki.netlabs.org/index.php/Developers_Workshop_2007
 
Guidelines for mail gathering and bi-weekly processing
This is intended to be a procedure on how to create the bi-weekly newsletter, so that multiple people are able to do it, in case others are away.
The news is gathered on a weekly basis. Sources for news are various. We know the following:
- #netlabs channel, just connect and see what comes by
 - http://news.netlabs.org/
 - various SVN timelines for the projects that are already in SVN (needs to be listed explicitly?)
 
There is a mail id on netlabs for mailing out the newsletter to various contacts. The mail id is: news at netlabs dot org It uses the following IMAP mailserver: mail dot netlabs dot org
For the start of a new newsletter a copy from the previous one can be made and then copy the new news into it, to make life easy :-) The easiest way to get the text is grabbing it from the webpage in normal view mode. Check the text a second time, and align it a bit. Address it with BCC to the following addresses:
- martin at os2world dot com
 - stevew at jafar dot hartnell dot edu
 - submit at os2voice dot org
 - webmaster at ecomstation dot com
 - webredactie at os2-gg dot nl
 - ktk at netlabs dot org
 - j dot van dot der dot heide at hccnet dot nl
 - os2info at gmx dot net
 
Don't forget the subject line with the next number and of it goes.
After the newsletter is sent the 'Netlabs bi-weekly newsletter' webpage has to be updated. (http://wiki.netlabs.org/index.php/Netlabs_bi_weekly_newsletter). Just copy the news on top of the others and add a heading.
Then the draft version of the bi-weekly page can be emptied and the heading for the next week can be added.
That is basicly the process of the bi-weekly newsletter.