<?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:"adobe"</description><language>en</language><lastBuildDate>Thu, 20 Aug 2015 22:07:57 -0000</lastBuildDate><item><title>Check on HTML tags allowed in Markdown</title><link>https://forge-allura.apache.org/p/allura/tickets/5316/</link><description>Whitelisted HTML tags are allowed in Markdown, but it seems that less are supported or they are handled differently now.  For example, see https://sourceforge.net/adobe/flexsdk/wiki/Flex%204/  This probably happened when we upgraded Markdown recently.  Check to see if its feasible to re-instate this support, particularly `&lt;div&gt;` tags with some styles which are useful for layout.  If it's not practical, we don't necessarily have to do it.</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/5316/</guid></item><item><title>Wiki preview is slightly narrower than actual</title><link>https://forge-allura.apache.org/p/allura/tickets/4250/</link><description>The following fits side-by-side on a wiki page with sidebar, but when previewing it, the 2nd div goes below the first.

~~~~
&lt;div class="grid-10"&gt;
blah 
&lt;/div&gt;
&lt;div class="grid-8"&gt;
blah
&lt;/div&gt;
~~~~</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/4250/</guid></item><item><title>Option to limit the tools shown in project list</title><link>https://forge-allura.apache.org/p/allura/tickets/4190/</link><description>The `[[projects]]` macro should support an option like ``grid_view_tools=git,wiki,tickets``  When in grid mode then only show the icons for those tool types.  Do a case-insensitive match against the tool types (not the mount point or label).


Update the help documentation also. Allura/allura/templates/neighborhood_help.html</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/4190/</guid></item><item><title>Neighborhood option to not show title area</title><link>https://forge-allura.apache.org/p/allura/tickets/4187/</link><description>The neighborhood admin form should have a checkbox which turns off the title area on the neighborhood landing page and neighborhood tools.  If the box is checked, the neighborhood name and logo will not be shown on those pages.  Projects pages will still have the standard title area.  Example: http://screencast.com/t/qKlVLH6VOntP</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/4187/</guid></item><item><title>Blog tool should be able to pull in rss feeds NEEDS CRON</title><link>https://forge-allura.apache.org/p/allura/tickets/4181/</link><description>The Blog/News tool should be able to pull in one or several external rss/atom feeds on a regular basis, convert new items' text or html to markdown, and create a regular entry in the tool.  The 'feedparser' package should be used for parsing feeds.  I don't know offhand what package can be used to convert html to markdown.

For the periodic fetching of rss feeds, the tool should expose a paster command via setup.py.  Then we can set up a cron job to run it.

