Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.adore | ||
|---|---|---|---|
| Product: | Community | Reporter: | Maria Teresa Delgado <mariateresa.delgado> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | Daniel.Hess, jan.lauermann, mariateresa.delgado, michael.behrisch, ngit, reza.dariani, sharon.corbett, stephan.lapoehn, Thomas.Lobig, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-automated-driving-open-research-adore | ||
| Whiteboard: | |||
| Bug Depends on: | 559050, 559051, 559223 | ||
| Bug Blocks: | |||
|
Description
Maria Teresa Delgado
All contributors are now registered at Eclipse. Do you currently need any more input on the other three open points? Best Daniel Hi Daniel, I have sent you an email in the previous days regarding the fact that some of your dependencies are using non approved 3rd party licenses. Look forward to receiving your comments on this. We are using two libraries with LGPL licenses, qpOASES and ZeroMQ. (Hopefully the FLOSS exception of XSD is considered to be compatible) ZeroMQ is employed by our plotting tool plotlab in order to have an output channel that is independent of the middle ware (we have the option to replace the middle ware, e.g. ROS1 by ROS2 or our internal tool Dominion). I believe ZeroMQ can be replaced relatively easily by any other “transport” library, such as nanomsg(MIT), rabbitmq (Mozilla) and maybe others. Yet, as far as I know ZeroMQ is the most performant solution. qpOASES is central to the core motion planning module and therefore quite important to the overall software library. It could in theory be replaced OSQP(Apache2.0), but that would take a lot of work and research and would considerably delay the publication of the project. I do not know how important the LGPL policy is to Eclipse. Of course it would be optimal from our perspective to continue with both libraries. We can offer to replace ZeroMQ. Maybe you even have a proposition of which alternative library to use. As it is very time-consuming to replace qpOASES, we would really like to seek approval of the Eclipse Board of Directors for that library. Draft: Petition for an exception to the Eclipse standard-licensing scheme We are applying for an Eclipse project "Eclipse ADORe" (Automated Driving Open Research), which covers planning, decision making and control of automated vehicles. A special focus lies on simulation and impact analysis of automated driving (AD), which benefits from our tight integration with Eclipse SUMO and our light-weight approach to overall vehicle control. Our team at DLR has been developing the code base since 2017 and would like to contribute as much of our know-how and software modules as possible, in order to facilitate open research on methods, safety and analysis of AD-impact on traffic. Our project currently links against two LGPL libraries, which is not in accordance with the standard Eclipse licensing policy. ZeroMQ for fast, system-independent inter-process communication. qpOASES for linear-quadratic optimization, applied in computation of optimal trajectories for the automated vehicles, (a core aspect of AD). Both libraries are state-of-the-art and well known for their performance. They enable us to simulate multiple vehicle automations on a standard multi-core pc and thus centrally support our goals described above. We would therefore like to petition the EMO Executive Director and/or the Eclipse Board of directors to allow us to continue the Eclipse project application process with an exception to the standard licensing scheme for the two libraries ZeroMQ and qpOASES. This is good information. Thanks for providing it. We'll get the IP Team to engage after we're done with the project creation (we'll get you to open an IP review request in parallel with the project's initial contribution). They have a process for this. We’ve received all of the project requirements and have scheduled the creation review to conclude on March 4th 2020. Please continue to monitor communication channels. Following the creation review, we will initiate the provisioning process. As part of this process, we will bring committers on board. To gain committer status, some paperwork [1] must be completed. The exact nature of that paperwork depends on several factors, including the employment status of the individual and the Eclipse Foundation membership status of the employer. If you can be ready with the paperwork in time for the completion of the creation review, then we can move quickly through the provisioning process. When we initiate provisioning, committers will be sent an email with instructions; please don't send any paperwork in until after you receive those instructions. Please encourage all future project committers to join the incubation mailing list [2]. We use this list to connect committers from new projects to their peers in other projects in the incubation phase and to mentors who can help answer questions and discuss issues related to the project onboarding process. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://dev.eclipse.org/mailman/listinfo/incubation I declare the Creation Review successful! We will initiate the project resources provisioning process shortly. Please tell your project committers to carefully monitor their email for a message from The Eclipse Foundation with instructions for providing committer paperwork [1]. Our IT team cannot allocate project resources until after we have processed the paperwork for at least one committer, so your attention in this matter will keep the process moving forward. Be advised that the paperwork process will time out after 120 days; any committers who are unable to complete their paperwork requirements in this timeframe will have to be elected to the project (your project mentors can provide assistance with this). The next step is to submit an initial contribution [2] for review by the IP Team. Please do not commit any code to an Eclipse Foundation Git repository until after you receive the IP Team's approval. You may only push content into project repositories after your initial contribution IP Request (referred to as Contribution Questionnaires or "CQs") receives “check in” and/or “full approval”. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management: A new repository has been created at Github for your project: https://github.com/eclipse/adore . Committers that have added their Github ID to their Eclipse.org accounts will start receiving invites to join the adore Github team shortly. Issue Tracker: Github issues have been enabled for your project. Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/adore-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/adore.git Commits will be published to www.eclipse.org/adore within 5 minutes Downloads: http://download.eclipse.org/adore Archives: http://archive.eclipse.org/adore Builds: You can upload releases to ~committer_id/downloads/adore via SFTP or SCP (to build.eclipse.org) or from a CI instance at Eclipse.org -M. Older builds should be moved to the archives area when they are no longer required. Your next step is to submit an initial contribution [1] for review by the IP Team. Please do not commit any code to an Eclipse Foundation Git repository until after you receive the IP Team's approval. You may only push content into project repositories after your initial contribution IP Request (referred to as Contribution Questionnaires or "CQs") receives “check in” and/or “full approval”. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution The project is up and running. I'm marking this as fixed. The next step for the project team is to engage in their first release and corresponding release review. There is more information and help in the handbook [1]. [1] https://www.eclipse.org/projects/handbook/#release |