https://forge-allura.apache.org/p/allura/tickets/You searched for assigned_to:"peterhartmann"enThu, 20 Aug 2015 22:07:57 -0000https://forge-allura.apache.org/p/allura/tickets/5942/Tim Van SteenburghThu, 20 Aug 2015 22:07:53 -0000https://forge-allura.apache.org/p/allura/tickets/5942/https://forge-allura.apache.org/p/allura/tickets/4655/The ForgeHg tool uses the Mercurial package which is GPLd. That means we can't distribute ForgeHg through Apache. We should make a separate repo for ForgeHg (sourceforge project, perhaps) and move it all there. ForgeHg should be installable as an optional dependency. See also [#4647]Dave BrondsemaThu, 20 Aug 2015 22:07:53 -0000https://forge-allura.apache.org/p/allura/tickets/4655/https://forge-allura.apache.org/p/allura/tickets/4648/Apply the AL2 license header to all files. There is a helper script at https://svn.apache.org/repos/private/committers/relicense/ and an audit tool at http://creadur.apache.org/rat/ Also create a NOTICE file. See http://www.apache.org/legal/src-headers.html for instructions See also http://incubator.apache.org/projects/allura.html section "Verify distribution rights" Dave BrondsemaThu, 20 Aug 2015 22:07:56 -0000https://forge-allura.apache.org/p/allura/tickets/4648/https://forge-allura.apache.org/p/allura/tickets/4647/See http://incubator.apache.org/projects/allura.html section "Verify distribution rights" See also http://www.apache.org/legal/resolved.html We should go through all our deps in requirements*.txt and check their licensing. Also check for any differently-licensed code files checked into our main codebase.Dave BrondsemaThu, 20 Aug 2015 22:07:52 -0000https://forge-allura.apache.org/p/allura/tickets/4647/https://forge-allura.apache.org/p/allura/tickets/3905/Goal: `pip install Allura` To do: * [#3883] make git & svn optional dependencies * make setup.py use the same dependencies as requirements.txt * http://cburgmer.posterous.com/pip-requirementstxt-and-setuppy * http://stackoverflow.com/questions/4150423/can-pip-install-dependencies-not-specified-in-setup-py-at-install-time * post AlluraTesting and ForgeWiki packages to pypi, since it is pretty hard to run Allura without them. Maybe others, like ForgeHg, are needed too? * provide installation instructions for this mode of installation - will be similar to README instructions, but not the same * tag git with the release (v0.1?)Dave BrondsemaFri, 24 Jul 2015 14:10:15 -0000https://forge-allura.apache.org/p/allura/tickets/3905/https://forge-allura.apache.org/p/allura/tickets/3883/[#3874] divided the requirements file. But we need to update the README to only do Mercurial, with further instructions for git and svn. Also, the code has a few dependencies on git and svn: * allura/ext/admin/templates/project_admin.html +46 * tests that use with_svn or with_git decorators * allura.tests.functional.test_admin:TestProjectAdmin.test_tool_list Dave BrondsemaThu, 20 Aug 2015 22:07:57 -0000https://forge-allura.apache.org/p/allura/tickets/3883/