<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet type="text/xsl" media="screen" href="/~d/styles/atom10full.xsl"?><?xml-stylesheet type="text/css" media="screen" href="http://feeds.feedburner.com/~d/styles/itemcontent.css"?><feed xmlns="http://www.w3.org/2005/Atom" xmlns:feedburner="http://rssnamespace.org/feedburner/ext/1.0" xml:lang="en-US">
  <id>tag:www.opensourcerails.com,2005:/projects</id>
  <link type="text/html" rel="alternate" href="http://www.opensourcerails.com" />
  
  <title>Open Source Rails</title>
  <updated>2009-07-03T13:46:58-07:00</updated>
  <link rel="self" href="http://feeds.feedburner.com/OpenSourceRails" type="application/atom+xml" /><feedburner:emailServiceId>OpenSourceRails</feedburner:emailServiceId><feedburner:feedburnerHostname>http://feedburner.google.com</feedburner:feedburnerHostname><atom10:link xmlns:atom10="http://www.w3.org/2005/Atom" rel="hub" href="http://pubsubhubbub.appspot.com" /><entry>
    <id>tag:www.opensourcerails.com,2005:Project/655</id>
    <published>2009-07-03T13:46:58-07:00</published>
    <updated>2009-07-03T13:46:58-07:00</updated>
    <link type="text/html" rel="alternate" href="http://feedproxy.google.com/~r/OpenSourceRails/~3/UC9zf1DPTzY/655-Instiki" />
    <title>Instiki</title>
    <content type="html">&lt;img alt="Screenshot" src="http://www.opensourcerails.com/screenshots/1384/medium/screenshot.png" style="float:left;margin-right:10px" /&gt;&lt;p&gt;Instiki is a basic wiki clone so pretty and easy to set up, youÃ¢â‚¬â„¢ll wonder if itÃ¢â‚¬â„¢s really a wiki. Instiki may not have all the features of the competitors, but what it does it does very well indeed.&lt;/p&gt;&lt;br style='clear:both' /&gt;&lt;img src="http://feeds.feedburner.com/~r/OpenSourceRails/~4/UC9zf1DPTzY" height="1" width="1"/&gt;</content>
    <author>
      <name />
    </author>
  <feedburner:origLink>http://www.opensourcerails.com/projects/655-Instiki</feedburner:origLink></entry>
  <entry>
    <id>tag:www.opensourcerails.com,2005:Project/106743</id>
    <published>2009-07-01T03:23:08-07:00</published>
    <updated>2009-07-01T03:23:08-07:00</updated>
    <link type="text/html" rel="alternate" href="http://feedproxy.google.com/~r/OpenSourceRails/~3/ljI2yt1NW-4/106743-Fat-Free-CRM" />
    <title>Fat Free CRM</title>
    <content type="html">&lt;img alt="Tasks" src="http://www.opensourcerails.com/screenshots/1369/medium/tasks.png" style="float:left;margin-right:10px" /&gt;&lt;p&gt;Fat Free CRM features include group collaboration through task assignments, campaign and lead management, contact lists, and opportunity tracking. Project goal is to spur CRM innovation by providing clean solid codebase that can be easily extended and customized by developers. &lt;/p&gt;&lt;br style='clear:both' /&gt;&lt;img src="http://feeds.feedburner.com/~r/OpenSourceRails/~4/ljI2yt1NW-4" height="1" width="1"/&gt;</content>
    <author>
      <name>mid</name>
    </author>
  <feedburner:origLink>http://www.opensourcerails.com/projects/106743-Fat-Free-CRM</feedburner:origLink></entry>
  <entry>
    <id>tag:www.opensourcerails.com,2005:Project/64</id>
    <published>2009-04-30T09:04:46-07:00</published>
    <updated>2009-04-30T09:04:46-07:00</updated>
    <link type="text/html" rel="alternate" href="http://feedproxy.google.com/~r/OpenSourceRails/~3/OgVjAWAGs0g/64-Spree" />
    <title>Spree</title>
    <content type="html">&lt;img alt="Picture_2" src="http://www.opensourcerails.com/screenshots/1358/medium/Picture_2.png" style="float:left;margin-right:10px" /&gt;&lt;p&gt;The goal of the project is to build a complete open source ecommerce solution for Ruby on Rails. The Rails commerce space is immature and is lacking serious solutions for developers looking for answers to their complex business needs. Rails is especially problematic because it is a relatively new technology and suffers from Ã¢â‚¬Å“small project mentality.Ã¢â‚¬Â Most open source projects in Rails are maintained by a single individual and tend to be limited in scope. Spree seeks to create a large and healthy open source community of the type that developers of other languages are used to participating in.&lt;/p&gt;

&lt;p&gt;The founder of Spree was motivated to start the project after failing to find an existing community in the Rails space dedicated to this vision. In addition, he was motivated by unsuccessful efforts to use other open source solutions in other programming languages, including (but not limited to) the infamous OS Commerce. These solutions seemed to be unsatisfactory when presented with even the simplest of use cases.&lt;/p&gt;&lt;br style='clear:both' /&gt;&lt;img src="http://feeds.feedburner.com/~r/OpenSourceRails/~4/OgVjAWAGs0g" height="1" width="1"/&gt;</content>
    <author>
      <name>schof</name>
    </author>
  <feedburner:origLink>http://www.opensourcerails.com/projects/64-Spree</feedburner:origLink></entry>
  <entry>
    <id>tag:www.opensourcerails.com,2005:Project/54011</id>
    <published>2009-04-06T21:25:46-07:00</published>
    <updated>2009-04-06T21:25:46-07:00</updated>
    <link type="text/html" rel="alternate" href="http://feedproxy.google.com/~r/OpenSourceRails/~3/C2dAqCo5KTE/54011-Moo" />
    <title>Moo</title>
    <content type="html">&lt;img alt="Moo-write" src="http://www.opensourcerails.com/screenshots/1336/medium/moo-write.jpg" style="float:left;margin-right:10px" /&gt;&lt;p&gt;“Moo” is a tool aimed at helping agile projects run colour coded, activity time-line based agile retrospectives.&lt;/p&gt;

