Bugzilla – Full Text Bug Listing
| Summary: | [proposal] tools.wildwebdeveloper (was "bluesky") | ||
|---|---|---|---|
| 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: | cdtdoug, cydnie.smith, denis.roy, gautier.desaintmartinlacaze, mistria, sharon.corbett, webmaster, zulus |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-bluesky-web-development-eclipse-ide | ||
| See Also: | https://dev.eclipse.org/ipzilla/show_bug.cgi?id=17267 | ||
| Whiteboard: | |||
| Bug Depends on: | 536650 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Can I now update the project proposal to be Eclipse Wild Web Developer? (In reply to Mickael Istria from comment #1) > Can I now update the project proposal to be Eclipse Wild Web Developer? Please do. I'll schedule the creation in the next review slot. Updated proposal with new name. We’ve received all of the project requirements and have scheduled the creation review to conclude on 08/23/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 We’ve received all of the project requirements and have scheduled the creation review to conclude on 08/01/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 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 It seems like the paperwork was processed for me so according to last comment, I should be able to open the Initial Contribution CQ. However, the CQ page tells me that the project isn't created on IPZilla so I cannot create CQ. Is there anything missing on my side? (In reply to Mickael Istria from comment #7) > It seems like the paperwork was processed for me so according to last > comment, I should be able to open the Initial Contribution CQ. However, the > CQ page tells me that the project isn't created on IPZilla so I cannot > create CQ. > Is there anything missing on my side? Just time. The webmaster's have to push some bits around to get the project into a ready state. They'll post a notice here when we're good-to-go. By way of process, the first step is to get committers sorted out. Once we have at least one committer ready to go, the webmaster starts provisioning the actual project resources. The time required to complete this is dependent on the depth of the webmaster's work queue. The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management: https://git.eclipse.org/r/#/admin/projects/wildwebdeveloper/wildwebdeveloper Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=wildwebdeveloper Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/wildwebdeveloper-dev Project Website repository: https://git.eclipse.org/r/#/admin/projects/www.eclipse.org/wildwebdeveloper Commits will be published to www.eclipse.org/wildwebdeveloper within 5 minutes Downloads: http://download.eclipse.org/wildwebdeveloper Archives: http://archive.eclipse.org/wildwebdeveloper Builds: You can upload releases to ~committer_id/downloads/wildwebdeveloper 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. I've opened all CQs. There is one that needs to be reopen as I clicked "withdraw" by mistake, it's the one about initial contrtibution https://dev.eclipse.org/ipzilla/show_bug.cgi?id=17267 . Can someone in IP team please take care of reopening? (In reply to Denis Roy from comment #9) > The project provisioning process is complete! Here you will find all of the > information regarding resources allocated to your project: > > Source Code Management: > https://git.eclipse.org/r/#/admin/projects/wildwebdeveloper/wildwebdeveloper > Issue Tracker: > https://bugs.eclipse.org/bugs/describecomponents.cgi?product=wildwebdeveloper On the project proposal, we selected the GitHub option. Can you please create the related GitHub repository and remove the Gerrit and Bugzilla entries for wildwebdeveloper? Thanks in advance! (In reply to Mickael Istria from comment #11) > On the project proposal, we selected the GitHub option. > Can you please create the related GitHub repository and remove the Gerrit > and Bugzilla entries for wildwebdeveloper? > Thanks in advance! Webmaster, we have checkin on the initial contribution. Can you please make this happen? (In reply to Wayne Beaton from comment #12) > Webmaster, we have checkin on the initial contribution. Can you please make > this happen? Done, committers that have added their Github ids to their Eclipse.org accounts should get invites to join the Github wildwebdeveloper team within an hour or so. -M. (In reply to Eclipse Webmaster from comment #13) > (In reply to Wayne Beaton from comment #12) > > > Webmaster, we have checkin on the initial contribution. Can you please make > > this happen? > > Done, committers that have added their Github ids to their Eclipse.org > accounts should get invites to join the Github wildwebdeveloper team within > an hour or so. Thanks. Is it also planned/possible to transfer issues from https://github.com/mickaelistria/eclipse-bluesky to https://github.com/eclipse/wildwebdeveloper/issues ? (In reply to Mickael Istria from comment #14) > Thanks. Is it also planned/possible to transfer issues from > https://github.com/mickaelistria/eclipse-bluesky to > https://github.com/eclipse/wildwebdeveloper/issues ? Can you please answer this? ^ Also, if it's possible to transfer issues, should I push the code anyway or is it better for you to first take care of migrating the issues? (In reply to Mickael Istria from comment #15) > (In reply to Mickael Istria from comment #14) > > Thanks. Is it also planned/possible to transfer issues from > > https://github.com/mickaelistria/eclipse-bluesky to > > https://github.com/eclipse/wildwebdeveloper/issues ? > > Can you please answer this? ^ > Also, if it's possible to transfer issues, should I push the code anyway or > is it better for you to first take care of migrating the issues? Webmaster, can you help? (In reply to Mickael Istria from comment #14) > Thanks. Is it also planned/possible to transfer issues from > https://github.com/mickaelistria/eclipse-bluesky to > https://github.com/eclipse/wildwebdeveloper/issues ? My understanding is that there is no way to move issues between repos. -M. (In reply to Eclipse Webmaster from comment #17) > My understanding is that there is no way to move issues between repos. When I contributed aCute, I think issues were migrated with new repo creation. IIRC, it involved changing ownership of former repo to EclipseFdn so the whole repo could be transferred or something like that. (In reply to Mickael Istria from comment #18) > IIRC, it involved changing ownership of former repo to EclipseFdn so the > whole repo could be transferred or something like that. I would expect the issues to stay if we were transferring the repo, but based on this bug I got the impression that a new repo was desired to make the history cleaner. -M. (In reply to Eclipse Webmaster from comment #19) > I would expect the issues to stay if we were transferring the repo, but > based on this bug I got the impression that a new repo was desired to make > the history cleaner. If it's possible to just transfer the repo, then I prefer it by far. I don't think I asked for a fresh repo at any time, but I may have been unclear at some point. Anyway, can we delete the current empty repo and transfer mickaelistria/eclipse-bluesky to eclipse/wildwebdeveloper? (In reply to Mickael Istria from comment #20) > Anyway, can we delete the current empty repo and transfer > mickaelistria/eclipse-bluesky to eclipse/wildwebdeveloper? Has the history been squashed? If so you'll need to invite 'eclipsewebmaster' to join the admin team for the existing repo and we can handle the move. -M. (In reply to Eclipse Webmaster from comment #21) > Has the history been squashed? If so you'll need to invite > 'eclipsewebmaster' to join the admin team for the existing repo and we can > handle the move. Ok thanks. So 1. I've just squashed the history on the master branch 2. I've renamed repository to wildwebdeveloper 3. I've added eclipsewebmaster as a collaborator on the repo Feel free to proceed whenever you can, and to ping me if there is anything wrong. I've accepted the invite, but you'll need to grant me admin permissions on the repo before I can move it. -M. (In reply to Eclipse Webmaster from comment #23) > I've accepted the invite, but you'll need to grant me admin permissions on > the repo before I can move it. Ok. It seems like I cannot add admins for personal repos. I've created a sandbox organization, transfered repo to it, and made eclipsewebmaster admin: https://github.com/sandbox-wildwebdeveloper/wildwebdeveloper/settings/collaboration Please check whether this new repo and additional permission give you the power you need. Ok I've moved the repo into the Eclipse org and set the team permissions. -M. (In reply to Eclipse Webmaster from comment #25) > Ok I've moved the repo into the Eclipse org and set the team permissions. Awesome! Thanks a lot! Next questions (I can open another ticket if it's preferred): can we have a CI instance for wildwebdeveloper? Yes please file a new bug for that. -M. 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 I've created https://projects.eclipse.org/projects/tools.wildwebdeveloper/reviews/0.1.0-release-review to initiate the first review of Wild Web Developer next week. This project has engaged in a release. I declare it fully operational. This bug is now closed! |