On 1/31/12 4:45 AM, Andrew Petro wrote:
Jason,
GitHub works for me, and I think will work well in general as a place to make
this source code publicly available and collaborate-upon-able.
While the Jasig CAS website presents a new BSD license as the current CAS
server license (because it is the current CAS server license), that's not the
preferred or default Jasig license anymore.
Rather, Apache 2.0 is preferred over (new) BSD for its better clarity of
protections for contributors and adopters.
See https://wiki.jasig.org/display/LIC/Jasig+Licensing+Policy
Incidentally, coming into compliance with this Jasig licensing policy is on the
roadmap for the CAS 3.5 release, and, I believe, a blocker for that release.
The very best way you can make it legally possible for Jasig to redistribute
your work incorporated into Jasig software products is to submit Contributor
License Agreements.
Jonathan and myself (programmers on the project) are emailing our
contributor forms today and we are also submitting the corporate level form.
After lots of discussion with our legal representative we discovered
that we are able to drop the SBIR data rights notice. I'm hoping to have
our code up on github by the time I go home today.
It's taken us a while internally to get to this state and I apologize
for what probably seems like slow progress. By the way, we're also
contacting the django-cas and the mod_auth_cas developers as we modified
those projects to support attribute release. We have some text for the
jasig newsletter too.
I'll let you know when the code is available on github.
Thank you!
Jason
--
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
