[D7] RESTWS Alias

We are currently quite busy with all the project applications and we prefer projects with a review bonus. Please help reviewing and put yourself on the high priority list, then we will take a look at your project right away :-)

Also, you should get your friends, colleagues or other community members involved to review this application. Let them go through the review checklist and post a comment that sets this issue to "needs work" (they found some problems with the project) or "reviewed & tested by the community" (they found no major flaws).

I'm a robot and this is an automated message from Project Applications Scraper.

I'm using this on http://dev.bioconnector.virginia.edu and confirm that http://dev.bioconnector.virginia.edu/content/introduction-pubmed-online-... now links correctly as does http://dev.bioconnector.virginia.edu/content/introduction-pubmed-online-... - very cool - I've been looking for this functionality for almost a year now, and am very grateful for the work that jaskaran.nagra has done here :)

Removing review bonus tag, you have not done all manual reviews, you just posted the output of an automated review tool. Make sure to read through the source code of the other projects, as requested on the review bonus page.

@klausi - my bad, while I am using this on 2 production sites, I haven't completed the review bonus work yet. thanks for the feedback

Once a project is moved to RTBC, then a git administrator has the chance to perform a final review. There are a lot of applications in the backlog, so one way we use to prioritize things is to use the bonus tag.

1. This doesn't follow code standards. Inline comments should begin with only slashes, even if they are multi-line comments i.e. //
   

   function restws_alias_path_add_format($path, $format) {
   
     /*
      * Check if any format is added to the path.
      * Not checking just $format to avoid .json.rdf.xml type paths.
      */

However, that isn't a blocker. Thanks for your contribution, Jaskaran Nagra!

I updated your account so you can promote this to a full project and also create new projects as either a sandbox or a "full" project.

Here are some recommended readings to help with excellent maintainership:

• Dries' post on Responsible maintainers
• Best practices for creating and maintaining projects
• Maintaining a drupal.org project with Git
• Commit messages - providing history and credit
• Release naming conventions.
• Helping maintainers in the issue queues

You can find lots more contributors chatting on IRC in #drupal-contribute. So, come hang out and stay involved!

Thanks, also, for your patience with the review process. Anyone is welcome to participate in the review process. Please consider reviewing other projects that are pending review. I encourage you to learn more about that process and join the group of reviewers.

Thanks to the dedicated reviewer(s) as well.

Let's leave it a t fixed, the issue will close automatically in 2 weeks.