On Sun, Jun 03, 2007 at 10:28:23AM -0700, John Sonnenschein wrote:
> 
> This is more or less a caricature of how Linux & NetBSD /actually/  
> work, but I just mean to outline the two development philosophies.
> 
> And yeah, it's not set in stone, but I think it does need some  
> discussion as to how we're to approach development initially

Of course there is no need to set anything in stone, but let's think
about what best works here for us and at least try to stick to it as
closely as possible.

I'm mostly a lurker here, as I don't currently have any hardware that
will run Solaris/PPC (I have tons of SPARC gear however, but that doesn't
help here *G*).  I am *extremely* interested in seeing this project a
success, because don't get me wrong, OSX is a neat OS, but as far as
I'm concerned, it's a desktop OS.  It doesn't have nearly the polish
and maturity of Solaris as a server OS.  Keep in mind I made it through
the SunOS 4.x to SunOS 5.x migration, so I may be a bit biased on how
I feel about Solaris. ;)

That completely useless bit of trivia aside, from what I've seen in lurking
here, there seems to be a fairly small number of active people on this
list as far as actual work getting done is concerned.  I think that is
going to be our greatest asset.  There is no reason we have to pick one
methodology over another, why not pick the best of both worlds?

I think a "commit first wins" policy helps promote getting work done, and
yes, we do all want to avoid duplicated effort, especially considering the
size of this particular development "team"; however, that means it is also
very simple for someone to announce what it is they intend on working on
and for us to mostly keep track of it.

Might I suggest a combination of the two?  Let's get a website somewhere
(I'd be more than happy to contribute to coding skills for that) somewhere
that tracks what people plan on doing.  "Commit first wins" still applies,
but make sure you see what everyone else is trying to accomplish and before
blindly plowing into a project, see if maybe you can't help someone else
who's already started, or who at least has the interest.

This is a team effort, so let's act like a team.  ;)

Just my minimal number of local currency.

-brian
-- 
"Perl can be fast and elegant as much as J2EE can be fast and elegant.
In the hands of a skilled artisan, it can and does happen; it's just
that most of the shit out there is built by people who'd be better
suited to making sure that my burger is cooked thoroughly."  -- Jonathan 
Patschke

Reply via email to