Hi All,
I've got a question regarding the possibility of making cyclonedds a top-level GitHub project. I'm not sure if this is the right list to ask that question, if it isn't, please let me know the right list. If it is, and I'm looking at the problem in the wrong way, please let me know too. It's just that making it a top-level project seems like the best solution.
There's two reasons for me to want to promote it to a top-level GitHub project.
1. Faster Travis and AppVeyor builds. Right now builds for pull requests take a long time and that'll only get worse when more projects are going to join.
2. Dependencies. We're planning on implementing a better IDL compiler to get quicker build and drop the Java dependency. Because we're looking to implement support for more language bindings, now seems like the right time to do that. Now, the IDL compiler will need a preprocessor. We've more-or-less decided to go with mcpp (
http://mcpp.sourceforge.net/). The product itself is hosted on SourceForge, which is a little slow and code is still hosted in svn. The biggest problem however is that the original author isn't doing any work on the project anymore and nobody can accept patches etc. For that reason we want to "fork" it (svn import on GitHub) to fix some small bugs etc. In my opinion hosting the project under a top-level cyclonedds GitHub project is the best place. That way it's neatly separated from the cyclonedds code while all members/privileges etc can be managed by the project leads and committers.
Please let me know if it's possible or if there are better ways to go about this.
Best regards,
Jeroen Koekkoek
_______________________________________________
iot-pmc mailing list
iot-pmc@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/iot-pmc