max at bruningsystems.com wrote:
> Hi,
> Torrey McMahon wrote:
>> Joseph Kowalski wrote:
>>
>>> Torrey McMahon wrote:
>>>
>>>> Nicolas Williams wrote:
>>>>
>>>> Why we still do architecture review, or discussions, over email is
>>>> beyond me. Email is horrible tool for such things. Con-calls are a
>>>> close second.
>>>>
>>> So, if these are bad, what is good? Only meetings (which are pretty
>>> much con-calls at this time)? Wikis? (What is the plural of
>>> "Wiki"?)
>>
>> I wouldn't say bad. I'd assert we could do much better.
>>
>> ---
>>
>> A project team wants to get an architecture review. They go to the
>> request website, fill in a forms, and the automated back end starts
>> the review process. They get a case number, spot on a twiki/website,
>> and notification goes out to people interested in such things. They
>> automatically get a case owner from the pool of ARC members. Owner
>> gets an email, contact info, etc. and starts mentoring the team as
>> needed.
>>
>> Over time the project team starts adding materials to the project
>> including a automagically cross-referenced set of interfaces. Each
>> interface is properly marked with its stability level - The nice
>> popup box explains what each is - and it gets added to the project
>> location. All the associated questionnaires are provided and answers
>> put into the backend database. ARC cases that preceded this one are
>> cross referenced and added to the "Prior Cases" section.
>>
>> If an ARC member is interested in a specific change to an interface
>> they can click it and get more information including
>> Change history
>> Code attached to the interface (Yes, I know this isn't code review.)
>> X levels of interfaces that are used, upstream or downstream, by
>> the interface in question
>>
>> If an ARC member has a question on a specific part of the case they
>> can add the question, mark the relevant materials, and await an
>> answer via email/rss/text. Previously asked questions, and any
>> answers, are automatically added to the case materials to avoid
>> people from asking the same questions ten times.
>>
>>
>>
> So, this is all Sun process, or OpenSolaris process? What is a
> "project team"? Are there "project teams"
> that are not all Sun? Or do I simply need to go back through
> arc-discuss to find out, in which case... sorry I asked.
> max
>
A "project team" is the group of people working on getting a project
integrated. It can be either Sun, or non-Sun people.
-- Garrett
