Bugzilla – Full Text Bug Listing
| Summary: | [proposal] ee4j.jsonb | ||
|---|---|---|---|
| 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: | dmitry.kornilov, nathan.rauh, sharon.corbett, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-project-json-b | ||
| Whiteboard: | |||
|
Description
Wayne Beaton
We’ve received all of the project requirements and have scheduled the creation review to conclude on March 7/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 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=jsonb
Outbound Communication:
Mailing list: https://accounts.eclipse.org/mailing-list/jsonb-dev
Project Website repository:
ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/ee4j/jsonb.git
Commits will be published to www.eclipse.org/ee4j/jsonb within 5 minutes
Downloads: http://download.eclipse.org/jsonb
Archives: http://archive.eclipse.org/jsonb
Builds: You can upload releases to ~committer_id/downloads/jsonb 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.
Quick status update: AFAICT, the project has an approved CQ for the initial contribution [1] and that initial contribution has been pushed to the project's repository [2]. A build instance [3] has been created, but is not currently configured. [1] https://dev.eclipse.org/ipzilla/show_bug.cgi?id=16450 [2] https://github.com/eclipse-ee4j/jsonb-api [3] https://ci.eclipse.org/jsonb/ We'll leave this bug open until after the project has completed its first successful release review. This project is fully operational. Bug has been resolved. |