Bugzilla – Full Text Bug Listing
| Summary: | [proposal] iot.kiso | ||
|---|---|---|---|
| Product: | Community | Reporter: | Cydnie Smith <cydnie.smith> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | hans-uwe.rempler, jreimann, sharon.corbett, wayne.beaton, webmaster, yong.shen |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| URL: | https://projects.eclipse.org/proposals/kiso | ||
| Whiteboard: | |||
| Bug Depends on: | 545903, 545904 | ||
| Bug Blocks: | |||
|
Description
Cydnie Smith
We’ve received all of the project requirements and have scheduled the creation review to conclude on May 15 2019. 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: A new repository has been created at Github for your project: https://github.com/eclipse/kiso . Committers that have added their Github ID to their Eclipse.org accounts will start receiving invites to join the kiso Github team shortly. Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=kiso Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/kiso-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/kiso.git Commits will be published to www.eclipse.org/kiso within 5 minutes Downloads: http://download.eclipse.org/kiso Archives: http://archive.eclipse.org/kiso Builds: You can upload releases to ~committer_id/downloads/kiso 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 Hello project team, It looks like we haven't received your initial contribution. Is there anything we can help with? For more information on the process, please check out the handbook: https://www.eclipse.org/projects/handbook/#starting (In reply to Cydnie Smith from comment #5) > Hello project team, > > It looks like we haven't received your initial contribution. Is there > anything we can help with? > > For more information on the process, please check out the handbook: > https://www.eclipse.org/projects/handbook/#starting Hi Cydnie, sorry for the delay. We had some (Bosch) challenges which we needed to address the last couple of months. But, now we're back on track. I uploaded the initial code contribution yesterday, see https://dev.eclipse.org/ipzilla/show_bug.cgi?id=21010. Now, I'll just wait for the review of our code drop and looking forward pushing the code to https://github.com/eclipse/kiso :) Cheers, Uwe Housekeeping. The project onboarding is complete. |