Archive | Site News RSS for this section

Find WordPress Themes You Need at SourceForge, and more!

wordpress-logo-simplified-bgAt SourceForge we work hard to make sure that visitors get the best search experience at SourceForge, that’s why we try to make easy to also find other great Open Source software developed elsewhere. Today we are proud to announce the SourceForge WordPress Themes Collection. It is a collection of free and popular WordPress themes, compatible with a theme editor for visually customizing those themes and their CSS. We will continue to update and expand this collection with time.

We look forward to your feedback. We’d like to learn more about how we can continue to improve the SourceForge experience for WordPress bloggers.

SourceForge Forced Password Change

On 2014-05-22, we triggered a forced password change for SourceForge users.

  • We have adopted a longer minimum password length standard.
  • There has been a change in our authentication layer, moving to a more modern Open Source platform.
  • Password hashing algorithm and key length has changed.
  • Forced password reset has occurred sitewide to ensure all stored password hashes meet these stronger standards.
  • All site users have been sent email asking for password change.
  • There has been no known breach or compromise of our systems.

SourceForge.net Password Reset Required

Greetings,

To make sure we’re following current best practices for security, we’ve made some changes to how we’re storing user passwords. As a result, the next time you go to login to your SourceForge.net account, you will be prompted to change your password. Once this is done, your password will be stored more securely. We recommend that you do this at your earliest convenience by visiting the SourceForge website and logging in.

And, as always, be vigilant about password security. Use a secure password, never include your password in an email, and don’t click on links for unsolicited password resets.

If you have any concerns about this, please contact SourceForge support at sfnet_ops@slashdotmedia.com

Best regards,
SourceForge Team

Feature Enhancement: Quick Ticket Filtering

We’ve recently added a new feature to make it easier to sort and filter tickets. Now, as an alternative to the existing filtering methods, clicking on a column header in a ticket view will allow you to select checkboxes to quickly filter the ticket list.

Filtering by Search

Previously, to filter tickets, the only way to do that was to use the search function.

Let’s use these test tickets as an example. I want to filter my ticket view to include only tickets with status “open”, owned by my test account “sillygoose”, in milestone “3.5″. To do this, I would enter this into the search function:

status:open AND assigned_to:sillygoose AND _milestone:3.5

It works, and it works well, but I have to remember (or look up) the different search terms.

New Quick Filtering

filter_ticketsLet’s try this again using the new method. To accomplish the same thing, just click “Status”, check “Open”; click “Owner”, select “sillygoose”; click “milestone”, select “3.5″. And voila, the tickets are filtered.

Advanced Filtering

Of course, this new feature doesn’t mean that the existing ticket search syntax isn’t still useful. If you need to do more advanced ticket filtering, the search function is more powerful (and you can save these searches for future re-use).

Here’s a couple examples that can only be done with the advanced search syntax:

* For list of tickets that are either unread (regardless of assignee) or any ticket that’s not closed and assigned to you, you could use the following search:
status:unread OR (!status:closed AND owned_by:$USER)

* For a list of tickets that were created between 2-5 years ago, and have been modified with the past three months:
created_date:[NOW-5YEARS TO NOW-2YEARS] && mod_date:[NOW-3MONTHS TO NOW]

We now have the best of both worlds, a few clicks is all it takes to do some quick filtering, but there’s still the power and flexibility of the advanced search when you need it.

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 path=example-documentation.md]]

include_demo

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: https://sourceforge.net/p/uberproject/wiki/include_demo/

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.