Verify if repository seems to be adequate to be released open-source

[Regent L'Archeveque]

Check if the actual content (copyrights, licences, libraries etc) does not seem to have potential issues to be released. The intent is to set to public ca.gc.asc_csa.apogy and ca.gc.asc_csa.apogy.ots repositories.

[prapicault]

I went through all the bundles and did not see anything obviously wrong. There is a number of things to discuss though: - Should we rename the bundles to the eclipse namespace before opening the repo? - The copyright appears after the package declaration whereas it typically appears before - Is all the generated code used? I'm mostly thinking about the edit plug-ins. - Do we have an idea of what will be API or not?

[Regent L'Archeveque]

1. I prefer to keep the actual namespace. However, this will be our priority once in incubation phase.
2. I created the issue #85 to fix the copyrights placement in classes. We have an automated script to cover this. Sebastien will fix this later this week.
3. Yes, the generated code is required. The edit plug-ins make the bridge between the business models and the UI.
4. For the API good point. We'll need to discuss about the strategy on this. We'll need your advices.