Christophe,
>"No getting started" documents for the newbies.
The "getting started" documentation is actually this mailing list. Lurking
on it with ears and eyes wide is how I got started. It not only introduces
you to the functionality and usability of the project, but also the
personalities, methodologies and the design. This mailing list is also
archived so is readily accessed. This is a major differance between OSS and
Commercial as commercial doesnt give this insight into the application, so
they abstract that loss of interaction by introducing you to their product
with a "getting started" document.
Not saying that a "getting started" document is a bad thing, they are always
useful, but I have gleaned more of turbines inner workings from the main
contributers here discussing and commenting as well as helping other users
and developers. There is much to be learned and gleaned from the collective
knowledge on display here.
>2. 'Customer/site' references. I'm trying to convince the European
>Concilum to build an enterprise portal based on the ASF.
In the projects we recieve we get a list of requirements and build a system
to satisfy those requirements. The choice of technologies is ours. If you
are the technical expert in the project, I would be throwing your weight
around. Not for any reasons of evangalism but for purely pragmatic reasons
:)
We currently have two systems in development based on Turbine, though
neither is deployed yet, one for AT&T the other for MDOT. I expect the AT&T
system to be out the door by the new year.
Cameron Riley
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
