[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [eclipse-scripting-dev] Setting up git support for contributing
- From: Christian Pontesegger <christian.pontesegger@xxxxxx>
- Date: Thu, 15 May 2014 16:57:30 +0200
- Delivered-to: email@example.com
- User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0
On 15.05.2014 16:16, Dinis Cruz wrote:
Ok, so from the https://wiki.eclipse.org/E4/Scripting/Contribute page
I see that the public git page is at
http://git.eclipse.org/c/e4/org.eclipse.e4.scripting.git/ with the
main repo at http://git.eclipse.org/c/e4/org.eclipse.e4.scripting.git/
page points to
https://projects.eclipse.org/projects/eclipse.e4/developer , is that
page still relevant? And if so, shouldn't /org.eclipse.e4.scripting.
You are right, so I just updated the CONTRIBUTING file.
Your best option to get the code is gerrit nowadays:
EASE is currently developed under the hood of the e4 incubator. As we
want to evolve and start working on releases we have to move out and
become a full eclipse project. We are currently in the preparation phase
for this step, so we have to move our code locations soon anyway.
I have to say that I have more experience in using GitHub than the
current Eclipse foundation set-up, so my current plan (unless you can
point me on a better direction) is to create a fork/clone of
http://git.eclipse.org/c/e4/org.eclipse.e4.scripting.git in GitHub and
use it as a base for my changes/patches/fixes/branches.
Eclipse Gerrit would be my preferred option, but if you fork on github
that will be fine anyway.
So far I am not familiar with the process of implementing changes you do
on github though. Would you provide patches for the eclipse repo then?
If you depend on external libraries like org.groovy you need to start
outside eclipse anyway. There I would opt to either fork from
EScriptMonkey on github or directly work on that project on github. If
you provide your github ID I could ask Arthur for the access rights