The starting point

What is our starting point?

Imagine you want to collaborate in an open source project. It should be easy, you think, just go there and program, but in fact, there are some soft rules to follow:

- First: you need resources. So we have started to work with the University of Seville to find people interested in Open Source, in cloud, and in working with us for an internship. Amazingly, we won't be alone, at least 3 companies will be collaborating.
- Second: a good value proposition,  I was going to recommend one of the books I am reading, but I have discovered that although the first book on business models was using licenses from creative commons for charts and slides, and thus was perfect to share, this one is not, so I don't recommend it any more...
- Third: we need some infrastructure, a small one, just enough to run RHEV so it can be managed. Working on that
- Fourth: whatever is needed to make the development, TDD (test framework), CI (Maven and/or Jenkins), a compiler,.
- Fifth: let's not reinvent the wheel... what open source components can be used which license is compatible with ManageIQ? The license should be compatible and no problem created beacuse of it. And architectural should be compatible too...
- Sixth: Documentation: where should we store documentation? Wiki style?

So I've been investigating and:
- Trello is a good tool to keep requirements and make them go through a Kanban process. Building a project there.
- Github is needed, upstream uses it already, so aligning is the sensible thing to do. We could think of some tool like Gerrit for code approval, but due to the small team we are, it wouldn't make sense to have an installation for gerrit onsite. We need to evaluate gerrithub as an interface to github, any way
- We are not mandating anything to code, as long as it works :D