Hi, I don't have a strong opinion on this. I get used to the current system and find it pretty usable. It's just one branch: gh-pages to deal with the documentation.
That said, if others want to manage the documentation directly into the master, I have nothing against it. Thanks. Best regards, Jérôme LELEU Founder of CAS in the cloud: www.casinthecloud.com | Twitter: @leleuj Chairman of CAS: www.jasig.org/cas | Creator of pac4j: www.pac4j.org 2014-12-10 18:16 GMT+01:00 Misagh Moayyed <mmoay...@unicon.net>: > Team, > > In the past, we have been making out-of-band mods to the CAS > documentation. This is painful and unnecessary [1]. I would like to spend a > bit of time to come up with a process that would have our working docs in > the same branch inside the repository and have the travis build > automatically push them out to the appropriate place under gh-pages. This > allows pull requests to contain mods to the docs in one changeset rather > than going back and forth between branches. Since it would be all > automated, there is no extra work required of the contributor, other than > making sure the docs are updated as well :) > > > > Make sense? > > > > So my approach would be to introduce a pom-based cas-server-documentation > module and modify our travis scripts to copy over the changes to the > relevant directory just like we are doing that today with javadocs, etc. > > > > Misagh > > > > [1] Pulling down gh-pages on slower connections is not exactly a pleasant > experience, even if you have sparse checkouts turned on. > > -- > You are currently subscribed to cas-dev@lists.jasig.org as: lel...@gmail.com > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev > > -- You are currently subscribed to cas-dev@lists.jasig.org as: arch...@mail-archive.com To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
