+1 on github all together. I'd even vote for moving the CI builds over to Github, using something like Travis CI, etc. Managing and keeping track of all these various systems is pretty time consuming.
> -----Original Message----- > From: William G. Thompson, Jr. [mailto:[email protected]] > Sent: Tuesday, June 11, 2013 12:48 PM > To: [email protected] > Subject: Re: [cas-dev] Yet Another Documentation Effort > > +1. Thoughts on moving issues to github as well? > > > On Tue, Jun 11, 2013 at 2:33 PM, Marvin S. Addison <[email protected]> > wrote: > > https://github.com/Jasig/cas/wiki > > > > We absolutely must have a 3.x - 4.x upgrade guide, and I figure I'll > > lead the effort to write it (tapping others as needed, of course, for > > specific > > areas.) The existing CASUM space is so disorganized and stale that I'm > > inclined to simply rewrite essential documentation in the same push > > along the lines of the skeleton referenced above. > > > > I would like to leverage the GitHub wiki since we've already got so > > many folks going there for source, issues, and pull requests; > > consequently it's fairly natural to make it our documentation hub. > > Additionally, it meets the requirement of a controlled location for > > official documentation written and curated by committers or otherwise > blessed contributors (i.e. signed ICLA). > > > > Thoughts? I'm happy to take recommendations for organization and > "essential" > > content. > > > > 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 -- 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
