ArchStudio Meeting: July 11, 2008
Meeting to discuss and decide on policies for ArchStudio development going forward.
Logistics
- Location:
- ICS2-136 on the UCI Campus
- Time:
- 11AM-5PM (scheduled); 11AM-4PM (actual)
- Notes:
- Thanks to Dick Taylor for lunch!
- Attendees:
Outcomes
- A set of new (proto-)policies for ArchStudio development documented on the ArchStudio wiki root page
Agenda
Eric Dashofy posted a list of questions. Kari Nies collected and summarized the responses. The questions were:
- Should we establish uniform standards for ArchStudio?
- What should they be?
- How do we enforce them?
- Here, I mean "standards" broadly:
- Coding standards
- Documentation standards
- Interface standards
- Code interfaces
- User Interfaces
- Branding and Marketing
- Standards for release
- etc.
- Who will participate in ArchStudio development, and what are their roles? What does the ArchStudio "org chart" look like? Is there one?
- What are the mechanisms to resolve disputes?
- What is the process or criteria by which we decide what new features to pursue or implement?
- How do we decide how to respond to external requests? How do we decide which ones to pursue and which ones to de-prioritize? Who is responsible for working on these requests? What are their responsibilities?
- How do we reconcile academic goals (investigate problems, write papers) with the development of a long-lived software environment?
- How do we maintain continuity for the product over time and across personnel changes? What kind of continuity should we maintain? How do we decide what to maintain in the long term and what to not maintain?
