| Re: [lyo-dev] Strawman Proposal for Refactoring eclipse/Lyo |
|
I like the proposal in the large. Some of these components will certainly benefit from a lightweight process if placed on GitHub.
But it would be nice to maintain a common community across both. (Common mailing lists, bug tracking(?), etc.) Do we even know who has access to GitHub’s Lyo accounts today? And, I just draw your attention to another set of contributions we need to consider. Namely, adaptor implementations that I don’t believe fall in the Samples
nor Reference Implementations categories. For example, we have the repositories org.eclipse.lyo.adapter.magicdraw.git & org.eclipse.lyo.adapter.simulink Besides structuring our repositories, I would also be nice if we can also put some effort in improving and structuring our documentation. I believe we currently
have a number of variants of the Bugzilla tutorial at the moment. I have otherwise some detailed comments, but I guess we can take that once we start executing. regards ______________________________ Jad El-khoury, PhD KTH Royal Institute of Technology School of Industrial Engineering and Management, Mechatronics Division Brinellvägen 83, SE-100 44 Stockholm, Sweden Phone: +46(0)8 790 6877 Mobile: +46(0)70 773 93 45 From: lyo-dev-bounces@xxxxxxxxxxx [mailto:lyo-dev-bounces@xxxxxxxxxxx]
On Behalf Of Jim Amsden In order to improve the usability of eclipse/Lyo contributions, and in particular OSLC4J as a means of developing OSLC client and server applications,
eclips/Lyo might benefit from some refactoring to better separate concerns, different RIO implementation architectures, client and server development, etc. It may also be useful to consider moving some of the RIO and sample code to GitHub as these projects
perhaps don't need, or are not sufficiently benefiting from the eclipse.org governance processes. |