Ticket search results

CC-BY 4.0 and SIL Open Font License

Dave Brondsema — Fri, 23 Sep 2022 16:10:15 -0000

Reported on the dev list: The license file mentions two licenses CC-BY 4.0 and the SIL Open Font License, both of these licenses are Category B and in general shouldn't be included in a source release. https://www.apache.org/legal/resolved.html#category-b https://www.apache.org/legal/resolved.html#cc-sa

review licenses of python dependencies

Dave Brondsema — Fri, 10 Sep 2021 18:41:54 -0000

I came across https://pypi.org/project/liccheck/ and thought we should see what it reports for Allura. With a .ini file like ``` [Licenses] authorized_licenses: bsd new bsd bsd license new bsd license simplified bsd apache apache 2.0 apache software license Apache Software mit mit license python software foundation license ``` output is: ``` $ liccheck -r requirements.txt -s lic.ini gathering licenses... 94 packages and dependencies. check authorized packages... 81 packages. check unknown packages... 13 packages. certifi (2019.6.16): ['MPL-2.0', 'Mozilla Public License 2.0 (MPL 2.0)'] dependencies: certifi << requests << pysolr certifi << requests << requests-oauthlib chardet (3.0.4): ['GNU Library or Lesser General Public License (LGPL)', 'LGPL'] dependencies: chardet << requests << pysolr chardet << requests << requests-oauthlib colander (1.7.0): ['BSD-derived (http://www.repoze.org/LICENSE.txt)'] dependency: colander feedparser (5.2.1): UNKNOWN dependency: feedparser ipaddress (1.0.22): ['Python Software Foundation'] dependency: ipaddress nose (1.3.7): ['GNU LGPL', 'GNU Library or Lesser General Public License (LGPL)'] dependency: nose pexpect (4.7.0): ['ISC', 'ISC License (ISCL)'] dependency: pexpect << ipython Pillow (6.2.2): ['Historical Permission Notice and Disclaimer (HPND)', 'HPND'] dependency: Pillow ptyprocess (0.6.0): ['ISC License (ISCL)'] dependency: ptyprocess << pexpect << ipython repoze.lru (0.7): ['BSD-derived (http://www.repoze.org/LICENSE.txt)'] dependency: repoze.lru << TurboGears2 simplegeneric (0.8.1): ['ZPL 2.1', 'Zope Public'] dependency: simplegeneric << ipython translationstring (1.3): ['BSD-like (http://repoze.org/license.html)'] dependency: translationstring << colander waitress (1.4.3): ['ZPL 2.1', 'Zope Public'] dependency: waitress << WebTest ``` - MPL is ok according to https://apache.org/legal/resolved.html#category-b but should be labelled (in NOTICE or LICENSE) - `chardet` LGPL is not good. - we use it directly and requests lib uses it and doesn't intend to change https://github.com/psf/requests/issues/3389 - chardet won't change their license: https://github.com/chardet/chardet/issues/36 - alternatives: https://github.com/Ousret/charset_normalizer or https://github.com/PyYoshi/cChardet (MPL multi licensed? https://github.com/PyYoshi/cChardet/issues/54) - another ASF project has discussed a bit at https://github.com/apache/airflow/issues/10667 - latest: https://github.com/psf/requests/pull/5797 - `nose` LGPL is not good - it is mostly a test runner, but we do import 'nose' modules within our tests - should switch to `pytest` anyway since nose isn't maintained - BSD-derived, BSD-like, ZPL, ISC, HPND are a like BSD/MIT and should be fine - `feedparser` is BSD 2-clause https://github.com/kurtmckee/feedparser/blob/develop/LICENSE

Migrate jenkins builds - due Aug 15

Dave Brondsema — Mon, 17 May 2021 15:07:02 -0000

For details see https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E Basically we need to move these: * https://builds.apache.org/job/Allura/ * https://builds.apache.org/job/Allura-licensing-check/ Over to https://ci-builds.apache.org/ Shouldn't be too hard since their configs are mostly inline bash scripts, no fancy plugin usage etc.

Move forge-allura self-hosting to new VM

Dave Brondsema — Mon, 17 May 2021 15:07:02 -0000

Very slow performance on our own self-hosting (this site) has occurred, often because of a process called "blocky.py" which I reported to Apache Infra at: https://issues.apache.org/jira/browse/INFRA-20414 and they also created https://issues.apache.org/jira/browse/INFRA-20427 They are recommending we upgrade to a new VM with new OS and config management which should fix it. The current VM `allura-vm2` setup notes are here: https://docs.google.com/document/d/1d0fiws7qVyjf-nfcqsIyFqzAsbUqm2yR66bJx6GtZKk/edit and https://issues.apache.org/jira/browse/INFRA-13262

