On Feb 1, 2007, at 11:25 PM, Stephen Hahn wrote:
* Scott Tracy <[EMAIL PROTECTED]> [2007-02-01 22:07]:
So, let's talk through this so I can understand. How would you work
on a design doc with the community? Walk through the normal SDF
process on something you want to develop from start to finish in the
open.
I don't think it's necessary to walk through the entirety of the
software development framework (SDF) to answer your question. I
think
that what's emerging (for me) from this discussion is that there
is a
desire for a OpenSolaris project proposal to follow some amount of
discussion in related community groups (via forum, or via IRC
maybe).
That is, the speculative phase of a project--between one pager
(internal announcement) and first design review--should take
part, at
least in part, in a sponsoring community group first. Once it
becomes
clear that the initial idea has garnered some interest (or bemused
tolerance), then a project proposal to -discuss is easily justified.
The point on the SDF or any software project is that at some point to
continue you need repositories to house information and establish a
permanent contact point with the community. I was trying to
understand how joint design documents would be housed and other
relevant information as an open project developed. And I don't
understand the point of rejecting a project just because source is
not immediately available.
The particular project here has a luxury of community groups to
choose
from: appliances, storage, and databases. If none of these
community
groups is responsive, that's useful feedback to the OGB, since
active
community groups are the backbone of the current draft constitution.
It does, no doubt. The community will react accordingly.
/Scott
_______________________________________________
opensolaris-discuss mailing list
[email protected]
