Jump to content

Netlabs News: Difference between revisions

From NikiWiki
MrFawlty (talk | contribs)
MrFawlty (talk | contribs)
Newsletter #33 processed
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]]
=== 16. April - 22. April ===
=== 23. April - 29. April ===
* FM/2
** Lot of work done, additions, defect fixes, changes.
** See: http://svn.netlabs.org/fm2/timeline
* kBuild
** A lot of hacking around...
** See: http://svn.netlabs.org/kbuild/timeline
* kLibC
** Many, many updates
** See: http://svn.netlabs.org/libc/timeline
* NewView
** Bug #19 fixed
** See: http://svn.netlabs.org/newview/timeline
* EDM/2
** 'Booting several operating systems' article multiple updates.
** See: http://www.edm2.com/index.php/Booting_several_operating_systems
** 'Dual Boot' article updated as well.
** See: http://www.edm2.com/index.php/Dual_Boot
=== 9. April - 15. April ===
* Sane2Twain
** Alpha prototype of an open source twain dsm
** This will enable programs like PMView and Maul Publisher to acquire images from your scanner
** Requires a recent SANE build from Paul Smedley
** For configuration and setting up a working environment a recent build of TAME/2 from Paul Smedley is needed as well
** Download: ftp://ftp.netlabs.org/incoming/sanetwaina01.zip
** SANE/TAME: http://smedley.info/sane.html
* FM/2
** Drag and drop fixes
** Check INI header
** See: http://svn.netlabs.org/fm2/timeline
* kBuild
** Some interesting observations
** See: http://svn.netlabs.org/kbuild/timeline
* kLibC
** Too much to mention!
** See: http://svn.netlabs.org/libc/timeline
* NewView
** Some fixes
** See: http://svn.netlabs.org/newview/timeline
* Qt/3
** DBCS input/output fixed
** See: http://svn.netlabs.org/qt3/timeline
* Samba
** Samba 3.0.25rc1 has been released.
** See: http://svn.netlabs.org/samba
** See: http://svn.netlabs.org/samba/timeline
* Voyager Desktop
** Some license stuff for updates and a correction
** See: http://svn.netlabs.org/v_desktop/timeline
* xATA
** A fix to allow multi mode with more than 16 sectors
** See: http://svn.netlabs.org/xata/timeline


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

Revision as of 21:21, 23 April 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

23. April - 29. April

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.