search

UWMadisonUcomm / uw-ui-toolkit

A web front-end toolkit based on Bootstrap for designing and developing modern, mobile-first websites for the University of Wisconsin-Madison
Apache License 2.0
16 stars 15 forks source link

Consider publishing to "Public" Maven repository instead #50

Closed nblair closed 9 years ago

nblair commented 10 years ago

The current Maven pom publishes the releases to an artifact repository named "UW Releases", which not only requires authentication, but specific authorization. By default most developers do not have access to any artifacts published in UW Releases; they must be granted specific fine-grained access.

Since this module is out in the public space, Shared Tools' Maven Artifact Repository offers another repository called "Public". Modules published in this space require no authentication/authorization; anyone that can access the repository can download the artifacts (restrictions are in place who can publish).

Switching to these repository comes with a caveat: licensing. Artifacts in this space have to include correct license information; this is described here:

https://wiki.doit.wisc.edu/confluence/display/ST/Configure+a+Project+for+the+Shared+Tools+Maven+Repository

and:

https://wiki.doit.wisc.edu/confluence/display/ST/License+and+Notice+Requirements

This would mean a license header (short form) would be attached to the JS/CSS assets in the deliverable, and we would need a proper NOTICE file for any assets not developed by us.

Should we consider going down this road? I can implement what is required, it would mean however that the assets would (automatically) get a license header attached.

WIP: https://github.com/nblair/uw-ui-toolkit/tree/publish-to-public-repository

nblair commented 10 years ago

Licensing actually may be a little more complex; since .css and .js seem to be not UW constructed items, but a combination of other resources (bootstrap, normalize, etc). Perhaps we don't need to actually attach a license to these files (since there are license comments from the original dependencies). We may not need to do anything other than include the license plugin, and exclude all resources from being modified.

nblair commented 10 years ago

The aforementioned branch would be ready to send as a Pull Request, if the original request is ok (that is, publishing to "Public" instead of "UW Releases").

jnweaver commented 10 years ago

Sounds good. Like you note, the project itself is public.