| [lyo-dev] OSLC4J project names in the rio repo |
This is moderately related to a previous topic on renaming the OSLC4J projects [1].
There is a slightly off-topic discussion in bug 415365 [2] that I'd like to bring onto the mailing list.
Basically it starts with the suggestion that the OSLC4J-based RIOs should have "rio" in their project/package name, e.g.:
org.eclipse.lyo.oslc4j.changemanagement > org.eclipse.lyo.oslc4j.changemanagement.rio
Steve Speicher then suggested that he prefers:
"org.eclipse.lyo.oslc4j.cm as the "parent" project identifier for all things developed using oslc4j for CM and then attach right "sub names" such as: ".rio", ".client", etc."
In principle I like Steve's suggestion, but I have the concern that for people new to OSLC the meaning of CM is ambiguous, i.e. is the C for Change or Configuration?
(Also the same with AM ... is that Asset or Architecture?)
On the Communications wiki there are some naming suggestions [3] that might be good to apply here. If those are followed, then the RIO for Change Management could be called:
org.eclipse.lyo.oslc4j.changemgmt.rio
That said, now that the whole discussion of projects in the RIO package is open, it seems odd to me that any of these packages have "oslc4j" in their names.
Do they extend OSLC4J and are a reusable asset for developers? I think the projects named "common" do, but only them. And in their case, isn't it strange that they're in the rio repo?
Here is a proposal to throw stones at:
Given the short names from the naming guidelines [3], rename as follows
org.eclipse.lyo.oslc4j.$long_name --> org.eclipse.lyo.rio.$short_name
org.eclipse.lyo.oslc4j.$long_name.common --> org.eclipse.lyo.oslc4j.$short_name
org.eclipse.lyo.oslc4j.$long_name.test --> org.eclipse.lyo.rio.$short_name.test
e.g. for Change Management:
org.eclipse.lyo.oslc4j.changemanagement --> org.eclipse.lyo.rio.changemgmt
org.eclipse.lyo.oslc4j.changemanagement.common --> org.eclipse.lyo.oslc4j.changemgmt
org.eclipse.lyo.oslc4j.changemanagement.test --> org.eclipse.lyo.rio.changemgmt.test
Separately, should the "common" projects be moved to a different repo?
[1]: http://dev.eclipse.org/mhonarc/lists/lyo-dev/msg00411.html
[2]: https://bugs.eclipse.org/bugs/show_bug.cgi?id=415365
[3]: http://open-services.net/wiki/communications/Workgroup-and-Spec-Naming-Style/
Best regards,
| Sean Kennedy | |||
| OSLC Community Development Leader for IBM Rational | |||
| Operations Coordinator for the OSLC Steering Committee | |||
| Phone: | +1-905-413-4385 | 8200 Warden Ave | |
| Fax: | +1-905-413-4850 | Markham, Ontario L6G 1C7 | |
| Email: | seanpk@xxxxxxxxxx | D1/R0A/8200/MKM | |
| LinkedIn: | http://www.linkedin.com/in/seanpk | Canada | |
| OSLC: Lifecycle integration inspired by the web | http://open-services.net | ||
| Eclipse Lyo: Enabling tool integration with OSLC | http://eclipse.org/lyo | ||
| There is nothing more powerful than an idea whose time has come. -- Victor Hugo | |||
| Sean Kennedy <seanpk@xxxxxxxxxx> |
| lyo-dev@xxxxxxxxxxx |
| 07/09/2013 12:54 PM |
| Re: [lyo-dev] Any objections to changing OSLC4J project names? |
| lyo-dev-bounces@xxxxxxxxxxx |
| Sean Kennedy | |||
| OSLC Community Development Leader for IBM Rational | |||
| Operations Coordinator for the OSLC Steering Committee | |||
| Phone: | +1-905-413-4385 | 8200 Warden Ave | |
| Fax: | +1-905-413-4850 | Markham, Ontario L6G 1C7 | |
| Email: | seanpk@xxxxxxxxxx | D1/R0A/8200/MKM | |
| LinkedIn: | http://www.linkedin.com/in/seanpk | Canada | |
| OSLC: Lifecycle integration inspired by the web | http://open-services.net | ||
| Eclipse Lyo: Enabling tool integration with OSLC | http://eclipse.org/lyo | ||
| There is nothing more powerful than an idea whose time has come. -- Victor Hugo | |||
