Community
Participate
Working Groups
We’ll use this Bugzilla record to track the onboarding process for the project. This channel will be the primary means of communication for the project team, your mentors, and the Eclipse Foundation during this process. To get started on your new project, we need to do the following: -Ensure that all of the committers listed on the proposal have Eclipse Foundation Accounts [1] -Identify a mentor for the project -Transfer ownership of the project name trademark to the Eclipse Foundation We will open separate Bugzilla records to track this. Once we have all of the requirements above and the proposal has been open for community review for a minimum of two weeks, we will schedule the project for creation. If you have any questions for us, please feel free to reach out anytime! As well, if you’d like an overview of the project creation process, check out our Project Handbook [2]. We look forward to working with you and your team to make this project a success! [1] https://accounts.eclipse.org/user/register [2] https://www.eclipse.org/projects/handbook/#starting
We’ve received all of the project requirements and have scheduled the creation review to conclude on April 15th 2020. 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 have one question/remark. The proposal suggest to have Jifa as a subproject of Memory Analyzer (at least this is my understanding of the meaning of "parent project: Memory Analyzer"). I wonder if this is appropriate. My understanding is that the Jifa would be more a kind of a consumer for MAT (i.e. MAT would be a dependency for Jifa), rather than a subproject. Also I do not expect that both projects would co-ordinate releases. What was the reason for putting Memory Analyzer as a parent project?
> I have one question/remark. I've added the "needinfo" tag to indicate that we need a response to this question. Note that as the project lead for Technology MAT, Krum would end up in the leadership chain for Eclipse Jifa if it is created as a subproject (so he gets a vote).
(In reply to Krum Tsvetkov from comment #2) > I have one question/remark. > The proposal suggest to have Jifa as a subproject of Memory Analyzer (at > least this is my understanding of the meaning of "parent project: Memory > Analyzer"). > I wonder if this is appropriate. > My understanding is that the Jifa would be more a kind of a consumer for MAT > (i.e. MAT would be a dependency for Jifa), rather than a subproject. > Also I do not expect that both projects would co-ordinate releases. > What was the reason for putting Memory Analyzer as a parent project? Hi, There is no special reason, mainly because a parent project must be specified in the proposal. And your understanding is right, The Jifa is a kind of consumer for MAT. Could you help us to specify a more suitable parent project? Thanks Denghui
Maria Teresa, let's just make this new project a direct subproject of the Eclipse Technology Top Level Project.
Hi all, I've modified the top level project for Jifa as requested, is now under Technology.
Hi Maria, According to the description(https://www.eclipse.org/projects/handbook/#paperwork), We don't need to do any paperwork if our company can provide MCCA. The current committers now are all from Alibaba, Alibaba has signed MCCA, but the effective date is May 1st. What should we do? Thanks, Denghui
Hi Denghui, in light of this new information, we'll need to postpone the project creation until the end of the month. The new date will be April 29th 2020. Please continue to monitor communication channels. regards, Maria Teresa
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: ssh://committer_id@git.eclipse.org:29418/jifa/jifa.git Issue Tracker: https://bugs.eclipse.org/bugs/describecomponents.cgi?product=jifa Outbound Communication: Mailing list: https://accounts.eclipse.org/mailing-list/jifa-dev Project Website repository: ssh://committer_id@git.eclipse.org:29418/www.eclipse.org/jifa.git Commits will be published to www.eclipse.org/jifa within 5 minutes Downloads: http://download.eclipse.org/jifa Archives: http://archive.eclipse.org/jifa Builds: You can upload releases to ~committer_id/downloads/jifa 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.
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. 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/#ip-initial-contribution
CQ 22264 for the initial contribution of Jifa
AFAICT the project submitted its initial contribution some time ago. Project team: do you have any release plans? it might be a good idea to schedule a progress review if you don't. Please let me know so I can start the process ASAP.
Hi Maria, We have two other features waiting for merging, and we plan to make a release after they are ready.
(In reply to Denghui Dong from comment #15) > Hi Maria, > > We have two other features waiting for merging, and we plan to make a > release after they are ready. Hi Denghui, that is great to hear. Please get in touch with the emo@eclipse.org directly when you're ready to go through the release. In the mean time I think we can close this bug.
Hi Maria, I want to add some check rules to jifa github project[1], but I found that I have no permission. Could you help me with this? And I also filed an issue for this, but no response. [1] https://github.com/eclipse/jifa/settings Denghui
> And I also filed an issue for this, but no response. https://bugs.eclipse.org/bugs/show_bug.cgi?id=573907
According to document[1], I need the admin permissions I think. [1] https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/managing-a-branch-protection-rule
Please file a separate issue at https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues.
okay, thanks
Filed https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/issues/969
