Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.lemminx | ||
|---|---|---|---|
| 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: | azerr, fbricon, mariateresa.delgado, sharon.corbett, thatnitind, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-lemminx | ||
| Whiteboard: | |||
| Bug Depends on: | 553554 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Fred, what short name are you using in the code base? That is, "org.eclipse.<what>"? I'd like to set the project's short name to match. As mentioned in the proposal, the namespace/package of the project would be org.eclipse.xml.ls > As mentioned in the proposal, the namespace/package of the project would be
> org.eclipse.xml.ls
Right. Since periods are meaningful in our project ids, we'll make the short name "xmlls". The project website will be, for example, eclipse.org/xmlls
So the new (approved) project name is LemMinX. That means we'll be technology.lemminx and the namespace will be org.eclipse.lemminx I've updated the project proposal: https://projects.eclipse.org/proposals/eclipse-lemminx We’ve received all of the project requirements and have scheduled the creation review to conclude on February 5th 2020. 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/lemminx-dev
Project Website repository:
ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/lemminx.git
Commits will be published to www.eclipse.org/lemminx within 5 minutes
Downloads: http://download.eclipse.org/lemminx
Archives: http://archive.eclipse.org/lemminx
Builds: You can upload releases to ~committer_id/downloads/lemminx 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. 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 Closing this bug since the project has already made its first release and seems to be fully operational. |