<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ticket search results</title><link>https://forge-allura.apache.org/p/allura/tickets/</link><description>You searched for assigned_to:"heiths"</description><language>en</language><lastBuildDate>Fri, 15 Apr 2016 15:16:55 -0000</lastBuildDate><item><title>Create wiki page button should work without admin access</title><link>https://forge-allura.apache.org/p/allura/tickets/8071/</link><description>Should be able to use the button with just 'edit' access, but the page goes through the `/admin/` url controller which requires admin access, and then the `create_wiki_page` function requires 'configure' access currently.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Fri, 15 Apr 2016 15:16:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8071/</guid></item><item><title>Don't duplicate titles on neighborhood pages</title><link>https://forge-allura.apache.org/p/allura/tickets/8046/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Fri, 05 Feb 2016 19:36:12 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8046/</guid></item><item><title>Update modal css (simple-flat-dark)</title><link>https://forge-allura.apache.org/p/allura/tickets/8036/</link><description>To coincide with the release of our new toolbar, we should give the lightbox modals a slightly newer look.

A dark, simple look would go a long way in improving our option’s aesthetic.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 25 Jan 2016 15:34:19 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8036/</guid></item><item><title>Finalize frontend eslint/jscs setup</title><link>https://forge-allura.apache.org/p/allura/tickets/8035/</link><description>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].</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Fri, 05 Feb 2016 20:42:11 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8035/</guid></item><item><title>Use Allura icon in favicon, footer, etc</title><link>https://forge-allura.apache.org/p/allura/tickets/8017/</link><description>We should use the Allura icon in more places like the favicon (existing favicon.ico file is a gzipped turbegears logo, and isn't referenced) and in the footer by our name.  Can copy from sf.net styling of that footer spot.  Maybe show the logo on the homepage or a default sitewide logo too?</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 25 Jan 2016 16:40:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8017/</guid></item><item><title>Speed up commit view by disabling copy detection by default  -- NEEDS INI</title><link>https://forge-allura.apache.org/p/allura/tickets/7963/</link><description>Currently git and mercurial detect copies when viewing commits.  This adds a significant amount of time to each request and is not a common enough occurrence to justify such a large performance hit on every view. 

But we should also probably add an option in the .ini that gives the option to enable copy detection (noting the performance penalty).


