Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.openk-usermodules | ||
|---|---|---|---|
| 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: | angelika.wittek, cydnie.smith, jhelming, jonas.tewolde, sharon.corbett, thorsten.jaspert, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-openk-user-modules | ||
| Whiteboard: | stalebug | ||
|
Description
Wayne Beaton
> -Transfer ownership of the project name trademark to the Eclipse Foundation
I'm pretty sure that we don't need to do anything with the trademark given that we already claim "openK". I'll confirm.
Since I'm pretty sure that we don't need to do any work on the trademark transfer, I have scheduled the creation review to conclude on July 4/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 Some of the names in the people list of the proposal are not linked with the related eclipse profile of the users. This should be checked (In reply to Jonas Tewolde from comment #3) > Some of the names in the people list of the proposal are not linked with the > related eclipse profile of the users. This should be checked This is an idiosyncrasy of our implementation. A link is rendered only when either the user has an existing relationship (e.g. is a committer on an existing project), or has used their Eclipse Foundation account to log in to projects.eclipse.org. AFAICT, all listed committers have Eclipse Foundation accounts; that's all that we need to provision the project. 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). [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution I've removed committer T. Meyer from the project committer list since he has not created an Eclipse Foundation account. He will have to be elected to the project after it is has been provisioned and established. 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/openk-usermodules/openk-usermodules.git Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=openk-usermodules Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/openk-usermodules-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/openk-usermodules.git Commits will be published to www.eclipse.org/openk-usermodules within 5 minutes Downloads: http://download.eclipse.org/openk-usermodules Archives: http://archive.eclipse.org/openk-usermodules Builds: You can upload releases to ~committer_id/downloads/openk-usermodules 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. IP requests are referred to as Contribution Questionnaires (CQs). When the initial CQ receives “check in” and/or “full approval” you are now ready to check the initial project code contribution into your project’s repository. [1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution Hi Wayne, Ina (ina.curdt@pta.de) was in the list of initial committers (https://projects.eclipse.org/projects/technology.openk-usermodules/reviews/creation-review). Her paperwork is done, but she is not a committer yet? Could you check if something went wrong? Thanks Jonas Hi Jonas, Ina's paperwork has been reviewed and her committer account has been provisioned. Let me know if there is anything else I can help with. Regards, Cydnie Your initial contribution has been approved and there is code in your source code repository; It is now time to plan your first release! If you haven't already done so, it is time to create a release record. If you have already created your release record, you may revise your date to most accurately reflect project progression. Once your release record is created, confirm the date and engage in the process. For more information about the release process, check out our handbook [1]! [1] https://www.eclipse.org/projects/handbook/#release Hello project team, AFAICT, your initial contribution was approved and you have no outstanding CQs. It looks like this project is active; however, there have been no releases planned. What is the status of your first release? If you need any assistance, please let us know! For more information on the release process, please feel free to check out our handbook [1]. [1] https://www.eclipse.org/projects/handbook/#release This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant. -- The automated Eclipse Genie. The project is operational. We're done here. Hint: it's been a full year, is it time to start thinking about a first release review? |