Archive | Site News RSS for this section

Feature Enhancement: Including Repository Content into Wiki

We’ve just rolled out a new feature which enhances the [[include]] wiki macro in Apache Allura (which powers SourceForge projects). Before this addition, the macro has typically used to include the contents of a different wiki page into the current page. This has now been expanded to to allow a file in a (SVN, Git, or Mercurial) repository to be the import source. We expect this will particularly useful for projects that like to keep their documentation in their repository, but also want it to be easily accessible from the web in a wiki.

Here’s an example of how this might work:

Let’s say I want to include this example document written in Markdown into a wiki page.

I go to the edit mode for the wiki page, and enter this macro:

[[include repo=git]]


Note: for the “repo”, you need to specify the name (ie., mount point) of the repository, not the type. In my example, the name of the repository is “git”.

And that’s it! You can now see the contents on the wiki page:

Of course, this feature works with SVN, Git, and Mercurial repositories on the SourceForge site. Another benefit of this feature, is that the import module supports a variety of formatting languages, so you’re no longer limited to just Markdown.

The format is detected by the file extension, we support the following:

Markdown: .md, .mkd, .mkdn, .mdown, .markdown
Textile: .textile
Creole: .creole
ReST: .rst, .rest, .rst.txt, .rest.txt

Source code file extensions (eg., .c and .py) will be syntax highlighted, but will otherwise be unformatted. All other file extensions will be rendered as plain-text. Binary files, of course, can’t be displayed.

Apache Allura Becomes Top-Level Project!

feather-smallThe Apache Software Foundation just announced Apache™ Allura™ as a Top-Level Project.

We are excited to see Allura finally put in the Olympus of Apache Top-Level projects. It has been an amazing journey, we launched the Allura project four years ago and just two years ago Allura was incubated at the ASF.

It has been an honor and a great pleasure to work with the Apache community, and we look forward to engage more and more with all developers interested in using and enhancing Apache Allura! Below a collection of quotes from people who have been participating, sponsoring and supporting the graduation process.

“The journey through the Apache Incubator made Allura a project for the community by the community,” said Dave Brondsema, Vice President of Apache Allura. “I can’t wait to see other Apache projects start using Allura, and hope to catch up with other Apache projects at the upcoming ApacheCon 2014 in Denver!”

“SourceForge has demonstrated their dedication to Open Source by putting their crown jewels into the custodianship of the Apache Software Foundation, and I’m excited to see where the project goes next as it embraces a larger community of users and developers,” said Rich Bowen, Executive Vice President, Apache Software Foundation.

“BerliOS recommends the SourceForge platform for migrating projects currently hosted on BerliOS. We value the fact that the SourceForge platform was first accepted as an Apache Incubator project and we are glad to see it now graduated,” said Lutz Henckel, berliOS project leader. “This achievement means SourceForge platform –now known as Apache Allura– is backed by a diverse and well-structured community. For projects hosted on SourceForge it also reduces the risk of vendor lock-in, as developing projects can get their data and software directly from the platform.”

“Apache Allura is an Open Source modular forge platform using a scalable architecture and with well-known technologies around Python,” says Alvaro del Castillo, Apache Allura committer and CTO of Bitergia. “It is easy to install and configure, a good bet for the future of collaborative software development around forges.”

“We entered the Allura community to suggest the introduction of new functionalities to improve awareness of people and projects. We found that the community was open to our ideas,” said Elisabetta Di Nitto, Associate professor of the University of Milan. “As a researcher I think this was a very interesting experience. We are glad we could influence the development of the forge and that the Allura community found our suggestions useful.”

“SourceForge is very happy that Apache Allura, already used by 431,000 projects, will now be extended and available to an even wider developer community,” said Gaurav Kuchhal, General Manager of SourceForge and Slashdot. “We stay committed to promoting open source projects by providing free marketing and global distribution, no matter where projects are developed.”

Read the full press-release at the Apache blog. See you there!

Project of the Month Changes…

Hi folks,

As most of you know, we have been doing a Project of the Month on SourceForge since October of 2002. When we feature a project, it’s a little like the Colbert Bump, projects get some visibility, and often, good things happen for these projects.

Starting this month, we are making a change in the program. We have recently returned to a Project of the Month voting process where you in the community have the power to select a project from a set of nominees we draw based on project growth, releases, and other data. This project is the “Community Choice.”

We are adding an additional project that is selected by our team, we’re calling the “Staff Pick.” Simply put, a member of our team generally comes across a project they have used, one they love, or one that solves an interesting problem. We consider such nominations from our team and pick one to highlight.

Both projects will get featured on the SourceForge front page. As well, we’ll do a blog post about them both, and continue to track them in our running PoTM historical list. As usual, we’ll also mention these in our monthly newsletter.

Many thanks to you all for your contribute to OSS; the Project of the Month has become what is is because of your contributions to making software that is important to you and that others love.

API Improvements: Bearer Tokens & Project Admin

Today we have launched some improvements to the API to allow you to more easily have programmatic access to your project data.  Bearer tokens are an extension to the existing OAuth negotiation that makes it vastly easier for your program to access the API.  Additionally, the API can now be used with the project data export launched in September to easily make regular backups of your project’s data, as well as now being able to install new tools for a project programmatically.

Bearer Tokens


On the OAuth tab under your Account settings, you can now generate a bearer token for any registered OAuth application.  These tokens are pre-negotiated, so your application doesn’t need to deal with the multi-step OAuth verification process and can just include the token in the access_token parameter to any HTTPS GET or POST request to the API.  Note: because these tokens grant all of the access rights of your account, you should protect them carefully and revoke any that you are no longer using.  More information on using bearer tokens, including example code, is available on the wiki.

Project Admin API

The project data export feature can now be accessed via the API, so you can schedule a project export, check the export’s status, and download the exported data, all programmatically.  There is even a drop-in script ready to do all of these steps for you.

Additionally, you can now install new tools, such as new repositories or ticket trackers, into your project via the API.  More information is available on the wiki.

New Feature – Forum Stats

We’re pleased to announce a new feature for all discussion forums on SourceForge: a graph of forum post statistics.  Check it out!  Here’s an example of what it looks like on the 7-Zip forums.

Screenshot of Forum Stats