Bugzilla – Full Text Bug Listing
| Summary: | [proposal] iot.oneofour | ||
|---|---|---|---|
| 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: | jreimann, philippe.schaller, sharon.corbett, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Mac OS X | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-oneofour | ||
| Whiteboard: | |||
| Bug Depends on: | 560988 | ||
| Bug Blocks: | |||
|
Description
Maria Teresa Delgado
The initial requirements should now be fulfilled. All listed committers have Eclipse accounts and I answered on the trademark ownership issue. I am fairly new to this. Is there anything else I need to do? Hi Philippe, after you send the Trademark agreement to Sharon and the trademark is approved we can move forward with the Creation review. For more information regarding the workflow please visit: https://www.eclipse.org/projects/handbook/#starting-proposal Hi, as far as I am informed there are no registered trademarks involved. The name 'OneOFour' came up during an email conversation on the emo mailing list and there is no prior use. Everything else is part of the existing Eclipse NeoSCADA project. Which means I wait for Sharon's answer on the subject on my statement on issue #560988. Thanks & regards Philippe We’ve received all of the project requirements and have scheduled the creation review to conclude on April 15th 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 As the project will be bootstrapped from content originating from the Eclipse NeoSCADA project (which is scheduled to be archived), I don't think there will be an initial contribution, but a restructuring review. 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/oneofour . Committers that have added their Github ID to their Eclipse.org accounts will start receiving invites to join the oneofour Github team shortly. Issue Tracker: Github issues have been enabled for your project. Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/oneofour-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/oneofour.git Commits will be published to www.eclipse.org/oneofour within 5 minutes Downloads: http://download.eclipse.org/oneofour Archives: http://archive.eclipse.org/oneofour Builds: You can upload releases to ~committer_id/downloads/oneofour via SFTP or SCP (to build.eclipse.org) or from a CI instance at Eclipse.org Older builds should be moved to the archives area when they are no longer required. -M. As far as I can tell, there has been no activity on this project. Please provide status update. Status update: - the relevant parts of NeoSCADA have been copied to https://github.com/eclipse/oneofour - updated project structure - updated library dependencies - simple integration into https://ci.eclipse.org/oneofour From my point of view we could cut a first release. Though, I might need a little help with the process... This project has never been expected to be one with a high beat rate. It has been created to salvage a tiny, but crucial, part of NeoSCADA which is used by two Apache Camel components. Honestly, other than that, I have no knowledge of it being used anywhere else. There are a couple of sore spots in the code mentioned in code comments by the previous maintainers. These can be addressed later. Hi Philippe, thank you for the update. If you are willing to make the first official release there is more information available in the handbook: https://www.eclipse.org/projects/handbook/#release-review Basically, release reviews require review documentation (PMC approval) and an intellectual property (IP) log check. Don't hesitate to contact me directly if you still have questions. Maria Teresa Hi all, After reading the relevant parts of Eclipse Project Handbook and comparing that with actual projects like e.g. Eclipse Hono a couple of changes have been made: Added: - LICENSE - NOTICE.md - CONRIBUTING.md - licenses and notices of dependencies Updated: - copyright and license headers of the Java files to match the templates from the Eclipse Project Handbook - dependency versions to such ones with approved CQs - copying of legal documents to META-INF folder inside JARs After that have been merged to the repository I humbly ask what the next steps are to be able to start a first, proper release review? I am quite sure there are plenty of missing things, especially in the details, but the above points were the most obvious ones. Best regards Philippe Hi Philippe, first thing to do is create a new release, using the committer tools you'll find at the right column of your project page. You need to be logged in in order to access these tools. I would recommend you draft your project release plan ahead in time, so our IP team can also plan to allocate the needed resources for your project accordingly. There is useful information about the release reviews process on the handbook: https://www.eclipse.org/projects/handbook/#release-review Once you've created the release record, you need to submit your IP log for EMO approval, and ask for PMC approval on the IoT PMC mailing list. Please make sure you start this process at least 2 weeks in advance. Please feel free to contact me or EMO if you need assistance with the process. Maria Teresa 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 |