Although by comparison, I'm relatively unfamiliar with the project's code base and issues around CAS code branching, I too am concerned that the focus of a roadmap remains on a long-term vision and its adherent functionality.
A roadmap should first inform those interested as to where a project is being steered. A clear statement of long-term goals is articulated at https://wiki.jasig.org/display/~wgthom/CAS+Roadmap# - "CAS4 aims to simplify federation and attribute exchange in the same-fashion that CAS1 and CAS2 simplified single sign on authentication. From an architectural standpoint, CAS will be redesigned to support emerging use cases and developing standards including OpenId, OAuth, SAML, and others. In addition, recognizing SSO and authentication's significance as part of the overall infrastructure of an organization, CAS4 will be designed to be more easily administered, monitored, audited, etc." There seems to be consensus in this discussion - evolve CAS toward the CAS4 vision ensuring along the way release numbering reflect the relative impact of code and configuration changes. Trying to rigidly stick to specific deliverables within specific release numbers does seem impractical in a community-based project, but shared expectation seems to be these would be altered as practicalities around developer resources arise and as proposals are reviewed for fit. Although there are multiple paths to a goal, a roadmap has more meaning when it attempts to define a step-wise path. This also helps inform new contributors and consumers regarding specific efforts the project has adopted in order to advance toward longer goals. Currently, if a preliminary path openly exists ( https://wiki.jasig.org/pages/viewpage.action?pageId=28574039) with resources committed to working through the path items in a particular order, it should be possible for additional items either from the roadmap just posted or wishlist items tackled by alternate developers to be assimilated with these lists (absent the pro forma release numberings). Brian On Fri, Sep 2, 2011 at 10:33 AM, Marvin Addison <[email protected]>wrote: > > I'm trying to steer away from top-down planning towards a more > > practical near-term bottom-up approach consistent with a Jasig style > > of development. > > This comment could be considered inflammatory because it suggests that > the project may presently suffer from top-down management, or that it > has in the past. Both Scott's roadmap and all development to date > have happened with community collaboration and in open venues where > anyone may review, comment, and participate. This seems to me > perfectly consistent with the "Jasig way," so I'm unclear on the basis > of your comment. > > I appreciate the practicality of the approach you've taken, however, > where roadmap items are accepted based on available developer > resources to accomplish them. That said, as far as I'm aware Scott > and I had agreed implicitly to work on all the items on > https://wiki.jasig.org/pages/viewpage.action?pageId=28574039. > > > Individual developers interested in committing to work should fill it out > > and bring discussion about intent and approach to the cas-dev list. > > I'm happy to approach the roadmap in this fashion, but let's not lose > the vision of the roadmap I cited above. I plan to move over items > from that roadmap that I will explicitly commit to working on in a > manner that is consistent with our current version numbering scheme. > I think we're in agreement that the version numbers matter much less > than the features within, so take the numbering with a grain of salt. > > Looks like I can't edit > https://wiki.jasig.org/display/~wgthom/CAS+Roadmap<https://wiki.jasig.org/display/%7Ewgthom/CAS+Roadmap>. > Is that > intentional, or am I missing something? > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
