Garrett D'Amore wrote:
Now that Sun has made official moves to de-support certain hardware (and
to be fair this is not new ... for example some people have wanted
UltraSPARC 1 support for a while now, but now it will be expanded to all
SPARC workstations other than U25 and U45), it seems like it might be a
good idea if we had a "community supported hardware" group and perhaps a
dedicated code base.
...
7) Obviously this would require a new Community Group inside OpenSolaris
* three core contributors needed (need to identify two more besides me)
* mailing lists and webpages on opensolaris.org
* code hosted in mercurial on hg.opensolaris.org
* possibly separate defects.os.o category? not sure.
I'm willing to start the process on this - including setting up an
initial consolidation -- if there is enough other community interest. I
need at least two other folks who are willing to act as CC's though. My
first nominations on this would be Juergen Keil, Rainer Orth, Steve
Stallion, and Jason King. Of course, I've not really verified any of
this with them yet; I'm happy to take other suggestions or volunteers.
Note that I'm also willing to volunteer as the initial gatekeeper on
this, performing builds, etc.
So, I really think this should be an ON Community Group-sponsored
project instead of a new community group.
This is the sort of project that needs to stay in sync with whatever the
ON community is doing so they can be aware of big gate or process
changes, and so that they can work together.
On a somewhat related note, in what seems like a lifetime ago, an idea
was puttered around about having a "kernel janitor"-like project for
OpenSolaris that would help new contributors and existing contributors
to ON.
In the sense that there would be a project where members would actively
review ON contributions from community members (with SCAs) and guide
them through the RTI process.
While that doesn't directly fit what you have here, I think that there's
a lot of overlap in the needs of that project and what you've proposed.
In particular, due to the relatively low volume of external ON
contributions that are currently seen, I suspect that if we see an
increase in them, there's a good chance it will come from what has been
proposed here.
So while I'm not trying to add extra to this or co-opt anyone into being
responsible for something else, I would really like to see the scope
expanded a bit here to encourage some natural growth.
Given the likely synergy between community contributions received for ON
and what this project is doing, it would seem logical to me to expand
the scope of this proposal to be a bit more generic in purpose.
I'm not offended if you think this is way out of scope :)
Cheers,
--
Shawn Walker
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