[#7925]</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 24 Aug 2015 14:29:16 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7963/</guid></item><item><title>Publish our RAML files</title><link>https://forge-allura.apache.org/p/allura/tickets/7939/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 10 Aug 2015 14:28:26 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7939/</guid></item><item><title>Fix pagination issue in the commit browser</title><link>https://forge-allura.apache.org/p/allura/tickets/7932/</link><description>The `index` method on `allura.controllers.repository.CommitBrowser` has an issue where every page from the pagination consists of an identical copy of the entire list.

so **?page=2** is the same as **?page=10** and they both contain a full (non-paged) version of the changes.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 27 Jul 2015 14:35:07 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7932/</guid></item><item><title> Speed up diff processing with binary files</title><link>https://forge-allura.apache.org/p/allura/tickets/7925/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 10 Aug 2015 14:27:58 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7925/</guid></item><item><title>Create frontend for new admin toolbar</title><link>https://forge-allura.apache.org/p/allura/tickets/7920/</link><description>This ticket is to create a new, streamlined system for managing tools in Allura. 

We would like to get rid of the "admin/tools" page and give admins the ability to create/edit/reorder/remove tools directly from the 'tool bar'. 

The idea is to have a 'edit' mode symbolized by a locked/unlocked icon (and other style indicators) that allow for an intuitive, in-place editing experience.  This, along with a contextual per-tool "Admin" section on the left navigation bar will completely replace the tools page.

The front-end aspect of this ticket is to create a toolbar from a json file that makes
ajax calls on modification.

Attached are rough sketches of how this should function.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 11 Jan 2016 15:27:23 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7920/</guid></item><item><title>New admin nav bar PLUS LOTS MORE see ticket description</title><link>https://forge-allura.apache.org/p/allura/tickets/7919/</link><description>This ticket ended up being extremely large and making these changes to Allura too:

 - new admin APIs, new `_nav.json` param
 - remove AdminModal widgets, use JS directly
 - remove sidebar_menu_widgets and admin_menu_widgets, using JS directly instead
 - refactor to share project lookup logic between NeighborhoodController and NeighborhoodRestController
 - better test failure messages if antispam validation issues
 - upgrade existing react code to 0.14
 - better calculation of tool/subproject ordinal values when installing
 - better tool descriptions</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 11 Jan 2016 15:27:29 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7919/</guid></item><item><title>Create a quick and dirty prototype for the new admin toolbar</title><link>https://forge-allura.apache.org/p/allura/tickets/7917/</link><description>Create a rough prototype of the admin toolbar with an edit mode.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Mon, 27 Jul 2015 14:35:30 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7917/</guid></item><item><title>Icon upload/edit is not clear</title><link>https://forge-allura.apache.org/p/allura/tickets/7898/</link><description>To change your project icon have you have to click a little pencil icon.  That is not obvious enough.  Also "No icon has been created." sounds weird.

Suggestion for project admin pages:

"No icon.  &lt;a&gt;Upload one [pencil icon]&lt;/a&gt;"

And for user-profile projects, which have different text:

"No user icon.  &lt;a&gt;Upload one [pencil icon]&lt;/a&gt;&lt;br&gt;
Or a &lt;a&gt;gravatar.com&lt;/a&gt; image will be used if available." </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 29 Jun 2015 14:23:33 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7898/</guid></item><item><title>Don't update merge request timestamps incorrectly</title><link>https://forge-allura.apache.org/p/allura/tickets/7894/</link><description>Merge request's "updated" timestamp changes when you view it and it calculates if a one-click merge is possible.  That shouldn't happen.  Make sure no other operations incorrectly update the timestamp either.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 13 Jul 2015 14:49:44 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7894/</guid></item><item><title>Improve markdown logic for cached vs threshold limits</title><link>https://forge-allura.apache.org/p/allura/tickets/7889/</link><description>The `markdown_render_max_length` param is an absolute limit to how big something can be for markdown conversion.  But `cached_convert()` was added later and is a better approach.  E.g. a very large ticket only has to get converted once and then its good, so a `markdown_render_max_length` isn't needed (we even have it set very high in development.ini because of this).

However, not all markdown conversions go through `cached_convert()`, for example, commit messages, outbound email bodies, or markdown files in repos.

So we should have `markdown_render_max_length` apply only to non-cached conversions and change its default value to something not so extremely high, maybe 100000.  Or possibly introduce a second option, one for cached and one for non-cached conversions.  Or develop a new caching mechanism that works for markdown text that isn't part of an artifact.

An example I came across was thousands of lines like this in the commit message itself, totaling around 500k chars:

~~~~
   renamed: ts/5.1/fastboot/fastboot-mangle -&gt; ts/5.2/fastboot/fastboot-mangle                                                                                                                             
   renamed: ts/5.1/fastboot/lib-boot -&gt; ts/5.2/fastboot/lib-boot                                                                                                                                           
   renamed: ts/5.1/fastboot/lib-rw -&gt; ts/5.2/fastboot/lib-rw                                                                                                                                               
   renamed: ts/5.1/fastboot/usr-rw -&gt; ts/5.2/fastboot/usr-rw                                                                                                                                               
   renamed: ts/5.1/kernel/alias/acpi -&gt; ts/5.2/kernel/alias/acpi                                                                                                                                           
   renamed: ts/5.1/kernel/alias/pcm -&gt; ts/5.2/kernel/alias/pcm              
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 29 Jun 2015 14:23:15 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7889/</guid></item><item><title>Tooltip for project admin</title><link>https://forge-allura.apache.org/p/allura/tickets/7885/</link><description>Add ToolTip for few input boxes to better guide admin users on type of content expected.

Design File Attached
Tool Tip Content file attached.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dipesh</dc:creator><pubDate>Mon, 29 Jun 2015 18:23:58 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7885/</guid></item><item><title>UnicodeEncodeError on ticket attachment diff</title><link>https://forge-allura.apache.org/p/allura/tickets/7874/</link><description>~~~~
File '/var/local/allura/ForgeTracker/forgetracker/tracker_main.py', line 1391 in update_ticket_from_widget
  self._update_ticket(data)
File '/var/local/allura/ForgeTracker/forgetracker/tracker_main.py', line 1455 in _update_ticket
  changes['attachments'] = attachments_info(self.ticket.attachments)
File '/var/local/allura/ForgeTracker/forgetracker/tracker_main.py', line 157 in attachments_info
  attach.content_type))
