Jump to content

Netlabs News: Difference between revisions

From NikiWiki
Diver (talk | contribs)
m shop as a link
MrFawlty (talk | contribs)
Processed newsletter #21
Line 3: Line 3:
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]]


In need of new clothes or office stuff or something to hug? And want to support netlabs at the same time? Then have a look at http://shop.netlabs.org, to find high quality goods. Quick response and delivered at your door. So you can look as part of the crowd at WSE as well! Thanks!
=== 6. November - 12. November ===
 
*
=== 30. October - 5. November ===
* Warpstock Europe 2006
** netlabs.org related sessions at WSE 2006
*** Netlabs EPM Distribution by Andreas Schnellbacher
*** WPA Security with Wireless LAN Monitor by Christian Langanke
*** The voyager project by Adrian Gschwend
*** netlabs.org: The crux with the community by Adrian Gschwend
** Please join us in Cologne, Germany from November 17 to 19
* kLIBC
** Various updates again
** See: http://svn.netlabs.org/libc/timeline
* Lucide
** Updated to Freetype 2.2.1
** German NLS updated
** See: http://svn.netlabs.org/lucide/timeline
* QT3 Library for OS/2
** Enhancements to the exception handling in the QT3 library
** See: http://svn.netlabs.org/qt3/timeline
* WarpVision
** DART fixes
** See: http://svn.netlabs.org/wvgui/timeline
 
=== 23. October - 29. October ===
* eCups
** This is a new project to get CUPS integrated into eCS
** See: http://svn.netlabs.org/ecups
* kLIBC
** Many updates
** See: http://svn.netlabs.org/libc/timeline
* Lucide
** Spanish NLS updated
** See: http://svn.netlabs.org/lucide/timeline
* QT3 Library for OS/2
** Enhancements to the exception handling in the QT3 library
** Fixes for UniAud in QSound
** See: http://svn.netlabs.org/qt3/timeline
* UniAud
** Support for Via 8251 added
** SB and HDA code updated, among others
** See: http://svn.netlabs.org/uniaud/timeline
* Voyager documentation
** The Voyager documentation is online via SVN now
** See: http://svn.netlabs.org/v_doc


=== Guidelines for mail gathering and bi-weekly processing ===
=== Guidelines for mail gathering and bi-weekly processing ===

Revision as of 19:52, 6 November 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

6. November - 12. November

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.