Brian Gupta wrote:
> Well, Indiana is intended to be a product - an OpenSolaris
distribution with a
> regular release schedule.
>
>
So, I'd expect to see some documents from you that describe this
product. Have you a 1-pager that describes the basics?
Project Description
Risks and Assumptions
Business Summary
Problem Area
Market/Requester
Business Justification
Competitive Analysis
Opportunity Window/Exposure
How will you know when you are done?
Technical Description
Details
Bug/RFE Number(s)
In Scope
Out of Scope
Doc Impact
Admin/Config impact
HA Impact
I18N/L10N impact
Packaging & Delivery
Security Impact
Dependencies
Resources & Schedule
Prototype Availability
Following review and approval of the 1-pager, I would expect to see a
Requirements Document that describes all the features/functionality that
we will include in the product, so we can agree on expectations and
begin work. What is the deadline for producing drafts of these two basic
documents for Indiana?
Ok, I think I see where the vision is going to hit a wall. There is
definitely a process disconnect between agile development and Solaris
development.
I'm not an engineer, so conversations about the details of development
processes are a bit over my head. However, I remember well the early
conversations I had with engineers who were coming into the Pilot
Program three years ago. They loved that we were opening the code and
building a community, but the majority of them also said that we ought
to make sure we don't dump our development processes and design
principles: http://opensolaris.org/os/community/on/os_dev_process/
Jim
--
Jim Grisanzio, Sr. Program Manager, OpenSolaris Engineering
http://blogs.sun.com/jimgris
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss@opensolaris.org