UnicodeEncodeError: 'ascii' codec can't encode characters in position 2-3: ordinal not in range(128)
~~~~</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7874/</guid></item><item><title>Git branch &amp; tag speedups  -- NEEDS INI</title><link>https://forge-allura.apache.org/p/allura/tickets/7873/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 29 Jun 2015 14:22:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7873/</guid></item><item><title>Upgrade docutils, Pygments and Babel, so docs can be built easily</title><link>https://forge-allura.apache.org/p/allura/tickets/7855/</link><description>Building our docs requires `pip install Sphinx` and the latest version of Sphinx uses significantly newer versions of docutils, Pygments, and Babel than Allura itself uses.  Allura doesn't work with the newer versions.  We should update Allura to use those versions, so that there is no difficulty in running Allura and building its docs with the same virtualenv.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7855/</guid></item><item><title>Don't update mod time when viewing artifact creates a cache</title><link>https://forge-allura.apache.org/p/allura/tickets/7852/</link><description>In addition to the fixes done in [#7834], a ticket can still be marked as updated just when viewed.  This happens if the cache was not created initially (e.g. ticket import - no view, or first view was under the threshold time) and then the cache was created upon a later view.   We need to skip updating `mod_date` and `last_updated` when a cache is set.  I think it's probably safe to set the `skip_mod_date` and `skip_last_updated` flags on the session, since there shouldn't be cases of rendering a markdown (viewing) in the same session as legitimately updating records (I hope).</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7852/</guid></item><item><title>Ability to close discussion on a ticket</title><link>https://forge-allura.apache.org/p/allura/tickets/7850/</link><description>It would be nice if a project admin could turn off comments on an individual ticket basis.  I believe this should be possible with our permission backend, we just need a UI for removing 'POST' and 'UNMODERATED_POST' on the individual artifact.  The "mark as private" checkbox does similar for the 'READ' permission.

We should also include it in solr so that it is possible to search by it (e.g. `discussion_closed: true/false`)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7850/</guid></item><item><title>Update theme for the documentation.</title><link>https://forge-allura.apache.org/p/allura/tickets/7835/</link><description>##### 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/)
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7835/</guid></item><item><title>Bug: viewing a ticket updates its 'updated' date</title><link>https://forge-allura.apache.org/p/allura/tickets/7834/</link><description>Merely viewing a ticket causes its 'updated' date to be updated.  That should not be.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7834/</guid></item><item><title>Logout issue</title><link>https://forge-allura.apache.org/p/allura/tickets/7831/</link><description>Currently the logout functionality of allura is not working.  The **allura-loggedin** cookie gets deleted as expected, but the session remains active.

It appears that by adding **self.session.delete()** to the logout method (on AuthenticationProvider), it fixes the issue.  But further analysis need to be done to see why **self.session.invalidate()** doesn't work as expected.

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7831/</guid></item><item><title>Update "new commits" email template</title><link>https://forge-allura.apache.org/p/allura/tickets/7825/</link><description>See attached screenshot for reference.  Several things that can be improved:

* "From" could be improved, e.g. "{{project name}} {{tool name}} repository"
* The branch name is specified in front of just the first commit, and then is blank on the rest of the commits.  IIRC this is bad for SVN commit messages too since they don't have real branches.  I think it could be better moved up as a section header "On `master` branch:".  Test with SVN and with Hg, and with commits on multiple branches.
* Markdown formatting in commit messages is not expected, e.g. `__future__` vs __future__.  When we render commits, e.g. at https://sourceforge.net/p/gazette/code/ci/2cece9731de397e508dfed34d3d6e3866e0a94ac we use a special rendering helper that is configured to do some stuff like artifact linking but not other markdown formatting.  We should use that for these commit emails too.
* It would be cleaner to make the commit message text be a link, instead of showing the full link URL in the email text.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:06:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7825/</guid></item></channel></rss>