Bugzilla – Full Text Bug Listing
| Summary: | [proposal] locationtech.technology.geowave | ||
|---|---|---|---|
| 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: | chris, cydnie.smith, derek.toolan, krum.tsvetkov, Paul.White, rfecher, sharon.corbett, thea.aldrich, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://www.locationtech.org/proposals/geowave | ||
| Whiteboard: | |||
| Bug Depends on: | 461535, 461537 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Stephanie, let's assume that the trademark process will conclude successfully and start the project creation process right away. Please schedule a creation review to conclude on April 19. I've scheduled the creation review to conclude on April 19/2017. 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 on 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 I declare this 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). Immediately following the provisioning process, your next step will be 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. In anticipation of this step, you may consider ensuring that your code has the required copyright headers and namespace (if applicable). If you have any questions, please send a message to emo@eclipse.org and we will provide assistance. Please encourage all project committers to join the incubation mailing list [3]. 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. An overview of the complete project creation process is in the Project Handbook [4]. [1] https://www.eclipse.org/projects/handbook/#paperwork [2] https://www.eclipse.org/projects/handbook/#ip-initial-contribution [3] https://dev.eclipse.org/mailman/listinfo/incubation [4] https://www.eclipse.org/projects/handbook/#starting 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[0]. This work can begin as soon as you have check in permission from EMO legal.
Issue Tracker:
https://bugs.locationtech.org/bugs/describecomponents.cgi?product=geowave
Mailing list: https://dev.locationtech.org/mailman/listinfo/geowave-dev
Downloads: http://download.locationtech.org/geowave
Archives: http://archive.locationtech.org/geowave
Builds: You can upload releases to ~committer_id/downloads/geowave via SFTP or SCP (to dev.locationtech.org) or from a CI instance at Locationtech.org
Older builds should be moved to the archives area when they are no longer required.
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 “checkin” and/or “full approval” you are now ready to check the initial project code contribution into your project’s repository.
[0] https://wiki.eclipse.org/GitHub
[1] https://www.eclipse.org/projects/handbook/#ip-initial-contribution
-M.
We just received initial checkin approval within this CQ: https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13537 I understand I still need to work with webmaster to perform the initial contribution on github. Thanks! Additionally, I have other questions but would rather take care of initial checkin first and foremost. My questions are related to what other LocationTech infrastructure it makes sense to start transitioning to and leveraging. Examples are: a) there's a reference to LocationTech CI (we currently run our own Jenkins CI as well as leverage Travis CI heavily, but would be interested in understanding more about LocationTech offerings). b) publishing maven artifacts to Nexus c) access to SCP/SFTP for downloads/archives (In reply to Rich Fecher from comment #5) > We just received initial checkin approval within this CQ: > https://dev.eclipse.org/ipzilla/show_bug.cgi?id=13537 > > I understand I still need to work with webmaster to perform the initial > contribution on github. Thanks! We can get this kicked-off so. The process involves Webmaster being assigned Collaborator w/ admin access to the repo we are transferring from [1]. This should allow Webmaster access to the 'Transfer Ownership' option accessible via the 'Settings' tab. The Webmaster username is 'eclipsewebmaster'. Note: from what I understand of Private GitHub repos, this option may not be available. If that is the case, choose the "Transfer ownership" option instead, which is available under Settings > Options. Choose eclipsewebmaster as the "New owner’s GitHub username or organization name". Once we have that, we can proceed to transfer the repo to this location [2]. [1] https://github.com/ngageoint/geowave [2] https://github.com/locationtech/geowave I can't add you as a contributor to ngageoint and therefore can't assign you as a collaborator on the team. However, I do think I can transfer ownership (at least the option is available to me, seems like I have the appropriate permissions). I'll initiate that tomorrow morning and as I understand it you have one day to accept before it expires. Thanks! (In reply to Rich Fecher from comment #7) > I can't add you as a contributor to ngageoint and therefore can't assign you > as a collaborator on the team. However, I do think I can transfer ownership > (at least the option is available to me, seems like I have the appropriate > permissions). I'll initiate that tomorrow morning and as I understand it > you have one day to accept before it expires. Thanks! Sounds good, we can get started on this tomorrow morning so. Tried to execute it this morning and I got an error message from GitHub: "You can only transfer a repository from an organization to yourself at this time" I'm a little tempted to try to transfer to my personal account and then from there to eclipsewebmaster but I *really* don't want to screw anything up (and somehow I'm expecting a different error and don't have high hopes of this being a workaround). I'm an admin for both the project and the ngageoint group, but there are still things I can't do because I am not the owner. For example I can't add members to ngageoint, I can only add existing ngageoint members to geowave. I looked a little here: https://help.github.com/articles/transferring-a-repository-owned-by-your-organization/ "If Allow members to delete or transfer repositories for this organization has been disabled in the organization, only organization owners can transfer organization repositories." Its possible I can't do this, I'm going to ping more people on our end, but also let me know if you have ideas. Thank you - we got the invite to the repo this morning, and I have completed the transfer [1]. The webhook, which will pull in all project committers for GeoWave, will kick-in within the next hour or so. This will alert project committers to subscribe to the newly created GeoWave GitHub team. This is based on the assumption that a GeoWave committer has added his or her GitHub username to his or her respective Eclipse profile [2] (NOTE: there is a field to do this under the 'Edit Profile' tab). [1] https://github.com/locationtech/geowave [2] https://accounts.eclipse.org we hadn't had our github user IDs in our profiles so we do not yet have write access to it. I added mine a few hours ago to my profile but still no luck. the issue is the io pages with all our documentation is now broken links (). I've gotten a couple emails about it being down. I went through and fixed all the links in a PR but can't get it merged until we get write access (or someone else merges it). Let me know if there's anymore I can do, or how best to ensure we can get access. Thanks for helping out! We appreciate it. (In reply to Rich Fecher from comment #11) > we hadn't had our github user IDs in our profiles so we do not yet have > write access to it. I added mine a few hours ago to my profile but still no > luck. > > the issue is the io pages with all our documentation is now broken links (). > I've gotten a couple emails about it being down. I went through and fixed > all the links in a PR but can't get it merged until we get write access (or > someone else merges it). Let me know if there's anymore I can do, or how > best to ensure we can get access. > > Thanks for helping out! We appreciate it. It looks like there may have been an issue with Webhook (which we are currently looking into). In the meantime, I have manaully added you to the repo, which should send out the notification. Let me know if this does not occur. It looks like gitter doesn't automatically move the room (from https://gitter.im/ngageoint/geowave to https://gitter.im/locationtech/geowave) and I *think* we need to create a new room. I tried to here: https://gitter.im/locationtech/home#createroom but it looks like I probably don't have the correct permissions within https://gitter.im/locationtech (ie. the locationtech gitter "community"). Can webmaster look into this for us? Thanks. (In reply to Rich Fecher from comment #13) > It looks like gitter doesn't automatically move the room (from > https://gitter.im/ngageoint/geowave to > https://gitter.im/locationtech/geowave) and I *think* we need to create a > new room. > Can webmaster look into this for us? Thanks. As far as I know, Webmaster does not administer Gitter (it's the first request I have received). You should have received a notification to join the GitHub repo once again - this is the result of the automated webhook that assigns all project committers to the locationtech-geowave team. For the moment this looks to be only you. However, as other committers (assuming there will be others) complete their CLA process, they too will get automatically added (bearing in mind my previous comment about adding GitHub Usernames to the associated Eclipse account). I needed to me a member of github/locationtech group before it would let me create the geowave gitter room. It is now resolved, I did just get an automated email to join the locationtech group which must have been a result of the webhook. Thanks! Greetings project team, It appears your initial contribution was approved (2017-11-15) and there are no open CQs; however, AFAICT, there have been no releases planned. What are your plans for your first release? For more information on releases, please check out our handbook [1]. [1] https://www.eclipse.org/projects/handbook/#release Greetings, Congratulations on your first release! As you have engaged in the release process, I declare this bug fully operational! This bug is now closed. |