[allura:tickets] #7312 NetBeans Allura Ticket System Support
--- ** [tickets:#7312] NetBeans Allura Ticket System Support** **Status:** open **Milestone:** limbo **Labels:** NetBeans **Created:** Fri Apr 04, 2014 11:22 AM UTC by Puce **Last Updated:** Fri Apr 04, 2014 11:22 AM UTC **Owner:** nobody I created an issue for NetBeans to support the Allura Ticketing system: https://netbeans.org/bugzilla/show_bug.cgi?id=243557 I created this issue to track that 3rd part issue. Maybe the Allura team could contribute this Allura integration. --- Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
[allura:tickets] #7168 Wiki macro to load content from repository
- **status**: code-review -- closed - **Milestone**: limbo -- forge-apr-18 --- ** [tickets:#7168] Wiki macro to load content from repository** **Status:** closed **Milestone:** forge-apr-18 **Labels:** for-community 42cc **Created:** Wed Feb 12, 2014 05:36 PM UTC by Chris Tsai **Last Updated:** Thu Apr 03, 2014 10:09 AM UTC **Owner:** nobody It would be really nice to have a wiki macro that could pull content from a repository. If we had this, we could include general end-user usage docs of the Allura platform (as opposed to the more operator geared docs at allura.sf.net), which would be distributed along with the Allura platform. This would also make it easier for general Allura docs to live side-by-side in a wiki that also contains more site specific information (like SourceForge). I believe this would also be a viable alternative to feature requests such as https://sourceforge.net/p/forge/feature-requests/58/ and https://sourceforge.net/p/forge/feature-requests/31/ --- Sent from sourceforge.net because dev@allura.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/ To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options. Or, if this is a mailing list, you can unsubscribe from the mailing list.
Re: Plans for pycon sprints
On 4/4/14 3:37 PM, Olemis Lang wrote: Hi ! :) On 4/4/14, Dave Brondsema d...@brondsema.net wrote: I am going to be at the development sprints after PyCon and plan on working on Allura. I am hoping to focus on some issues that have arisen from more new people trying out Allura for the first time. I've started tracking those tickets with this label: https://sourceforge.net/p/allura/tickets/search?q=labels%3Agetting-started Looks very useful indeed ... I looked at sprints page [1]_ few days ago I did not find Allura . I think several other committers will be at PyCon too. Look forward to meeting up. I will be there and I'm hoping to have some time to go beyond Apache(tm) Bloodhound and Brython (should a sprint be organized for those projects) . Cool, we should try to get the Bloodhound and Allura tables near each other. By the time I estimate I'll have a macbook with Mac OS Mavericks , so I'd appreciate if some instructions could be provided for performing such dev mode installation on that platform as fast as possible (= and yes , it's a newbie question but please bear with me , now I'm very busy preparing for PyCon and it's possible that I'll be mostly offline in the next few days ... ) The vagrant install is easiest: https://forge-allura.apache.org/p/allura/wiki/Install%20and%20Run%20Allura%20-%20Vagrant/ I've run the INSTALL.markdown on native OSX and it works fine too (skipping the SVN parts, since pysvn is a pain). -- Dave Brondsema : d...@brondsema.net http://www.brondsema.net : personal http://www.splike.com : programming
