NikiWiki - User contributions [en]

Talk:Warpstock Europe Websites

2007-04-19T16:05:37Z

CHennecke:

Feel free to add your comment here.

WarpVision Development

2007-04-02T15:38:27Z

CHennecke: /* Suggestions for Milestones */ added MMPM/2 integration

This document is used to collect ideas what must be changed to start again with WarpVision development. This is by no means a complete document, so please help to finish it!

=== How to improve development ===
* Create a standard test environment including potentially problematic video and audio files
** files that don't play at all or crash WarpVision
** files that need a long time to be scanned
** files that exhibit video/audio sync problems
* Create a document that describes in '''full detail what''' a tester has to do and '''how'''
** There are various ways that WarpVision outputs usefull information, they have to be listed and explained
* Record user and tester reports in an "experience database" so the developer(s) can relate changes to effects more easily--also at later points for previous versions
* We need clear milestones
* Have a test plan for '''every''' major release
** This can only work if we have a number of testers for WarpVision
* Standardize the build environment with the help of Christian Langanke
* Make it easier for testers and users to find appropriate versions
** Follow a strict version numbering scheme
** Record changes, preferably in "non-developer speak"
* Update the user documentation (INF file)

==== Suggestions for Milestones ====
* Finish the playlist including:
** reordering items in the playlist via drag and drop
** removing selected items from the playlist by hitting the delete key
** enable menu items of the playlist pop-up menu to be applied to several selected files (last, first, ...)
* Implement DVD menus/subtitles
* Fix the broken audio-playback in current SVN code.
* Clean up the settings notebook which is currently too large and obfuscated
** Move unrelated items to "subpages" or new tabs
*** Move "Show time info" and "Enable history" to Interface page 1 called "Interface"
*** Move subtitle and OSD settings to new Interface page 3 called "Display"
*** Rename Interface page 2 "Aspect ratio" to "Screen"
*** Move "Desktop color" from "System" tab to Interface page 3
*** Move "CD preread time" from "Other" group on "System" tab to "DVD/VCD" tab
*** "DVD/VCD" tab could be renamed to "Media"
* Include instructions on how to checkout the freaking code! This should be also mentioned on the TRAC page
* Integrate the stuff into MMPM/2 instead, as David O'Connor tried with [http://doconnor.reamined.on.ca/xine/ Xine]

=== How to raise money ===
* from the os2world.com thread
** Collect up front $5000 to $6000 by $20 per subscription for 1 year. This means 200 to 300 people must subscribe to this project. Make 5 milestones. Subscribers vote as to whether the milestone has been reached and the programmer is paid $1000 per milestone.

Warpstock Europe Websites

2007-04-02T15:32:24Z

CHennecke: /* Organizational features */ added handout CD item

==Introduction==

This goal of this wiki page is to discuss a web site concept for Warpstock Europe and other OS/2 related events. This is for the visitors and organizers of such events--'''you.''' So your input is most welcome. If you would like to contribute, ask Robert Henschel (os2info at gmx dot net) for an account.

==Warpstock Europe homepage (www.warpstock.eu)==

The main page should focus on the fact that the entire world might hit it. So what we should show here is a brief description of what Warpstock Europe is about. Needless to say, the entire stuff should be kept informative but "neutral"--in the sense of "advocacy-free." Anything else could alienate potential visitors and exhibitors and create a "OS/2 lunatics" image.

===Target groups===

Next, let's see who will be most probably coming there and for what. First of all, let's focus on those parts of the website that are accessible to everyone (without a special login so to say).

* WSE visitors? Yes. They will either look at the previous events (transcripts, photo gallery, etc.) or look around to get information about the upcoming event(s). Maybe they'll be looking for contacts or a possibility to subscribe to a newsletter.

* WSE organizers and helping hands? Only partially. Those interested in helping out need some information on areas they can help, what they might get in return, and whom to contact. Once this phase is over, they've got their "internal" site. Except perhaps for checking out how this site looks after updating it.

* WSE Sponsors? Yes. We should include information on how to support a) the organisation itself and b) a specific (upcoming) event. Contacts and general information (e.g., required size of their logo, etc.) should be provided on a dedicated page.

* Speakers? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
*** requirements for presentations (guidelines for formatting and effects, file formats, '''deadlines''')
** for a specific event:
*** contacts
*** time tables
*** meals and accomodation
*** infrastructure (network, provided computers, audio)
*** presentation templates (for OO.org, LaTeX Beamer, S5)
*** etc.

* Exhibitors? Yes. Exhibitors are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being an exhibitor works
*** what being an exhibitor means
** for a specific event:
*** contacts
*** fees for commercial exhibitors? (Well, I guess we can forget that one.)
*** booth size
*** infrastructure (network, mains, tables)
*** Time-frame for mounting/unmounting
*** liability and insurance
*** meals and accomodation
*** etc.

* Press? Perhaps. That would be great. We should set up a press room with logos, pictures, fact sheets / summaries, and contacts.

* Newbies? Yes. This can either be WSE-newbies or even OS/2+eCS-newbies. Give a warm welcome and take the pain out of getting "an insider" or "member of the club."

* "Foreign" webmasters? Yes. They will look for information about how to provide links to events on their sites or who to syndicate with news feeds.

* Crawlers, robots, engines? Yes. We will need to keep an eye on search-engine-friendly link formatting and hiding sensitive data somehow. Also we should try to avoid automated submissions or subscriptions/signups in forums, etc.

===Features===

