Bugzilla – Full Text Bug Listing
| Summary: | [proposal] ecd.openvsx | ||
|---|---|---|---|
| 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: | miro.spoenemann, paul.buck, sharon.corbett, sven.efftinge, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-extension-registry | ||
| Whiteboard: | |||
| Bug Depends on: | 552865 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Per Bug 552865, we'll rename this project "Eclipse Open VSX Registry". What technical namespace will you use for this content? I'd like to try and align the project short name with that if it makes sense. Short name: openvsx Repository: github.com/eclipse/openvsx Java namespace: org.eclipse.openvsx We’ve received all of the project requirements and have scheduled the creation review to conclude on December 4/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:
Source Code Management:
As your project's main Git repository is hosted at GitHub, we will need to move it to the Eclipse organization. This work can begin as soon as you have check in permission from EMO legal.
Issue Tracker:
Github issues will be enabled for your project.
Outbound Communication:
Mailing list: https://accounts.eclipse.org/mailing-list/openvsx-dev
Project Website repository:
ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/openvsx.git
Commits will be published to www.eclipse.org/openvsx within 5 minutes
Downloads: http://download.eclipse.org/openvsx
Archives: http://archive.eclipse.org/openvsx
Builds: You can upload releases to ~committer_id/downloads/openvsx 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.
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 Thanks! We will work on an initial contribution in the following weeks, but probably we won't submit it before Christmas. @Webmaster we would like to have the source code on GitHub. Shall I create a new bug for that? Metadata for the GitHub repository: https://github.com/eclipse/openvsx Description: An open-source registry for VS Code extensions Topics: theia, vscode, extension, registry, eclipse Website: http://eclipse.org/openvsx (In reply to Miro Spoenemann from comment #7) > @Webmaster we would like to have the source code on GitHub. Shall I create a > new bug for that? No this bug will do for the initial repo. I've created the requested repo and commiters should receive access the next time the sync tool runs. Once you've added some code we can update the metadata, as those tools are currently unavailable. -M. The project page tells me "This project is not configured to accept CQs. Most likely, this is because the project has been recently created and the process of provisioning resources for the project has not yet concluded. Please contact emo@eclipse.org if you feel you have received this message in error." Is there anything missing? > Is there anything missing?
It looks like we neglected to click the checkbox that designates the project as "active" and so the script that adds the component to IPZilla did not run. I've marked the project as active; it will be added to IPZilla when the script runs tonight. Sorry for the inconvenience.
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 |