Valentine's Day: in love with OpenSource My company Tirasa is definitely a small company. But we do love OpenSource, we've always loved it, even before becoming Tirasa. This is the reason why we have started an OpenSource project for building an Identity Manager, and subsequently brought it to the Apache Software Foundation.
Valentine's Day: in love with OpenSource
My company Tirasa is definitely a small company. But we do love OpenSource, we've always loved it, even before becoming Tirasa.
This is the reason why we have started an OpenSource project for building an Identity Manager, and subsequently brought it to the Apache Software Foundation. Today, Apache Syncope - read more about its history.
This is the reason why we have based our sales proposal on nice and successful OpenSource projects like as Hippo CMS and Apache Cocoon.
We also had enough free cycles to start a couple of projects on our own:
- ConnId
built to help drive development of Connectors, a consistent generic layer between applications and target resources; - HippoCocoonToolkit
alternative, Apache Cocoon 3.0 based, toolkit for building web sites while relying upon Hippo CMS and Repository.
No OpenSource without infrastructure
When you accumulate some experience in contributing to large OpenSource projects in big foundations like the ASF, you suddenly realize that no OpenSource project can develop and evolve without some infrastructure service: source code repository, issue tracker, mailing list, ...
Naturally, the ASF provides everything necessary to Syncope and Cocoon (and to a lot of other projects).
From the other side, OneHippo is big enough for powering Hippo CMS with all bells and whistles.
....and what about Tirasa and its two small projects?
The Cloud comes to the rescue
Fortunately, there are nowadays many free and open services available to anyone who wants to run its own OpenSource project, so we have been able to empower
- GitHub for source control and website (via Pages)
- Sonatype OSS for making Maven artifacts available at central repository
- GoogleGroups for mailing list(s)
- Atlassian OnDemand JIRA (for issue tracking) and Confluence (for wiki)
these services need to be approved upfront by Atlassian, but you can always use GitHub's features, less cool but still functional - Travis CI for continuous integration and deploy to Sonatype OSS snapshot repository at every successful build
And the nicest thing is that every service is integrated with each other: when committing to GitHub the fix for an issue, JIRA makes an update, a notification e-mail is sent and a build is triggered on Travis. Priceless.
So what?
So nothing, just relieving that if a small company like ours can run multiple OpenSource projects without loosing blood in infrastructure service, it's because of the large availability of free services in this modern Internet that someone still calls "the Cloud".
...and guess who is helping running our dedicated support site and live demo for Apache Syncope? Thank you, Openshift!
Yes, Excellent! 