Good questions Darren. Perhaps we could interest our education folks in doing an online tutorial on the ARC process with at least a cursory fly over of some of the more common best practices.
We've resourced and financed similar efforts in the past for other knowledge that it was deemed important to work into the corporate DNA. An example is the Sun Sigma course. It would only be effective if it was similarly measured and mandated throughout the engineering organization with each manager having visibility to the completion percentage in his organization and a "complete by" date. Of course we should make it so that external folks have access to the same content. - mark Darren Reed wrote: > As part of the discussion around Service Tags on Wednesday, > it was obvious that the ARC community needs to do something > to try and ensure that project teams are better prepared when > coming to PSARC. This requires more/better communication > from PSARC out to those whom it serves (the development > community that delivers code into ON.) > > Today we have a growing list of questions that embodies > some of the architectural issues that projects need to be > aware of and while this document serves the ARC well by > telling us about various aspects of the project, it doesn't > give the project team any information about what is considered > to be "good architecture." > > But it's not like there hasn't been any work in this area. > The SAC has a collection of Best Practices documents that > can be found at: > > http://sac.eng/BestPractices/ > > and on opensolaris.org at: > > http://www.opensolaris.org/os/community/arc/ > > (The presentation of all the documents via the menu on the left > is not the best interface I've seen for delivery documents via > the web.) > > (btw, we need to add the "Firewall Friendliness" to these..) > > Looking at the documents there, my first comment is that if > more projects read through these documents then we'd have > fewer questions to answer in PSARC. For example, almost > every project that delivers a new SMF service gets asked > about a rights profile and if you read through the SMF BP, > it mentions RBAC profiles. So the question that comes to > mind is how do we get more projects reading the BPs that > we have published as/before they start their project and > build into it a design that takes all of this BP work into > consideration? > > Or maybe the solution isn't that hard... > > In order to see better delivery of projects to PSARC, do we > simply need to transform the BP documents into HOW-TOs? > > Darren > > _______________________________________________ > opensolaris-arc mailing list > opensolaris-arc at opensolaris.org >
