Community
Participate
Working Groups
We need to re-evaluate how COSMOS drivers are packaged. The following wiki page explores some ideas: http://wiki.eclipse.org/Build_Packaging_for_COSMOS
Assigning this to Saurabh to work with development to figure out the best way to package the COSMOS drivers. Saurabh, this is important for us to have by the time that COSMOS releases, which means that we should have the bulk of this done by i10 and only bug fixes done for this in i11.
Assigning to Leonard as per Saurabh's/Jack's request.
Hi Ali, Most of the suggestions provided in wiki page have been implemented. Do you feel that we should have one more meeting to close this bug. I suppose when we introduce WSDM tooling and SDD related stuff then these requirement might change.
Hi Saurabh I think it makes sense in dividing COSMOS based on branches of System Management. With the code we currently have in COSMOS we can have two top-level categories: "Data Integration" and "Deployment". Each category will have runtime, tooling, and samples. We can also have a common top-level category to include all core components. Here's the overall structure I have in mind: Framework |_ Runtime Data Integration (requires Framework) |_ Runtime |_ Samples |_ Tooling Deployment (requires Framework) |_ Runtime |_ Samples |_ Tooling We need to revisit this prior to our release. I would change the target to i11/future but I wouldn't close this yet. Thanks.
The proposed build structure wiki page was updated on May 27, and I think it represents a consensus decision. What is the target iteration for completing these changes?
