Netlabs News: Difference between revisions
→12. February - 18. February: added Config.sys project news |
→12. February - 18. February: added UniAud and WarpVision discussion links |
||
Line 9: | Line 9: | ||
** What happened and how to continue? | ** What happened and how to continue? | ||
** See: http://blog.netlabs.org/?p=6 | ** See: http://blog.netlabs.org/?p=6 | ||
* UniAud Suggestions | |||
** Contribute your ideas how to continue UniAud Development | |||
** See: http://wiki.netlabs.org/index.php/UniAudio_Development | |||
* WarpVision Suggestions | |||
** Contribute your ideas how to continue WarpVision Development | |||
** See: http://wiki.netlabs.org/index.php/WarpVision_Development | |||
* DOSBox Version 0.66 RC1 | * DOSBox Version 0.66 RC1 | ||
** The release candidate of version 0.66 of DOSBox is available for OS/2 from CVS as of 2007/02/08. | ** The release candidate of version 0.66 of DOSBox is available for OS/2 from CVS as of 2007/02/08. |
Revision as of 10:36, 18 February 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
12. February - 18. February
- UniAud & WarpVision
- What happened and how to continue?
- See: http://blog.netlabs.org/?p=6
- UniAud Suggestions
- Contribute your ideas how to continue UniAud Development
- See: http://wiki.netlabs.org/index.php/UniAudio_Development
- WarpVision Suggestions
- Contribute your ideas how to continue WarpVision Development
- See: http://wiki.netlabs.org/index.php/WarpVision_Development
- DOSBox Version 0.66 RC1
- The release candidate of version 0.66 of DOSBox is available for OS/2 from CVS as of 2007/02/08.
- Download:
- Small version containing only the necessary files: ftp://ftp.netlabs.org/incoming/dosbox_small_0_66_rc1.exe
- Full version additionally including debugging binaries: ftp://ftp.netlabs.org/incoming/dosbox_full_0_66_rc1.exe
- Sources package: ftp://ftp.netlabs.org/incoming/dosbox_sources_0_66_rc1.exe
- Updates to the The Config.sys Documentation Project
- OS/2-eCS Commands, RUN Statements and DEVICE Statements sections were updated
- See: http://www.edm2.com/index.php/The_Config.sys_Documentation_Project/OS/2-eCS_Commands
- S*e: http://www.edm2.com/index.php/The_Config.sys_Documentation_Project/RUN_Statements
- See: http://www.edm2.com/index.php/The_Config.sys_Documentation_Project/DEVICE_Statements
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.