Advertisement
Tag Archives: Allura

JAXenter Puts Spotlight on Apache Allura in Interview with VP and SourceForge Chief Engineer Dave Brondsema

JAXenter recently put the spotlight on Apache Allura by interviewing SourceForge Principal Engineer and VP at Apache Allura, Dave Brondsema. With this interview, JAXenter sought to get a better idea of what Apache Allura is all about and what makes it different from other software forges.

In the interview, Dave Brondsema begins by talking about the main idea behind Apache Allura, which is a flexible open source hosting platform primarily designed to run all the tools needed in a software development project. Written in Python, it was initially developed at SourceForge and is currently the biggest deployment of Allura for all open source projects here.

According to Dave, Apache Allura is differentiated from other software forges due primarily to its flexibility, both for users and system administrators. Projects can choose which tools to use and how to name them, or have several of each with fine-grained permissions. Allura’s architecture also makes things extensible and pluggable. With each tool basically a plugin, anyone can develop their own, build on top of core functionality and cross-link between tools. Dave goes on to identify other extension points, as well as what added features he’s currently working on.

Asked about the future of Allura, Dave states that like most open source projects, they don’t have a specific roadmap but anyone willing to help with contributions is very welcome.

Click here to read the full interview.

Project upgrades: Inactive projects

Over the coming days, we’ll be starting the process of upgrading projects which have not yet upgraded to the new SourceForge platform. We’re starting with projects which have been inactive for the longest period of time, and moving forward from there. This will allow us to further test and streamline the bulk upgrade process, as well as speed the process of moving us off of the old platform.

Rest assured that if your project has had activity within the last year, we’re not going to upgrade them at this time. There will be a further communication with individual projects once we get that far. However, if you’ve been waiting to upgrade, now is the time to go ahead and do it before we get to you.

If there’s a particular issue that is keeping you from upgrading, we need to hear about it soon, so that we can address it quickly. Several of the issues that various projects had been waiting for have been resolved in recent weeks, so you may wish to check back on the tickets where your particular item of concern is being tracked.

If you’re ready to upgrade, you can do so on the project upgrade page.

Searching for tickets

Note: This article refers to projects on the new SourceForge platform. You should upgrade if you haven’t already.

If you’re searching your project’s tracker for a ticket, you have a single text field in which to enter your search, and you may be unaware of the rich syntax that’s available for crafting searches.

For the full details, click the “Help” button on any search results page:

Screen Shot 2013-02-08 at 3.25.47 PM

But the purpose of this blog post is to show you a few simple examples so that you’re aware of what’s possible.

First, if you just enter a keyword, you’re searching for that word in the title or description of a ticket. While that may be sufficient if you only have a few tickets, it quickly becomes unmanageable.

The next thing you need to know is what fields you can investigate. Here’s the complete list:

User who owns the ticket – assigned_to
Labels assigned to the ticket – labels
Milestone the ticket is assigned to – _milestone
Last modified date – mod_date_dt
Body of the ticket – text
Number of ticket – ticket_num
User who created the ticket – reported_by
Status of the ticket – status
Title of the ticket – summary
Votes up/down of the ticket – votes_up/votes_down (if enabled in tool options)
Votes total of the ticket – votes_total
Imported legacy id – import_id
Custom field – the field name with an underscore in front, like _custom

Any field can be included in a search query. So if you wanted to search for tickets about ‘fishing’ that aren’t closed, you can do:

summary:fishing AND !status:closed

You can combine more complex searches by using parentheses:

summary:export AND !(status:closed OR status:wont-fix)

If you use labels (aka tags) on all of your tickets, this can also be a great way to find the tickets that you want:

labels:community AND (status:open OR status:in-progress)

If you want to know what your project worked on in a particular week, you can use a mod_date_dt search to look for tickets that were modified in that time range:

mod_date_dt:[2013-02-04T00:00:00Z TO 2013-02-08T23:59:59Z]

Finally, if you use a particular search a lot, you can save it for later use. Click on “Edit Searches” in the left sidebar, and then “Add Bin” at the bottom of that page. Give it a name, and put your search terms into the ‘Terms’ field.

There’s more you can do with searches. As I mentioned above, click the ‘Help’ button for the docs. For the exhaustive docs, see the Lucene query syntax tutorial on SolrTutorial.com.

Who’s upgrading?