Test with both a twitter rss feed, and a wordpress blog feed.  Make sure those work well.</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/4181/</guid></item><item><title>GA tracking for Neighborhood and projects</title><link>https://forge-allura.apache.org/p/allura/tickets/3970/</link><description>Gold-level neighborhoods and above should be able to enter a GA tracking ID for the neighborhood, and also for individual projects.  Then use techniques documented at http://code.google.com/apis/analytics/docs/tracking/asyncUsageGuide.html#MultipleCommands to set up the JS to use those additional ids.</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/3970/</guid></item><item><title>Create markdown macro for displaying RSS feeds</title><link>https://forge-allura.apache.org/p/allura/tickets/3717/</link><description>The following tag from Adobe's confluence wiki could not be supported when migrating to ForgeWiki:

    {rss:url= http://weblogs.macromedia.com/mxna/xml/rss.cfm?query=bySmartCategory&amp;smartCategoryId=41&amp;smartCategoryKey=2F0CC3A7-EA0D-20DF-DCD1A4D83A0ACA69|max=8|titleBar=false|showTitlesOnly=true}

This embeds a portion of an RSS feed into the wiki.  This would be a nice feature to support in ForgeWiki.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Cory Johns</dc:creator><pubDate>Wed, 04 Feb 2015 17:47:21 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/3717/</guid></item><item><title>Allow svn checkout customization - INI UPDATE</title><link>https://forge-allura.apache.org/p/allura/tickets/2692/</link><description>Our SVN checkout URLs always append /trunk since that is a common pattern, but it doesn't work with all projects.  Also, it doesn't work on new empty repos.

We could check to see if 'trunk' is present and if not, omit the 'trunk' append.  Additionally, it could be nice to let admins customize the checkout path to whatever they want.</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/2692/</guid></item><item><title>Add limit option to project list macro</title><link>https://forge-allura.apache.org/p/allura/tickets/2599/</link><description>It's hardcoded to 100 right now, should be configurable.</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/2599/</guid></item><item><title>Wiki macro for best-download</title><link>https://forge-allura.apache.org/p/allura/tickets/2598/</link><description>Resurrect the code for showing the best-download button from the old 'Home' tool (uses JS, from sfpy) and make it a macro, probably `[[download_button]]`</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/2598/</guid></item><item><title>Update projects macro to allow list display</title><link>https://forge-allura.apache.org/p/allura/tickets/2374/</link><description>only display_mode='grid' works now</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/2374/</guid></item><item><title>Don't show project icon placeholder</title><link>https://forge-allura.apache.org/p/allura/tickets/1532/</link><description>The gray project icon placeholder doesn't look very good.  So if there is no project icon, don't show the placeholder in the project header.  Just the project name.</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Dave Brondsema</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:56 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1532/</guid></item><item><title>SVN repo not showing full tree - NEEDS SCRIPT</title><link>https://forge-allura.apache.org/p/allura/tickets/1192/</link><description>The 1.5 release tag is not showing up in the code browser for SVN on the adobe SMP project: 

https://sourceforge.net/adobe/smp/svn/195/tree/tags/ or see attached

But when I checkout the code, and look at the tags directory we have it. 

         2:02:08 mark@:temp$ cd tags
         12:02:17 mark@:tags$ ls
         1.0gm		1.5gm		1.5rc2
         1.5-sprint-4	1.5rc1		neon_sprint_3
</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1192/</guid></item><item><title>Svn repo not showing logs anymore</title><link>https://forge-allura.apache.org/p/allura/tickets/1093/</link><description>https://sourceforge.net/adobe/smp/svn/

Still shows in analyzing state....</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Mark Ramm</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:54 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/1093/</guid></item><item><title>Add paging to the neighborhood home pages (/u/, /p/, /adobe/)</title><link>https://forge-allura.apache.org/p/allura/tickets/745/</link><description>As the # of users and projects grows, these pages are getting *really* big and will only get bigger -- page them to 25 or so projects per page.

Use this for inspiration: https://sourceforge.net/directory/</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/745/</guid></item><item><title>SCM: source code view for text files with non-standard extensions</title><link>https://forge-allura.apache.org/p/allura/tickets/725/</link><description>*Originally created by:* n_oostendorp

We should allow users to view any text file, reguardless of extensions, to test browse the TLF adobe project and view .as and .mxml files

eg https://sourceforge.net/adobe/tlf/svn/12/tree/trunk/textLayout/src/flash/text/ime/CompositionAttributeRange.as

Mark says we should be able to look at the "magic number" to tell the file type</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/725/</guid></item><item><title>markdown: extra spaces after links</title><link>https://forge-allura.apache.org/p/allura/tickets/633/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-06-22 16:50:02.868000
Assigned to:nobody
Using a markdown valid link you get an extra anchored whitespace after the link which is anchor wrapped, but not after.  We should trim whitespace from either side of anchor text.

ie [ Page Name ](/) &amp;lt;-- extra anchored whitespace</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/633/</guid></item><item><title>markdown: whitespace disappears in code blocks</title><link>https://forge-allura.apache.org/p/allura/tickets/629/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-06-22 15:41:00.555000
Assigned to:nobody
When I add a code block, it kills whitespace between lines:

	:::perl
	my @list = qw(a b c);
	my $noblankline = shift @list;
	
	my $previouslineshouldbeblank = pop @list;

Instead, it should preserve this space.

</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:53 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/629/</guid></item><item><title>gravatar display issues</title><link>https://forge-allura.apache.org/p/allura/tickets/628/</link><description>*Originally created by:* sf-overlords

Created by: noostendorp
Created date: 2010-06-22 15:35:54.115000
Assigned to:wolf
There are a few issues with the gravatar system i would like to fix:

- Gravatar hover should always show full name, not email address.  On project page ATM it's email, on wiki authors its full name.

- Gravatar defaults (the weird shapes) should never be shown.  If the gravatar is not set, use the users project icon.  If that is not set use the empty silhouette. 

- The gravatar should use the users email address which is listed on SF.net/account not @users.sf.net</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/628/</guid></item><item><title>Configure oembed</title><link>https://forge-allura.apache.org/p/allura/tickets/381/</link><description>*Originally created by:* sf-overlords

Created by: mramm
Created date: 2010-05-17 02:38:36.552000
Assigned to:dean
We should configure it so that embed#url links work in production. </description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Tue, 31 Mar 2015 20:50:01 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/381/</guid></item><item><title>Enforce some openness in permissions</title><link>https://forge-allura.apache.org/p/allura/tickets/173/</link><description>*Originally created by:* sf-overlords

Created by: mramm
Created date: 2010-04-03 21:48:49.225000
Assigned to:nobody
Projects and artifacts should be readable by anon, and it should be impossible to remove that perm, except in limited time spans, for security issues or what not. 


  1. Adobe wants to have private/hidden projects (30day from project creation max)
  1. The length of time something will probably eventually be a neighborhood wide setting. 



</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Thu, 20 Aug 2015 22:07:55 -0000</pubDate><guid>https://forge-allura.apache.org/p/allura/tickets/173/</guid></item></channel></rss>