Bugzilla – Full Text Bug Listing
| Summary: | [proposal] modeling.hawk | ||
|---|---|---|---|
| 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: | agarcdomi, denis.roy, Ed.Merks, philippe.krief, sharon.corbett, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-hawk | ||
| Whiteboard: | stalebug | ||
| Bug Depends on: | 536188, 536189 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Dear Wayne, Sorry for the delay in responding this: I was away at a conference last week. Thank you for your help! I think we have two things done out of three: * We understand that the trademark search is now done and that we should use "Eclipse Hawk" everywhere once the project is created. * Dimitris Kolovos, Konstantinos Barmpis and myself all have Eclipse accounts as well. That leaves the mentor. Should we look for a mentor ourselves, or will you propose one? Kind regards, Antonio (In reply to Antonio Garcia-Dominguez from comment #1) > That leaves the mentor. Should we look for a mentor ourselves, or will you > propose one? I have a prospect. I'll keep you updated. Ed Merks has volunteered to mentor. 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 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/hawk/hawk Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=hawk Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/hawk-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/hawk.git Commits will be published to www.eclipse.org/[shortname] within 5 minutes Downloads: http://download.eclipse.org/hawk Archives: http://archive.eclipse.org/hawk Builds: You can upload releases to ~committer_id/downloads/hawk 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. Thank you for this! We will start migrating over from Github ASAP. I have tried to push our current codebase to https://git.eclipse.org/r/hawk/hawk/, and whether I use my Eclipse username (agarciad) or my Eclipse email (agarcdomi@gmail.com), I receive an Unauthorized error message. The repository does not mention a SSH URL to access our repository, either: https://git.eclipse.org/r/#/admin/projects/hawk/hawk Could we enable SSH-based push access to our repository? (In reply to Antonio Garcia-Dominguez from comment #8) > I have tried to push our current codebase to > https://git.eclipse.org/r/hawk/hawk/, and whether I use my Eclipse username > (agarciad) or my Eclipse email (agarcdomi@gmail.com), I receive an > Unauthorized error message. > > The repository does not mention a SSH URL to access our repository, either: > > https://git.eclipse.org/r/#/admin/projects/hawk/hawk > > Could we enable SSH-based push access to our repository? Webmaster, we could use your help here, please. (In reply to Antonio Garcia-Dominguez from comment #8) > Could we enable SSH-based push access to our repository? Our Gerrit instance provides both HTTPS and SSH URLs, but you need to use a custom password to access the HTTPS URLs(login to gerrit -> settings -> HTTP Password to see or set the current password) Here's the SSH URL for your repo: ssh://committer_id@git.eclipse.org:29418/hawk/hawk I'd recommend adding your public key (settings -> public keys) just to make it easier. -M. While going through the initial CQ, we realized the project had been created with only EPL 2.0, while we wanted to have EPL 2.0 + GPL 3.0 as secondary license. The secondary license is required for our Neo4j backend, since Neo4j is GPL 3.0 licensed. We would like to have the source code for it hosted in Eclipse. The Eclipse-hosted binary distributions would have only EPL 2.0-compatible artifacts, and the GPL 3.0 licensed bits would be distributed from outside Eclipse. Would it be possible to correct this? (In reply to Antonio Garcia-Dominguez from comment #11) > Would it be possible to correct this? Done. 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 up and running. I'm marking this as fixed. |