...
- the possibility of being able to introduce new functionality to 2.7 should be explicitly stated
- Staffing of release team - anthony and pete identified, and then somebody unknown. some clarification of their responsibilities. explicitly calling for one or two more people.
- a 2.8 branch manager should be identified early
- pragmatism ... people willing to be branch manager depends on deployment schedules, 2.7 schedule may be in jeopardy if there are no schools willing to adopt it. Whether or not one deploys can be influenced by feature set, and so 2.7 may introduce risks here.
- brings up the old question of release philosophy: time-based v. feature-based, etc.
- uncomfortable with suggestion of PC's role in targeting particular releases, shouldn't set hard boundaries
- is there a pragmatic benefit to southern hemisphere sites? UCT in particular: would favor independent project releases instead. A forums release would be more useful than a full 2.7 as currently described.What are good prospects for projects ready to work with us, and targeting
Prospects for 2.x
...
projects:
- Chuck with LTI, Kirk Alexander with Gradebook2, Assignments2 at IU, Nuno with SiteStats, perhaps others
- LTI a good first prospect in some ways, but won't present a thorough workout of the process because it's fairly narrow. Still, may present some issues that would be good to work through (such as cross-institutional support).
- Whatever we start with, wouldn't want it to be something that might tend toward rejection
- It's not really rejection, it's more a process of identifying what more is needed, and helping people to get there. It's valuable to raise these questions in a solvable form. Spur to doing work in incubation
- Would be good to review code in light of our ability to support it; eg LTI touches on portal - who's working on that, who can, and what would that mean for maintenance expectations?
- Would something like LTI allow us to fast-forward the development stages in a collapsed timeframe?
- Need to get projects to self-document, with standardized documentation to show that it's gone through the steps.
- Wouldn't want to have to say "Do these steps," then check them off, then come back with more steps and keep ratcheting things up ... want to lay things out clearly ahead of time
- Whether or not there's a maintenance team ... might influence these decisions [aside: Anthony's working on a proposal for this]
...