<?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 labels:"pycon"</description><language>en</language><lastBuildDate>Thu, 17 Mar 2016 20:39:13 -0000</lastBuildDate><item><title>Notification template error cleanup</title><link>https://forge-allura.apache.org/p/allura/tickets/3895/</link><description>Errors like this look scary (they appear during setup and also regular usage), but they aren't a problem really

    20:58:09,557 DEBUG [allura.model.notification] Error rendering notification template Git Repository: mail/Git Repository.txt</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3895/</guid></item><item><title>On tracker main page, the mass edit link is wrong</title><link>https://forge-allura.apache.org/p/allura/tickets/3880/</link><description>On https://sourceforge.net/p/allura/tickets/ the mass edit link goes to `https://sourceforge.net/p/allura/tickets/edit/?q={%22status%22%3A+{%22%24in%22%3A+[%22in-progress%22%2C+%22blocked%22%2C+%22validation%22%2C+%22open%22%2C+%22code-review%22]}}&amp;sort=ticket_num+desc&amp;limit=25` which doesn't work (returns 0 tickets)</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3880/</guid></item><item><title>PKG-INFOs currently show UNKNOWN for most fields</title><link>https://forge-allura.apache.org/p/allura/tickets/1740/</link><description>*Originally created by:* jowens81

In the eggs for each of the packages PKG-INFO currently doesn't fill in most metadata.

[PEP 345][1] describes field requirements, options, and formatting for python package metadata.

[1]: http://www.python.org/dev/peps/pep-0345/
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1740/</guid></item><item><title>Fork Doesn't Currently Copy All Branches</title><link>https://forge-allura.apache.org/p/allura/tickets/1738/</link><description>*Originally created by:* jowens81

It looks like a fork doesn't currently copy all branches.  Using an allura fork as an example only master is pulled down into the fork.   
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sun, 08 Mar 2015 00:04:04 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1738/</guid></item><item><title>README.markdown needs SOLR config</title><link>https://forge-allura.apache.org/p/allura/tickets/1726/</link><description>*Originally created by:* jowens81

*Originally owned by:* jowens81

The ubuntu build out in README.markdown points to the default location of ~/src/forge/solr_config/conf but doesn't copy the example config from solr's source into place.

Just needs a one line addition to add the cp command for putting a basic config in place.

Allura could also redistribute a basic config  for solr in the repository if licensing permits.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1726/</guid></item><item><title>Repository Browser Doesn't Indicate Current Branch</title><link>https://forge-allura.apache.org/p/allura/tickets/1725/</link><description>*Originally created by:* jowens81

*Originally owned by:* jowens81

When viewing a repository the current branch isn't shown on page initially or after selecting a branch to view.

Could easily be indicated with a * or the like next to the branch name in the left column's branch list 

eg.
Branches
=======
Master
Dev *
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 24 Mar 2011 03:04:59 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1725/</guid></item><item><title>Make interactive commit browser for scm</title><link>https://forge-allura.apache.org/p/allura/tickets/1716/</link><description>Show a list of commits at the top with a view of the highlighted commit below with a diff</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Jenny Steele</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1716/</guid></item><item><title>Fix kombu problem with multiple workers in reactors</title><link>https://forge-allura.apache.org/p/allura/tickets/1712/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1712/</guid></item><item><title>Fix repo forking</title><link>https://forge-allura.apache.org/p/allura/tickets/1708/</link><description>Fork is broke. fixit!</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1708/</guid></item><item><title>Remove unnecessary things from req.txt</title><link>https://forge-allura.apache.org/p/allura/tickets/1703/</link><description>numpy, django</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1703/</guid></item><item><title>Not possible to use REST API over SSL</title><link>https://forge-allura.apache.org/p/allura/tickets/1665/</link><description>Currently, if you make REST API request over SSL, it gets redirected to login page, because of the redirection logic we have (SSL access only for web UI logged users). Apparently, /rest/* URLs should be exempt from this logic.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Sokolovsky</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1665/</guid></item><item><title>Add more allura docs, from Kyle/Dave's notes</title><link>https://forge-allura.apache.org/p/allura/tickets/1633/</link><description/><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1633/</guid></item><item><title>Search existing tickets for similar text/summary when creating new tickets, to reduce # of dupes</title><link>https://forge-allura.apache.org/p/allura/tickets/1616/</link><description>Search existing tickets for similar summary and description when creating new tickets, displaying a page asking the user if their ticket is a duplicate of one of the tickets returned (if a close enough match is found).  If a match is found, open that ticket's page, pre-filling the comment box with the description from the aborted ticket creation, allowing the user to comment on the existing ticket without losing any typing they did. </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Thu, 17 Mar 2016 20:39:13 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1616/</guid></item><item><title>Show current directory in scm breadcrumb</title><link>https://forge-allura.apache.org/p/allura/tickets/1607/</link><description>*Originally owned by:* jowens81

