<?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:"sf-current"</description><language>en</language><lastBuildDate>Thu, 28 Apr 2016 20:15:30 -0000</lastBuildDate><item><title>Remove Google Code importers</title><link>https://forge-allura.apache.org/p/allura/tickets/8054/</link><description>Google Code is in archive mode, so importers as they are now don't work - and some tests fail too.  Supporting the archive format would be nice, but at least for now we should just remove the importers.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Wed, 27 Jan 2016 18:43:59 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8054/</guid></item><item><title>API support for attachments in export</title><link>https://forge-allura.apache.org/p/allura/tickets/8052/</link><description>* after [#8051], update API to support the new attachments param
* update API docs
* republish API docs</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 25 Jan 2016 17:09:58 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8052/</guid></item><item><title>Backend support for attachments in exports</title><link>https://forge-allura.apache.org/p/allura/tickets/8051/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Wed, 09 Mar 2016 21:44:07 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8051/</guid></item><item><title>Allow removing a milestone from a ticket</title><link>https://forge-allura.apache.org/p/allura/tickets/8050/</link><description>Currently after putting a ticket into a milestone, there's no way to remove it from the milestone.

https://sourceforge.net/p/forge/feature-requests/4/</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 25 Jan 2016 17:04:28 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8050/</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>API for current site notification</title><link>https://forge-allura.apache.org/p/allura/tickets/8044/</link><description>Expose the current site notification (i.e. `ThemeProvider.get_site_notification` logic) as an API.

The `request.cookies` might be able to stay as it is, but likely should support those values being passed in as regular API params.  The `response.set_cookie` probably should be returned as response values.

Make sure the RAML api docs are updated.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Wed, 27 Jan 2016 17:43:01 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8044/</guid></item><item><title>Better handing of tmp dirs during merge</title><link>https://forge-allura.apache.org/p/allura/tickets/8042/</link><description>Doing a one-click merge of a very large repo can potentially cause problems if the working dir is bigger than the tmp dir mount supports.

* `def merge` can use a try/finally so that `shutil.rmtree` always runs even if the clone fails (e.g. out of disk space)
* see if its possible to a shared clone (see also `_shared_clone`) so the object files don't have to get copied, reducing disk usage and execution time.

It'd be nice if we could set a max size limit and check that in `can_merge` or `merge_allowed` but it doesn't seem to be a way to check the size of a working copy ahead of time.  There is `git count-objects -vH` but that's just the repo size, not the working copy.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Wed, 27 Jan 2016 20:43:32 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8042/</guid></item><item><title>Upgrade SimpleMDE and contribute our toggleCodeBlock</title><link>https://forge-allura.apache.org/p/allura/tickets/8040/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 28 Apr 2016 20:15:30 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8040/</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>Easy way to view all posts from a certain user, and flag as spam</title><link>https://forge-allura.apache.org/p/allura/tickets/8020/</link><description>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.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Wed, 27 Jan 2016 17:17:46 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8020/</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>Subprojects not checked for 'deleted' flag</title><link>https://forge-allura.apache.org/p/allura/tickets/8005/</link><description>Subprojects don't get their 'deleted' flag checked, so they are still accessible to non-admins.  We should fix this.

Also, if there is a deleted subproject and a regular tool of the same name, the regular tool should always take precedence.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Mon, 28 Mar 2016 16:19:06 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/8005/</guid></item><item><title>Remove old tool configuration page</title><link>https://forge-allura.apache.org/p/allura/tickets/7921/</link><description>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.
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Heith Seewald</dc:creator><pubDate>Fri, 05 Feb 2016 19:12:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/7921/</guid></item><item><title>Add attachments to Export [ss5383]</title><link>https://forge-allura.apache.org/p/allura/tickets/6662/</link><description>[forge:site-support:#5383]

&gt;I like the new Project Data Export feature, but what about attachments to wiki, ticket, or discussion items? Not that I really want these encoded into a JSON file, but this isn't really a complete "copy for safekeeping" if the export only has URLs to sourceforge.net for any attached images, patch files, etc.

1. We should put the attachments in a separate folder
2. We should make attachments optional, so folks won't get an enormous backup if they don't want it</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Tsai</dc:creator><pubDate>Wed, 09 Mar 2016 21:43:49 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/6662/</guid></item></channel></rss>