atom.xml

<?xml version="1.0" encoding="utf-8"?>
<feed xmlns="http://www.w3.org/2005/Atom">

  <title><![CDATA[KandanApp]]></title>
  <link href="http://kandanapp.com/atom.xml" rel="self"/>
  <link href="http://kandanapp.com/"/>
  <updated>2013-04-28T13:41:29-07:00</updated>
  <id>http://kandanapp.com/</id>
  <author>
    <name><![CDATA[Kandan Crew]]></name>
    
  </author>
  <generator uri="http://octopress.org/">Octopress</generator>

  
  <entry>
    <title type="html"><![CDATA[Initial Ruby 2.0 Support]]></title>
    <link href="http://kandanapp.com/blog/2013/03/14/initial-ruby-2-dot-0-support/"/>
    <updated>2013-03-14T06:52:00-07:00</updated>
    <id>http://kandanapp.com/blog/2013/03/14/initial-ruby-2-dot-0-support</id>
    <content type="html"><![CDATA[<p>We&#8217;ve been working hard on a variety of different things (bugs, new features etc)the last few releases and we&#8217;re pleased to announce that the current <strong>MASTER</strong> branch of Kandan now supports Ruby 2.0.0 as well as Ruby 1.9.3.</p>

<p>Any other versions of Ruby <strong>ARE NOT</strong> supported.</p>

<!-- more -->


<p><img src="http://kandanapp.com/images/kandan_ruby2.png"></p>

<p>Currently most of the development team is using Ruby 2.0 by default and both of our Heroku test instances to include the <a href="http://kandan-demo.kandanapp.com">Demo Server</a> are running using Ruby 2.0.</p>

<p>If you plan on upgrading to Ruby 2.0 on Heroku do not forget to make the changes in the Gemfile to support this as <code>ruby '1.9.3'</code> now becomes <code>ruby '2.0.0'</code>.</p>

<p>If you notice any issues using Ruby 2.0 please bring them to our attention over at the <a href="https://github.com/kandanapp/kandan/issues">Issue Tracker</a></p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[Kandan Hubot Adapter 1.0]]></title>
    <link href="http://kandanapp.com/blog/2013/03/12/kandan-hubot-adapter-1-dot-0/"/>
    <updated>2013-03-12T11:11:00-07:00</updated>
    <id>http://kandanapp.com/blog/2013/03/12/kandan-hubot-adapter-1-dot-0</id>
    <content type="html"><![CDATA[<p>Now that we&#8217;ve released Kandan 1.1 we spent a little time focusing on getting a Hubot Adapter for Kandan up and running. After a week or so we now feel comfortable announcing the 1.0 release of the Kandan Hubot Adapter.</p>

<p>A lot of you aren&#8217;t going to be familiar with <a href="http://hubot.github.com/">Hubot</a> so here&#8217;s a brief primer.</p>

<!-- more -->


<h4>What is Hubot?</h4>

<p><a href="http://github.com">GitHub, Inc.,</a> wrote the first version of Hubot to automate their company chat room.Hubot is open source, written in CoffeeScript on Node.js, and easily deployed on platforms like Heroku. More importantly, Hubot is a standardized way to share scripts between everyone&#8217;s robots.</p>

<h4>What can Hubot do?</h4>

<p>Hubot ships with a <a href="https://github.com/github/hubot/tree/master/src/scripts">small group of core scripts</a>: things like posting images, translating languages, and integrating with Google Maps.</p>

<p>The real fun happens when you add your own scripts. Github maintains a <a href="https://github.com/github/hubot-scripts">repository of community Hubot scripts</a> that you can add to your own robot.</p>

<h4>Kandan Hubot Adapter Demo</h4>

<p>You can demo the Kandan Hubot Adapter in action over on our <a href="http://kandan-demo.kandanapp.com">Demo Server</a>. Here is a full list of the commands available to it:</p>

<ul>
<li><code>hubot &lt;keyword&gt; tweet</code> - Returns a link to a tweet about <keyword></li>
<li><code>hubot convert me &lt;expression&gt; to &lt;units&gt;</code> - Convert expression to given units.</li>
<li><code>hubot help</code> - Displays all of the help commands that Hubot knows about.</li>
<li><code>hubot help &lt;query&gt;</code> - Displays all help commands that match <query>.</li>
<li><code>hubot image me &lt;query&gt;</code> - The Original. Queries Google Images for <query> and returns a random top result.</li>
<li><code>hubot map me &lt;query&gt;</code> - Returns a map view of the area returned by <query>.</li>
<li><code>hubot math me &lt;expression&gt;</code> - Calculate the given expression.</li>
<li><code>hubot mustache me &lt;query&gt;</code> - Searches Google Images for the specified query and mustaches it.</li>
<li><code>hubot ping</code> - Reply with pong</li>
<li><code>hubot pug me</code> - Receive a pug</li>
<li><code>hubot show me &lt;user/repo&gt; pulls [with &lt;regular expression&gt;]</code> - Shows open pull requests for that project by filtering pull request&#8217;s title.</li>
<li><code>hubot the rules</code> - Make sure hubot still knows the rules.</li>
<li><code>hubot time</code> - Reply with current time</li>
<li><code>hubot translate me &lt;phrase&gt;</code> - Searches for a translation for the <phrase> and then prints that bad boy out.</li>
<li><code>hubot translate me from &lt;source&gt; into &lt;target&gt; &lt;phrase&gt;</code> - Translates <phrase> from <source> into <target>. Both <source> and <target> are optional</li>
<li><code>hubot travis me &lt;user&gt;/&lt;repo&gt;</code> - Returns the build status of https://github.com/<user>/<repo></li>
<li><code>hubot youtube me &lt;query&gt;</code> - Searches YouTube for the query and returns the video embed link.</li>
<li><code>ship it</code> - Display a motivation squirrel</li>
</ul>


<p>You can head over to <a href="https://github.com/kandanapp/hubot-kandan">Github Repo</a> to download and test out on your own Kandan installation. The Installation instructions aren&#8217;t perfect but they do in fact work.</p>

<h4>Contributing</h4>

<p>Contributions are welcome. To get your work considered please do the following:</p>

<ul>
<li>Fork this project</li>
<li>Create a feature/bug fix branch</li>
<li>Hack away, committing often and frequently</li>
<li>Push your branch up to your fork</li>
<li>Submit a pull request</li>
</ul>

]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[UI/UX Refresh Ideas For Kandan]]></title>
    <link href="http://kandanapp.com/blog/2013/03/08/ui-slash-ux-refresh-ideas-for-kandan/"/>
    <updated>2013-03-08T11:28:00-08:00</updated>
    <id>http://kandanapp.com/blog/2013/03/08/ui-slash-ux-refresh-ideas-for-kandan</id>
    <content type="html"><![CDATA[<h3>A general overview of how to fix some things in the layout.</h3>

<p><img src="http://kandanapp.com/images/ui_ux_1.jpg"></p>

<!-- more -->


<ul>
<li>Having the channels in a scroll area as opposed to a tabbed area allows for there to not be a limit on number of channels in one network. Tabs bunch up when there are too many channels.</li>
<li>The people area should have it’s own space. This allows for better visibility of who is in the room when there are a lot of people connected. It also adds focus to the area instead of it just being a general module. Knowing who is in the room is a pretty important feature and should not be lumped into the same category as a module.</li>
<li>The module area is for tools that are available to the room. I could imagine all kinds of tools that could go on this “toolbelt”.</li>
<li>The chat area has not changed at all except for a slight reduction in it’s width.</li>
</ul>


<h3>An overview of the module / “toolbelt” area.</h3>

<p><img src="http://kandanapp.com/images/ui_ux_2.jpg"></p>

<p>Having module icons in a tool area is compact and allows for more freedom when making potential future modules.</p>

<h3>The People area</h3>

<p><img src="http://kandanapp.com/images/ui_ux_3.jpg"></p>

<p>The people area is basically the same except that it gets it’s own area. I also think there should be a small area under the name dedicated to any data that needs to be displayed such as status.</p>

<h3>The Channels area</h3>

<p><img src="http://kandanapp.com/images/ui_ux_4.jpg"></p>

<p>The channels area is basically just a list of available channels. I didn’t include a channel delete button anywhere because I think that the admin should be the only one to create and delete channels. I think this is important because a troll could potentially get in and delete all the channels. You could also figure out how to not let trolls in.</p>

<h3>Other Suggestions</h3>

<ul>
<li>I think that the the sound and notifications should be set under the user settings.</li>
<li>The area for the logo should be a little bit bigger. People like to brand the tools they use.</li>
<li>I think that the twitter bootstrap default styles should not be changed. People should be able to make skins/themes.</li>
<li>An upload media button would be cool sitting right next to the submit button in the chat box.</li>
</ul>

]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[Welcoming Kandan 1.1]]></title>
    <link href="http://kandanapp.com/blog/2013/02/28/welcoming-kandan-1-dot-1/"/>
    <updated>2013-02-28T11:01:00-08:00</updated>
    <id>http://kandanapp.com/blog/2013/02/28/welcoming-kandan-1-dot-1</id>
    <content type="html"><![CDATA[<p>The Kandan Team is pleased to announce the Official 1.0 release of <a href="https://github.com/kandanapp/kandan">Kandan</a> an Open Source alternative to HipChat.</p>

<p>What is Kandan? Kandan is a private chat service for your company or team. You can invite colleagues to share ideas and files in a persistent group chat room or rooms.</p>

<p>Unlike HipChat or other alternatives, Kandan is completely Open Source and can be hosted internally or externally by your organization or by a third party.</p>

<!-- more -->


<h3>What&#8217;s New in 1.1</h3>

<p>These are the major changes that are now in 1.1</p>

<ul>
<li>Added an Adminstrative Console. This is very basic at the moment but will allow any admin to set the max number of rooms, set a Kandan installation as public or private, and will perform basic user management.

<ul>
<li><img src="http://kandanapp.com/images/kandan_1.1_admin.png"></li>
</ul>
</li>
<li>Room names have been added as unique. An error is now shown if a user tries to create a room with a name that&#8217;s already in use.

<ul>
<li><img src="http://kandanapp.com/images/kandan_1.1_rooms.png"></li>
</ul>
</li>
<li>We&#8217;ve extended the emoticon plugin to support the full <a href="http://www.emoji-cheat-sheet.com/">emoji set</a>

<ul>
<li><img src="http://kandanapp.com/images/kandan_1.1_emojis.png"></li>
</ul>
</li>
<li>Added Desktop notifications. This will work out of the box with Chrome or Safari. If you&#8217;re using Firefox you will need to install <a href="https://addons.mozilla.org/en-us/firefox/addon/html-notifications/">HTML Desktop Notifications</a>

<ul>
<li><img src="http://kandanapp.com/images/kandan_1.1_notifications.png"></li>
</ul>
</li>
<li>We&#8217;ve added support for @mentions.

<ul>
<li><img src="http://kandanapp.com/images/kandan_1.1_mentions.png"></li>
</ul>
</li>
<li>Added plugin suport for <a href="http://vimeo.com">Vimeo</a>

<ul>
<li><img src="http://kandanapp.com/images/kandan_1.1_vimeo.png"></li>
</ul>
</li>
<li>Added &amp; tested <a href="https://github.com/kandanapp/kandan/wiki/Installation#wiki-appfog">installation instructions</a> for <a href="https://www.appfog.com/">AppFog</a>.</li>
</ul>


<h3>Get Involved</h3>

<p>Since Kandan is a fully open-source app, we would appreciate if you dive in and start adding features, fixing bugs (what bugs?), and cleaning up the code.</p>

<p>To find out how to best contribute please read our <a href="https://github.com/kandanapp/kandan/blob/master/CONTRIBUTING.md">Contributing Guidelines</a>.</p>

<p>For a full list of changes please take a look at the <a href="https://github.com/kandanapp/kandan/blob/master/CHANGELOG.md">CHANGELOG</a></p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[Kandan 1.0 Release Announcement]]></title>
    <link href="http://kandanapp.com/blog/2013/02/06/kandan-1-dot-0-release-announcement/"/>
    <updated>2013-02-06T20:51:00-08:00</updated>
    <id>http://kandanapp.com/blog/2013/02/06/kandan-1-dot-0-release-announcement</id>
    <content type="html"><![CDATA[<h3>Announcement</h3>

<p>The Kandan Team is pleased to announce the Official 1.0 release of <a href="https://github.com/kandanapp/kandan">Kandan</a> an Open Source alternative to HipChat.</p>

<p>What is Kandan? Kandan is a private chat service for your company or team. You can invite colleagues to share ideas and files in a persistent group chat room or rooms.</p>

<p>Unlike HipChat or other alternatives, Kandan is completely Open Source and can be hosted internally or externally by your organization or by a third party.</p>

<!-- more -->


<h3>Features</h3>

<p>These are features that work out of the box on any provider:</p>

<ul>
<li>Easy deploy to CloudFoundry, Heroku, dotCloud, etc.</li>
<li>Collaborative team chat</li>
<li>Unlimited channels</li>
<li>Embed formats for images and youtube videos with requests for others (twitter, facebook, g+, etc.)</li>
<li>Synchronized sound player - play any audio-tag compatible url for the whole channel (Pending :P)</li>
<li>/me command!</li>
<li>Highly extensible plugin format</li>
</ul>


<h3>Get Involved</h3>

<p>Since Kandan is a fully open-source app, we would appreciate if you dive in and start adding features, fixing bugs (what bugs?), and cleaning up the code.</p>

<p>But before you jump right in there there are a few caveats.</p>

<p>If you&#8217;re going to contribute code then you&#8217;re going to have to sign our <a href="http://www.clahub.com/agreements/kandanapp/kandan">Contributor License Agreement</a> (hereafter referred to as CLA) which is modeled after the one that <a href="http://nodejs.org">NodeJS</a> uses.</p>

<p>A CLA is a legal document in which you state you are entitled to contribute the code/documentation/translation to the project you’re contributing to and are willing to have it used in distributions and derivative works. This means that should there be any kind of legal issue in the future as to the origins and ownership of any particular piece of code, then that project has the necessary forms on file from the contributor(s) saying they were permitted to make this contribution.</p>

<p>The CLA also ensures that once you have provided a contribution, you cannot try to withdraw permission for its use at a later date. People and companies can therefore use that software, confident that they will not be asked to stop using pieces of the code at a later date.</p>

<p>You will also really want to take heart and read these two blog posts.</p>

<ul>
<li><a href="http://kandanapp.com/blog/2013/02/05/how-to-contribute-code/">How to Contribute Code</a></li>
<li><a href="http://kandanapp.com/blog/2013/02/05/how-to-contribute-issues/">How to Contribute Issues</a></li>
</ul>


<p>Make sure you check out these resources as well.</p>

<ul>
<li>GitHub <a href="https://github.com/kandanapp/kandan/issues">Issues Tracker</a></li>
<li>Twitter <a href="https://twitter.com/kandanapp">@kandanapp</a></li>
<li><a href="http://kandan-demo.kandanapp.com/">Kandan Demo</a> (Yes we eat our own DogFood)</li>
</ul>


<p>And here is the CHANGELOG for the 1.0 release.</p>

<hr />

<h3>CHANGELOG</h3>

<h4>[v1.0]</h4>

<ul>
<li><a href="http://github.com/kandanapp/kandan/commit/38f4875">38f4875</a> Create CONTRIBUTING.md <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/605c237">605c237</a> Update README.md <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/c42c82b">c42c82b</a> Update README.md <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/6c025a8">6c025a8</a> Update README.md <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/f5be2b4">f5be2b4</a> Update README.md <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/fadff2d">fadff2d</a> Merge pull request #43 from fusion94/master <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/0646509">0646509</a> Correctly set channel and user in bootstrapped messages thanks to @madx Fixes #32 <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/46207f4">46207f4</a> Merge pull request #41 from fusion94/master <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/809cf7b">809cf7b</a> biggish commit on style. Fixes #13 #34 #36 #37 <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/22a0816">22a0816</a> Merge pull request #33 from kandanapp/update-paperclip <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/75c4666">75c4666</a> Updating paperclip, stage uno <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/8d4a9dd">8d4a9dd</a> Merge pull request #30 from fusion94/master <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/a39ddbc">a39ddbc</a> Moving from displaying email to displaying usernames, username is now required to register. Fixes #2 <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/ae3f5a3">ae3f5a3</a> Merge pull request #28 from amanelis/coverage <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/40d3df8">40d3df8</a> Added simplecov to spec helper <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/c74d2ed">c74d2ed</a> Added coverage/ dir to gitignore <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/dcb131f">dcb131f</a> Added simplecov to Gemfile <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/c6b9651">c6b9651</a> Update README.md <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/9bf68fa">9bf68fa</a> Merge pull request #27 from jrgifford/upgrade-sass <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/626cc2e">626cc2e</a> updated to sass 3.2.5 <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/f762ba4">f762ba4</a> Merge pull request #14 from jrgifford/local-installs <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/69bed6a">69bed6a</a> Fixes #8 <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/0c3e253">0c3e253</a> added not pushing public/system/* to .gitignore. also set default channel to be named lobby. fixed #9 <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/d112c8b">d112c8b</a> Modified two things:   - travis.yml   - gemfile.lock to remove the dependency on git-based jasmine <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/4d770f5">4d770f5</a> Merge pull request #5 from amanelis/spec-updates <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/253a030">253a030</a> Fixes issue #6 <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/350dde9">350dde9</a> Merge remote branch kandan/master <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/7965928">7965928</a> ci-skip added build status to readme <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/50e0e38">50e0e38</a> Added travis.yml. <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/bf80a5e">bf80a5e</a> correcting typo on a URL in README <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/b453b72">b453b72</a> adding links to UPDATE section of README <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/f529046">f529046</a> added an UPDATE section of the README <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/291884a">291884a</a> updating links in README <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/3c47fcb">3c47fcb</a> oops a typo <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/dcb016e">dcb016e</a> potential width fix <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/840525f">840525f</a> width issues <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/d3131dd">d3131dd</a> resolving file attachment issues <strong>(Tony Guntharp)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/628138f">628138f</a> Removed rails default images, all tests pass :green_heart: <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/2ad13e5">2ad13e5</a> Changed up when not authenticated <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/5409535">5409535</a> Re wrote a few expects in model specs <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/827cde1">827cde1</a> Changed up the before blocks, calling methods to many times <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/6c790fa">6c790fa</a> Added faker gem for a few testing purposes <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/c712a4f">c712a4f</a> Line for intialize on precompile found twice :trollface: <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/6e6ec3b">6e6ec3b</a> Don&#8217;t need to require factory_girl <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/89a59fa">89a59fa</a> Added db cleaner to spec config <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/987a39a">987a39a</a> Added db cleaner and a few other handy development gems <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/452962e">452962e</a> Whitespace <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/a8a9442">a8a9442</a> Slight modification to how the api controller spec is structured <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/4d81157">4d81157</a> Removed rack-mini-profiler, decided wasn&#8217;t worthy right now <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/46fa134">46fa134</a> More factory girl updates to deprication <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/c572837">c572837</a> Updated factory deprication for next <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/c94a8ee">c94a8ee</a> Added some better gems for development <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/bc8e10d">bc8e10d</a> Was already using sqlite locally :trollface: <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/84ea429">84ea429</a> Added rvmrc to the gitignore file <strong>(Alex Manelis)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/000ea1f">000ea1f</a> Merge pull request #36 from bielefeldt/master <strong>(Sean Grove)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/dead52c">dead52c</a> README change with Heroku S3 integrations <strong>(response)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/baa502c">baa502c</a> Update Readme <strong>(Kev Zettler)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/ba2c630">ba2c630</a> Removed Cloudfuji references from readme <strong>(Kev Zettler)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/5b8bb9b">5b8bb9b</a> Merge pull request #34 from jrgifford/master <strong>(Kev Zettler)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/5606ea4">5606ea4</a> :heart: Guard, fixed specs to work with latest factory girl. <strong>(James Gifford)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/6978925">6978925</a> Merge pull request #33 from jrgifford/master <strong>(Kev Zettler)</strong></li>
<li><a href="http://github.com/kandanapp/kandan/commit/a1fd6f9">a1fd6f9</a> Updated rails to avoid ActionPack vuls. <strong>(James Gifford)</strong></li>
</ul>

]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[How to Contribute Code]]></title>
    <link href="http://kandanapp.com/blog/2013/02/05/how-to-contribute-code/"/>
    <updated>2013-02-05T15:17:00-08:00</updated>
    <id>http://kandanapp.com/blog/2013/02/05/how-to-contribute-code</id>
    <content type="html"><![CDATA[<div class="alert alert-info">
    <i class="icon-exclamation-sign icon-3x"></i>This is a living Document. The most recent copy is always available on the <a href="https://github.com/kandanapp/kandan/wiki/How-to-Contribute-Code">Wiki</a>
</div>


<h3>How To Contribute Code</h3>

<p>Whether you&#8217;ve got a bugfix, documentation update, or new feature for us, these are the steps to follow to contribute code back into the main kandan repo.</p>

<p><strong>1. Get the latest code from Github</strong></p>

<p>You&#8217;ll need to understand a little bit about how git and gihub work before this step (if you need an introduction guide, Github <a href="http://learn.github.com/p/intro.html">has a good one</a> you can learn from). In simple terms, log in to github, visit the Kandan project page, and click the &#8220;fork&#8221; button to create your own copy of the repo.  You will push your changes to this new repo under your own github account, and we will pull changes into the main repo from there.</p>

<!-- more -->


<p>For the sake of the rest of the examples in this guide, we&#8217;re going to assume your Github username is &#8221;<strong>GITHUB_USERNAME</strong>&#8221; and use that in our examples.</p>

<p>Now, we want to grab the latest from this newly created repository and pull it down to your local machine. Getting the latest code from your repo is simple, just clone it:</p>

<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'>git clone git://github.com/GITHUB_USERNAME/kandan.git
</span><span class='line'><span class="nb">cd </span>kandan
</span></code></pre></td></tr></table></div></figure>


<p>This will give you a directory called &#8220;kandan&#8221; on your local machine with the latest checkout from your fork of the main kandan repo. <strong>Note:</strong> this is <em>not</em> a direct reference to the main kandan repo. When you make changes in your fork, you&#8217;ll need to let us know about it so we can pull it over&#8230;.but that&#8217;s later in the process.</p>

<p><strong>2. Add a remote for the main kandan repo</strong></p>

<p>One thing you&#8217;ll need to do to make things easier to integrate and keep up to date in your fork is to add the main kandan repo as a remote reference. This way you can fetch the latest code from the production version and integrate it. So, here&#8217;s how to set that up:</p>

<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'>git remote add upstream https://github.com/kandanapp/kandan.git
</span><span class='line'>git remote   <span class="o">(</span>this will list out your remotes, showing the new one we added<span class="o">)</span>
</span></code></pre></td></tr></table></div></figure>


<p>Then, when you need to pull the latest from the main kandan repo, you just fetch and merge the master branch:</p>

<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'>git fetch upstream
</span><span class='line'>git merge upstream/master
</span></code></pre></td></tr></table></div></figure>


<p>You can also use <em>git pull upstream master</em> if you want it all in one step.</p>

<p><strong>3. Making a branch for your changes</strong></p>

<p>When adding features or bug fixes, please create a separate branch for each changeset you want us to pull in, either with the issue number in the branch name or with an indication of what the feature is. To create the branch, do something like this:</p>

<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
<span class='line-number'>2</span>
<span class='line-number'>3</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'>git branch   <span class="o">(</span>lists your current branches<span class="o">)</span>
</span><span class='line'>git branch my_new_code   <span class="o">(</span>makes a new branch called my_new_code<span class="o">)</span>
</span><span class='line'>git checkout my_new_code
</span></code></pre></td></tr></table></div></figure>


<p>If you&#8217;re working on an issue in the Issues list for the main kandan repo, use the naming convention &#8220;kandan-[issue-num]&#8221; for your branch name to help us keep track of what your patch actually fixes</p>

<p><strong>4. Push your code and make a pull request</strong></p>

<p>When you have finished making your changes, you&#8217;ll need to push up your changes to your fork so we can grab them. With them all committed, push them:</p>

<figure class='code'><figcaption><span></span></figcaption><div class="highlight"><table><tr><td class="gutter"><pre class="line-numbers"><span class='line-number'>1</span>
</pre></td><td class='code'><pre><code class='bash'><span class='line'>git push upstream kandan-<span class="o">[</span>issue-num<span class="o">]</span>
</span></code></pre></td></tr></table></div></figure>


<p>This pushes everything in that branch up. Then you can go back over to the main kandan github page and issue a pull request from there.  Tell us what you want us to merge and what it does/fixes, and one of us will pick it up.</p>

<p>That lets us know that there&#8217;s something new from you that needs to be pulled in. We&#8217;ll review it and get back to you about it if we have any questions. Otherwise, we&#8217;ll integrate it and let you know when it&#8217;s in!</p>

<h3>Conclusion</h3>

<p>Hope this guide helps you get started in contributing to the kandan project! If you still have questions, don&#8217;t hesitate to send an email over to admin@kandanapp.com and we&#8217;ll get back to you.</p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[How to Contribute Issues]]></title>
    <link href="http://kandanapp.com/blog/2013/02/05/how-to-contribute-issues/"/>
    <updated>2013-02-05T14:07:00-08:00</updated>
    <id>http://kandanapp.com/blog/2013/02/05/how-to-contribute-issues</id>
    <content type="html"><![CDATA[<div class="alert alert-info">
    <i class="icon-exclamation-sign icon-3x"></i>This is a living Document. The most recent copy is always available on the <a href="https://github.com/kandanapp/kandan/wiki/How-to-Contribute-Issues">Wiki</a>
</div>


<h3>Overview</h3>

<p>Spotting and reporting genuine issues in our platform is one of the most accessible ways to contribute but, in equal measure, also the most tricky to do well. If you use this guide as reference when you raise a ticket, it will reduce the chance of delays in it reaching our development team.</p>

<h3>Searching Issues</h3>

<p>Tickets for outstanding issues often contain workarounds shared by our development team, or links to threads that provide discussions and solutions between our community members. Otherwise, they will tell you when a fix for a issue was created and the build you need to obtain in order to take advantage of it.</p>

<!-- more -->


<p>It is not necessary to waste time debugging incorrect Kandan behavior that has either already been fixed or has a known workaround. Being familiar with GitHub&#8217;s powerful issue search tool, will enable you to easily access this information.</p>

<h2>Submitting Issues</h2>

<h3>The Issue-Reporting Lifecycle</h3>

<p>We are keenly-committed to being as open to feedback from our community as possible, to ensure that the platform becomes more stable and featureful in the shortest time. It cannot be underestimated how crucial community-reported bugs are to achieving this goal. Hence, if you find a issue, and you are able to reproduce it reliably with a simple use case, then we will be very grateful if you would report it to us.</p>

<p>That said, the creation of tickets in the Issue Tracker should not be taken lightly. The management of each ticket can consume considerable resources, and so inaccurate or bogus submissions take unnecessary time away from what we would all prefer our development teams to be doing - improving the code.</p>

<p>In addition to accuracy, tickets that are concise, complete, unemotional and objective are the ones our teams appreciate the most.</p>

<h3>Issue Tracker Workflow Diagram</h3>

<p><img src="https://raw.github.com/kandanapp/kandan/resources/GH-Issue_Tracker.png" alt="GitHub Issue Tracker Workflow" /></p>

<h3>Creating a Use Case</h3>

<p>A &#8220;use case&#8221; is working code or reproduction scenario that reliably reproduces a specific issue. What sets the quality use cases apart from the rest is that they contain the least possible code while still demonstrating the issue. Take pride in your use case; make it an art!</p>

<p>Being in the habit of writing use cases as part of your troubleshooting process can significantly decrease the time we address your issue. This is because it can differentiate user errors from issues in the platform.</p>

<h3>Creating a Issue</h3>

<ul>
<li>Create a Issue, only after there is no doubt about the issue&#8217;s existence, Create one ticket per issue, bearing the following in mind:

<ul>
<li>keep to the point: concise, complete and factual tickets are the most appreciated</li>
<li>include all the information: without a use case we probably cannot accept your issue</li>
<li>watch your issue</li>
</ul>
</li>
</ul>


<h3>Conclusion</h3>

<p>We do not underestimate the time and conscientiousness involved in raising good issues, and we very much appreciate it. Although we&#8217;d love to chat with you. Adding a ticket asking how to do XYZ probably isn&#8217;t a good idea.</p>

<p>Thank you for all your efforts!</p>
]]></content>
  </entry>
  
  <entry>
    <title type="html"><![CDATA[Kandan an Open Source Alternative to HipChat]]></title>
    <link href="http://kandanapp.com/blog/2013/02/03/kandan-an-open-source-alternative-to-hipchat/"/>
    <updated>2013-02-03T14:37:00-08:00</updated>
    <id>http://kandanapp.com/blog/2013/02/03/kandan-an-open-source-alternative-to-hipchat</id>
    <content type="html"><![CDATA[<h3>Introduction</h3>

<p>Today We&#8217;d like to introduce you to <a href="https://github.com/kandanapp/kandan">Kandan</a> an Open Source alternative to HipChat.</p>

<p>What is Kandan? Kandan is a private chat service for your company or team. You can invite colleagues to share ideas and files in a persistent group chat room or rooms.</p>

<p>Unlike HipChat or other alternatives, Kandan is completely Open Source and can be hosted internally or externally by your organization or by a third party.</p>

<!-- more -->


<h3>Background</h3>

<p>Kandan was originally developed by <a href="http://cloudfuji.com/">Cloudfuji</a> and they started development on it back on March 6th of 2012. Development went pretty fast and furious until about June 4th of 2012. After that there wasn&#8217;t another commit to the repository until some pull requests came in during the month of January of 2013.</p>

<p>In talking with the team at Cloudfuji both <a href="http://jamesrgifford.com/">James Gifford</a> and <a href="http://fusion94.org">Tony Guntharp</a> agreed to take over maintenance of the project.</p>

<h3>Features</h3>

<p>These are features that work out of the box on any provider:</p>

<ul>
<li>Easy deploy to CloudFoundry, Heroku, dotCloud, etc.</li>
<li>Collaborative team chat</li>
<li>Unlimited channels</li>
<li>Embed formats for images and youtube videos with requests for others (twitter, facebook, g+, etc.)</li>
<li>Synchronized sound player - play any audio-tag compatible url for the whole channel (Pending :P)</li>
<li>/me command!</li>
<li>Highly extensible plugin format</li>
</ul>


<h3>Get Involved</h3>

<p>Since Kandan is a fully open-source app, we would appreciate if you dive in and start adding features, fixing bugs (what bugs?), and cleaning up the code.</p>

<p>Make sure you check out these resources as well.</p>

<ul>
<li>GitHub <a href="https://github.com/kandanapp/kandan/issues">Issues Tracker</a></li>
<li>Twitter <a href="https://twitter.com/kandanapp">@kandanapp</a></li>
<li><a href="http://kandan-demo.kandanapp.com/">Kandan Demo</a> (Yes we eat our own DogFood)</li>
</ul>


<p>You can also email us at admin@kandanapp.com</p>

<h3>Conclusion</h3>

<p>We&#8217;re targetting a 1.0 release in just about two weeks time which will primarily consist of bug fixes. After that release we plan on doing regular minor releases that add new features so if there&#8217;s anything you want to see in newer versions please create an <a href="https://github.com/kandanapp/kandan/issues">Issue</a>.</p>
]]></content>
  </entry>
  
</feed>