Netlabs News: Difference between revisions
Removed ADCD info, was not correct |
Updated news for QT and WarpVision |
||
Line 2: | Line 2: | ||
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]] | ||
=== 23. October - 29. October === | |||
* | |||
=== 16. October - 22. October === | === 16. October - 22. October === | ||
* | * Qt for OS/2 | ||
** Various fixes again | |||
** See: http://svn.netlabs.org/qt3 | |||
* WarpVision | |||
** Demuxer fixes | |||
** See: http://svn.netlabs.org/wvgui | |||
=== 09. October - 15. October === | === 09. October - 15. October === | ||
* Voyager | * Voyager | ||
Line 14: | Line 21: | ||
** Still working on implementation of new Intel chips (HDA), good progress. | ** Still working on implementation of new Intel chips (HDA), good progress. | ||
** Ticket 33 solved | ** Ticket 33 solved | ||
** See: http://svn.netlabs.org/uniaud | |||
* Lucide/2 | * Lucide/2 | ||
** Speed optimized compilation done | ** Speed optimized compilation done | ||
Line 19: | Line 27: | ||
** Made it ready for OpenWatcom 1.6 | ** Made it ready for OpenWatcom 1.6 | ||
** Tickets 54, 74, 78, 79, 92, 138 and 141 solved | ** Tickets 54, 74, 78, 79, 92, 138 and 141 solved | ||
** See: http://svn.netlabs.org/lucide | |||
* Qt for OS/2 | * Qt for OS/2 | ||
** Various fixes | ** Various fixes | ||
** See: http://svn.netlabs.org/qt3 | |||
* WarpVision | * WarpVision | ||
** ffmpeg updated | ** ffmpeg updated | ||
** Various internal fixes | ** Various internal fixes | ||
** Ticket 130 solved | ** Ticket 130 solved | ||
** See: http://svn.netlabs.org/wvgui | |||
=== Guidelines for mail gathering and bi-weekly processing === | === Guidelines for mail gathering and bi-weekly processing === |
Revision as of 21:08, 22 October 2006
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
23. October - 29. October
16. October - 22. October
- Qt for OS/2
- Various fixes again
- See: http://svn.netlabs.org/qt3
- WarpVision
- Demuxer fixes
- See: http://svn.netlabs.org/wvgui
09. October - 15. October
- Voyager
- First version of design book online
- See: http://voyager.netlabs.org/
- WDSybil updated
- UniAud
- Still working on implementation of new Intel chips (HDA), good progress.
- Ticket 33 solved
- See: http://svn.netlabs.org/uniaud
- Lucide/2
- Speed optimized compilation done
- Added version information to plugin description
- Made it ready for OpenWatcom 1.6
- Tickets 54, 74, 78, 79, 92, 138 and 141 solved
- See: http://svn.netlabs.org/lucide
- Qt for OS/2
- Various fixes
- See: http://svn.netlabs.org/qt3
- WarpVision
- ffmpeg updated
- Various internal fixes
- Ticket 130 solved
- See: http://svn.netlabs.org/wvgui
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.