Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Ruby microservices community practices
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
  1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Chris Beer  
View profile  
 More options Jun 9 2011, 4:48 pm
From: Chris Beer <beerc...@gmail.com>
Date: Thu, 9 Jun 2011 13:48:27 -0700 (PDT)
Local: Thurs, Jun 9 2011 4:48 pm
Subject: Ruby microservices community practices
Here are some proposed practices for releasing Ruby implementations of
microservices.

First, the gems should reside under the "microservices" organization
of github [1]. Text documentation should be marked up using the
textile format.

The gem should contain a README with a brief description of the
specification, a link to the appropriate spec (and version), and a
brief section containing usage examples.

We prefer implementations to be licensed using the Apache Public
License v2.

Optionally, a TODO file may live in the root of the project containing
next steps for the gem implementation.

Gems should be documented using YARD-style method documentation.

Gems should be tested using rspec, and should include an rcov coverage
task.

For integration with the continuous integration server, include a
'hudson' task that runs the tests, generates documentation, and
coverage reports.

The Lockit gem contains a simple Rakefile [2] that you may want to use
as a template.

Gems should be versioned using Semantic Versioning, and released to
rubygems frequently.

[1] https://github.com/microservices
[2] https://github.com/microservices/lockit/blob/master/Rakefile


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »