Bugzilla – Full Text Bug Listing
| Summary: | [proposal] tools.corrosion | ||||||
|---|---|---|---|---|---|---|---|
| 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: | akurtakov, cdtdoug, Lars.Vogel, lbullen, sharon.corbett, wayne.beaton, webmaster | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 10 | ||||||
| URL: | https://projects.eclipse.org/proposals/eclipse-redox-eclipse-ide-rust | ||||||
| Whiteboard: | |||||||
| Bug Depends on: | 529674 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Kasandra Darwin
I've updated the project name based on the results of the trademark search. We’ve received all of the project requirements and have scheduled the creation review to conclude on February 21/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 Created attachment 272560 [details]
The corrosion logo
Here is the updated logo for Eclipse Corrosion.
(In reply to Lucas Bullen from comment #3) > Created attachment 272560 [details] > The corrosion logo > > Here is the updated logo for Eclipse Corrosion. Ignore this. Attached to wrong bug. Mike, I believe that we can reasonably assert that this logo is derived from the Eclipse Logo and so we require board approval. Can you either correct me if I'm wrong or tee this up for that approval, please? (In reply to Wayne Beaton from comment #5) > Mike, I believe that we can reasonably assert that this logo is derived from > the Eclipse Logo and so we require board approval. > > Can you either correct me if I'm wrong or tee this up for that approval, > please? It has already been started I believe: https://bugs.eclipse.org/bugs/show_bug.cgi?id=529697 (In reply to Wayne Beaton from comment #5) > Mike, I believe that we can reasonably assert that this logo is derived from > the Eclipse Logo and so we require board approval. > > Can you either correct me if I'm wrong or tee this up for that approval, > please? Ignore this, apparently I just follow people off cliffs like a lemming. 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 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). [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: As your project's main Git repository is hosted at GitHub, we will need to move it to the Eclipse organization and flatten any previous history. This work can begin as soon as you have check in permission from EMO legal. Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=corrosion Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/corrosion-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/corrosion.git Commits will be published to www.eclipse.org/corrosion within 5 minutes Downloads: http://download.eclipse.org/corrosion Archives: http://archive.eclipse.org/corrosion Builds: You can upload releases to ~committer_id/downloads/corrosion 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. @EclipseWebmaster, I have been sent to you from https://dev.eclipse.org/ipzilla/show_bug.cgi?id=15779 for help making the initial commit. When attempting to commit as I usually would I receive an error: Can't connect to any repository: git clone ssh://lbullen@git.eclipse.org:29418/corrosion/corrosion (git clone ssh://lbullen@git.eclipse.org:29418/corrosion/corrosion: not found.) What is the correct course of action? Thank you. (In reply to Lucas Bullen from comment #10) > > Can't connect to any repository: git clone > ssh://lbullen@git.eclipse.org:29418/corrosion/corrosion (git clone > ssh://lbullen@git.eclipse.org:29418/corrosion/corrosion: not found.) > > What is the correct course of action? Thank you. I'm not able to replicate this. I've also taken a quick look in the Gerrit logs and I don't see any errors for your account(I do see a failed login though). Does the clone work if you use the https URL? -M. Got it to work, thank you for pointing me towards the knowledge that my gerrit and http passwords are different entities @EclipseWebmaster, To help increase exposure and potential contributors, we wish to host the Corrosion repo on GitHub instead of Gerrit. The project history has been squashed and can be found here: https://github.com/LucasBullen/corrosion/tree/48284edfc2730d3166c2270698490882453b6089 Is this possible and if so what else is required from me? Is there anything still needed from corrosion contributors to do? Have we missed some step? (In reply to Lucas Bullen from comment #13) > @EclipseWebmaster, To help increase exposure and potential contributors, we > wish to host the Corrosion repo on GitHub instead of Gerrit. The project > history has been squashed and can be found here: > https://github.com/LucasBullen/corrosion/tree/ > 48284edfc2730d3166c2270698490882453b6089 > > Is this possible and if so what else is required from me? You can absolutely use Github for your project. Since you have squashed the history there are a couple of options. 1) I can create a new Github repo (github.com/eclipse/corrosion) and you can push the squashed repo to it. 2) You can invite 'eclipsewebmaster' to join the admin team for the existing repo and we will move it into the eclipse organization on github. -M. (In reply to Eclipse Webmaster from comment #15) > Since you have squashed the history there are a couple of options. > > 1) I can create a new Github repo (github.com/eclipse/corrosion) and you can > push the squashed repo to it. > > 2) You can invite 'eclipsewebmaster' to join the admin team for the existing > repo and we will move it into the eclipse organization on github. Let's go with option 2, sent invitation: https://github.com/LucasBullen/corrosion/invitations I've accepted the invite, but as I'm not an admin I can't move the repo. -M. (In reply to Eclipse Webmaster from comment #17) > I've accepted the invite, but as I'm not an admin I can't move the repo. > > -M. Sent a collaborator invite instead of a transfer request. Request sent. OK I've accepted the transfer and have moved it into the Eclipse org (https://github.com/eclipse/corrosion). Next time the sync tools run they should create the Corrosion Github team and invite active committers to join it. -M. The project is up and running. I declare success. |