&lt;p&gt;By providing a simple means to log events, it replaces the need to stimulate memories of what happened during the increment of work (typically an iteration).&lt;/p&gt;

&lt;p&gt;This allows more events to be captured and therefore not lost in the midst of time.&lt;/p&gt;&lt;br style='clear:both' /&gt;&lt;img src="http://feeds.feedburner.com/~r/OpenSourceRails/~4/C2dAqCo5KTE" height="1" width="1"/&gt;</content>
    <author>
      <name>mangled</name>
    </author>
  <feedburner:origLink>http://www.opensourcerails.com/projects/54011-Moo</feedburner:origLink></entry>
  <entry>
    <id>tag:www.opensourcerails.com,2005:Project/53146</id>
    <published>2009-04-02T05:00:50-07:00</published>
    <updated>2009-04-02T05:00:50-07:00</updated>
    <link type="text/html" rel="alternate" href="http://feedproxy.google.com/~r/OpenSourceRails/~3/1XVkaCcQOQI/53146-BrowserCMS" />
    <title>BrowserCMS</title>
    <content type="html">&lt;img alt="Picture_3" src="http://www.opensourcerails.com/screenshots/1330/medium/Picture_3.png" style="float:left;margin-right:10px" /&gt;&lt;p&gt;BrowserCMS is intended to offer features comparable to commercial CMS products, which can support larger teams of editors. This means having a robust set of features as part of its core, as well as the capability to customize it via modules.&lt;/p&gt;

&lt;p&gt;Here's a quick overview of some of the more notable features:&lt;/p&gt;

&lt;p&gt;    * It's just Rails: Each CMS project is a rails project that depends on the BrowserCMS gem. Developers can add new controllers, views, etc; just like any rails project.
&lt;br /&gt;    * Direct in context editing: Users can browse their site to locate content and change it right on the page itself.
&lt;br /&gt;    * Design friendly Templates: Pages aren't just a template and giant single chunk of HTML. Templates can be built to have multiple editable areas, to allow for rich designs that are still easy to manage by non-technical users.
&lt;br /&gt;    * Sitemap: An explorer/finder style view of sections and pages in a site allowing users to add and organize pages.
&lt;br /&gt;    * Content Library: Provides a standardized 'CRUD' interface to allow users to manage both core and custom content types.
&lt;br /&gt;    * Content API: A set of behaviors added to ActiveRecord which allow for versioning, auditing, tagging and other content services provided by the CMS.
&lt;br /&gt;    * Section Based Security: Admins can control which users can access specific sections (public users), as well as who can edit which pages (cms users).
&lt;br /&gt;    * Workflow: Supports larger website teams where some users can contribute, but not publish. Users can assign work to other publishers to review.
&lt;br /&gt;    * Page Caching: Full page caching allows the web server (Apache) to serve HTML statically when they don't change.&lt;/p&gt;&lt;br style='clear:both' /&gt;&lt;img src="http://feeds.feedburner.com/~r/OpenSourceRails/~4/1XVkaCcQOQI" height="1" width="1"/&gt;</content>
    <author>
      <name>railsjedi</name>
    </author>
  <feedburner:origLink>http://www.opensourcerails.com/projects/53146-BrowserCMS</feedburner:origLink></entry>
  <entry>
    <id>tag:www.opensourcerails.com,2005:Project/52738</id>
    <published>2009-03-29T16:07:55-07:00</published>
    <updated>2009-03-29T16:07:55-07:00</updated>
    <link type="text/html" rel="alternate" href="http://feedproxy.google.com/~r/OpenSourceRails/~3/NdW3z6n9zNk/52738-Mystic" />
    <title>Mystic</title>
    <content type="html">&lt;img alt="Mystic_ss_1_normal" src="http://www.opensourcerails.com/screenshots/1318/medium/mystic_ss_1_normal.png" style="float:left;margin-right:10px" /&gt;&lt;p&gt;Mystic is an open source trouble ticket system written in ruby on rails(RoR). It is designed to be fast, flexible and customizable. It also provides a simple, easy to use interface that's quite intuitive. Tickets are used for several purposes, from internal project management, customer support/troubleshooting, reminders, and much more. &lt;/p&gt;

&lt;p&gt;Features:&lt;/p&gt;

&lt;p&gt;   Seperate and Protected user, tech, and admin areas
&lt;br /&gt;   Ajax-powered ticket viewing &amp; editing
&lt;br /&gt;   Activity Logging
&lt;br /&gt;   Ticket Category and Ticket Status Customization
&lt;br /&gt;   Much More!
&lt;/p&gt;&lt;br style='clear:both' /&gt;&lt;img src="http://feeds.feedburner.com/~r/OpenSourceRails/~4/NdW3z6n9zNk" height="1" width="1"/&gt;</content>
    <author>
      <name>hulihanapplications</name>
    </author>
  <feedburner:origLink>http://www.opensourcerails.com/projects/52738-Mystic</feedburner:origLink></entry>
</feed>
