Bugzilla – Full Text Bug Listing
| Summary: | [proposal] iot.hip | ||
|---|---|---|---|
| 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: | contact, cydnie.smith, healy.mark.a, jreimann, sharon.corbett, webmaster |
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| URL: | https://projects.eclipse.org/proposals/eclipse-hip | ||
| Whiteboard: | |||
| Bug Depends on: | 532910, 532911 | ||
| Bug Blocks: | |||
|
Description
Wayne Beaton
Hi Wayne, In relation to the "non standard licensing" - I'm flexible on the licensing used, so if it's easier to change the licensing model, we can do this instead? Mark It looks like the project proposal already indicates EPL 2.0? But I guess you are referring to the code on Github being ASLv2? You being the sole copyright holder (I think?) it would certainly make things simpler for you to just relicense the existing codebase under EPL, otherwise we will need to get approval from the Eclipse Foundation's Board of Directors as Wayne mentioned. (In reply to Mark Healy from comment #1) > In relation to the "non standard licensing" - I'm flexible on the licensing > used, so if it's easier to change the licensing model, we can do this > instead? Sorry, this is boilerplate text that I forget to tune. I should have removed that line. Please ignore. No problem Wayne, although Benjamin raises a good point on the GitHub repos - I'm happy to use EPL for these also. Let me know if you want me to update these now, or if it can wait until later in the process Jens has volunteered to mentor. I'll update the proposal. We’ve received all of the project requirements and have scheduled the creation review to conclude on April 18/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 Congratulations! Your project review is 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 The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management:(Existing at Github) 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. This work can begin as soon as you have check in permission from EMO legal. Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=hip Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/hip-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/hip.git Commits will be published to www.eclipse.org/hip within 5 minutes Downloads: http://download.eclipse.org/hip Archives: http://archive.eclipse.org/hip Builds: You can upload releases to ~committer_id/downloads/hip 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. Thanks Matt. Mark, 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 & Matt, That's great, thanks for all your help. I'll start working on the CQ Have a great weekend Mark @mark: Let me know when you have any questions about CQs, the Eclipse IP process or anything else. You can contact me directly via e-mail if you like. It appears that the initial contribution has been checked in, but there have been no contributions to the repository since then. What is the status of this project? What are your plans regarding your first release? I'm finalising a couple of things at the moment: - A final CQ for the project dependencies - expect to have this complete later this week - A first draft of the HIP specifications - to be completed over the next 2 weeks Once these are in place, I will be amending the initial contribution to reflect the updated specification and would expect to have an initial release by the end of Q3 My original roadmap had the specifications scheduled for release by end of Q2, so I'm about 5-6 weeks behind schedule Greetings, It looks like your initial contribution received final approval on 2018-10-03; but AFAICT there hasn't been much activity since 2018-05-09. What is the status of this project? Is there anything we can do to help? Now that your initial has been approved, your next step is to start planning your first release. For more information about the release process, check out our handbook [1]. [1] https://www.eclipse.org/projects/handbook/#release Hi Cydnie, Just a quick update. The original submission was written in JS - and has been a complete nightmare to maintain in terms of dependencies. Approx 6 weeks ago, I refactored about 60% of the code to Java, leveraging Vertx, in order to reduce dependencies from several hundred to a small handful. I expect to submit the refactored code in the next 2 weeks. In terms of what I need from you guys- for now, just patience :) Once I've submitted the new codebase, I'd like to discuss adding additional git repos and, if possible, a maven repo for modules (Vertx Verticles) - but I'll prioritize getting the updated code submitted and an initial release first. Thanks Mark Hi, I've submitted a CQ [1] for the refactored code Thanks Mark [1]https://dev.eclipse.org/ipzilla/show_bug.cgi?id=19699 This project was terminated. See bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=549683 I declare this bug closed. |