-1 to move the issue trackers to github. I find JIRA to be a very
good tool for that.
I'm pretty sure I agree with you on that point, at least for the time being.
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.
I suppose it's a personal matter, but I find dealing with disorganized
content overwhelming. It's simply easier for me to start over than to
curate the entire body of CASUM documentation, deciding what to keep and
what to discard. In the interest of time and effort I'm obliged to start
over.
More globally, I'm wondering : what will happen when we will move (in
a couple of years) to nextbigscmtool.com ?
Good point. What's really compelling about the GitHub wiki is that the
documentation is itself a Git repository:
[email protected]:Jasig/cas.wiki.git
That makes it trivial to pack up the documentation markdown and move it
somewhere else, or migrate it to a documentation module maintained with
the source. This approach gives us some fairly decent WYSIWYG editor
tools as well as the flexibility to edit in plan text using whatever
tools you want; and the icing is that we can easily pack up and move in
the future. I'm sold and I hope this at least partially allays your
concerns about portability.
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
