...
- Open Planning - Gather requirements and use an open process to advance the uPortal framework
- Sharing the load - enable collaboration, resource sharing and expertise transfer for planning and implementing requirements
- Preventing Limiting local forks - ease contributing local modifications/enhancements into the base uPortal framework
- Harness the community - Involve large & small institutions, vendors, and individuals
Deliverables
Vision
| Insert excerpt |
|---|
...
|
...
|
...
Requirements
| Insert excerpt |
|---|
...
|
...
...
|
...
|
Development Roadmaps
Development plans are expressed in 6 month roadmaps solidified at the semi-annual developer meetings detailing:
- planned features and scope for the next 6 months
- task assignments & resource requests
- longer term development goals
Initial Milestones & Status
...
Target Dates | Task | Status |
|---|---|---|
Feb 06 | Start with seed of core institutions and players | in progress completed |
March 06 | Seed library with lists | completed |
Spring Dev Meeting | Follow up at uP developers meeting
| completed |
May 06 | Put out for community review before JA-SIG conference
| completed |
Summer uPortal Conference | Solicit contributions and feedback at JA-SIG 2006 Summer Conference
|
|
July 06 | incorporate conference contributions and feedback
|
|
Fall Dev Meeting | use to build roadmap at Fall developers meeting | completed |
Winter JA-SIG Conference | Update requirements library and gather information on community priorities and needs/requests |
|
...
The Framework Coordinator gathers our vision and requirements for a portal framework to build a strategy for the future. He is also responsible for leading the translation of our strategy into a development roadmap and coordinating follow up and action items between development meetings and conferences.
- Point of contact for collaboration, filters (or delegates) suggestions and comments
- Coordinate activity (email lists, schedule conference calls, follow up on action items/deliverables)
- Key player in the roadmap planning process, especially pre-developer meeting groundwork
- Work with branch leads to incorporate roadmap items into specific release schedules
- Moderate discussions, maintain agendas, track progress
- Reports regularly to the JA-SIG Board on the state of uPortal development
Currently in this role: Jason Jason
Release Engineer
- Incorporate road map items into branch-specific release schedules consistent with the Release Strategy
- Coordinate development efforts related to implementing features/changes within a particular development line
Currently in this role: Andrew Petro on the uPortal 2 stream; Eric Dalquist on the uPortal 3 stream
Core Developers
Informal group of experts and leaders. Possible responsibilies responsibilities include:
- coordinate/maintain requirements and plans for a specific functional area
- contribute expertise, advice, and code
- represent significant stakeholders.
Documentation Coordinator
| Insert excerpt | ||||||
|---|---|---|---|---|---|---|
|
uPortal Manual Coordinator
- Point of contact for collaboration and updates to the uPortal Manual
- Reports regularly to the Documentation Coordinator on the state of uPortal Manual efforts
Community Contributors
Community members expressing their wants and needs for a portal framework
- Outline vision, requirements, and use cases
- Provide resources (developer time, money, expertise)