-1 from my side also. > More globally, I'm wondering : what will happen when we will move (in a > couple of years) to nextbigscmtool.com ? Exactly.
Sure, we need to rework the CASUM. Also, I think we should modify the left hand menu on http://www.jasig.org/cas to point people directly to the documentation. Many people asked my where the documentation can be found, as it is not obvious that you need to click on "Community", then you need to know that the "Wiki" link also holds the CAS Server documentation (it only states that it is the repository for the CAS protocol and clients, not the CASUM). I recommend to add a menu link "Documentation" to the http://www.jasig.org/cas menu so people easily find the related wiki startpage https://wiki.jasig.org/display/CAS/Home Best regards, Robert Am 12.06.2013 um 10:59 schrieb jleleu <[email protected]>: > Hi, > > -1 to move the issue trackers to github. I find JIRA to be a very good tool > for that. > > Regarding documentation, I'm not so enthousiastic to move everything to > github. It would be easier to handle pull requests for documentation's > improvments though, but I'm not sure that it's such an important feature to > have. > > We already have a lot of documentation on the wiki and Confluence is a good > tool. Maybe we can just reorganize the whole documentation and add the > appropiate links on github pointing to the Confluence's wiki pages. > > +1 to create a migration guide from 3.x to 4.0. > > More globally, I'm wondering : what will happen when we will move (in a > couple of years) to nextbigscmtool.com ? -- 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
