Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mylyn-dev] Some Primary questions before beginning to contribute.

That is what we list on the contributor reference so it should work. But if you have any problems you may need to use the SSH URL instead.

Sam


--
Sam Davis
Software Engineer, Tasktop Dev
Committer, Eclipse Mylyn
http://tasktop.com


On Wed, Jul 30, 2014 at 6:50 AM, suryakanth.eclipsedev <suryakanth.eclipsedev@xxxxxxxxx> wrote:
Hi Sam,
        I can see 4 repositories:
ssh://seclipsedev@xxxxxxxxxxxxxxx:29418/mylyn/org.eclipse.mylyn.tasks

https://seclipsedev@xxxxxxxxxxxxxxx/r/p/mylyn/org.eclipse.mylyn.tasks

https://git.eclipse.org/r/p/mylyn/org.eclipse.mylyn.tasks

git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.tasks

Is there any problem if use the last repository for source code access instead of ssh one.


Thanks,
Surya.



On 7/29/2014 9:23 PM, Sam Davis wrote:
Hi Surya,

Thanks for your interest in contributing. The first thing to look at is the contributor reference. That will answer a lot of your questions.

The process for  becoming a committer is that you must first make substantial contributions to a project (e.g. many bug fixes or some major features). If your contributions are of a high enough quality, someone may nominate you for committer rights, and then there would be an election where other committers could vote +1 or -1. Note that the Mylyn project is broken into several sub-projects and there's a separate election for committer rights on each one, e.g. someone might be a committer on Mylyn Tasks but not Mylyn Context.

All contributions must go through Gerrit. Each contribution must get a +2 from a committer and and a +1 from Hudson (passing build) before it can be merged.

We have not decided on a date for the next release - it will happen when we have enough changes to make it worthwhile. There will be a release in September for Luna SR1 but it may only be a service release (see bug 439453).

As for where to contribute, any open bug that is assigned to mylyn-triaged@xxxxxxxxxxx would be very useful. Here's one you might find interesting:

218896: [patch][editor] display changes of old -> new values
https://bugs.eclipse.org/bugs/show_bug.cgi?id=218896

I already pushed a review to Gerrit but it needs more work and I won't have time to get back to it in the near future. Feel free to push a new review to Gerrit.

Cheers,
Sam


--
Sam Davis
Software Engineer, Tasktop Dev
Committer, Eclipse Mylyn
http://tasktop.com


On Tue, Jul 29, 2014 at 6:48 AM, suryakanth.eclipsedev <suryakanth.eclipsedev@xxxxxxxxx> wrote:
Hi,
     My Name is Surya. I would like to contribute to Mylin. Down to point, I have some questions.

1. I want to become a committer in the future. Can anybody help me with the process, steps and mentor me so that i will get necessary experience setup and mindset?
2. At what level I need Gerrit access. The question is whether every contribution should go through Gerrit or a simple Git commit record is sufficient for bug fixes.
3. What is the workflow for acceptance of a contribution?
4. When is the next release and how do I know what bugs/components are the places which I can contribute.


Thanks,
Surya.
_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-dev



_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-dev


_______________________________________________
mylyn-dev mailing list
mylyn-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mylyn-dev


Back to the top