Opened 14 years ago
Last modified 13 years ago
#11 closed task (FIXED)
Develop policy for external code in our repository
Reported by: | Christopher Allan Webber | Owned by: | Will Kahn-Greene |
---|---|---|---|
Priority: | minor | Milestone: | 0.0.4 |
Component: | infrastructure | Keywords: | |
Cc: | Parent Tickets: |
Description
StatusNet has both good writeup of legalcode descriptions of external libraries: `https://gitorious.org/statusnet/mainline/blobs/master/README#line90 <https://gitorious.org/statusnet/mainline/blobs/master/README#line90>`_ And also has a good policy for external libraries: `https://gitorious.org/statusnet/mainline/blobs/master/extlib/README <https://gitorious.org/statusnet/mainline/blobs/master/extlib/README>`_ Evan has made clear that it's cool (even a good idea) for us to just copy that extlib/README file and adapt it to mediagoblin, and that's what we should do. We should also find a nice directory to keep these all in, and just use symlinks to move them around to appropriate places (eg, bootstrap.py from zc.buildout can be symlinked to the toplevel of the package, jquery can be symlinked to the mediagoblin static app media directory).
Change History (10)
comment:3 by , 14 years ago
Milestone: | 0.0.2 → 0.0.3 |
---|
comment:3 by , 14 years ago
I'm not going to get to this for 0.0.3, but this is high on my list of things to work out for July.
comment:4 by , 14 years ago
I've merged in our first "external" code, 960.gs, as part of: `https://gitorious.org/mediagoblin/mediagoblin/commit/f7bcfafff0388d50c75c72ca8da63235e9715d93 <https://gitorious.org/mediagoblin/mediagoblin/commit/f7bcfafff0388d50c75c72ca8da63235e9715d93>`_ We should get this policy and etc in properly thusly :) Will, let's talk about this when you get back from traveling. No rush beforehand though!
comment:5 by , 13 years ago
Component: | → Infrastructure |
---|---|
Milestone: | 0.0.3 → 0.0.4 |
comment:5 by , 13 years ago
Tweaking the title a bit. This specifically applies to code created by other projects that we're including in our repository and will be shipped in our source tarball. It does not apply to code that is in a library that gets pulled in through buildout or other installation methods. If I'm incorrect about this clarification, someone poke me.
comment:6 by , 13 years ago
Status: | New → In Progress |
---|
I: 1. created an extlib/ directory 2. put a big README in there based on the one from Status.net (with an appropriate attribution at the bottom) 3. downloaded 960.gs and put the README in extlib/960.gs/ as well as the files we were using 4. redid the symlinks 5. overhauled the COPYING file so that it covered things better with urls for the licenses if they don't happen to be in the distribution I think that covers the work. It's in merge request `#13 </issues/13>`_.
comment:7 by , 13 years ago
Status: | In Progress → Closed |
---|
Chris merged it in. Marking this as closed.
Note:
See TracTickets
for help on using tickets.