http://wiki.osafoundation.org/bin/view/Journal/EngineeringWikiArea
I took a whack at putting Alec and Bear's stuff into a Structure for
the Engineering portion of the Wiki. I also created a shell for
Platform/Services Group, Scooby, Cosmo and QA.
Bear, I tried to shuffle the Build/Release stuff around user
activities. But I'm just doing it without really understanding what
I'm moving around, so please feel free to re-shuffle accordingly.
Am I right to assume that:
1. Most end-users/design contributors coming to the wiki will be
interested in the OSAF Eco-system? How Chandler/Scooby/Cosmo work
together?
2. Most developers coming to the project will be interested in
Developer Documentation organized by Project: Chandler, Scooby, Cosmo.
Mimi
On Apr 10, 2006, at 12:43 PM, Mike Taylor wrote:
On Apr 10, 2006, at 2:07 PM, Ted Leung wrote:
Also, we are looking for some help in fleshing out parts of the
taxonomy. On pages 3 and 4 of Mimi's document, there are spaces
which are broken down by team and project. We could really use
some input from QA, Build/Release, and some folks in engineering
on what should go in those spaces.
Builds (Chandler, Scooby, Cosmo, OSAF Server (aka snarf), Tools)
Platform Notes -- Info on differences between Windows, OS X, Linux
Detailed steps -- build recipes for each platform
Web pages -- Continuous Builds, Tinderbox, Bonsai, LXR, Source
Tools -- Subversion, Cygwin, ???
Release
Release checklist
QA links -- pre/post release testing
links to past releases
---
Bear
Build and Release Engineer
Open Source Applications Foundation (OSAF)
[EMAIL PROTECTED]
http://www.osafoundation.org
[EMAIL PROTECTED]
http://code-bear.com
PGP Fingerprint = 9996 719F 973D B11B E111 D770 9331 E822 40B3 CD29
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
Open Source Applications Foundation "General" mailing list
http://lists.osafoundation.org/mailman/listinfo/general
