Netlabs News: Difference between revisions
added new week |
Updates for March 11-18 |
||
Line 5: | Line 5: | ||
If you are looking for the bi-weekly newsletter, please go here: [[Netlabs_bi_weekly_newsletter]] | If you are looking for the bi-weekly newsletter, please go here: [[Netlabs_bi_weekly_newsletter]] | ||
=== 19. March - 25. March === | |||
=== 12. March - 18. March === | === 12. March - 18. March === | ||
* FM/2 | |||
** Many updates and various fixes | |||
** Release 3.5.8 ready | |||
** See: http://svn.netlabs.org/fm2/timeline | |||
* NewView | |||
** Quite some updates again | |||
** See: http://svn.netlabs.org/newview/timeline | |||
* Samba | |||
** Some updates | |||
** See: http://svn.netlabs.org/samba/timeline | |||
* Scanner support for OS/2 | |||
** Some initial loads | |||
** See: http://svn.netlabs.org/sane2twain/timeline | |||
* Voyager Desktop | |||
** WPDrives and WPRootFolderclasses added and some fixes | |||
** See: http://svn.netlabs.org/v_desktop/timeline | |||
* Voyager NOM | |||
** Some fixes and updates | |||
** See: http://svn.netlabs.org/v_nom/timeline | |||
* xATA | |||
** Some minor internal updates | |||
** See: http://svn.netlabs.org/xata/timeline | |||
=== Guidelines for mail gathering and bi-weekly processing === | === 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. | 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. |
Revision as of 17:41, 18 March 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
19. March - 25. March
12. March - 18. March
- FM/2
- Many updates and various fixes
- Release 3.5.8 ready
- See: http://svn.netlabs.org/fm2/timeline
- NewView
- Quite some updates again
- See: http://svn.netlabs.org/newview/timeline
- Samba
- Some updates
- See: http://svn.netlabs.org/samba/timeline
- Scanner support for OS/2
- Some initial loads
- See: http://svn.netlabs.org/sane2twain/timeline
- Voyager Desktop
- WPDrives and WPRootFolderclasses added and some fixes
- See: http://svn.netlabs.org/v_desktop/timeline
- Voyager NOM
- Some fixes and updates
- See: http://svn.netlabs.org/v_nom/timeline
- xATA
- Some minor internal updates
- See: http://svn.netlabs.org/xata/timeline
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.