Netlabs News

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

22. January - 28 January

• netlabs server
  • The server will be moved tonight!
  • There will be new webpages online but they will be very basic for the moment! Adrian will work on that afterwards :-)
  • TRAC & Subversion should move tomorrow Tuesday, reaction will be much faster on the new server.
  • IRC will move to its own network for reasons that will be explained later. Right now irc.netlabs.org points to irc.aroa.ch
• The Config.sys Documentation Project
  • The Config.sys documentation project is now hosted in the EDM2 Wiki
  • See: http://www.edm2.com/index.php/The_Config.sys_Documentation_Project
• UniAud
  • Fix TRAP in Intel chips
  • Latest HDA patches from ALSA
  • Added missed files to SVN
  • Applied latest modifications of ALSA
  • Reworked sharing between DART and UNIAUD API
  • R&D on sharing on single stream cards
• WarpVision
  • Added support for g726 codec (Panasonic LCD TV's writing audio in this format. M.b. other, dunno)
  • R&D for DVD menu
  • Working under recording
• DWS 2007
  • It will be held a bit later, ***** July 7 and 8 *****.
  • Still in Amsterdam, The Netherlands
  • See: http://wiki.netlabs.org/index.php/Developers_Workshop_2007
• kBuild
  • Many additions and fixes
  • See: http://svn.netlabs.org/kbuild/timeline
• Lucide
  • RC1 released
  • German, Swedish and French updates
  • Various additions
  • See: http://svn.netlabs.org/lucide/timeline
• NewView
  • Various updates and fixes
  • See: http://svn.netlabs.org/newview/timeline

15. January - 21 January

• netlabs server
• UniAud
  • HDA code updated
  • AC97 code updated. A couple new codecs added. Some AD 19XX codecs features expanded
  • Other hardware updates from ALSA keep going
• WarpVision
  • Fixed a DART issue (no sound)
  • Fixed slider position when playing RM files
  • Fixed (134, 135)
  • Fixed dvd rip playback
  • variouse FFMPEG updates and other small fixes
• FM/2
  • Split user added commands association, toolbar entries
  • See: http://svn.netlabs.org/fm2/timeline
• kBuild
  • Many updates again
  • See: http://svn.netlabs.org/kbuild/timeline
• Lucide
  • Freetype update to version 2.3.0
  • Use UClip library from Yuri Dario for clipboard operations
  • French NLS update
  • Use raw data format for print queue, this avoid metafile creation
  • See: http://svn.netlabs.org/lucide/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.