Bugzilla – Full Text Bug Listing
| Summary: | [proposal] iot.kuksa | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Community | Reporter: | Kasandra Darwin <kasandra.darwin> | ||||
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> | ||||
| Status: | RESOLVED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | cydnie.smith, jnhuva, johannes.kristan, robert.hoettger, sharon.corbett, wayne.beaton, webmaster | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows NT | ||||||
| URL: | https://projects.eclipse.org/proposals/eclipse-kuksa | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | |||||||
| Bug Blocks: | 526371, 526372 | ||||||
| Attachments: |
|
||||||
|
Description
Kasandra Darwin
We’ve received all of the project requirements and have scheduled the creation review to conclude on DEC 6, 2017. 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 Congratulations! Your project review is 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 60 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). [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: ssh://committer_id@git.eclipse.org:29418/kuksa/org.eclipse.kuksa.git Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=kuksa Outbound Communication: Mailing list: https://dev.eclipse.org/mailman/listinfo/kuksa-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/kuksa.git Commits will be published to www.eclipse.org/kuksa within 5 minutes Downloads: http://download.eclipse.org/kuksa Archives: http://archive.eclipse.org/kuksa Builds: You can upload releases to ~committer_id/downloads/kuksa 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 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. IP requests are referred to as Contribution Questionnaires (CQs). When the initial CQ receives “check in” and/or “full approval” you are now ready to check the initial project code contribution into your project’s repository. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution Created attachment 273700 [details]
Kuksa initial contribution
Please find attached Kuksa's initial contribution for the initial IP check. Please get back to me regarding questions, remarks, issues, etc.
(In reply to Robert Hoettger from comment #5) > Created attachment 273700 [details] > Kuksa initial contribution Hi Robert. I see that you've also attached this to the IPZilla record (CQ) [1]. The IP Team will communicate with you via that CQ. [1] https://dev.eclipse.org/ipzilla/show_bug.cgi?id=16130 The initial contribution has recently been IP checked successfully. Our plan is to have 5 GitHub repositories, i.e. * Kuksa.Apps * Kuksa.Cloud * Kuksa.IDE * Kuksa.Integration * Kuksa.InVehicle What is the process to trigger / support this plan? Apart from the website repo, we may use org.eclipse.kuksa.git for the integration activities, but this is subject to further investigations. (In reply to Robert Hoettger from comment #7) > What is the process to trigger / support this plan? According to the project proposal, your plan is to host these repositories on GitHub. If this is indeed the case, tell the webmaster specifically what you need to do (e.g. do existing repositories need to be moved, or new ones created?) Webmaster is monitoring this channel, so you can make your request here. Yes, we would like to stick to the project proposal, i.e., request the five new repositories * Kuksa.Apps * Kuksa.Cloud * Kuksa.IDE * Kuksa.Integration * Kuksa.InVehicle at the GitHub Eclipse Foundation space (there is nothing to be moved). I would then push the respective parts of the initial contribution to the corresponding repositories, if I am granted access (account name is rohoet). (In reply to Robert Hoettger from comment #9) > I would then push the respective parts of the initial contribution to the > corresponding repositories, if I am granted access (account name is rohoet). If you've specified your GitHub id in your account (http://accounts.eclipse.org), this access should be granted automatically. I've created the repos and updated the Kuksa metadata. Project committers should be invited to join the Kuksa Gtihub team in an hour or so when the sync tool runs. -M. Your initial contribution has been approved and there is code in your source code repository, it's time to plan your first release. The handbook [1] contains more information about the release process. [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. |