Bugzilla – Full Text Bug Listing
| Summary: | [proposal] technology.apogy | ||||||
|---|---|---|---|---|---|---|---|
| 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: | andrea.ross, cydnie.smith, gael.blondelle, jayjaybillings, kasandra.darwin, mariateresa.delgado, mike.milinkovich, pascal, pierre.allard, regent.larcheveque, sharon.corbett, webmaster | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Linux | ||||||
| URL: | https://projects.eclipse.org/proposals/apogy | ||||||
| Whiteboard: | stalebug | ||||||
| Bug Depends on: | 488610 | ||||||
| Bug Blocks: | |||||||
| Attachments: |
|
||||||
|
Description
Wayne Beaton
I've scheduled the creation review to conclude on April 6/2016. 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 [2] https://dev.eclipse.org/mailman/listinfo/incubation The Eclipse Foundation Contributor’s License Agreement has not been signed and agreed to yet by the CSA committers as the implication of the License are being reviewed by our Legal Department. This should happen next week. (In reply to Pierre Allard from comment #2) > The Eclipse Foundation Contributor’s License Agreement has not been signed > and agreed to yet by the CSA committers as the implication of the License > are being reviewed by our Legal Department. This should happen next week. This could just be a minor terminology problem, but I believe that the agreements that CSA should be reviewing for Apogy's committers is the Eclipse Individual Committer Agreement[1] and Employer Consent Form[2]. An alternate would be the Eclipse Member Committer Agreement[3], but I don't think that the CSA is actually a Member of the Eclipse Foundation. The Eclipse Contributor License Agreement[4] is for contributors to Eclipse projects, not Committers. Hope that helps! [1] http://www.eclipse.org/legal/committer_process/EclipseIndividualCommitterAgreementFinal.pdf [2] http://www.eclipse.org/legal/committer_process/employer_consent.pdf [3] http://www.eclipse.org/legal/committer_process/EclipseMemberCommitterAgreementFinal.pdf [4] http://www.eclipse.org/legal/CLA.php 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 Wayne, That a good news. We work on the paperwork here. Meanwhile, just a little question. We would like to add some people in the interested parties section. It seems we lost edit privileges and cannot modify the proposal anymore. Is that normal? (In reply to Regent LArcheveque from comment #5) > It seems we lost edit privileges and cannot modify the proposal > anymore. Is that normal? That's normal. We lock down proposals after we've created the project. I can, however, update the interested parties section for you. You can either give me a list here, or send it via private email. Ok. Here's the list 1. Charles Rivest, Zeligsoft (Papyrus for Real Time (Papyrus-RT) Commiter) 2. Steeve Monier (steve.monnier@obeo.fr), OBEO, (I believe he is Sirius Commiter) 3. Jerome Oufella (jerome.oufella@savoirfairelinux.com), Savoir-faire Linux 4. Mathieu Larose (mathieu.larose@savoirfairelinux.com), Savoir-faire Linux 5. William Bourque (wfb@xiphos.com), Xiphos Technologies Thanks ;-) (In reply to Regent LArcheveque from comment #7) > Ok. Here's the list Done Could you add Pascal Rapicault in the committers list please? (In reply to Regent LArcheveque from comment #9) > Could you add Pascal Rapicault in the committers list please? I can't. The project has already been created which means that we need to do a committer election for Pascal. As a mentor, Pascal can help you through this process. I noticed that I made a typo with one interested party. Could you fix it please? Change the following line: Steeve Monier (steve.monnier@obeo.fr), OBEO, (I believe he is Sirius Commiter) By: Steve Monnier (steve.monnier@obeo.fr), OBEO Thanks ;-) (In reply to Regent LArcheveque from comment #11) > I noticed that I made a typo with one interested party. Could you fix it > please? Fixed Thanks Wayne. Is it normal the change is not yet reflected on the Apogy proposal site (https://projects.eclipse.org/proposals/apogy)? (In reply to Regent LArcheveque from comment #13) > Thanks Wayne. Is it normal the change is not yet reflected on the Apogy > proposal site (https://projects.eclipse.org/proposals/apogy)? It's there. Maybe you need to refresh your browser? (In reply to Wayne Beaton from comment #14) > (In reply to Regent LArcheveque from comment #13) > > Thanks Wayne. Is it normal the change is not yet reflected on the Apogy > > proposal site (https://projects.eclipse.org/proposals/apogy)? > > It's there. Maybe you need to refresh your browser? Funny. I restarted and used different browsers and used a different network (LTE) and I do not see the changes? (In reply to Regent LArcheveque from comment #15) > Funny. I restarted and used different browsers and used a different network > (LTE) and I do not see the changes? It is at this point that I must sheepishly admit that I only actually fixed the last name the first time around. I've fixed it all now. (In reply to Wayne Beaton from comment #16) > (In reply to Regent LArcheveque from comment #15) > > Funny. I restarted and used different browsers and used a different network > > (LTE) and I do not see the changes? > > It is at this point that I must sheepishly admit that I only actually fixed > the last name the first time around. I've fixed it all now. Thanks Wayne. I really appreciate your support. The project provisioning process is complete! Here you will find all of the information regarding resources allocated to your project: Source Code Management:(At Eclipse) ssh://committer_id@git.eclipse.org:29418/apogy/apogy.git Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=apogy Outbound Communication: Mailing list: https://dev.eclipse.org/mailman/listinfo/apogy-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/apogy.git Commits will be published to www.eclipse.org/apogy within 5 minutes Downloads: http://download.eclipse.org/apogy Archives: http://archive.eclipse.org/apogy Builds: You can upload releases to ~committer_id/downloads/apogy 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. 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 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? The project is really active. We are planning the first drop before the end of August. (In reply to Regent LArcheveque from comment #21) > The project is really active. We are planning the first drop before the end > of August. AFAICT, there hasn't been any commits against the public repository [1] since March. Where is the active development taking place? There is information in the handbook regarding what needs to happen to prepare for the first official release [2]. [1] https://git.eclipse.org/r/apogy/apogy [2] https://eclipse.org/projects/handbook/#release You are right Wayne. Nothing has been committed since March. I just came back progressively to work last June and I got my committer accesses two weeks ago (I omitted to fill a form). Now everything is set. Meanwhile I have continued to refactor the code in our original BitBucket repository https://bitbucket.org/apogy/ca.gc.asc_csa.apogy/ (branch eclipse). We have not touched any Third Party bundles. Just our contributions. Basically, I have renamed the bundles to org.eclipse.apogy and reorganise and separate the generated and custom code inside the bundles to facilitate maintenance. Few bug fixes but no new functionalities. I know you analysed the code and I presume you need to re-analyze this new drop. I am sorry for this inconvenience. I can make a drop early next week. Also I need to revisit the handbook to refresh my memory. Regent ;-) (In reply to Regent LArcheveque from comment #23) > You are right Wayne. Nothing has been committed since March. I just came > Meanwhile I have continued to refactor the code in our original BitBucket > repository https://bitbucket.org/apogy/ca.gc.asc_csa.apogy/ (branch > eclipse). We have not touched any Third Party bundles. Just our > contributions. Basically, I have renamed the bundles to org.eclipse.apogy > and reorganise and separate the generated and custom code inside the bundles > to facilitate maintenance. Few bug fixes but no new functionalities. I > know you analysed the code and I presume you need to re-analyze this new > drop. I am sorry for this inconvenience. Please do update the existing CQ with the new code drop and explain what's changed to the IP Team. Sure I'll do it. We are in the process of renaming the plug-ins to use the org.eclipse.apogy prefix. Do we need to submit these updates as a stand alone file stripped of all git history, or can we create a new branch on the Apogy git repository and include a reference to it in the CQ with a description of the changes ? Once rename is complete, you will need to attach an archive of all the files (without history). This set of files will be the starting point of your new git repo at eclipse. Created attachment 275955 [details]
Update to initial contribution
This is an update to the initial contribution for Apogy. It includes the following changes compared to the last version of the initial contribution:
1) The plugins + packages has been renamed to use the org.eclipse prefix;
2) The legals files (LICENSE.md, NOTICE.md and CONTRIBUTING.txt) have been added to all plugins;
3) Bug fixes have been included.
4) A few plugins have been created and added.
(In reply to Pierre Allard from comment #28) > This is an update to the initial contribution for Apogy. It includes the > following changes compared to the last version of the initial contribution: AFAICT the IP Team has granted "checkin" and project code has been added to the Git repository [1]. Do the changes that you've uploaded here represent an significantly changed code base, or can we reasonably argue that they changes are ongoing "normal development" sorts of work done by committers. Unless there are circumstances that demand otherwise, you and the project team can just push updates into the project repository. [1] http://git.eclipse.org/c/apogy/apogy.git Most of the work has been in the plugin renaming. We can say that this drop is "normal development" to get our code to be Eclipse compliant. (In reply to Pierre Allard from comment #30) > Most of the work has been in the plugin renaming. > > We can say that this drop is "normal development" to get our code to be > Eclipse compliant. Great. In that case, I think that you should just be pushing these changes into the project repository. You don't need to attach them here. As long as you're following the IP Due Diligence process (the short version is that project committers can just push the work that they do directly to the repository), your committers can just push to the repository. 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. Hi Pierre, we've noticed that despite the fact that this bug hasn't had any activity in a while, the Eclipse Apogy project is still active. Is the project ready to engage in a release review? Information on how to do this is available on the Eclipse Handbook, and can be found here: https://www.eclipse.org/projects/handbook/#release https://www.eclipse.org/projects/handbook/#release-review Let us know if you have any questions. (In reply to Maria Teresa Delgado from comment #33) > Hi Pierre, > we've noticed that despite the fact that this bug hasn't had any activity in > a while, the Eclipse Apogy project is still active. > Is the project ready to engage in a release review? > Information on how to do this is available on the Eclipse Handbook, and can > be found here: > https://www.eclipse.org/projects/handbook/#release > https://www.eclipse.org/projects/handbook/#release-review > Let us know if you have any questions. Hi Maria, The project is still active, I am working on a regular basis on fixes and improvements. I have looked at the information on the release process (thanks for the links). Looking at what is required, I found I am not ready to go through a release review at this time, but I am planning to do so. Thanks, Pierre Housekeeping. The project is fully active. |