Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.set | ||
|---|---|---|---|
| Product: | Community | Reporter: | Cydnie Smith <cydnie.smith> |
| Component: | Proposals and Reviews | Assignee: | Eclipse Management Organization <emo> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | bleidiessel.joachim, christoph.klaus, denis.roy, mariateresa.delgado, mkoegel, reiner.broedel, sharon.corbett, wayne.beaton, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Windows 10 | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-planpro-toolbox | ||
| Whiteboard: | |||
| Bug Depends on: | 541658, 541659 | ||
| Bug Blocks: | |||
|
Description
Cydnie Smith
The RailPL license is not a OSI-approved open source license, can the existing artifacts be re-licensed under the EPL-2.0? Can you describe how the LGPL licensed content and how it is used by the project? We’ve received all of the project requirements and have scheduled the creation review to conclude on 01/31/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 Apologies, We’ve received all of the project requirements and have scheduled the creation review to conclude on 02/06/2019. 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 We have not yet received paperwork from any of your project committers. Without this paperwork, we cannot move forward on the provisioning process for your new project. Please let me know if there is anything that I can do to assist. 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/set/set.git Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=set Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/set-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/set.git Commits will be published to www.eclipse.org/set within 5 minutes Downloads: http://download.eclipse.org/set Archives: http://archive.eclipse.org/set Builds: You can upload releases to ~committer_id/downloads/[shortname] 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 Greetings project team, It looks like we haven't received your initial contribution. Is there anything we can assist with? For more information on the edp, feel free to check out our handbook: https://www.eclipse.org/projects/handbook/#starting Project team, what is your status? Dear Wayne, the initial contribution was made today. https://dev.eclipse.org/ipzilla/show_bug.cgi?id=22199 Hope that fits! We are awaiting your comments. Thanks and best regards! > Source Code Management: > > ssh://committer_id@git.eclipse.org:29418/set/set.git The set project is hosted on gitlab: https://gitlab.eclipse.org/eclipse/set/set The above Gerrit repo can be deleted. Hi Wayne, Christoph and I pushed the initial code contribution [1] to our Eclipse Gitlab repo. Best regards, Joachim [1] https://gitlab.eclipse.org/eclipse/set/set/-/commit/ff3a7154298d2e5d9ef35315862fb901ab0e97ea Hi Wayne, any news on the code check? Do we have to do something to start the procedure or is it still ongoing? Thanks for advice! Best regards, Christoph > any news on the code check? Do we have to do something to start the
> procedure or is it still ongoing? Thanks for advice!
The IP team has it in their queue. In the meantime, the project team can write code and push commits.
I'm trying to get a sense for the third-party content used by the project. It looks like some test bundles are missing and the target is trying to pull from a server that's not accessible to me. Am I missing something?
(In reply to Wayne Beaton from comment #14) > It looks like some test bundles are missing and the target is trying to pull > from a server that's not accessible to me. Am I missing something? Dear Wayne, you are right, we just committed the code 'as is' for the ip check and therefore have dependencies to internal mirrors of p2 repositories containing third party. If its suitable for the process (and I understand that it is) we would start to adapt the dependencies to public repos. Same goes for the test bundles which we omitted for the ip check. > you are right, we just committed the code 'as is' for the ip check and > therefore have dependencies to internal mirrors of p2 repositories > containing third party. If its suitable for the process (and I understand > that it is) we would start to adapt the dependencies to public repos. Yes please do. Please get your repository into a "buildable" state. > Same goes for the test bundles which we omitted for the ip check. If you have not done so already, be sure to pass those test bundles to the IP for review as "project code". Once you have everything in a buildable state, I'll help you sort out your third party content. There's some help in the handbook regarding what we do about third party content [1] [1] https://www.eclipse.org/projects/handbook/#ip-third-party AFAICT this project seems to be inactive. Project team: can you provide a status update or should I consider the project as a candidate for termination? We are aware of the slow process and are sorry for that. We had to take some organizational steps forward (I.e. our company now is a eclipse fnd. member) but are now starting to commit the current codebase. (In reply to Maria Teresa Delgado from comment #17) > AFAICT this project seems to be inactive. > Project team: can you provide a status update or should I consider the > project as a candidate for termination? (In reply to Joachim Bleidiessel from comment #18) > We are aware of the slow process and are sorry for that. We had to take some > organizational steps forward (I.e. our company now is a eclipse fnd. member) > but are now starting to commit the current codebase. > > (In reply to Maria Teresa Delgado from comment #17) > > AFAICT this project seems to be inactive. > > Project team: can you provide a status update or should I consider the > > project as a candidate for termination? No problem Joachim. Please connect directly with the EMO (emo@eclipse.org) when the project is ready to engage in an official release review. In the mean time we can close this bug. |