Bugzilla – Full Text Bug Listing
| Summary: | [proposal] iot.keyple | ||
|---|---|---|---|
| Product: | Community | Reporter: | Wayne Beaton <wayne.beaton> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | contact, cydnie.smith, jreimann, nicolas.generali, pierre.terree, sharon.corbett, webmaster, yvonne.yam |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-keyple | ||
| Whiteboard: | |||
| Bug Depends on: | 536371, 536372 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Note that the requested project licensing scheme (dual licensed EPL-2.0 and EDL-1.0) is preapproved via the Eclipse IoT Top Level Project Charter. We have a mentor. I believe that we're good-to-go. Cydnie, can you take the next step to schedule this into the October 3 review slot? One committer, Florent, does not have an Eclipse Foundation Account (at least not with the specified email address). Can somebody from the project team connect with them to ensure that they register with the Eclipse Foundation [1]? Committers that do not have an account will be removed from the proposal before we engage in the provision process following the review period. [1] https://accounts.eclipse.org Dear all, I have removed Florent from the list of the commiters. Regards, Yvonne YAM We’ve received all of the project requirements and have scheduled the creation review to conclude on October 3, 2018. 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 time frame 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/keyple . Committers that have added their Github ID to their Eclipse.org accounts will start receiving invites to join the keyple Github team shortly. Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=keyple Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/keyple-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/keyple.git Commits will be published to www.eclipse.org/keyple within 5 minutes Downloads: http://download.eclipse.org/keyple Archives: http://archive.eclipse.org/keyple Builds: You can upload releases to ~committer_id/downloads/keyple 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. Your initial contribution has been approved; it is now time to plan your first release! If you haven't already done so, it is time to create a release record. If you have already created your release record, you may revise your date to most accurately reflect project progression. Once your release record is created, confirm the date and engage in the process. For more information about the release process, check out our handbook [1]! [1] https://www.eclipse.org/projects/handbook/#release Greetings project team, It looks like you have two releases planned for April - one was for April 2, and the other for April 30th - but it appears you haven't engaged in the release process yet. What is the status of these releases? Is there anything we can assist with? For more information on the release process, please check out the handbook [1]. [1] https://www.eclipse.org/projects/handbook/#release Congratulations, you have engaged in your first release. I declare this project fully operational. This bug is now resolved. |