I get asked a few times a week for examples of projects that have already upgraded to the New SourceForge. Here’s some of the projects that have upgraded so far this month.

  • MinGW – Minimalist GNU for Windows

    MinGW: A native Windows port of the GNU Compiler Collection (GCC), with freely distributable import libraries and header files for building native Windows applications; includes extensions to the MSVC runtime to support C99 functionality.

  • Fuduntu

    Punny Name Serious Distro! Optimized for portable computers. Fuduntu includes the latest stable kernel, Chromium, Integrated Adobe Flash and Fluendo MP3 codecs, Thunderbird, Pidgin, and VLC. Available for immediate installation after installing are packages important to many “desktop focused” users including Steam and Netflix!

  • Pidgin

    See http://pidgin.im/about/ for more information. Pidgin is an instant messaging program which lets you log in to accounts on multiple chat networks simultaneously. It runs on Windows, Linux, and other UNIX operating systems. Pidgin is compatible with the following chat networks out of the box: AIM, ICQ, Google Talk, Jabber/XMPP, MSN Messenger, Yahoo!, Bonjour, Gadu-Gadu, IRC, MXit, Novell GroupWise Messenger, Lotus Sametime, SILC, SIMPLE, MySpaceIM, and Zephyr. It is written in C and makes heavy use of GLib and GTK+. Finch is a command line instant messaging program. It also lets you log in to accounts on multiple chat network simultaneously, and it is compatible with the same chat networks as Pidgin. It is written in C and makes heavy use of GLib and ncurses.

  • qBittorrent

    An advanced and multi-platform BitTorrent client with a nice Qt4 user interface as well as a Web UI for remote control and an integrated search engine. qBittorrent aims to meet the needs of most users while using as little CPU and memory as possible.

  • SugarCRM – commercial open source CRM

    A complete CRM system for businesses of all sizes. CRM helps your business gain and retain customers. Core CRM functionality includes sales automation, marketing campaigns, support cases, email, calendaring and more. Developers can easily extend the application with new CRM functionality unique to your business. Built in PHP, supports MySQL and SQL Server.

  • SleepyHead

    Open-source, cross platform, sleep tracking software with a focus on monitoring CPAP treatment.

  • Workrave

    Workrave is a program that assists in the recovery and prevention of Repetitive Strain Injury (RSI). The program frequently alerts you to take micro-pauses, rest breaks and restricts you to your daily limit.

  • ISPConfig Hosting Control Panel

    ISPConfig – ISP management and Hosting Control Panel. ISPConfig manages one or more webservers, mailservers, BIND DNS server, FTP servers, MySQL databases and virtual Servers with an easy to use webinterface for administrators, resellers and clients.

  • Stunt Rally

    Holds only newer Releases (from 1.2). Visit homepage on http://code.google.com/p/vdrift-ogre/

  • NSClient++

    NSClient++ is a windows service that allows performance metrics to be gathered by Nagios (and possibly other monitoring tools). It is an attempt to create a NSClient and NRPE compatible but yet extendable performance service for windows.

Allura feature highlight – Artifact Linking

A very cool feature in the new SourceForge (Allura) that we haven’t touted enough is artifact linking. The ability to link to other parts of the forge is available in every Allura tool, providing tight integration between the various aspects of your project.

Any forge resource (“artifact”) can be linked with surrounding square brackets, e.g. [MyPage] or [#123]. These artifact links can take several forms.

Simple Links

Most commonly, the artifact identifier can simply be surrounded with square brackets. Here are some examples:


[MyWikiPage] # Wiki - name of wiki page
[#123] # Tracker - ticket number
[r10721] # SVN - revision number
[3b9d48] # Git & Mercurial - first 6 characters of revision hash
[2012/02/my-post] # Blog - post slug, including YYYY/MM/ prefix
[a6d38f98] # Discussion Thread - thread id
[a6d38f98#42f8] # Discussion Post - thread_id#post_id

Two-part Links

To link to an artifact in a specific tool, use the form: [tool:artifact], where tool is the name of the tool as it appears in the URL. Two-part links are useful when you have two tools of the same type installed. For example, let’s say you have a ‘bugs’ tracker and a ‘features’ tracker installed, and you want to link to the first ticket in each:


[bugs:#1]
[features:#1]

Put a tracker artifact link in a commit message to link that message to the ticket in the code browser.

Three-part Links

To link to an artifact in another project, use the form: [project:tool:artifact], where ‘project’ is the name of the project as it appears in the URL. For example:

[allura:wiki:Home]

To link to an artifact in a subproject, use the form: [project/subproject:tool:artifact], where ‘subproject’ is the name of the subproject as it appears in the URL. For example:

[allura/sub:code:3b9d48]

Back-links

Any time that you link to an artifact, that artifact will automatically link back. For example, if you link from ticket #2 to ticket #3, ticket #3 will automatically have a ‘Related’ section added to it, with a link back to ticket #2. Similarly, if you link to a ticket from a wiki page, that page will have a link back to the ticket.

Inline documentation

In any editing environment (ie, if you’re editing a blog post or a wiki page) you’ll see a “Formatting Help” button that will give you a pop-up help window with formatting instructions. That includes artifact linking, as well as all other aspects of formatting in Markdown.