Hi Caroline,

Sorry for my silence (other project activities have taken over my life
at the moment).  I would like to see this.  As someone who commits
less that others and whose brain seems to flush information all to
readily, having the documented processes to refer to would be very



On 10 Jul, 14:23, cem <[EMAIL PROTECTED]> wrote:
> On Jun 14, 4:58 pm, Caroline Maynard <[EMAIL PROTECTED]> wrote:
> > [EMAIL PROTECTED] wrote:
> > > Caroline, would
> > > you be prepared to commit what you think the various important things
> > > to get right are to a page up on the web site a osoa.org? If you don't
> > > have time to do this I could extract thoughts from the email archive
> > > and document but would be good to get a brain dump.
> > What we're talking about here is not really release process but
> > development process. I'm certainly not intending to stand up for big
> > cumbersome processes. To my mind, prompt management of Tuscany defects
> > according to >their< rules is a basic courtesy to the Tuscany developers
> > who are kind enough to to help us, that's all.
> > OTOH, this test-driven development thing was my personal response to the
> > confused state that I alone had let the bug tracker get into, which took
> > me a few days to disentangle. I would really like the team to stick with
> > it even now that Matthew is working on SDO as well as SCA, because I do
> > believe that a smaller amount of work earlier will save us more time
> > later, and reduce the number of unwanted side-effects that we see.
> > Documenting how the project is run is a big undertaking. I think it
> > would be a Good Thing, and to be authoritative, one that all the
> > projects leads would need to take part in. It just so happens that I
> > have on my desk right now a copy of Karl Fogel(my hero)'s book Producing
> > Open Source Software, and he points to the Hacker's Guide to Subversion
> > (http://svn.collab.net/repos/svn/trunk/www/hacking.html) as a good
> > example of project guidelines (well he would say that, wouldn't he?).
> > Would you like me to create a wiki page with the subheadings defined in
> > that document? If everyone likes that idea, then I promise to contribute
> > some stuff under some of the subheadings. (For more, see
> >http://producingoss.com/en/written-rules.html-I love that man).
> I had a positive response from Simon on this, but between us we only
> represent half of the current committers :-(
> I think I would be wasting my time starting a project charter unless
> there is more buy-in - I would just be <insert vulgar expression here/>. Not 
> sure how to interpret silence, but indifference will kill it as
> effectively as hostility.

You received this message because you are subscribed to the Google Groups 
"phpsoa" group.
To post to this group, send email to phpsoa@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 

Reply via email to