[trimming out much of the cc list]
On Wed, 12 Dec 2007, Stephen Hahn wrote:
> We ("the SCM royal we") would gratefully take review and test help
> from anyone with time.
I would offer to help, and I think that Masa Murayama might be interested,
as I have been encouraging him to use Mercurial. I'm trying to approach
this in the sense that we have a community developer, whom will need to
maintain his code and will be using Mercurial as the SCM of course.
While I realize we're not where we need to be, today, we do have the
ability to clone with Mercurial and this allows the bits to flow external
to the community. From that aspect, Masa has been pulling the sources with
Mercurial in the work to put his driver back, he might be able to offer
you feedback and/or input as well.
Maybe we could twist one of the pubs folks, like either Alta Elstad or
Michelle Olson (both of whom have been very helpful to our community), to
start documenting some of this process. Does that sound useful at this
point? Having streaming media that explains such process would be helpful
as well, might be able to scheme something in that area...
What are you wanting to review and test?
The other interesting piece semi-related to this is that in the case of
Masa, he has used gcc for much of his development, and as of recent he's
started to use Studio. It would be good if we had more documentation on
approaching open source development, from the external communities in the
sense that others will most likely be familiar with gnu tools, but not as
familiar with using the studio tools.
Ironically, I have worked with Studio for quite a time while Masa was
using gcc, and we didn't have any glaring problem, I just think it's
better for all developers to be using the same tools.;-)
--
Alan DuBoff - Solaris x86 IHV/OEM Group