Only the path from *parent* up is shown.  The current directory name is not show, but should be.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:57 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1607/</guid></item><item><title>Merge ForgeMail functionality into Allura</title><link>https://forge-allura.apache.org/p/allura/tickets/1590/</link><description>find the parts of ForgeMail that are actually used and move just those parts into Allura (probably under ext).  Then get rid of ForgeMail.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Wolf</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:52 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1590/</guid></item><item><title>Convert templates to use dotted-name dispatch</title><link>https://forge-allura.apache.org/p/allura/tickets/1564/</link><description>Currently, we have a routine that hits every tool and 'overlays' its templates directory onto the Jinja2 search path.  This makes it difficult to determine by looking at the code where a template lives.  Change the Jinja2 template loader so that it uses explicit lookup via dotted name (e.g. forgeblog.templates.foo) -- see the Genshi code in TG for an example of how to do this.

Alternatively, use the Pyramid approach of *package*:*path*, e.g. forgeblog:templates/foo.html -- whichever is easier.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1564/</guid></item><item><title>Update sphinx docs in Allura/docs/</title><link>https://forge-allura.apache.org/p/allura/tickets/1558/</link><description>Read the docs, try following them.  Update/enhance as needed.  Generated copy at http://allura.sourceforge.net/</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1558/</guid></item><item><title>Make sure markup doesn't show in scm code browser</title><link>https://forge-allura.apache.org/p/allura/tickets/1556/</link><description>Example at https://sourceforge.net/p/scmtestproject/git/ci/47af3847177772fe14ead831ed23012470951c50/tree/bar?force=True</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1556/</guid></item><item><title>Automatically install link to parent when creating subproject</title><link>https://forge-allura.apache.org/p/allura/tickets/1543/</link><description>When creating a subproject, we should automatically create a link tool back to the parent project</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Sat, 04 Apr 2015 07:26:50 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1543/</guid></item><item><title>SCM layer: computing diffs for a repo is very slow</title><link>https://forge-allura.apache.org/p/allura/tickets/1540/</link><description>Refreshing from scratch a repo with some 2000 commits takes around half an hour, both for git and hg. Most time is spent in "computing diffs" stage.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Sokolovsky</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1540/</guid></item><item><title>Change ticket bins (solr) to ticket filters (mongo)</title><link>https://forge-allura.apache.org/p/allura/tickets/1510/</link><description>The bin creation UI should be something like the general ticket edit UI, and rather than creating a SOLR query, it should create a list of mongo filters, and bin's should be based on mongo queries.

Our current "saved search" implementation should continue to exist, but for "realtime" buckets it should be deprecated in favor of "filters", which will actually be realtime since they are based on mongo data, not SOLR. 

Reasons: 

* all the saved searches we actually use (and all the ones I've seen in other projects) are just filters. 
* this will eliminate the need to make solr updates be "near real time" 
* improved UI for creating "bins" that are based on filters with no need for project admins to learn the underlying field names.

The UI should allow multi-select for $in operations, which should be a sufficient replacement for most OR uses.

We'll need to add several indexes for a lot of the common filters, possible examples:

* (app_config_id, milestone)
* (app_config_id, status)
* (app_config_id, status, milestone)  -- actually iirc, if this existed, the one above it would not be needed
* etc

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Fri, 01 Jul 2011 14:21:30 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1510/</guid></item><item><title>If artifacts comment was edited, this should be noted</title><link>https://forge-allura.apache.org/p/allura/tickets/1124/</link><description>For data integrity purposes, if a ticket, etc. comment was edited since creation, there should be notice "last edited DDDD by UUUU". nd maybe even add and display edit count.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Paul Sokolovsky</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1124/</guid></item><item><title>Prototype SCM stats</title><link>https://forge-allura.apache.org/p/allura/tickets/940/</link><description>Quick spike task (we should timebox it a bit) to investigate the possibilities of doing SCM stats. </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Mon, 12 Sep 2011 17:31:25 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/940/</guid></item><item><title>SCM - Write a 'clone this' bookmarklet that allows cloning to sf.net from github/bitbucket/etc projects</title><link>https://forge-allura.apache.org/p/allura/tickets/873/</link><description>The JS should be simple once we have [#872] completed</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Rick Copeland</dc:creator><pubDate>Sun, 21 Dec 2014 00:05:09 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/873/</guid></item><item><title>Discussion: re-encode HTML-only email input to markdown</title><link>https://forge-allura.apache.org/p/allura/tickets/386/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-05-17 20:12:45.922000
Assigned to:nobody

As a user, I would like to comment from via an email from a funky email client which sends HTML-only mail.  My comment should appear in a converted markdown from the HTML's content.

This should be kept low cost if possible, so a crude solution is fine.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sat, 10 Jan 2015 22:29:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/386/</guid></item></channel></rss>