https://forge-allura.apache.org/p/allura/tickets/You searched for labels:"sf-4"enThu, 28 Apr 2016 20:15:30 -0000https://forge-allura.apache.org/p/allura/tickets/8051/Update the export tasks with a flag for including attachments or not. How to organize / reference the files in the export .zip is not determined yet, but is obviously important. [#6662] will be the frontend for this.Dave BrondsemaWed, 09 Mar 2016 21:44:07 -0000https://forge-allura.apache.org/p/allura/tickets/8051/https://forge-allura.apache.org/p/allura/tickets/8046/When on neighborhood level pages like a wiki, the project and neighborhood name are both displayed but they are the same and it looks weird, especially if they run into each other. We should omit one on pages of that type.Dave BrondsemaFri, 05 Feb 2016 19:36:12 -0000https://forge-allura.apache.org/p/allura/tickets/8046/https://forge-allura.apache.org/p/allura/tickets/8040/Now that [#7987] has us on a standard rendering of code blocks, we should contribute our `toggleCodeBlock` functionality back to SimpleMDE. It needs a bit of cleanup with extra `\n` insertion no longer needed. We'll need to upgrade to the latest version, which might require some changes. And once our contribution is accepted, upgrade to that release too.Dave BrondsemaThu, 28 Apr 2016 20:15:30 -0000https://forge-allura.apache.org/p/allura/tickets/8040/https://forge-allura.apache.org/p/allura/tickets/8035/Finalize and cleanup our eslint/jscsrc setup. This can be a working standard that evolves over time -- but we should get something in place now so that we can start collecting feedback. *(Dave has a few tweaked config files attached - they need more work though)* Then apply these styles to [#7919].Heith SeewaldFri, 05 Feb 2016 20:42:11 -0000https://forge-allura.apache.org/p/allura/tickets/8035/https://forge-allura.apache.org/p/allura/tickets/8024/The site admin pages should have a way to manage site notifications. Also, make sure to update the Site Notification part of the docs.Dave BrondsemaMon, 11 Jan 2016 15:26:50 -0000https://forge-allura.apache.org/p/allura/tickets/8024/https://forge-allura.apache.org/p/allura/tickets/8023/Site notifications would be more useful if they had options to control who they were shown to and on what pages. For the user, some obvious options are show to everyone, or show to project devs/admins. I can't think of others right now. For the pages, tool type(s) could be a useful selection. But all pages are a tool (plus I'd like this to be able to work with external code that can integrate with Allura) so a url regex would be a good option too. That'd cover lots of possibilities (specific neighborhood, specific project, auth pages, create project page, etc).Dave BrondsemaMon, 11 Jan 2016 15:26:44 -0000https://forge-allura.apache.org/p/allura/tickets/8023/https://forge-allura.apache.org/p/allura/tickets/8020/The moderation page should have a field to filter by a username - then it will be easier to get a list of all the posts by a user in that forum, and select-all to mark as spam. Also, when in the regular view of a post and you click "Spam" and the message goes away, we should show a little message box in its place that explains what just happened, and a link to go over to the moderation view and see all posts by the user (so project admins know that is possible and have an easy way to get there). An undo link there would be very nice too.Dave BrondsemaWed, 27 Jan 2016 17:17:46 -0000https://forge-allura.apache.org/p/allura/tickets/8020/https://forge-allura.apache.org/p/allura/tickets/8004/Per discussion at thread http://mail-archives.apache.org/mod_mbox/allura-dev/201510.mbox/%3CCAOH-DerrdKor_BdfecYXoF0sfiZ%3DK893%3DzmQiet%2B%2Bc_-8vMUSw%40mail.gmail.com%3EDave BrondsemaMon, 02 Nov 2015 15:09:14 -0000https://forge-allura.apache.org/p/allura/tickets/8004/https://forge-allura.apache.org/p/allura/tickets/7987/Switch from our custom `FencedCodeProcessor` to the standard extension https://pythonhosted.org/Markdown/extensions/fenced_code_blocks.html so that we can support \`\`\` style, and so that blank lines are not needed before and after the `~~~~` blocks. This will get us more closely aligned with the CommonMark standard, and the syntax highlighting of the markdown editor, and the However, the format for denoting the language inside the block is different there than the [CodeHilite](https://pythonhosted.org/Markdown/extensions/code_hilite.html) extension which we are already using (and our current `~~~~` uses as well since it simply makes an indented block). So we'll have to figure out how to reconcile that.Dave BrondsemaMon, 11 Jan 2016 15:26:25 -0000https://forge-allura.apache.org/p/allura/tickets/7987/https://forge-allura.apache.org/p/allura/tickets/7957/There have been reported problems with uwsgi: http://lists.unbit.it/pipermail/uwsgi/2015-July/008104.html We should make sure it works and document it. For mod_wsgi we can borrow & simplify from our forge-allura.apache.org setup. Once done, it'll help with our [#7908] docker setup.Dave BrondsemaMon, 21 Sep 2015 14:06:01 -0000https://forge-allura.apache.org/p/allura/tickets/7957/https://forge-allura.apache.org/p/allura/tickets/7956/See if these are upstream bugs, report them, see if we can fix them * when you get multiple levels deep in a list, some lines are colored green * any sort of `foo:bar` text with a colon in it gets turned into a link style. Should have a smarter URL pattern * within a blockquote section, the Image button is highlighted instead of blockquote button * `#foobar` heading without a space after #, does not get styled like a heading Dave BrondsemaMon, 21 Sep 2015 14:05:40 -0000https://forge-allura.apache.org/p/allura/tickets/7956/https://forge-allura.apache.org/p/allura/tickets/7955/It'd be nice to add more toolbar buttons to support inserting formatting like: * `~~~~` code blocks * strikethrough * backticks * tables * headers Tables & headers might need a drop-down to support choosing which one, so not sure if that is realistic. Syntax highlighting of those elements (especially our code blocks) would be nice too, but perhaps a lot of work? See if we can include tooltip text on the new buttons too. I note that our custom preview and help buttons don't have tooltips.Dave BrondsemaMon, 21 Sep 2015 14:05:55 -0000https://forge-allura.apache.org/p/allura/tickets/7955/https://forge-allura.apache.org/p/allura/tickets/7948/When editing text in the new markdown editor, the cursor can be off by a line (or few?). This seems to happen reliably, but exact cause is not narrowed down yet. Seems to only be when editing existing content, not when creating new content (even pasting the exact same text). I think it has to do with the initial height of the input area being tall. Sometimes I can get the cursor to work properly again if I add or delete enough rows to make the textarea resize some amount.Dave BrondsemaMon, 24 Aug 2015 14:29:42 -0000https://forge-allura.apache.org/p/allura/tickets/7948/https://forge-allura.apache.org/p/allura/tickets/7939/As followup to [#6797] we should find some way to publish our RAML files. E.g. as static HTML pages, and/or as a live demo so people can try it out.Dave BrondsemaMon, 10 Aug 2015 14:28:26 -0000https://forge-allura.apache.org/p/allura/tickets/7939/https://forge-allura.apache.org/p/allura/tickets/7926/If we want to create additional web pages (e.g. for news, feature announcements, howtos) with the same theme as the homepage then we should set up some light-weight system for publishing them easily. http://blog.getpelican.com/ might be a good option, since it is python-based. Repo is at https://svn.apache.org/repos/asf/allura/site/ Also consider switching our web repo from SVN to https://blogs.apache.org/infra/entry/git_based_websites_availableDave BrondsemaMon, 27 Jul 2015 14:35:22 -0000https://forge-allura.apache.org/p/allura/tickets/7926/https://forge-allura.apache.org/p/allura/tickets/7925/In a git repo with a large amount of binary files, our diff processing can be very inefficient. We should test if a file is binary and exclude it from the diff processing section.Heith SeewaldMon, 10 Aug 2015 14:27:58 -0000https://forge-allura.apache.org/p/allura/tickets/7925/https://forge-allura.apache.org/p/allura/tickets/7924/Our icons should be updated and support hidpi screens. [Font awesome](http://fortawesome.github.io/Font-Awesome/) might be a good choice or possibly [fontello](http://fontello.com/). Licenses need to be taken into consideration and included in the appropriate places.Heith SeewaldMon, 02 Nov 2015 15:09:18 -0000https://forge-allura.apache.org/p/allura/tickets/7924/https://forge-allura.apache.org/p/allura/tickets/7922/Create a collapsible admin section on the left sidebar of each tool.Heith SeewaldMon, 24 Aug 2015 14:30:09 -0000https://forge-allura.apache.org/p/allura/tickets/7922/https://forge-allura.apache.org/p/allura/tickets/7921/After the new tool admin system is implemented, we should remove all traces of the old tools page. A number of tests will have to be updated also, that use the tools page to manage tools. Heith SeewaldFri, 05 Feb 2016 19:12:56 -0000https://forge-allura.apache.org/p/allura/tickets/7921/https://forge-allura.apache.org/p/allura/tickets/7907/We have a hacky setup for solr (both step-by-step and docker install): * we wget solr, instead of using a system package * we copy our schema into the solr example dir * we run `start.jar` directly instead of a service For docker, we should be able to use a solr image that somebody else has set up. For the step-by-step we should use system packages and perhaps borrow ideas from the solr container's Dockerfile.Dave BrondsemaMon, 14 Dec 2015 16:10:57 -0000https://forge-allura.apache.org/p/allura/tickets/7907/https://forge-allura.apache.org/p/allura/tickets/7873/I saw that git pages on forge-allura.apache.org were slow, so I looked at stats.log and saw that the sidebar was the slowest part. I did some additional digging and found 2 specific areas for improvement: * in `git_main.py` change `default_branch_name` to a `@LazyProperty` since it is called many times inside a loop in `RepositoryApp.sidebar_menu` * Since `sidebar_menu` only requests a certain number of branches, pass that "limit" all the way through to `git_repo.py`'s `branches` method so that `is_valid()` is only called a minimum number of times needed. * make sure the default branch logic to put it at the top of the list still works (e.g. always put it at the top first) In addition to those changes, generalize and apply the same approach to the tags. And also check ForgeHg to see if mercurial can benefit the same way.Dave BrondsemaMon, 29 Jun 2015 14:22:52 -0000https://forge-allura.apache.org/p/allura/tickets/7873/https://forge-allura.apache.org/p/allura/tickets/7836/A merge request works ok if the downstream (forked) repo has all of the upstream (parent) repo's commits. But if the upstream repo has new commits on it, then the merge request shows 0 commits. This is because `MergeRequest._commits` can't find the upstream HEAD in the forked repo, so the `log()` doesn't work. We should have a smarter technique for finding the list of added commits. We should also have better error handling and message to the user when it can't be found since that'll probably still happen sometimes.Dave BrondsemaThu, 20 Aug 2015 22:06:09 -0000https://forge-allura.apache.org/p/allura/tickets/7836/https://forge-allura.apache.org/p/allura/tickets/7835/##### Update the documentation theme to the "mobile first" [read the docs](https://github.com/snide/sphinx_rtd_theme). * Remove `Allura/docs/_templates/layout.html`, but make sure we can still link back to Allura home. * Restructure the `toctree` to improve side bar navigation: ("Introduction", "Running Allura", etc). Reference: [1](http://django-cms.readthedocs.org), [2](http://www.graphicall.org/ftp/ideasman42/html/introduction/) Heith SeewaldThu, 20 Aug 2015 22:06:09 -0000https://forge-allura.apache.org/p/allura/tickets/7835/https://forge-allura.apache.org/p/allura/tickets/7832/We should support APIs to manage webhooks so that 3rd-party sites can use oauth to configure a webhook on behalf of a user. This is a common practice to make it easier for the user.Dave BrondsemaThu, 20 Aug 2015 22:06:09 -0000https://forge-allura.apache.org/p/allura/tickets/7832/https://forge-allura.apache.org/p/allura/tickets/7830/Add a button to merge requests to merge the branch on the server-side. Of course, don't do it if there are conflicts. Also need to consider server-side filesystem permissions and make sure install docs are updated if needed, etc.Dave BrondsemaThu, 20 Aug 2015 22:06:09 -0000https://forge-allura.apache.org/p/allura/tickets/7830/