If that wasn't yet enough work to do, we actually are planning something '''great''' and '''new''' which means:

* the site will stay for years, even decades, maybe forever
* the site will be enlarged with every event taking place
* the site is the SPOC (single point of contact) for WSE, thus needs to be '''good'''
* did I mention that the site needs to look good?

Keeping that in mind, we need "modern" stuff: Easy to use and useful (and good-looking...):

* CMS supporting multiple languages
* forums for people to chat, discuss, and maybe create carpools
* newsletter and news RSS feeds (->subscriptions)
* downloads (screensaver, link logos, presentations, etc.)
* picture gallery
** pre-event: location
** post-event: pictures from event
* calendar, maybe downloadable as iCal
** other events
** presentations
* shop (registration, merchandising, sponsor units, etc.)
* FAQ
* maybe event / organisation "blogs," e.g., for visitors to describe their impressions/experiences
* of course a database behind most of the parts

Okay, that's it for the "public" site.

===Organizational features===

Next, we need a somehow "restricted" area for people involved in doing events. This needs to provide the following:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
** etc.
* various docs:
** How to organize an OS/2 event (assign team members to specific organizational areas, insurance, catering, etc.)
** cost calculation help
** PR templates
** exhibitor and speaker info templates
** visitor info templates
** how to invite people from eastern Europe
** How to create a handout CD
** etc.
* hardware stuff:
** Who has video projectors?
** Who provided WLAN APs last year?
** etc.
* per-event:
** who brings what
** what happens when and where
** etc.
* forums general/per event
* maybe a collaboration/groupware with
** calendars
** todos
** project manager (including status, gant charts) for activities
* event schedule manager
** every presentation should be held twice
** speakers can do more than one presentation, but they can't do that at the same time
** speakers can team up (make sure speaker team members are not individual speakers of different presentation at the same time)
** two presentations shouldn't be held at the same time twice (on a second day)
** maybe code from the old OS2.org Warpstock Europe administration backend could be recycled
* role-focused mailboxes (team-driven, independent from a individuals). Could be IMAP: This would help in getting to run a team-oriented mail stuff and to keep everything online in one place.

===Administrational features===

A considerable amount of the facts that comprise the information provided on the site will evolve over time. Thus the online information needs to be updated. The best way would be to provide a means for collaborative work: a wiki. This would significantly reduce the need to mail files back and forth.

==Portal for OS/2 related events (warpevents.eu)==

Now, so far all of the above deals with Warpstock Europe. But most of it also applies to other Warp events, be it Czech Warpstock, Developer Workshop, WarpWochenende, or even a local club.

While most of them already have a dedicated website or will set up something on their own for various reasons, why not have a single website for worldwide events that basically is a calendar. Here we can show all events that deal with OS/2 and eCS, regardless of size, scope, or subject. This should include reports regarding the status of work on the next events, at least in the pre-website phase (search for location, etc.). Imagine a site that shows the whole world that we're still alive with stuff happening almost weekly at different places around the globe.

We don't want to get in competition with OS/2 World.com or others--this site will focus on "events," not technology or software. Just take this webpage as a single spot to concentrate (info in one place) and distribute (link to other sites).

Also, the site needs to provide some of the information about event organization from the "internal" Warpstock Europe site:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
* various docs:
** How to organize an OS/2 event
** cost calculation help

Furthermore, it wouldn't hurt to offer reports from previous events.

Just an idea on the organisation and interaction/delegation between the sites. As you see, we're not too sure about how we can get a useable setup valid for us as well as for others. We'll rely on your support here.

==Warpstock Europe "Board"==

The official "club" or "board" behind WSE is a totally different topic and has nothing to do with the website being discussed here. At some point perhaps, the WSE "board" will be taking over the responsability of the warpstock.eu website, but that doesn't matter as of now and more importantly: We should not wait for the board to care about the site. It might take years to get a board (if ever). So let's get the site done for our own sake and let's see what wse".org" will become later.

==Hosting and CMS==

This will be done by Thomas Klein via a professional 3rd party (neutral) hoster (DomainFactory) and he is willing to pay for that at least in the first year.

This will '''not''' be an own server! This means:
* less administration work
* proven, safe, secure and easy-to-use
* no dealing with hardware and operating system
* commercial-grade, professional-level and '''fulltime''' free customer support
* hosting service can be shot in case of problems ;-)

It also means that the server will '''not''' run OS/2, but some Unix. ''We need to get the job done!'' Instead of fiddling around with hardware and software we can rely on proven solutions. This enables us to focus on the site and its content.

===Why a CMS? (Content Management System)===

* people without HTML knowledge can work on the content
* several people can work on the site without the need for someone to insert the changes into code
* we don't have to mess around with static pages (copying, renaming)
* we don't need to watch on keeping a consistent layout thoughout the site
* we don't need to trick around to get multiple language support
* we don't need to share (or have access to) local files on a PC and to FTP-upload them
In short: Once set up, we can focus on ''getting the job done'' faster, simpler and more in time!

===Possible choices===

For the CMS we can see two alternatives:

* TYPO3
** loads of extensions available
** might require a higher-powered hosting package
** not sure yet if supported by shared hosting environment limitations
* Joomla
** one-click install possible, works well in hosting environment
** might lack available extensions, thus more work (?)

Both are freely available, open sourced, and there are many extensions that can be used to add functionality.

For TYPO3, this extension could be interesting: [http://typo3.org/extensions/repository/view/pt_conference/0.4.0/] It does not provide all we need yet, though.

If it turns out that we '''really''' need this, the internal site for organizers could use eGroupware. But this should only be a last resort as a consistent user-interface is desirable. (Adapting eGroupware to match with a site's framework style is tedious... and out of the scope of our intended work)

Warpstock Europe Websites

2007-03-05T23:30:46Z

CHennecke: /* Introduction */ Added account info

==Introduction==

This goal of this wiki page is to discuss a web site concept for Warpstock Europe and other OS/2 related events. This is for the visitors and organizers of such events--'''you.''' So your input is most welcome. If you would like to contribute, ask Robert Henschel (os2info at gmx dot net) for an account.

==Warpstock Europe homepage (www.warpstock.eu)==

The main page should focus on the fact that the entire world might hit it. So what we should show here is a brief description of what Warpstock Europe is about. Needless to say, the entire stuff should be kept informative but "neutral"--in the sense of "advocacy-free." Anything else could alienate potential visitors and exhibitors and create a "OS/2 lunatics" image.

===Target groups===

Next, let's see who will be most probably coming there and for what. First of all, let's focus on those parts of the website that are accessible to everyone (without a special login so to say).

* WSE visitors? Yes. They will either look at the previous events (transcripts, photo gallery, etc.) or look around to get information about the upcoming event(s). Maybe they'll be looking for contacts or a possibility to subscribe to a newsletter.

* WSE organizers and helping hands? Only partially. Those interested in helping out need some information on areas they can help, what they might get in return, and whom to contact. Once this phase is over, they've got their "internal" site. Except perhaps for checking out how this site looks after updating it.

* WSE Sponsors? Yes. We should include information on how to support a) the organisation itself and b) a specific (upcoming) event. Contacts and general information (e.g., required size of their logo, etc.) should be provided on a dedicated page.

* Speakers? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
*** requirements for presentations (guidelines for formatting and effects, file formats, '''deadlines''')
** for a specific event:
*** contacts
*** time tables
*** meals and accomodation
*** infrastructure (network, provided computers, audio)
*** presentation templates (for OO.org, LaTeX Beamer, S5)
*** etc.

* Exhibitors? Yes. Exhibitors are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being an exhibitor works
*** what being an exhibitor means
** for a specific event:
*** contacts
*** fees for commercial exhibitors? (Well, I guess we can forget that one.)
*** booth size
*** infrastructure (network, mains, tables)
*** Time-frame for mounting/unmounting
*** liability and insurance
*** meals and accomodation
*** etc.

* Press? Perhaps. That would be great. We should set up a press room with logos, pictures, fact sheets / summaries, and contacts.

* Newbies? Yes. This can either be WSE-newbies or even OS/2+eCS-newbies. Give a warm welcome and take the pain out of getting "an insider" or "member of the club."

* "Foreign" webmasters? Yes. They will look for information about how to provide links to events on their sites or who to syndicate with news feeds.

* Crawlers, robots, engines? Yes. We will need to keep an eye on search-engine-friendly link formatting and hiding sensitive data somehow. Also we should try to avoid automated submissions or subscriptions/signups in forums, etc.

===Features===

If that wasn't yet enough work to do, we actually are planning something '''great''' and '''new''' which means:

* the site will stay for years, even decades, maybe forever
* the site will be enlarged with every event taking place
* the site is the SPOC (single point of contact) for WSE, thus needs to be '''good'''
* did I mention that the site needs to look good?

Keeping that in mind, we need "modern" stuff: Easy to use and useful (and good-looking...):

* CMS supporting multiple languages
* forums for people to chat, discuss, and maybe create carpools
* newsletter and news RSS feeds (->subscriptions)
* downloads (screensaver, link logos, presentations, etc.)
* picture gallery
** pre-event: location
** post-event: pictures from event
* calendar, maybe downloadable as iCal
** other events
** presentations
* shop (registration, merchandising, sponsor units, etc.)
* FAQ
* maybe event / organisation "blogs," e.g., for visitors to describe their impressions/experiences
* of course a database behind most of the parts

Okay, that's it for the "public" site.

===Organizational features===

Next, we need a somehow "restricted" area for people involved in doing events. This needs to provide the following:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
** etc.
* various docs:
** How to organize an OS/2 event (assign team members to specific organizational areas, insurance, catering, etc.)
** cost calculation help
** PR templates
** exhibitor and speaker info templates
** visitor info templates
** how to invite people from eastern Europe
** etc.
* hardware stuff:
** Who has video projectors?
** Who provided WLAN APs last year?
** etc.
* per-event:
** who brings what
** what happens when and where
** etc.
* forums general/per event
* maybe a collaboration/groupware with
** calendars
** todos
** project manager (including status, gant charts) for activities
* event schedule manager
** every presentation should be held twice
** speakers can do more than one presentation, but they can't do that at the same time
** speakers can team up (make sure speaker team members are not individual speakers of different presentation at the same time)
** two presentations shouldn't be held at the same time twice (on a second day)
** maybe code from the old OS2.org Warpstock Europe administration backend could be recycled
* role-focused mailboxes (team-driven, independent from a individuals). Could be IMAP: This would help in getting to run a team-oriented mail stuff and to keep everything online in one place.

===Administrational features===

A considerable amount of the facts that comprise the information provided on the site will evolve over time. Thus the online information needs to be updated. The best way would be to provide a means for collaborative work: a wiki. This would significantly reduce the need to mail files back and forth.

==Portal for OS/2 related events (warpevents.eu)==

Now, so far all of the above deals with Warpstock Europe. But most of it also applies to other Warp events, be it Czech Warpstock, Developer Workshop, WarpWochenende, or even a local club.

While most of them already have a dedicated website or will set up something on their own for various reasons, why not have a single website for worldwide events that basically is a calendar. Here we can show all events that deal with OS/2 and eCS, regardless of size, scope, or subject. This should include reports regarding the status of work on the next events, at least in the pre-website phase (search for location, etc.). Imagine a site that shows the whole world that we're still alive with stuff happening almost weekly at different places around the globe.

We don't want to get in competition with OS/2 World.com or others--this site will focus on "events," not technology or software. Just take this webpage as a single spot to concentrate (info in one place) and distribute (link to other sites).

Also, the site needs to provide some of the information about event organization from the "internal" Warpstock Europe site:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
* various docs:
** How to organize an OS/2 event
** cost calculation help

Furthermore, it wouldn't hurt to offer reports from previous events.

Just an idea on the organisation and interaction/delegation between the sites. As you see, we're not too sure about how we can get a useable setup valid for us as well as for others. We'll rely on your support here.

==Warpstock Europe "Board"==

The official "club" or "board" behind WSE is a totally different topic and has nothing to do with the website being discussed here. At some point perhaps, the WSE "board" will be taking over the responsability of the warpstock.eu website, but that doesn't matter as of now and more importantly: We should not wait for the board to care about the site. It might take years to get a board (if ever). So let's get the site done for our own sake and let's see what wse".org" will become later.

==Hosting and CMS==

This will be done by Thomas Klein via a professional 3rd party (neutral) hoster (DomainFactory) and he is willing to pay for that at least in the first year.

This will '''not''' be an own server! This means:
* less administration work
* proven, safe, secure and easy-to-use
* no dealing with hardware and operating system
* commercial-grade, professional-level and '''fulltime''' free customer support
* hosting service can be shot in case of problems ;-)

It also means that the server will '''not''' run OS/2, but some Unix. ''We need to get the job done!'' Instead of fiddling around with hardware and software we can rely on proven solutions. This enables us to focus on the site and its content.

===Why a CMS? (Content Management System)===

* people without HTML knowledge can work on the content
* several people can work on the site without the need for someone to insert the changes into code
* we don't have to mess around with static pages (copying, renaming)
* we don't need to watch on keeping a consistent layout thoughout the site
* we don't need to trick around to get multiple language support
* we don't need to share (or have access to) local files on a PC and to FTP-upload them
In short: Once set up, we can focus on ''getting the job done'' faster, simpler and more in time!

===Possible choices===

For the CMS we can see two alternatives:

* Typo3
** loads of extensions available
** might require a higher-powered hosting package
** not sure yet if supported by shared hosting environment limitations
* Joomla
** one-click install possible, works well in hosting environment
** might lack available extensions, thus more work (?)

Both are freely available, open sourced, and there are many extensions that can be used to add functionality.

For Typo3, this extension could be interesting: [http://typo3.org/extensions/repository/view/pt_conference/0.4.0/] It does not provide all we need yet, though.

If it turns out that we '''really''' need this, the internal site for organizers could use eGroupware. But this should only be a last resort as a consistent user-interface is desirable. (Adapting eGroupware to match with a site's framework style is tedious... and out of the scope of our intended work)

Warpstock Europe Websites

2007-03-02T14:03:56Z

CHennecke: /* Why a CMS? (Content Management System) */ Fixed typo

==Introduction==

This goal of this wiki page is to discuss a web site concept for Warpstock Europe and other OS/2 related events. This is for the visitors and organizers of such events--'''you.''' So your input is most welcome.

==Warpstock Europe homepage (www.warpstock.eu)==

The main page should focus on the fact that the entire world might hit it. So what we should show here is a brief description of what Warpstock Europe is about. Needless to say, the entire stuff should be kept informative but "neutral"--in the sense of "advocacy-free." Anything else could alienate potential visitors and exhibitors and create a "OS/2 lunatics" image.

===Target groups===

Next, let's see who will be most probably coming there and for what. First of all, let's focus on those parts of the website that are accessible to everyone (without a special login so to say).

* WSE visitors? Yes. They will either look at the previous events (transcripts, photo gallery, etc.) or look around to get information about the upcoming event(s). Maybe they'll be looking for contacts or a possibility to subscribe to a newsletter.

* WSE organizers and helping hands? Only partially. Those interested in helping out need some information on areas they can help, what they might get in return, and whom to contact. Once this phase is over, they've got their "internal" site. Except perhaps for checking out how this site looks after updating it.

* WSE Sponsors? Yes. We should include information on how to support a) the organisation itself and b) a specific (upcoming) event. Contacts and general information (e.g., required size of their logo, etc.) should be provided on a dedicated page.

* Speakers? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
*** requirements for presentations (guidelines for formatting and effects, file formats, '''deadlines''')
** for a specific event:
*** contacts
*** time tables
*** meals and accomodation
*** infrastructure (network, provided computers, audio)
*** presentation templates (for OO.org, LaTeX Beamer, S5)
*** etc.

* Exhibitors? Yes. Exhibitors are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being an exhibitor works
*** what being an exhibitor means
** for a specific event:
*** contacts
*** fees for commercial exhibitors? (Well, I guess we can forget that one.)
*** booth size
*** infrastructure (network, mains, tables)
*** Time-frame for mounting/unmounting
*** liability and insurance
*** meals and accomodation
*** etc.

* Press? Perhaps. That would be great. We should set up a press room with logos, pictures, fact sheets / summaries, and contacts.

* Newbies? Yes. This can either be WSE-newbies or even OS/2+eCS-newbies. Give a warm welcome and take the pain out of getting "an insider" or "member of the club."

* "Foreign" webmasters? Yes. They will look for information about how to provide links to events on their sites or who to syndicate with news feeds.

* Crawlers, robots, engines? Yes. We will need to keep an eye on search-engine-friendly link formatting and hiding sensitive data somehow. Also we should try to avoid automated submissions or subscriptions/signups in forums, etc.

===Features===

If that wasn't yet enough work to do, we actually are planning something '''great''' and '''new''' which means:

* the site will stay for years, even decades, maybe forever
* the site will be enlarged with every event taking place
* the site is the SPOC (single point of contact) for WSE, thus needs to be '''good'''
* did I mention that the site needs to look good?

Keeping that in mind, we need "modern" stuff: Easy to use and useful (and good-looking...):

* CMS supporting multiple languages
* forums for people to chat, discuss, and maybe create carpools
* newsletter and news RSS feeds (->subscriptions)
* downloads (screensaver, link logos, presentations, etc.)
* picture gallery
** pre-event: location
** post-event: pictures from event
* calendar, maybe downloadable as iCal
** other events
** presentations
* shop (registration, merchandising, sponsor units, etc.)
* FAQ
* maybe event / organisation "blogs," e.g., for visitors to describe their impressions/experiences
* of course a database behind most of the parts

Okay, that's it for the "public" site.

===Organizational features===

Next, we need a somehow "restricted" area for people involved in doing events. This needs to provide the following:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
** etc.
* various docs:
** How to organize an OS/2 event (assign team members to specific organizational areas, insurance, catering, etc.)
** cost calculation help
** PR templates
** exhibitor and speaker info templates
** visitor info templates
** how to invite people from eastern Europe
** etc.
* hardware stuff:
** Who has video projectors?
** Who provided WLAN APs last year?
** etc.
* per-event:
** who brings what
** what happens when and where
** etc.
* forums general/per event
* maybe a collaboration/groupware with
** calendars
** todos
** project manager (including status, gant charts) for activities
* event schedule manager
** every presentation should be held twice
** speakers can do more than one presentation, but they can't do that at the same time
** speakers can team up (make sure speaker team members are not individual speakers of different presentation at the same time)
** two presentations shouldn't be held at the same time twice (on a second day)
** maybe code from the old OS2.org Warpstock Europe administration backend could be recycled
* role-focused mailboxes (team-driven, independent from a individuals). Could be IMAP: This would help in getting to run a team-oriented mail stuff and to keep everything online in one place.

===Administrational features===

A considerable amount of the facts that comprise the information provided on the site will evolve over time. Thus the online information needs to be updated. The best way would be to provide a means for collaborative work: a wiki. This would significantly reduce the need to mail files back and forth.

==Portal for OS/2 related events (warpevents.eu)==

Now, so far all of the above deals with Warpstock Europe. But most of it also applies to other Warp events, be it Czech Warpstock, Developer Workshop, WarpWochenende, or even a local club.

While most of them already have a dedicated website or will set up something on their own for various reasons, why not have a single website for worldwide events that basically is a calendar. Here we can show all events that deal with OS/2 and eCS, regardless of size, scope, or subject. This should include reports regarding the status of work on the next events, at least in the pre-website phase (search for location, etc.). Imagine a site that shows the whole world that we're still alive with stuff happening almost weekly at different places around the globe.

We don't want to get in competition with OS/2 World.com or others--this site will focus on "events," not technology or software. Just take this webpage as a single spot to concentrate (info in one place) and distribute (link to other sites).

Also, the site needs to provide some of the information about event organization from the "internal" Warpstock Europe site:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
* various docs:
** How to organize an OS/2 event
** cost calculation help

Furthermore, it wouldn't hurt to offer reports from previous events.

Just an idea on the organisation and interaction/delegation between the sites. As you see, we're not too sure about how we can get a useable setup valid for us as well as for others. We'll rely on your support here.

==Warpstock Europe "Board"==

The official "club" or "board" behind WSE is a totally different topic and has nothing to do with the website being discussed here. At some point perhaps, the WSE "board" will be taking over the responsability of the warpstock.eu website, but that doesn't matter as of now and more importantly: We should not wait for the board to care about the site. It might take years to get a board (if ever). So let's get the site done for our own sake and let's see what wse".org" will become later.

==Hosting and CMS==

This will be done by Thomas Klein via a professional 3rd party (neutral) hoster (DomainFactory) and he is willing to pay for that at least in the first year.

This will '''not''' be an own server! This means:
* less administration work
* proven, safe, secure and easy-to-use
* no dealing with hardware and operating system
* commercial-grade, professional-level and '''fulltime''' free customer support
* hosting service can be shot in case of problems ;-)

It also means that the server will '''not''' run OS/2, but some Unix. ''We need to get the job done!'' Instead of fiddling around with hardware and software we can rely on proven solutions. This enables us to focus on the site and its content.

===Why a CMS? (Content Management System)===

* people without HTML knowledge can work on the content
* several people can work on the site without the need for someone to insert the changes into code
* we don't have to mess around with static pages (copying, renaming)
* we don't need to watch on keeping a consistent layout thoughout the site
* we don't need to trick around to get multiple language support
* we don't need to share (or have access to) local files on a PC and to FTP-upload them
In short: Once set up, we can focus on ''getting the job done'' faster, simpler and more in time!

===Possible choices===

For the CMS we can see two alternatives:

* Typo3
** loads of extensions available
** might require a higher-powered hosting package
** not sure yet if supported by shared hosting environment limitations
* Joomla
** one-click install possible, works well in hosting environment
** might lack available extensions, thus more work (?)

Both are freely available, open sourced, and there are many extensions that can be used to add functionality.

For Typo3, this extension could be interesting: [http://typo3.org/extensions/repository/view/pt_conference/0.4.0/] It does not provide all we need yet, though.

If it turns out that we '''really''' need this, the internal site for organizers could use eGroupware. But this should only be a last resort as a consistent user-interface is desirable. (Adapting eGroupware to match with a site's framework style is tedious... and out of the scope of our intended work)

Warpstock Europe Websites

2007-03-02T14:03:08Z

CHennecke: /* Hosting and CMS */ added item regarding HTML knowledge, modified formatting

==Introduction==

This goal of this wiki page is to discuss a web site concept for Warpstock Europe and other OS/2 related events. This is for the visitors and organizers of such events--'''you.''' So your input is most welcome.

==Warpstock Europe homepage (www.warpstock.eu)==

The main page should focus on the fact that the entire world might hit it. So what we should show here is a brief description of what Warpstock Europe is about. Needless to say, the entire stuff should be kept informative but "neutral"--in the sense of "advocacy-free." Anything else could alienate potential visitors and exhibitors and create a "OS/2 lunatics" image.

===Target groups===

Next, let's see who will be most probably coming there and for what. First of all, let's focus on those parts of the website that are accessible to everyone (without a special login so to say).

* WSE visitors? Yes. They will either look at the previous events (transcripts, photo gallery, etc.) or look around to get information about the upcoming event(s). Maybe they'll be looking for contacts or a possibility to subscribe to a newsletter.

* WSE organizers and helping hands? Only partially. Those interested in helping out need some information on areas they can help, what they might get in return, and whom to contact. Once this phase is over, they've got their "internal" site. Except perhaps for checking out how this site looks after updating it.

* WSE Sponsors? Yes. We should include information on how to support a) the organisation itself and b) a specific (upcoming) event. Contacts and general information (e.g., required size of their logo, etc.) should be provided on a dedicated page.

* Speakers? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
*** requirements for presentations (guidelines for formatting and effects, file formats, '''deadlines''')
** for a specific event:
*** contacts
*** time tables
*** meals and accomodation
*** infrastructure (network, provided computers, audio)
*** presentation templates (for OO.org, LaTeX Beamer, S5)
*** etc.

* Exhibitors? Yes. Exhibitors are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being an exhibitor works
*** what being an exhibitor means
** for a specific event:
*** contacts
*** fees for commercial exhibitors? (Well, I guess we can forget that one.)
*** booth size
*** infrastructure (network, mains, tables)
*** Time-frame for mounting/unmounting
*** liability and insurance
*** meals and accomodation
*** etc.

* Press? Perhaps. That would be great. We should set up a press room with logos, pictures, fact sheets / summaries, and contacts.

* Newbies? Yes. This can either be WSE-newbies or even OS/2+eCS-newbies. Give a warm welcome and take the pain out of getting "an insider" or "member of the club."

* "Foreign" webmasters? Yes. They will look for information about how to provide links to events on their sites or who to syndicate with news feeds.

* Crawlers, robots, engines? Yes. We will need to keep an eye on search-engine-friendly link formatting and hiding sensitive data somehow. Also we should try to avoid automated submissions or subscriptions/signups in forums, etc.

===Features===

If that wasn't yet enough work to do, we actually are planning something '''great''' and '''new''' which means:

* the site will stay for years, even decades, maybe forever
* the site will be enlarged with every event taking place
* the site is the SPOC (single point of contact) for WSE, thus needs to be '''good'''
* did I mention that the site needs to look good?

Keeping that in mind, we need "modern" stuff: Easy to use and useful (and good-looking...):

* CMS supporting multiple languages
* forums for people to chat, discuss, and maybe create carpools
* newsletter and news RSS feeds (->subscriptions)
* downloads (screensaver, link logos, presentations, etc.)
* picture gallery
** pre-event: location
** post-event: pictures from event
* calendar, maybe downloadable as iCal
** other events
** presentations
* shop (registration, merchandising, sponsor units, etc.)
* FAQ
* maybe event / organisation "blogs," e.g., for visitors to describe their impressions/experiences
* of course a database behind most of the parts

Okay, that's it for the "public" site.

===Organizational features===

Next, we need a somehow "restricted" area for people involved in doing events. This needs to provide the following:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
** etc.
* various docs:
** How to organize an OS/2 event (assign team members to specific organizational areas, insurance, catering, etc.)
** cost calculation help
** PR templates
** exhibitor and speaker info templates
** visitor info templates
** how to invite people from eastern Europe
** etc.
* hardware stuff:
** Who has video projectors?
** Who provided WLAN APs last year?
** etc.
* per-event:
** who brings what
** what happens when and where
** etc.
* forums general/per event
* maybe a collaboration/groupware with
** calendars
** todos
** project manager (including status, gant charts) for activities
* event schedule manager
** every presentation should be held twice
** speakers can do more than one presentation, but they can't do that at the same time
** speakers can team up (make sure speaker team members are not individual speakers of different presentation at the same time)
** two presentations shouldn't be held at the same time twice (on a second day)
** maybe code from the old OS2.org Warpstock Europe administration backend could be recycled
* role-focused mailboxes (team-driven, independent from a individuals). Could be IMAP: This would help in getting to run a team-oriented mail stuff and to keep everything online in one place.

===Administrational features===

A considerable amount of the facts that comprise the information provided on the site will evolve over time. Thus the online information needs to be updated. The best way would be to provide a means for collaborative work: a wiki. This would significantly reduce the need to mail files back and forth.

==Portal for OS/2 related events (warpevents.eu)==

Now, so far all of the above deals with Warpstock Europe. But most of it also applies to other Warp events, be it Czech Warpstock, Developer Workshop, WarpWochenende, or even a local club.

While most of them already have a dedicated website or will set up something on their own for various reasons, why not have a single website for worldwide events that basically is a calendar. Here we can show all events that deal with OS/2 and eCS, regardless of size, scope, or subject. This should include reports regarding the status of work on the next events, at least in the pre-website phase (search for location, etc.). Imagine a site that shows the whole world that we're still alive with stuff happening almost weekly at different places around the globe.

We don't want to get in competition with OS/2 World.com or others--this site will focus on "events," not technology or software. Just take this webpage as a single spot to concentrate (info in one place) and distribute (link to other sites).

Also, the site needs to provide some of the information about event organization from the "internal" Warpstock Europe site:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
* various docs:
** How to organize an OS/2 event
** cost calculation help

Furthermore, it wouldn't hurt to offer reports from previous events.

Just an idea on the organisation and interaction/delegation between the sites. As you see, we're not too sure about how we can get a useable setup valid for us as well as for others. We'll rely on your support here.

==Warpstock Europe "Board"==

The official "club" or "board" behind WSE is a totally different topic and has nothing to do with the website being discussed here. At some point perhaps, the WSE "board" will be taking over the responsability of the warpstock.eu website, but that doesn't matter as of now and more importantly: We should not wait for the board to care about the site. It might take years to get a board (if ever). So let's get the site done for our own sake and let's see what wse".org" will become later.

==Hosting and CMS==

This will be done by Thomas Klein via a professional 3rd party (neutral) hoster (DomainFactory) and he is willing to pay for that at least in the first year.

This will '''not''' be an own server! This means:
* less administration work
* proven, safe, secure and easy-to-use
* no dealing with hardware and operating system
* commercial-grade, professional-level and '''fulltime''' free customer support
* hosting service can be shot in case of problems ;-)

It also means that the server will '''not''' run OS/2, but some Unix. ''We need to get the job done!'' Instead of fiddling around with hardware and software we can rely on proven solutions. This enables us to focus on the site and its content.

===Why a CMS? (Content Management System)===

* people without HTML knowledge can work on the content
* several people can work on the site without the need of someone to insert the changes into code
* we don't have to mess around with static pages (copying, renaming)
* we don't need to watch on keeping a consistent layout thoughout the site
* we don't need to trick around to get multiple language support
* we don't need to share (or have access to) local files on a PC and to FTP-upload them
In short: Once set up, we can focus on ''getting the job done'' faster, simpler and more in time!

===Possible choices===

For the CMS we can see two alternatives:

* Typo3
** loads of extensions available
** might require a higher-powered hosting package
** not sure yet if supported by shared hosting environment limitations
* Joomla
** one-click install possible, works well in hosting environment
** might lack available extensions, thus more work (?)

Both are freely available, open sourced, and there are many extensions that can be used to add functionality.

For Typo3, this extension could be interesting: [http://typo3.org/extensions/repository/view/pt_conference/0.4.0/] It does not provide all we need yet, though.

If it turns out that we '''really''' need this, the internal site for organizers could use eGroupware. But this should only be a last resort as a consistent user-interface is desirable. (Adapting eGroupware to match with a site's framework style is tedious... and out of the scope of our intended work)

Main Page

2007-03-01T16:34:28Z

CHennecke: /* Roadmap */ Changed links for better presentation

__NOTOC__

Welcome to the Wiki at netlabs.org. You will find a lot of interesting information about OS/2 and [http://www.ecomstation.com eCS] on this page. 
If you are interested in joining the '''community mailinglist''' please have a look [[Mailinglists | here]]!

'''QUICKNEWS''': We prevent registering new users from now on till we fixed the spamming-problems on the Wiki, sorry! If you want to have a user send an email to ktk [at] netlabs.org and we will do one. Will be fixed ASAP.

== Roadmap ==
Where are we now and where could we go. Open for discussions.

*[[Ideas]] - This is so far a random collection of ideas and stuff we have in our heads and which probably is worth creating a project for.
** [[Ideas#New_PM_Controls|New PM Controls]]

* [[Community]] - Discussions about the netlabs.org community, website, and so on. Complain here :)

* [[The Warp Wishlist]]- The OS/2 Warp WishList is now available on wiki format.

* [[Netlabs bi weekly newsletter]] - ''New'' The latest netlabs.org news

* [[Netlabs News]] - Even later than above

* [[Warpstock Europe Websites]] - Discussion of a concept that aims to provide infrastructure and information to organizers, and information and services to users/visitors.

* [[UniAudio Development]] Universal Audio Driver Development Discussion

* [[WarpVision Development]] WarpVision media player development discussion

*[[Fundraising campaign]] - Projects that could be realized, support your favourite one!

*[[XWorkplace]] - XWorkplace Future Plans and Ideas

*[[DOSBox Port]] - DOSBox Port for OS/2-eCS Project

*[[Odin]] - ODIN Project todo and Ideas

*[[eSchemes]] - eComStation WPS-based look & feel system

*[[Mr2ice]] - MR/2 ICE is a full featured OS/2 native mail and news client.

*[[MMOS2 Related Projects]] - A list of MMO2 Related sofware developments.

== Shop == [[Image:Netlabs_watch.png|frame|netlabs watch]]
We do have a shop for shirts and more ... [http://shop.netlabs.org shop.netlabs.org]! Prices include a small extra to support netlabs.org's future...

== New Logo and Redesign ==
* [[Redesign]] - The new logo is choosen and a first and hopefully final draft for the new site layout has been created - check it out ;)

== Development ==

NOTE: This section should not be extended anymore. We reloaded the [http://www.edm2.com EDM/2 magazine] and we recommend to put all developer stuff in there. This wiki is a mess at the moment and we will clean that up one day and migrate the stuff that makes sense to EDM/2. Thanks!

This section contains hints and tricks and descriptions of undocumented
stuff. Undocumented means there's no official documentation or the
documentation (for example included on DevCon CDs) isn't available to
the public anymore. But DON'T JUST COPY any documentation you may have into the Wiki. Keep in mind it's copyrighted!

* [[Undocumented stuff]]
* [[Mozilla]] - some stuff regarding building Mozilla on OS/2
* [http://www.edm2.com/index.php/SDL SDL] - some tips & tricks about how to port applications using SDL to OS/2
* [http://www.edm2.com/index.php/How_to_program_for_the_WPS WPS] - how to program for the [http://en.wikipedia.org/wiki/Workplace_Shell WPS]. Note: the german Wikipedia may have more information about the WPS. Go [http://de.wikipedia.org/wiki/Workplace_Shell here].

==OS/2 and eCS resources==
===Drivers===
*Visit http://www.os2warp.be if you want to know if your hardware is supported.
*See a [http://www.ecomstation.it/pido2/home/mircomir/fixpak.php?lang=en driver list] generated from eCSoft/2 database.

===Software===
For software have a look here:

* http://hobbes.nmsu.edu
* http://en.ecomstation.ru/apecs.php
* http://www.ecomstation.it/ecsoft2/
* http://www.unixos2.org - ported *nix tools. A little bit cumbersome to find stuff there but nevertheless worth the effort

===Programs===
How to use specific programs, HowTos, FAQs etc.

MR/2 ICE [[mr2ice]] is a full featured OS/2 native mail and news client.

==netlabs.org Servers==
===ToDo's & History===
This is the list of tasks for netlabs.org Webservers and the history of what I (ktk) did
*[[netlabs.org]]

===Mail account===
Some information for those who own a mailbox at netlabs.org
*[[netlabs.org Mailing]]
===Admin Guide===
So far it's more or less just me who does all the work on netlabs.org webpages and this somewhat sucks because like this a lot of stuff depends on my lazyness. The following document explains the tasks necessary to create a new project at netlabs.org, including setting up CVS repositories, creating webpages and so on. I hope that I will find some volunteers one day who help me on doing that.
*[[Admin Guide]]

Main Page

2007-03-01T16:33:02Z

CHennecke: /* Roadmap */ Added Warpstock Europe Websites discussion

__NOTOC__

Welcome to the Wiki at netlabs.org. You will find a lot of interesting information about OS/2 and [http://www.ecomstation.com eCS] on this page. 
If you are interested in joining the '''community mailinglist''' please have a look [[Mailinglists | here]]!

'''QUICKNEWS''': We prevent registering new users from now on till we fixed the spamming-problems on the Wiki, sorry! If you want to have a user send an email to ktk [at] netlabs.org and we will do one. Will be fixed ASAP.

== Roadmap ==
Where are we now and where could we go. Open for discussions.

*[[Ideas]] - This is so far a random collection of ideas and stuff we have in our heads and which probably is worth creating a project for.
** [[Ideas#New_PM_Controls|New PM Controls]]

* [[Community]] - Discussions about the netlabs.org community, website, and so on. Complain here :)

* [[The Warp Wishlist]]- The OS/2 Warp WishList is now available on wiki format.

* [[Netlabs bi weekly newsletter]] - ''New'' The latest netlabs.org news

* [[Netlabs News]] - Even later than above

* [[Warpstock_Europe_Websites]] - Discussion of a concept that aims to provide infrastructure and information to organizers, and information and services to users/visitors.

* [[UniAudio_Development]] Universal Audio Driver Development Discussion

* [[WarpVision_Development]] WarpVision media player development discussion

*[[Fundraising campaign]] - Projects that could be realized, support your favourite one!

*[[XWorkplace]] - XWorkplace Future Plans and Ideas

*[[DOSBox Port]] - DOSBox Port for OS/2-eCS Project

*[[Odin]] - ODIN Project todo and Ideas

*[[eSchemes]] - eComStation WPS-based look & feel system

*[[Mr2ice]] - MR/2 ICE is a full featured OS/2 native mail and news client.

*[[MMOS2 Related Projects]] - A list of MMO2 Related sofware developments.

== Shop == [[Image:Netlabs_watch.png|frame|netlabs watch]]
We do have a shop for shirts and more ... [http://shop.netlabs.org shop.netlabs.org]! Prices include a small extra to support netlabs.org's future...

== New Logo and Redesign ==
* [[Redesign]] - The new logo is choosen and a first and hopefully final draft for the new site layout has been created - check it out ;)

== Development ==

NOTE: This section should not be extended anymore. We reloaded the [http://www.edm2.com EDM/2 magazine] and we recommend to put all developer stuff in there. This wiki is a mess at the moment and we will clean that up one day and migrate the stuff that makes sense to EDM/2. Thanks!

This section contains hints and tricks and descriptions of undocumented
stuff. Undocumented means there's no official documentation or the
documentation (for example included on DevCon CDs) isn't available to
the public anymore. But DON'T JUST COPY any documentation you may have into the Wiki. Keep in mind it's copyrighted!

* [[Undocumented stuff]]
* [[Mozilla]] - some stuff regarding building Mozilla on OS/2
* [http://www.edm2.com/index.php/SDL SDL] - some tips & tricks about how to port applications using SDL to OS/2
* [http://www.edm2.com/index.php/How_to_program_for_the_WPS WPS] - how to program for the [http://en.wikipedia.org/wiki/Workplace_Shell WPS]. Note: the german Wikipedia may have more information about the WPS. Go [http://de.wikipedia.org/wiki/Workplace_Shell here].

==OS/2 and eCS resources==
===Drivers===
*Visit http://www.os2warp.be if you want to know if your hardware is supported.
*See a [http://www.ecomstation.it/pido2/home/mircomir/fixpak.php?lang=en driver list] generated from eCSoft/2 database.

===Software===
For software have a look here:

* http://hobbes.nmsu.edu
* http://en.ecomstation.ru/apecs.php
* http://www.ecomstation.it/ecsoft2/
* http://www.unixos2.org - ported *nix tools. A little bit cumbersome to find stuff there but nevertheless worth the effort

===Programs===
How to use specific programs, HowTos, FAQs etc.

MR/2 ICE [[mr2ice]] is a full featured OS/2 native mail and news client.

==netlabs.org Servers==
===ToDo's & History===
This is the list of tasks for netlabs.org Webservers and the history of what I (ktk) did
*[[netlabs.org]]

===Mail account===
Some information for those who own a mailbox at netlabs.org
*[[netlabs.org Mailing]]
===Admin Guide===
So far it's more or less just me who does all the work on netlabs.org webpages and this somewhat sucks because like this a lot of stuff depends on my lazyness. The following document explains the tasks necessary to create a new project at netlabs.org, including setting up CVS repositories, creating webpages and so on. I hope that I will find some volunteers one day who help me on doing that.
*[[Admin Guide]]

Warpstock Europe Websites

2007-03-01T13:06:27Z

CHennecke: /* Target groups */ Corrected typos in exhibitor item

==Introduction==

This goal of this wiki page is to discuss a web site concept for Warpstock Europe and other OS/2 related events. This is for the visitors and organizers of such events--'''you.''' So your input is most welcome.

==Warpstock Europe homepage (www.warpstock.eu)==

The main page should focus on the fact that the entire world might hit it. So what we should show here is a brief description of what Warpstock Europe is about. Needless to say, the entire stuff should be kept informative but "neutral"--in the sense of "advocacy-free." Anything else could alienate potential visitors and exhibitors and create a "OS/2 lunatics" image.

===Target groups===

Next, let's see who will be most probably coming there and for what. First of all, let's focus on those parts of the website that are accessible to everyone (without a special login so to say).

* WSE visitors? Yes. They will either look at the previous events (transcripts, photo gallery, etc.) or look around to get information about the upcoming event(s). Maybe they'll be looking for contacts or a possibility to subscribe to a newsletter.

* WSE organizers and helping hands? Only partially. Those interested in helping out need some information on areas they can help, what they might get in return, and whom to contact. Once this phase is over, they've got their "internal" site. Except perhaps for checking out how this site looks after updating it.

* WSE Sponsors? Yes. We should include information on how to support a) the organisation itself and b) a specific (upcoming) event. Contacts and general information (e.g., required size of their logo, etc.) should be provided on a dedicated page.

* Speakers? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
*** requirements for presentations (guidelines for formatting and effects, file formats, '''deadlines''')
** for a specific event:
*** contacts
*** time tables
*** meals and accomodation
*** infrastructure (network, provided computers, audio)
*** presentation templates (for OO.org, LaTeX Beamer, S5)
*** etc.

* Exhibitors? Yes. Exhibitors are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being an exhibitor works
*** what being an exhibitor means
** for a specific event:
*** contacts
*** fees for commercial exhibitors? (Well, I guess we can forget that one.)
*** booth size
*** infrastructure (network, mains, tables)
*** Time-frame for mounting/unmounting
*** liability and insurance
*** meals and accomodation
*** etc.

* Press? Perhaps. That would be great. We should set up a press room with logos, pictures, fact sheets / summaries, and contacts.

* Newbies? Yes. This can either be WSE-newbies or even OS/2+eCS-newbies. Give a warm welcome and take the pain out of getting "an insider" or "member of the club."

* "Foreign" webmasters? Yes. They will look for information about how to provide links to events on their sites or who to syndicate with news feeds.

* Crawlers, robots, engines? Yes. We will need to keep an eye on search-engine-friendly link formatting and hiding sensitive data somehow. Also we should try to avoid automated submissions or subscriptions/signups in forums, etc.

===Features===

If that wasn't yet enough work to do, we actually are planning something '''great''' and '''new''' which means:

* the site will stay for years, even decades, maybe forever
* the site will be enlarged with every event taking place
* the site is the SPOC (single point of contact) for WSE, thus needs to be '''good'''
* did I mention that the site needs to look good?

Keeping that in mind, we need "modern" stuff: Easy to use and useful (and good-looking...):

* CMS supporting multiple languages
* forums for people to chat, discuss, and maybe create carpools
* newsletter and news RSS feeds (->subscriptions)
* downloads (screensaver, link logos, presentations, etc.)
* picture gallery
** pre-event: location
** post-event: pictures from event
* calendar, maybe downloadable as iCal
** other events
** presentations
* shop (registration, merchandising, sponsor units, etc.)
* FAQ
* maybe event / organisation "blogs," e.g., for visitors to describe their impressions/experiences
* of course a database behind most of the parts

Okay, that's it for the "public" site.

===Organizational features===

Next, we need a somehow "restricted" area for people involved in doing events. This needs to provide the following:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
** etc.
* various docs:
** How to organize an OS/2 event (assign team members to specific organizational areas, insurance, catering, etc.)
** cost calculation help
** PR templates
** exhibitor and speaker info templates
** visitor info templates
** how to invite people from eastern Europe
** etc.
* hardware stuff:
** Who has video projectors?
** Who provided WLAN APs last year?
** etc.
* per-event:
** who brings what
** what happens when and where
** etc.
* forums general/per event
* maybe a collaboration/groupware with
** calendars
** todos
** project manager (including status, gant charts) for activities
* event schedule manager
** every presentation should be held twice
** speakers can do more than one presentation, but they can't do that at the same time
** two presentations shouldn't be held at the same time twice
** maybe code from the old OS2.org Warpstock Europe administration backend could be recycled
* role-focused mailboxes (team-driven, independent from a individuals). Could be IMAP: This would help in getting to run a team-oriented mail stuff and to keep everything online in one place.

===Administrational features===

A considerable amount of the facts that comprise the information provided on the site will evolve over time. Thus the online information needs to be updated. The best way would be to provide a means for collaborative work: a wiki. This would significantly reduce the need to mail files back and forth.

==Portal for OS/2 related events (warpevents.eu)==

Now, so far all of the above deals with Warpstock Europe. But most of it also applies to other Warp events, be it Czech Warpstock, Developer Workshop, WarpWochenende, or even a local club.

While most of them already have a dedicated website or will set up something on their own for various reasons, why not have a single website for worldwide events that basically is a calendar. Here we can show all events that deal with OS/2 and eCS, regardless of size, scope, or subject. This should include reports regarding the status of work on the next events, at least in the pre-website phase (search for location, etc.). Imagine a site that shows the whole world that we're still alive with stuff happening almost weekly at different places around the globe.

We don't want to get in competition with OS/2 World.com or others--this site will focus on "events," not technology or software. Just take this webpage as a single spot to concentrate (info in one place) and distribute (link to other sites).

Also, the site needs to provide some of the information about event organization from the "internal" Warpstock Europe site:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
* various docs:
** How to organize an OS/2 event
** cost calculation help

Furthermore, it wouldn't hurt to offer reports from previous events.

Just an idea on the organisation and interaction/delegation between the sites. As you see, we're not too sure about how we can get a useable setup valid for us as well as for others. We'll rely on your support here.

==Warpstock Europe "Board"==

The official "club" or "board" behind WSE is a totally different topic and has nothing to do with the website being discussed here. At some point perhaps, the WSE "board" will be taking over the responsability of the warpstock.eu website, but that doesn't matter as of now and more importantly: We should not wait for the board to care about the site. It might take years to get a board (if ever). So let's get the site done for our own sake and let's see what wse".org" will become later.

==Hosting and CMS==

This will be done by Thomas Klein via a professional hoster (Domain Factory) (and maybe also paid for by him in the first year).

This will '''not''' be an own server! This means:
* less administration work
* no dealing with hardware and operating system
* hosting service can be shot in case of problems ;-)

It also means that the server will '''not''' run OS/2, but some Unix. ''We need to get the job done!'' Instead of fiddling around with hardware and software we can rely on proven solutions. This enables us to focus on the site and its content.

For the CMS we can see two alternatives:

* Typo3
* Joomla

Both are freely available, open sourced, and there are many extensions that can be used to add functionality.

For Typo3, this extension could be interesting: [http://typo3.org/extensions/repository/view/pt_conference/0.4.0/] It does not provide all we need yet, though.

If it turns out that we '''really''' need this, the internal site for organizers could use eGroupware. But this should only be a last resort as a consistent user-interface is desirable.

Warpstock Europe Websites

2007-02-28T22:26:34Z

CHennecke: /* Hosting */ Added CMS

==Introduction==

This goal of this wiki page is to discuss a web site concept for Warpstock Europe and other OS/2 related events. This is for the visitors and organizers of such events--'''you.''' So your input is most welcome.

==Warpstock Europe homepage (www.warpstock.eu)==

The main page should focus on the fact that the entire world might hit it. So what we should show here is a brief description of what Warpstock Europe is about. Needless to say, the entire stuff should be kept informative but "neutral"--in the sense of "advocacy-free." Anything else could alienate potential visitors and exhibitors and create a "OS/2 lunatics" image.

===Target groups===

Next, let's see who will be most probably coming there and for what. First of all, let's focus on those parts of the website that are accessible to everyone (without a special login so to say).

* WSE visitors? Yes. They will either look at the previous events (transcripts, photo gallery, etc.) or look around to get information about the upcoming event(s). Maybe they'll be looking for contacts or a possibility to subscribe to a newsletter.

* WSE organizers and helping hands? Only partially. Those interested in helping out need some information on areas they can help, what they might get in return, and whom to contact. Once this phase is over, they've got their "internal" site. Except perhaps for checking out how this site looks after updating it.

* WSE Sponsors? Yes. We should include information on how to support a) the organisation itself and b) a specific (upcoming) event. Contacts and general information (e.g., required size of their logo, etc.) should be provided on a dedicated page.

* Speakers? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
*** requirements for presentations (guidelines for formatting and effects, file formats, '''deadlines''')
** for a specific event:
*** contacts
*** time tables
*** meals and accomodation
*** infrastructure (network, provided computers, audio)
*** presentation templates (for OO.org, LaTeX Beamer, S5)
*** etc.

* Exhibitors? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
** for a specific event:
*** contacts
*** fees for commercial exhibitors? (Well, I guess we can forget that one.)
*** booth size
*** infrastructure (network, mains, tables)
*** Time-frame for mounting/unmounting
*** liability and insurance
*** meals and accomodation
*** etc.

* Press? Perhaps. That would be great. We should set up a press room with logos, pictures, fact sheets / summaries, and contacts.

* Newbies? Yes. This can either be WSE-newbies or even OS/2+eCS-newbies. Give a warm welcome and take the pain out of getting "an insider" or "member of the club."

* "Foreign" webmasters? Yes. They will look for information about how to provide links to events on their sites or who to syndicate with news feeds.

* Crawlers, robots, engines? Yes. We will need to keep an eye on search-engine-friendly link formatting and hiding sensitive data somehow. Also we should try to avoid automated submissions or subscriptions/signups in forums, etc.

===Features===

If that wasn't yet enough work to do, we actually are planning something '''great''' and '''new''' which means:

* the site will stay for years, even decades, maybe forever
* the site will be enlarged with every event taking place
* the site is the SPOC (single point of contact) for WSE, thus needs to be '''good'''
* did I mention that the site needs to look good?

Keeping that in mind, we need "modern" stuff: Easy to use and useful (and good-looking...):

* CMS supporting multiple languages
* forums for people to chat, discuss, and maybe create carpools
* newsletter and news RSS feeds (->subscriptions)
* downloads (screensaver, link logos, presentations, etc.)
* picture gallery
** pre-event: location
** post-event: pictures from event
* calendar, maybe downloadable as iCal
** other events
** presentations
* shop (registration, merchandising, sponsor units, etc.)
* FAQ
* maybe event / organisation "blogs," e.g., for visitors to describe their impressions/experiences
* of course a database behind most of the parts

Okay, that's it for the "public" site.

===Organizational features===

Next, we need a somehow "restricted" area for people involved in doing events. This needs to provide the following:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
** etc.
* various docs:
** How to organize an OS/2 event (assign team members to specific organizational areas, insurance, catering, etc.)
** cost calculation help
** PR templates
** exhibitor and speaker info templates
** visitor info templates
** how to invite people from eastern Europe
** etc.
* hardware stuff:
** Who has video projectors?
** Who provided WLAN APs last year?
** etc.
* per-event:
** who brings what
** what happens when and where
** etc.
* forums general/per event
* maybe a collaboration/groupware with
** calendars
** todos
** project manager (including status, gant charts) for activities
* event schedule manager
** every presentation should be held twice
** speakers can do more than one presentation, but they can't do that at the same time
** two presentations shouldn't be held at the same time twice
** maybe code from the old OS2.org Warpstock Europe administration backend could be recycled
* role-focused mailboxes (team-driven, independent from a individuals). Could be IMAP: This would help in getting to run a team-oriented mail stuff and to keep everything online in one place.

===Administrational features===

A considerable amount of the facts that comprise the information provided on the site will evolve over time. Thus the online information needs to be updated. The best way would be to provide a means for collaborative work: a wiki. This would significantly reduce the need to mail files back and forth.

==Portal for OS/2 related events (warpevents.eu)==

Now, so far all of the above deals with Warpstock Europe. But most of it also applies to other Warp events, be it Czech Warpstock, Developer Workshop, WarpWochenende, or even a local club.

While most of them already have a dedicated website or will set up something on their own for various reasons, why not have a single website for worldwide events that basically is a calendar. Here we can show all events that deal with OS/2 and eCS, regardless of size, scope, or subject. This should include reports regarding the status of work on the next events, at least in the pre-website phase (search for location, etc.). Imagine a site that shows the whole world that we're still alive with stuff happening almost weekly at different places around the globe.

We don't want to get in competition with OS/2 World.com or others--this site will focus on "events," not technology or software. Just take this webpage as a single spot to concentrate (info in one place) and distribute (link to other sites).

Also, the site needs to provide some of the information about event organization from the "internal" Warpstock Europe site:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
* various docs:
** How to organize an OS/2 event
** cost calculation help

Furthermore, it wouldn't hurt to offer reports from previous events.

Just an idea on the organisation and interaction/delegation between the sites. As you see, we're not too sure about how we can get a useable setup valid for us as well as for others. We'll rely on your support here.

==Warpstock Europe "Board"==

The official "club" or "board" behind WSE is a totally different topic and has nothing to do with the website being discussed here. At some point perhaps, the WSE "board" will be taking over the responsability of the warpstock.eu website, but that doesn't matter as of now and more importantly: We should not wait for the board to care about the site. It might take years to get a board (if ever). So let's get the site done for our own sake and let's see what wse".org" will become later.

==Hosting and CMS==

This will be done by Thomas Klein via a professional hoster (Domain Factory) (and maybe also paid for by him in the first year).

This will '''not''' be an own server! This means:
* less administration work
* no dealing with hardware and operating system
* hosting service can be shot in case of problems ;-)

It also means that the server will '''not''' run OS/2, but some Unix. ''We need to get the job done!'' Instead of fiddling around with hardware and software we can rely on proven solutions. This enables us to focus on the site and its content.

For the CMS we can see two alternatives:

* Typo3
* Joomla

Both are freely available, open sourced, and there are many extensions that can be used to add functionality.

For Typo3, this extension could be interesting: [http://typo3.org/extensions/repository/view/pt_conference/0.4.0/] It does not provide all we need yet, though.

If it turns out that we '''really''' need this, the internal site for organizers could use eGroupware. But this should only be a last resort as a consistent user-interface is desirable.

Warpstock Europe Websites

2007-02-28T22:09:00Z

CHennecke: Moved note about WSE board to own section

==Introduction==

This goal of this wiki page is to discuss a web site concept for Warpstock Europe and other OS/2 related events. This is for the visitors and organizers of such events--'''you.''' So your input is most welcome.

==Warpstock Europe homepage (www.warpstock.eu)==

The main page should focus on the fact that the entire world might hit it. So what we should show here is a brief description of what Warpstock Europe is about. Needless to say, the entire stuff should be kept informative but "neutral"--in the sense of "advocacy-free." Anything else could alienate potential visitors and exhibitors and create a "OS/2 lunatics" image.

===Target groups===

Next, let's see who will be most probably coming there and for what. First of all, let's focus on those parts of the website that are accessible to everyone (without a special login so to say).

* WSE visitors? Yes. They will either look at the previous events (transcripts, photo gallery, etc.) or look around to get information about the upcoming event(s). Maybe they'll be looking for contacts or a possibility to subscribe to a newsletter.

* WSE organizers and helping hands? Only partially. Those interested in helping out need some information on areas they can help, what they might get in return, and whom to contact. Once this phase is over, they've got their "internal" site. Except perhaps for checking out how this site looks after updating it.

* WSE Sponsors? Yes. We should include information on how to support a) the organisation itself and b) a specific (upcoming) event. Contacts and general information (e.g., required size of their logo, etc.) should be provided on a dedicated page.

* Speakers? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
*** requirements for presentations (guidelines for formatting and effects, file formats, '''deadlines''')
** for a specific event:
*** contacts
*** time tables
*** meals and accomodation
*** infrastructure (network, provided computers, audio)
*** presentation templates (for OO.org, LaTeX Beamer, S5)
*** etc.

* Exhibitors? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
** for a specific event:
*** contacts
*** fees for commercial exhibitors? (Well, I guess we can forget that one.)
*** booth size
*** infrastructure (network, mains, tables)
*** Time-frame for mounting/unmounting
*** liability and insurance
*** meals and accomodation
*** etc.

* Press? Perhaps. That would be great. We should set up a press room with logos, pictures, fact sheets / summaries, and contacts.

* Newbies? Yes. This can either be WSE-newbies or even OS/2+eCS-newbies. Give a warm welcome and take the pain out of getting "an insider" or "member of the club."

* "Foreign" webmasters? Yes. They will look for information about how to provide links to events on their sites or who to syndicate with news feeds.

* Crawlers, robots, engines? Yes. We will need to keep an eye on search-engine-friendly link formatting and hiding sensitive data somehow. Also we should try to avoid automated submissions or subscriptions/signups in forums, etc.

===Features===

If that wasn't yet enough work to do, we actually are planning something '''great''' and '''new''' which means:

* the site will stay for years, even decades, maybe forever
* the site will be enlarged with every event taking place
* the site is the SPOC (single point of contact) for WSE, thus needs to be '''good'''
* did I mention that the site needs to look good?

Keeping that in mind, we need "modern" stuff: Easy to use and useful (and good-looking...):

* CMS supporting multiple languages
* forums for people to chat, discuss, and maybe create carpools
* newsletter and news RSS feeds (->subscriptions)
* downloads (screensaver, link logos, presentations, etc.)
* picture gallery
** pre-event: location
** post-event: pictures from event
* calendar, maybe downloadable as iCal
** other events
** presentations
* shop (registration, merchandising, sponsor units, etc.)
* FAQ
* maybe event / organisation "blogs," e.g., for visitors to describe their impressions/experiences
* of course a database behind most of the parts

Okay, that's it for the "public" site.

===Organizational features===

Next, we need a somehow "restricted" area for people involved in doing events. This needs to provide the following:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
** etc.
* various docs:
** How to organize an OS/2 event (assign team members to specific organizational areas, insurance, catering, etc.)
** cost calculation help
** PR templates
** exhibitor and speaker info templates
** visitor info templates
** how to invite people from eastern Europe
** etc.
* hardware stuff:
** Who has video projectors?
** Who provided WLAN APs last year?
** etc.
* per-event:
** who brings what
** what happens when and where
** etc.
* forums general/per event
* maybe a collaboration/groupware with
** calendars
** todos
** project manager (including status, gant charts) for activities
* event schedule manager
** every presentation should be held twice
** speakers can do more than one presentation, but they can't do that at the same time
** two presentations shouldn't be held at the same time twice
** maybe code from the old OS2.org Warpstock Europe administration backend could be recycled
* role-focused mailboxes (team-driven, independent from a individuals). Could be IMAP: This would help in getting to run a team-oriented mail stuff and to keep everything online in one place.

===Administrational features===

A considerable amount of the facts that comprise the information provided on the site will evolve over time. Thus the online information needs to be updated. The best way would be to provide a means for collaborative work: a wiki. This would significantly reduce the need to mail files back and forth.

==Portal for OS/2 related events (warpevents.eu)==

Now, so far all of the above deals with Warpstock Europe. But most of it also applies to other Warp events, be it Czech Warpstock, Developer Workshop, WarpWochenende, or even a local club.

While most of them already have a dedicated website or will set up something on their own for various reasons, why not have a single website for worldwide events that basically is a calendar. Here we can show all events that deal with OS/2 and eCS, regardless of size, scope, or subject. This should include reports regarding the status of work on the next events, at least in the pre-website phase (search for location, etc.). Imagine a site that shows the whole world that we're still alive with stuff happening almost weekly at different places around the globe.

We don't want to get in competition with OS/2 World.com or others--this site will focus on "events," not technology or software. Just take this webpage as a single spot to concentrate (info in one place) and distribute (link to other sites).

Also, the site needs to provide some of the information about event organization from the "internal" Warpstock Europe site:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
* various docs:
** How to organize an OS/2 event
** cost calculation help

Furthermore, it wouldn't hurt to offer reports from previous events.

Just an idea on the organisation and interaction/delegation between the sites. As you see, we're not too sure about how we can get a useable setup valid for us as well as for others. We'll rely on your support here.

==Warpstock Europe "Board"==

The official "club" or "board" behind WSE is a totally different topic and has nothing to do with the website being discussed here. At some point perhaps, the WSE "board" will be taking over the responsability of the warpstock.eu website, but that doesn't matter as of now and more importantly: We should not wait for the board to care about the site. It might take years to get a board (if ever). So let's get the site done for our own sake and let's see what wse".org" will become later.

==Hosting==

This will be done by Thomas Klein via a professional hoster (Domain Factory) (and maybe also paid for by him in the first year).

This will '''not''' be an own server! This means:
* less administration work
* no dealing with hardware and operating system
* hosting service can be shot in case of problems ;-)

It also means that the server will '''not''' run OS/2, but some Unix. ''We need to get the job done!'' Instead of fiddling around with hardware and software we can rely on proven solutions. This enables us to focus on the site and its content.

Warpstock Europe Websites

2007-02-28T22:04:01Z

CHennecke: Initial page

==Introduction==

This goal of this wiki page is to discuss a web site concept for Warpstock Europe and other OS/2 related events. This is for the visitors and organizers of such events--'''you.''' So your input is most welcome.

==Warpstock Europe homepage (www.warpstock.eu)==

The main page should focus on the fact that the entire world might hit it. So what we should show here is a brief description of what Warpstock Europe is about. Needless to say, the entire stuff should be kept informative but "neutral"--in the sense of "advocacy-free." Anything else could alienate potential visitors and exhibitors and create a "OS/2 lunatics" image.

===Target groups===

Next, let's see who will be most probably coming there and for what. First of all, let's focus on those parts of the website that are accessible to everyone (without a special login so to say).

* WSE visitors? Yes. They will either look at the previous events (transcripts, photo gallery, etc.) or look around to get information about the upcoming event(s). Maybe they'll be looking for contacts or a possibility to subscribe to a newsletter.

* WSE organizers and helping hands? Only partially. Those interested in helping out need some information on areas they can help, what they might get in return, and whom to contact. Once this phase is over, they've got their "internal" site. Except perhaps for checking out how this site looks after updating it.

* WSE Sponsors? Yes. We should include information on how to support a) the organisation itself and b) a specific (upcoming) event. Contacts and general information (e.g., required size of their logo, etc.) should be provided on a dedicated page.

* Speakers? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
*** requirements for presentations (guidelines for formatting and effects, file formats, '''deadlines''')
** for a specific event:
*** contacts
*** time tables
*** meals and accomodation
*** infrastructure (network, provided computers, audio)
*** presentation templates (for OO.org, LaTeX Beamer, S5)
*** etc.

* Exhibitors? Yes. Speakers are visitors as well, true, but we ''must'' cuddle them by having dedicated pages, with information
** in general:
*** describing how being a speaker works
*** what being a speaker means
** for a specific event:
*** contacts
*** fees for commercial exhibitors? (Well, I guess we can forget that one.)
*** booth size
*** infrastructure (network, mains, tables)
*** Time-frame for mounting/unmounting
*** liability and insurance
*** meals and accomodation
*** etc.

* Press? Perhaps. That would be great. We should set up a press room with logos, pictures, fact sheets / summaries, and contacts.

* Newbies? Yes. This can either be WSE-newbies or even OS/2+eCS-newbies. Give a warm welcome and take the pain out of getting "an insider" or "member of the club."

* "Foreign" webmasters? Yes. They will look for information about how to provide links to events on their sites or who to syndicate with news feeds.

* Crawlers, robots, engines? Yes. We will need to keep an eye on search-engine-friendly link formatting and hiding sensitive data somehow. Also we should try to avoid automated submissions or subscriptions/signups in forums, etc.

===Features===

If that wasn't yet enough work to do, we actually are planning something '''great''' and '''new''' which means:

* the site will stay for years, even decades, maybe forever
* the site will be enlarged with every event taking place
* the site is the SPOC (single point of contact) for WSE, thus needs to be '''good'''
* did I mention that the site needs to look good?

Keeping that in mind, we need "modern" stuff: Easy to use and useful (and good-looking...):

* CMS supporting multiple languages
* forums for people to chat, discuss, and maybe create carpools
* newsletter and news RSS feeds (->subscriptions)
* downloads (screensaver, link logos, presentations, etc.)
* picture gallery
** pre-event: location
** post-event: pictures from event
* calendar, maybe downloadable as iCal
** other events
** presentations
* shop (registration, merchandising, sponsor units, etc.)
* FAQ
* maybe event / organisation "blogs," e.g., for visitors to describe their impressions/experiences
* of course a database behind most of the parts

Okay, that's it for the "public" site.

===Organizational features===

Next, we need a somehow "restricted" area for people involved in doing events. This needs to provide the following:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
** etc.
* various docs:
** How to organize an OS/2 event (assign team members to specific organizational areas, insurance, catering, etc.)
** cost calculation help
** PR templates
** exhibitor and speaker info templates
** visitor info templates
** how to invite people from eastern Europe
** etc.
* hardware stuff:
** Who has video projectors?
** Who provided WLAN APs last year?
** etc.
* per-event:
** who brings what
** what happens when and where
** etc.
* forums general/per event
* maybe a collaboration/groupware with
** calendars
** todos
** project manager (including status, gant charts) for activities
* event schedule manager
** every presentation should be held twice
** speakers can do more than one presentation, but they can't do that at the same time
** two presentations shouldn't be held at the same time twice
** maybe code from the old OS2.org Warpstock Europe administration backend could be recycled
* role-focused mailboxes (team-driven, independent from a individuals). Could be IMAP: This would help in getting to run a team-oriented mail stuff and to keep everything online in one place.

===Administrational features===

A considerable amount of the facts that comprise the information provided on the site will evolve over time. Thus the online information needs to be updated. The best way would be to provide a means for collaborative work: a wiki. This would significantly reduce the need to mail files back and forth.

==Portal for OS/2 related events (warpevents.eu)==

Now, so far all of the above deals with Warpstock Europe. But most of it also applies to other Warp events, be it Czech Warpstock, Developer Workshop, WarpWochenende, or even a local club.

While most of them already have a dedicated website or will set up something on their own for various reasons, why not have a single website for worldwide events that basically is a calendar. Here we can show all events that deal with OS/2 and eCS, regardless of size, scope, or subject. This should include reports regarding the status of work on the next events, at least in the pre-website phase (search for location, etc.). Imagine a site that shows the whole world that we're still alive with stuff happening almost weekly at different places around the globe.

We don't want to get in competition with OS/2 World.com or others--this site will focus on "events," not technology or software. Just take this webpage as a single spot to concentrate (info in one place) and distribute (link to other sites).

Also, the site needs to provide some of the information about event organization from the "internal" Warpstock Europe site:

* contact lists:
** event hosting facilities
** knowledge stakeholders
** previously involved people
* various docs:
** How to organize an OS/2 event
** cost calculation help

Furthermore, it wouldn't hurt to offer reports from previous events.

Just an idea on the organisation and interaction/delegation between the sites. As you see, we're not too sure about how we can get a useable setup valid for us as well as for others. We'll rely on your support here.

Note: The official "club" or "board" behind WSE is a totally different topic and has nothing to do with the website being discussed here. At some point perhaps, the WSE "board" will be taking over the responsability of the warpstock.eu website, but that doesn't matter as of now and more importantly: We should not wait for the board to care about the site. It might take years to
get a board (if ever). So let's get the site done for our own sake and let's see what wse".org" will become later.

==Hosting==

This will be done by Thomas Klein via a professional hoster (Domain Factory) (and maybe also paid for by him in the first year).

This will '''not''' be an own server! This means:
* less administration work
* no dealing with hardware and operating system
* hosting service can be shot in case of problems ;-)

It also means that the server will '''not''' run OS/2, but some Unix. ''We need to get the job done!'' Instead of fiddling around with hardware and software we can rely on proven solutions. This enables us to focus on the site and its content.

WarpVision Development

2007-02-26T11:51:15Z

CHennecke: /* How to improve development */ added code checkout instructions

This document is used to collect ideas what must be changed to start again with WarpVision development. This is by no means a complete document, so please help to finish it!

=== How to improve development ===
* Create a standard test environment including potentially problematic video and audio files
** files that don't play at all or crash WarpVision
** files that need a long time to be scanned
** files that exhibit video/audio sync problems
* Create a document that describes in '''full detail what''' a tester has to do and '''how'''
** There are various ways that WarpVision outputs usefull information, they have to be listed and explained
* Record user and tester reports in an "experience database" so the developer(s) can relate changes to effects more easily--also at later points for previous versions
* We need clear milestones
* Have a test plan for '''every''' major release
** This can only work if we have a number of testers for WarpVision
* Standardize the build environment with the help of Christian Langanke
* Make it easier for testers and users to find appropriate versions
** Follow a strict version numbering scheme
** Record changes, preferably in "non-developer speak"
* Update the user documentation (INF file)

==== Suggestions for Milestones ====
* Finish the playlist including:
** reordering items in the playlist via drag and drop
** removing selected items from the playlist by hitting the delete key
** enable menu items of the playlist pop-up menu to be applied to several selected files (last, first, ...)
* Implement DVD menus/subtitles
* Fix the broken audio-playback in current SVN code.
* Clean up the settings notebook which is currently too large and obfuscated
** Move unrelated items to "subpages" or new tabs
*** Move "Show time info" and "Enable history" to Interface page 1 called "Interface"
*** Move subtitle and OSD settings to new Interface page 3 called "Display"
*** Rename Interface page 2 "Aspect ratio" to "Screen"
*** Move "Desktop color" from "System" tab to Interface page 3
*** Move "CD preread time" from "Other" group on "System" tab to "DVD/VCD" tab
*** "DVD/VCD" tab could be renamed to "Media"
* Include instructions on how to checkout the freaking code! This should be also mentioned on the TRAC page

=== How to raise money ===
* from the os2world.com thread
** Collect up front $5000 to $6000 by $20 per subscription for 1 year. This means 200 to 300 people must subscribe to this project. Make 5 milestones. Subscribers vote as to whether the milestone has been reached and the programmer is paid $1000 per milestone.

UniAudio Development

2007-02-22T14:28:57Z

CHennecke: /* How to raise money */ Added SSI/Mensys

This document is used to collect ideas about what has to change to start with UniAudio development again. This is by no means a complete document, so please help to finish it!

=== How to improve development ===
* Always try to make the audio hardware available to the developer or have a tester you can trust
** Usually, it does not cost that much to purchase a sound card
*** Especially compared to the actual money that was spend on the developer!
** If the card is not onboard, we should try to make it available to the developer
** If not, we have to find a tester that helps the developer
** If there is no tester, and the developer has no hardware, than we should not work on that
* Create a document that describes in '''full detail what''' a tester has to do and '''how'''
** There are various ways in which UniAudio outputs usefull information, those have to be listed and explained
* Record user and tester reports in an "experience database" so the developer(s) can relate changes to effects more easily--also at later points for previous versions
* We need clear milestones
* Have a test plan for '''every''' major release
** This can only work if we have a number of testers for UniAudio
** It would be nice to have a list of "tested" vs. "untested" hardware, not just a list of what should work
*** It would be beneficial to have a database where the hardware can be listed and a set of tests defined, this would help take care of the plan for testing as well as the list of "tested" vs. "untested" hardware. Then the testers can mark the tests they have performed (I have never tried to record on this machine for instance and don't have a mic but could sign off on other tests).
* Standardize the build environment with the help of Christian Langanke
* Make it easier for testers and users to find appropriate versions
** Follow a strict version numbering scheme
** Record changes, preferably in "non-developer speak"
* Document the Uniaud API so other developers can put it to use
* have more then one developer on the project (less dependency, multiple eyes on the same problems, fall back, knowledge exchange)

=== Suggestions for Milestones ===
* building a new release from the current svn repository
* closing all old bugreports (no-one knows the status of the old bugs)
* applying ALSA patches to be in sync
* test HDA support
* test APM support (including APM in ACPI)
* create an easy to use PM mixer, maybe based on LBMix
* create an up-to-date list of supported chips

=== How to raise money ===
* from the os2world.com thread
** Collect up front $5000 to $6000 by $20 per subscription for 1 year. This means 200 to 300 people must subscribe to this project. Make 5 milestones. Subscribers vote as to whether the milestone has been reached and the programmer is paid $1000 per milestone.
 
* A Subscription based model
** Before all this can start, netlabs.org proposes a small number of milestones for the project and finds a developer that would be interested to work on the project (the latter would be nice, but is not a must)
** People are paying up front a subscription for one year, say $15
*** This is required to have access to the voting procedure and all other privileges for sponsors
** In addition, they can (but don't have to!) vote for milestones with $1 per vote or they can create a new milestone for $1
*** The amount of money must be small enough, to not having to argue with users if the milestone is not fulfilled!
*** It must clearly be stated that voting for a milestone does NOT guarantee that this milestone will be reached in a given time!
*** After all, it may be that developers find out later that the feature cannot be implemented or something the like
**** And then I really don't want to get into the situation of having to pay back amounts of $1 to a couple of users!
*** However, proposing a new milestone also means they have to describe it in more than 1 sentence!!!
** This will create a list of milestones, ordered by importance for the users
** The total money that is collected will then be distributed over the milestones, weighted by the priority
*** this needs some more thinking :-)
** Sponsors get
*** access to release binaries (and the source together with build instructions)
*** access to test binaries (and the source together with build instructions)
*** access to beta version binaries (and the source together with build instructions)
*** access to a support forum to post questions and bug reports
**** we would have to find out how to verify the subscription for the forum (without adding too much work!)
*** a way to ask for hardware support - via creating a new milestone
*** a way to steer development (now I am getting abstract :-) ) - again via purchasing a milestone ?!
** Normal users get
*** access to release binaries (and the source together with build instructions)
*** access to a page where they can learn what they will have access to when they pay ;-)
* Get SSI/Mensys involved. After all, this audio driver is an essential component of future eComStation releases. You cannot sell an OS that doesn't have basic sound support. Basic sound means: stereo play and record, a GUI mixer. Multichannel 3D stuff is not required.

UniAudio Development

2007-02-19T19:51:07Z

CHennecke: /* Suggestions for Milestones */ fixed typos, added mixer

Main Page

2007-02-16T14:50:58Z

CHennecke: added WarpVision development discussion item

__NOTOC__

Welcome to the Wiki at netlabs.org. You will find a lot of interesting information about OS/2 and [http://www.ecomstation.com eCS] on this page. 
If you are interested in joining the '''community mailinglist''' please have a look [[Mailinglists | here]]!

'''QUICKNEWS''': We prevent registering new users from now on till we fixed the spamming-problems on the Wiki, sorry! If you want to have a user send an email to ktk [at] netlabs.org and we will do one. Will be fixed ASAP.

== Roadmap ==
Where are we now and where could we go. Open for discussions.

*[[Ideas]] - This is so far a random collection of ideas and stuff we have in our heads and which probably is worth creating a project for.
** [[Ideas#New_PM_Controls|New PM Controls]]

* [[Community]] - Discussions about the netlabs.org community, website, and so on. Complain here :)

* [[The Warp Wishlist]]- The OS/2 Warp WishList is now available on wiki format.

* [[Netlabs bi weekly newsletter]] - ''New'' The latest netlabs.org news

* [[Netlabs News]] - Even latest than above

* [[UniAudio_Development]] Universal Audio Driver Development Discussion

* [[WarpVision_Development]] WarpVision media player development discussion

*[[Fundraising campaign]] - Projects that could be realized, support your favourite one!

*[[XWorkplace]] - XWorkplace Future Plans and Ideas

*[[DOSBox Port]] - DOSBox Port for OS/2-eCS Project

*[[Odin]] - ODIN Project todo and Ideas

*[[eSchemes]] - eComStation WPS-based look & feel system

*[[Mr2ice]] - MR/2 ICE is a full featured OS/2 native mail and news client.

*[[MMOS2 Related Projects]] - A list of MMO2 Related sofware developments.

== Shop == [[Image:Netlabs_watch.png|frame|netlabs watch]]
We do have a shop for shirts and more ... [http://shop.netlabs.org shop.netlabs.org]! Prices include a small extra to support netlabs.org's future...

== New Logo and Redesign ==
* [[Redesign]] - The new logo is choosen and a first and hopefully final draft for the new site layout has been created - check it out ;)

== Development ==

NOTE: This section should not be extended anymore. We reloaded the [http://www.edm2.com EDM/2 magazine] and we recommend to put all developer stuff in there. This wiki is a mess at the moment and we will clean that up one day and migrate the stuff that makes sense to EDM/2. Thanks!

This section contains hints and tricks and descriptions of undocumented
stuff. Undocumented means there's no official documentation or the
documentation (for example included on DevCon CDs) isn't available to
the public anymore. But DON'T JUST COPY any documentation you may have into the Wiki. Keep in mind it's copyrighted!

* [[Undocumented stuff]]
* [[Mozilla]] - some stuff regarding building Mozilla on OS/2
* [http://www.edm2.com/index.php/SDL SDL] - some tips & tricks about how to port applications using SDL to OS/2
* [http://www.edm2.com/index.php/How_to_program_for_the_WPS WPS] - how to program for the [http://en.wikipedia.org/wiki/Workplace_Shell WPS]. Note: the german Wikipedia may have more information about the WPS. Go [http://de.wikipedia.org/wiki/Workplace_Shell here].

==OS/2 and eCS resources==
===Drivers===
*Visit http://www.os2warp.be if you want to know if your hardware is supported.
*See a [http://www.ecomstation.it/pido2/home/mircomir/fixpak.php?lang=en driver list] generated from eCSoft/2 database.

===Software===
For software have a look here:

* http://hobbes.nmsu.edu
* http://en.ecomstation.ru/apecs.php
* http://www.ecomstation.it/ecsoft2/
* http://www.unixos2.org - ported *nix tools. A little bit cumbersome to find stuff there but nevertheless worth the effort

===Programs===
How to use specific programs, HowTos, FAQs etc.

MR/2 ICE [[mr2ice]] is a full featured OS/2 native mail and news client.

==netlabs.org Servers==
===ToDo's & History===
This is the list of tasks for netlabs.org Webservers and the history of what I (ktk) did
*[[netlabs.org]]

===Mail account===
Some information for those who own a mailbox at netlabs.org
*[[netlabs.org Mailing]]
===Admin Guide===
So far it's more or less just me who does all the work on netlabs.org webpages and this somewhat sucks because like this a lot of stuff depends on my lazyness. The following document explains the tasks necessary to create a new project at netlabs.org, including setting up CVS repositories, creating webpages and so on. I hope that I will find some volunteers one day who help me on doing that.
*[[Admin Guide]]

WarpVision Development

2007-02-16T14:49:10Z

CHennecke: changed ordered list items to unordered

This document is used to collect ideas what must be changed to start again with UniAudio development. This is by no means a complete document, so please help to finish it!

=== How to improve development ===
* Create a standard test environment including potentially problematic video and audio files
** files that don't play at all or crash WarpVision
** files that need a long time to be scanned
** files that exhibit video/audio sync problems
* Create a document that describes in '''full detail what''' a tester has to do and '''how'''
** There are various ways that WarpVision outputs usefull information, they have to be listed and explained
* Record user and tester reports in an "experience database" so the developer(s) can relate changes to effects more easily--also at later points for previous versions
* We need clear milestones
* Have a test plan for '''every''' major release
** This can only work if we have a number of testers for WarpVision
* Standardize the build environment with the help of Christian Langanke
* Make it easier for testers and users to find appropriate versions
** Follow a strict version numbering scheme
** Record changes, preferably in "non-developer speak"
* Update the user documentation (INF file)

==== Suggestions for Milestones ====
* Finish the playlist including:
** reordering items in the playlist via drag and drop
** removing selected items from the playlist by hitting the delete key
** enable menu items of the playlist pop-up menu to be applied to several selected files (last, first, ...)
* Implement DVD menus/subtitles
* Fix the broken audio-playback in current SVN code.
* Clean up the settings notebook which is currently too large and obfuscated
** Move unrelated items to "subpages" or new tabs
*** Move "Show time info" and "Enable history" to Interface page 1 called "Interface"
*** Move subtitle and OSD settings to new Interface page 3 called "Display"
*** Rename Interface page 2 "Aspect ratio" to "Screen"
*** Move "Desktop color" from "System" tab to Interface page 3
*** Move "CD preread time" from "Other" group on "System" tab to "DVD/VCD" tab
*** "DVD/VCD" tab could be renamed to "Media"

=== How to raise money ===
* still empty

WarpVision Development

2007-02-16T14:48:13Z

CHennecke: created Wiki entry

This document is used to collect ideas what must be changed to start again with UniAudio development. This is by no means a complete document, so please help to finish it!

=== How to improve development ===
* Create a standard test environment including potentially problematic video and audio files
** files that don't play at all or crash WarpVision
** files that need a long time to be scanned
** files that exhibit video/audio sync problems
* Create a document that describes in '''full detail what''' a tester has to do and '''how'''
** There are various ways that WarpVision outputs usefull information, they have to be listed and explained
* Record user and tester reports in an "experience database" so the developer(s) can relate changes to effects more easily--also at later points for previous versions
* We need clear milestones
* Have a test plan for '''every''' major release
** This can only work if we have a number of testers for WarpVision
* Standardize the build environment with the help of Christian Langanke
* Make it easier for testers and users to find appropriate versions
** Follow a strict version numbering scheme
** Record changes, preferably in "non-developer speak"
* Update the user documentation (INF file)

==== Suggestions for Milestones ====
# Finish the playlist including:
** reordering items in the playlist via drag and drop
** removing selected items from the playlist by hitting the delete key
** enable menu items of the playlist pop-up menu to be applied to several selected files (last, first, ...)
# Implement DVD menus/subtitles
# Fix the broken audio-playback in current SVN code.
# Clean up the settings notebook which is currently too large and obfuscated
** Move unrelated items to "subpages" or new tabs
*** Move "Show time info" and "Enable history" to Interface page 1 called "Interface"
*** Move subtitle and OSD settings to new Interface page 3 called "Display"
*** Rename Interface page 2 "Aspect ratio" to "Screen"
*** Move "Desktop color" from "System" tab to Interface page 3
*** Move "CD preread time" from "Other" group on "System" tab to "DVD/VCD" tab
*** "DVD/VCD" tab could be renamed to "Media"

=== How to raise money ===
* still empty

UniAudio Development

2007-02-16T14:25:08Z

CHennecke: added appropriate versions stuff

This document is used to collect ideas what must be changed to start again with UniAudio development. This is by no means a complete document, so please help to finish it!

=== How to improve development ===
* Always try to make the audio hardware available to the developer or have a tester you can trust
** Usually, it does not cost that much to purchase a sound card
*** Especially compared to the actual money that was spend on the developer!
** If the card is not onboard, we should try to make it available to the developer
** If not, we have to find a tester that helps the developer
** If there is no tester, and the developer has no hardware, than it we should not work on that
* Create a document that describes in '''full detail what''' a tester has to do and '''how'''
** There are various ways that UniAudio outputs usefull information, they have to be listed and explained
* Record user and tester reports in an "experience database" so the developer(s) can relate changes to effects more easily--also at later points for previous versions
* We need clear milestones
* Have a test plan for '''every''' major release
** This can only work if we have a number of testers for UniAudio
** It would be nice to have a list of "tested" vs. "untested" hardware, nut just a list of what should work
* Standardize the build environment with the help of Christian Langanke
* Make it easier for testers and users to find appropriate versions
** Follow a strict version numbering scheme
** Record changes, preferably in "non-developer speak"
* Document the Uniaud API so other developers can put it to use

=== How to raise money ===
* still empty

UniAudio Development

2007-02-16T14:20:13Z

CHennecke: added experience database and Uniaud API suggestions

This document is used to collect ideas what must be changed to start again with UniAudio development. This is by no means a complete document, so please help to finish it!

=== How to improve development ===
* Always try to make the audio hardware available to the developer or have a tester you can trust
** Usually, it does not cost that much to purchase a sound card
*** Especially compared to the actual money that was spend on the developer!
** If the card is not onboard, we should try to make it available to the developer
** If not, we have to find a tester that helps the developer
** If there is no tester, and the developer has no hardware, than it we should not work on that
* Create a document that describes in '''full detail what''' a tester has to do and '''how'''
** There are various ways that UniAudio outputs usefull information, they have to be listed and explained
* Record user and tester reports in an "experience database" so the developer(s) can relate changes to effects more easily--also at later points for previous versions
* We need clear milestones
* Have a test plan for '''every''' major release
** This can only work if we have a number of testers for UniAudio
** It would be nice to have a list of "tested" vs. "untested" hardware, nut just a list of what should work
* Standardize the build environment with the help of Christian Langanke
* Document the Uniaud API so other developers can put it to use

=== How to raise money ===
* still empty