If you are joining remotely via telephone, Adobe Connect, or Skype, please use a headset-microphone, or at least earphones. Please use the mute feature when you are not speaking.
Interactive meeting - Adobe Connect
We routinely share a screen during the call. You can view the screen via our Adobe Connect meeting room at http://connect.iu.edu/omrsdf. For large meetings, the room has the ability to broadcast audio and connect to a telephone-based system as well, as controlled by the meeting hosts.
More effectively giving people fair warning of upcoming features
For example, we created a mailing list long ago to target module authors to notify them of upcoming changes. This could be a Talk forum and/or creating a distribution list via modulus (published modules)
Improve accuracy of Road Map page to reflect where efforts/resources will be directed
Indicate what is *really* scheduled work (currently, things listed under the next Platform and Refapp releases), versus what's really just a backlog (currently, things on the Refapp 2.6+ and Someday sections)
Better reflect reality (e.g., currently largely driven by what organizations are prioritizing, with a nudge towards community-priority tickets)
Improve documentation and design of wish list (someday) features
How should the platform road map be prioritized?
Have guidelines that let developers & implementations know how things get prioritized
We should be more honest, and make sure people actually know that mostly things are *not* prioritized in any intentional way
Clarify how legacy versions are supported
Help describe how anyone in the community can backport a feature to an earlier version (including what is or what is not appropriate for backporting)
Explicit product architecture team (mix of developers/BAs/PMs/SMEs/Product owners) driving the vision
Responsible for balancing all inputs and defining the priorities
Generates the priority-ranked backlog of tasks/projects to reach the vision
Not responsible for driving day-to-day development
Invest in defining/describing projects/features
Share these (e.g., via wiki or Talk), allowing volunteers (individuals or orgs) to take them on
Consider having feature-driven releases (i.e., release manager's job is to get feature X into a release)
Separate Platform and Reference Application technical road maps