Tag Archives: updates

Enhanced Project Reviews Functionality

SourceForge has enhanced its review and rating system over the past several months. This involves moving from our current Thumbs Up/Down recommendation system to a more robust 5-star review system. We believe the new system allows users a more expressive way to rate and review a project and gives our projects a better understanding of their reviews.

We have performed this move to the new system in stages. With our last update, the number of ratings weren’t matching the numbers of reviews because we were displaying the old recommendation counts. Today we have released an update to display the individual ratings in the same way we were displaying the recommendations and also fixed several minor issues. We believe this will make for a great review and rating experience for users and project administrators.

Project rating break down.

Project rating break down.

With this latest update, we have mapped all the previous Thumbs Up ratings to 5-star ratings and all the previous Thumbs Down to 1-star ratings. This will create the base for the average rating score you will see for your project. You will notice in the image above that you are only seeing mostly 5 or 1 star ratings.

Filter reviews easily.

Filter reviews easily.

As project owners on SourceForge, as ratings begin to fill out, you will be able to get a detailed understanding of how people feel about your project. You will of course also see the reviews associated with each rating and be able to clearly identify the experiences that are common between a 5 or 4 star rating and a 2 or 1 star rating. The advantage here is narrowing the information down and getting specifics about what is making your users happy and what is not.

Browsing for projects

Browsing for projects

Also, this will not change how the search and browse rankings that projects currently receive work. Internally ratings of 3-star or higher become a +1 and ratings of 2-star or lower become a -1 and those rankings will still be calculated in the exact same way we calculate them now; using lower bound of the Wilson score confidence interval for a Bernoulli parameter (you can read about it here).

We would love your feedback on how to keep enhancing this Reviews experience on SourceForge, so leave a comment or drop a line to CommunityTeam@sourceforge.net.

Project Navigation UI Update

A long awaited update is finally here. Since we’ve started moving projects to the new platform, there’s been an inconsistency between the project navigation bars between different project pages. This has now been addressed, and the navigation bar looks the same across the various project pages. To give you an idea of how different the navigation was,

Before:

Summary page

before_summary

Tickets page

before_tickets

After:

Summary page

after_summary

Tickets page

after_tickets

 

Ah, that’s much better. And it’s not just the styling that’s changed, if you look closely at the actual items in the old navigation bar, a few items (Summary, Files, etc.) might appear in one place, but not the other, or their order may differ. This has now been fixed so that the navigation bar contents will always match. We also revamped the space above the nav bar to be more appealing (and consistent between tools).

Finally, a shortlist of some other navigation improvements that have been made in recent weeks:

  • Similar tools are grouped together to save space in the navigation bar (the threshold is configurable on Admin -> Tools)
  • Drop down menus for grouped items
  • Capitalization is now consistent with the label setting

Platform updates

With the platform upgrade process nearing completion, the folks in Engineering are starting to turn their sights back to site improvements, and here are just a few of the things that they’ve done in the last couple of weeks.

Bulk editing of tickets is a way to make a lot of changes very quickly. Unfortunately, if you edited 50 tickets, you’d get 50 email messages telling you what changed. Now, just one message will be sent with a summary of what has changed.

With the upgrade to the latest version of Solr, tool search results (for tickets, wiki pages, forums, blog posts, etc) now shows the date the item was last changed, and has an option to sort by date instead of relevancy. Additionally, search results will have keywords highlighted.

Code snapshots have been changed to zip files, to make them work better for windows users.

Repository names can now contain . and _ and + characters. We did this primarily for projects that are upgrading, but could be useful for anyone.

A while ago we added the ability to collapse multiple tools of the same type (ie, several repositories, or several trackers) into a single menu item which linked to a list of those tools. We’ve now added a drop-down menu of those items as well, to save you some time in navigating to a resource.

Platform Updates: members, tags and user search

As I mentioned in the last platform updates post, we’re primarily focused on upgrade-related work lately, but we found time to put in a few enhancements to the platform in the last sprint.

A new macro was added to the wiki syntax. Putting [[members]] in a wiki article will produce a list of all the members of the project. By default, this is limited to 20 members, with a link to a full list if you’ve got more than that. You can link directly to that longer list, if you like. For example, here’s TikiWiki’s full list of developers.

Screen Shot 2013-04-19 at 11.01.19 AM

Next, the interfaces for adding tags to tickets was improved to make it easier to find tags that you’ve already used. Starting to type a tag will produce a dropdown of tags from which to select.

Screen Shot 2013-04-19 at 11.04.26 AM

And, we’ve added a $USER variable that you can use in ticket searches, which will be replaced, at search time, with the currently-active user. For example, if you search for reported_by:$USER, the variable $USER, you’ll get all the tickets reported by the currently logged in user. In this way, you can add a saved search to your ticket tracker so that each user can keep tabs on their own tickets.

So, if you look at the Allura ticket tracker, you’ll see a new “My Tickets” button under “Searches”, which will show you the tickets you’ve opened. (Of course, you’ll have to be logged in for that to work.)

We’re really looking forward to being done with the upgrade process, so that we can focus more on improving the developer experience, and we’d love to hear your feedback on what we should work on next. You can see what’s scheduled for upcoming sprints, and vote on tickets, in the Allura ticket tracker.

Platform update: Download snapshot

As of this morning, you’ll notice a new feature in the SourceForge code browser. It’s pretty self-explanatory.

Screen Shot 2013-04-04 at 9.55.14 AM

Clicking on the ‘Download Snapshot’ link will generate a tarball (tar.gz file) of the revision that you’re looking at. This snapshot is generated on the fly, so you’re certain to get the latest cut, but we cache that snapshot so that someone else requesting the same tarball won’t have to wait for it to generate.

If you’re interested, you can see the ticket and some of the implementation details in the ticket tracker, and you can see what else is coming down the road by perusing the upcoming milestones, also in the ticket tracker, and vote for stuff you’d like to see happen a little sooner.