Sorry for the delay in responding. I can't answer about FOSS projects, but I can explain where we are with an open development infrastructure.
On 12/ 3/08 05:12 PM, Mark Martin wrote: > I'd like to bring 2 items forward for discussion that I have been > pondering on for some time. > > Firstly, it'd be nice to see a timeline for when particular tools may be > delivered that would make it easier for external contributors to > contribute. Ignoring the fact that there seems to be more priority > given for allowing community package managers to contribute to the IPS > repositories than for allowing existing contributors to contribute, I'd > like to know what to expect regarding the following projects and/or tools: > OpenRTI > defects.OSo vs. bugs.OSo Last year, we thought we could easily move the ON gate outside once it transitioned to Mercurial, but the reality proved more complicated because that move is tied to multiple internal tools, processes and data sets that can't just be moved outside in their entirety. One example of that is OpenRTI, which is on hold for the moment. Porting the internal tool and making it access d.o.o was the easy part. The harder parts involve re-architecting processes to use two RTI tools and distinguish between people with CAs vs Sun IDs. The complexities have caused us to re-group in the area of open development infrastructure to focus on making collaboration and participation easier until we can get the ON gate, in particular, outside the firewall. Work areas include: - Tools/Hg work: Follow-up work to the initial tools integration that was part of the ON transition to Mercurial and continuing work with Sun teams on their transition to the use of Mercurial. - bugs.opensolaris.org: We are taking ownership of this application and will then be working to enhance it to address some of the problems community members currently have as they try to participate in conversations about and work on bugs in the Bugster database. - defect.opensolaris.org: My team will most likely be taking ownership of this to turn it in to a production system. Currently, we're trying to clarify the boundaries between this system and Bugster which is groundwork for specifying a valid use of d.o.o for tracking bugs destined for integration into the onnv-gate. - Contributions: Another item on the list is to look at the sponsor program to find ways to make it work better. One idea is to investigate the possibility of some kind of an ON patch submission process, possibly run as a project. Because things have changed, it's become clear that extending the 'SCM Migration Project' to include all of this won't work well, so we will be creating an 'open development' project this quarter. We are also working on a new program roadmap to publish information about what's going on in the areas being worked by people on my team. We are hoping to get that up on the site this month. Thanks. Bonnie > ARC tools (including case listing sliming, open/external access to > submit, inspect, manage cases, up-to-date schedule and case information, > et al) > > In general, I am of a mind that this is something that the OGB should be > concerned with -- are communities or projects reporting what they're > doing, or at least communicating scedules? I'm sure in many cases they > exist, they're just not being reported publicly. Yes, I'm aware many > dates would be fictional and I accept I may be the only one that cares > about this (although I suspect not). I have, up till now, been assuming > that lowering the bar for long tail contribution is such a low priority > that there have been no resources allocated and thus no time short of > infinity, but I'd like to know for sure that this is the case. > > Secondly, FOSS projects continue to come out of the far corners of Sun, > ARC, and integrate. I have asked a for the list of what projects are > being ported and with what priority, but this apparently doesn't need to > be an openly disclosed bit of information. Should it be? Am I the only > one that cares? Sun staffs its work as it wants, but it'd be nice to > know what to expect with regard to project priorities for the rest of us > external contributors. > > Thanks, > Mark > > > > > _______________________________________________ > ogb-discuss mailing list > [email protected] > http://mail.opensolaris.org/mailman/listinfo/ogb-discuss _______________________________________________ website-discuss mailing list [email protected]