Website: make our own dedicated download page

Dave Brondsema — Mon, 17 May 2021 15:07:01 -0000

Instead of just release announcements and links to the download page for a release, we should have a page that links to the latest release, our KEYS used in signing, instructions, etc. This is to comply with https://www.apache.org/dev/release-download-pages.html#download-page and https://www.apache.org/dev/release-distribution#download-links and be acceptable for announce @ apache . org announcements.

Upgrade mongo on allura-vm

Dave Brondsema — Mon, 24 Sep 2018 19:36:21 -0000

Label suggestions don't work, since they require mongodb aggregation. We have an old version of mongo and should upgrade it. Perhaps upgrading to next stable ubuntu release would include it (check with infra before doing it)

Script to set up MovedTicket records for tickets we're moving to Apache

Dave Brondsema — Thu, 20 Aug 2015 22:07:00 -0000

Create a script that will take a file with a list of Allura ticket numbers (generated with [#7510]) and delete those ticket records. For safety, would be good to save them in some temp mongo collection, or keep them in the current collection but with some new special app_config_id (so we don't risk losing any data). And also create "moved ticket" records for each, with URLs like https://forge-allura.apache.org/p/allura/tickets/NNN Test this out locally and make sure it will work well as a solution for having some tickets moved out of the SF Allura tracker into the Apache host, and some kept on SF. Make any code changes in ForgeTracker code if needed.

Test extracting Allura tickets for Apache move

Dave Brondsema — Thu, 20 Aug 2015 22:07:00 -0000

Re: Do an export of tickets from SF Allura and write a script to go through the JSON and: * filter out all deleted & private tickets (except #6054) * change "QA" field to "Reviewer" * change "size" field to a labels like "sf-1", "sf-2", etc * change milestone: * to "backlog" if open/in-progress/validation/review/blocked * to "released" if closed/wontfix/invalild Or even better would to look at the git tags for releases 1.0.0, 1.0.1, and 1.1.0 and find the tickets that go into those, and assign milestones appropriately. Can default a ton of tickets to 1.0.0 and then smaller set for 1.0.1 and 1.1.0 Then import locally as a test run and see how it works.

Make static web page for Allura

Dave Brondsema — Thu, 20 Aug 2015 22:07:54 -0000

allura.apache.org needs something on it Repo for it is at https://svn.apache.org/repos/asf/allura/site/trunk/

create an ASF theme

Dave Brondsema — Tue, 25 Mar 2014 15:27:17 -0000

We should have an Apache theme, which: * sets the footer contents (currently done in master theme in [#7274]) * hide 'brought to you by'; or maybe a config option for that (currently done via CSS at /p/_admin/overview) * sets the logo (currently done via css/js hack at /p/_admin/overview) * possibly have better placement of required License, Sponsorship, Thanks, Security, Apache.org links. Maybe a separate menu line? If we have other projects on the site, they would need those links too - although potentially need to customize them. * override home page content?

Graduation items

Dave Brondsema — Thu, 20 Aug 2015 22:07:00 -0000

* http://incubator.apache.org/guides/graduation.html#life-after-graduation * Rename home wiki page yet again (call it just "Home" this time?) and update old home pages which have links/includes to the new. * Add news item and pointers to new site, on http://incubator.apache.org/projects/allura.html

ensure /var/run/allura is created on allura-vm.a.o

Dave Brondsema — Mon, 10 Aug 2015 15:21:57 -0000

After a reboot /var/run/allura wasn't there, which is needed by mod_wsgi and reactor/taskd scripts. I manually did: ~~~~ root@allura-vm:/var/run# mkdir allura root@allura-vm:/var/run# chgrp allura allura root@allura-vm:/var/run# chmod g+w allura ~~~~ And then work with INFRA to get this into the puppet config for this host. (Probably some other things we should get in there too)

Get 'activity' tool working on forge-allura

Dave Brondsema — Thu, 20 Aug 2015 22:07:55 -0000

It exists but 404s. https://forge-allura.apache.org/p/allura/activity/

Move our published docs to forge-allura.apache.org

Dave Brondsema — Thu, 20 Aug 2015 22:07:54 -0000

Our docs are currently published to http://allura.sourceforge.net/docs/ via a post-commit job on a SourceForge internal jenkins instance. We should publish the docs on our Apache site, perhaps at a URL like https://forge-allura.apache.org/p/allura/docs/ (currently a redirect). We could do this by configuring that particular URL in Apache to serve from a directory instead of go to the allura wsgi app. We should move the post-commit publish to the Apache Jenkins job at https://builds.apache.org/job/Allura/ or perhaps to the updating cron on the allura-vm host. Lastly, we'll want http://allura.sourceforge.net/docs/* to redirect to the new locations.

Forking on forge-allura.apache.org should work

Dave Brondsema — Thu, 20 Aug 2015 22:07:00 -0000

Users should be able to fork https://forge-allura.apache.org/p/allura/git/ Currently you can make a fork, but there's no way to get your code or to push it back. The 'allura' project on our server there is basically a readonly copy with pointers to https://git-wip-us.apache.org/repos/asf?p=incubator-allura.git For forks (and any other type of local project on the server) to work, we could run git services on the allura-vm host. And probably need some code/config changes to support having a different checkout URL for the 'allura' repo vs other repos.

Move API docs from sf.net wiki to Allura (with raml?)

Dave Brondsema — Mon, 24 Aug 2015 14:30:22 -0000

Right now the allura API docs are at https://sourceforge.net/p/forge/documentation/Allura%20API/ They should be moved to Allura itself. We should also consider writing the API docs with [RAML](http://raml.org/) which looks very nice to me. Simple and readable, has composition for things like "pagination" which apply to multiple endpoints. With RAML we could also show interactive documentation with "try it live" functionality at http://www.apihub.com/

forge-allura.a.o system changes

Dave Brondsema — Thu, 20 Aug 2015 22:07:54 -0000

* Upgrade mongo. 2.0 doesn't support aggregations * run ensure_index (how do we want to do this regularly?) * install `ack-grep` system package * change logging. `/var/local/apache-vm.ini` has it configured to go to stderr which goes to separate logs in /var/log/allura for smtp_server and taskd. But the webapp's logs are nowhere to be found (by me). `/etc/apache2/sites-enabled/allura` has an ErrorLog directive but I don't see anything in `/var/local/log/allura-httpd-error_log` * once that is done, I think there will be "Error opening image" errors, because thumbnails aren't being created. We have both PIL and Pillow installed. We should uninstall PIL and may need to re-install Pillow again.

forge-allura.a.o keeps missing git metadata

Dave Brondsema — Thu, 20 Aug 2015 22:07:55 -0000

https://forge-allura.apache.org/p/allura/git/ref/master/ keeps showing "The metadata for this repository is missing. To fix, please try a refresh." After refreshing it, the code does appear, but a while later (after next cron run?) it is missing again.

Route incoming email based on X-Delivered-To

Dave Brondsema — Wed, 06 Nov 2013 17:20:30 -0000

We need to be able to route incoming email that all goes to the same address, but is distinguished by `X-Delivered-To`. Perhaps it should be a config option to enable it? Per ASF infra: > Our default way of forwarding is by doing sth like > RCPT TO: > , which means the original envelope recipients are only in > X-Delivered-To (IIRC) headers added by our MX.

Make an Apache release

Peter Hartmann — Thu, 20 Aug 2015 22:07:57 -0000

As part of incubation process, Allura project must demonstrate it's ability to make a release. A release must conform to [ASF release policy](http://www.apache.org/dev/release.html). Additional related documents: - [ASF Incubation Policy](http://incubator.apache.org/incubation/Incubation_Policy.html) - [Publishing Releases](http://www.apache.org/dev/release-publishing) - [A Guide To Release Management During Incubation](http://incubator.apache.org/guides/releasemanagement.html)

Move irc chat bot to apache

Dave Brondsema — Wed, 13 Mar 2013 18:50:53 -0000

Move allura tickets to apache

Dave Brondsema — Thu, 20 Aug 2015 22:07:00 -0000

Need to discuss exactly what should be moved. There are many private non-allura tickets that the SF team has been tracking at sf.net/p/allura/tickets Also various fields are not needed for the allura project (just internal to SF team planning)

Move allura wiki to apache

Dave Brondsema — Thu, 20 Aug 2015 22:07:20 -0000

After [#4646] we should move sf.net/p/allura/wiki content to allura-vm.apache.org/p/allura/wiki We can do this with the `wiki-copy.py` script, which is currently in SF's private repo, but should be moved over to Allura proper. It'll copy main page content, but not attachments, history or comments I don't think. We'll have to manually deal with those. After complete, a link tool can be set up at sf.net/p/allura/wiki to redirect to apache. IIRC, it should handle specific pages correctly too.

Replace tageditor js with Apache-license-compatible alternative

Tim Van Steenburgh — Thu, 20 Aug 2015 22:07:53 -0000

ActivityStream should state it's copyright

Peter Hartmann — Thu, 20 Aug 2015 22:07:53 -0000

As of now, ActivityStream lacks any sort of copyright and licensing information, both on PyPI or in the codebase itself. It's probably a minor issue since the code, I believe, has been developed in-house. But from Allura perspective it's still and external dependency and hence it's copyright status should be as clear as possible.