Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-21 Thread Mark Struberg
Oh just seen Betrand was faster than I. So all done already. LieGrue, strub > Am 21.10.2016 um 16:24 schrieb Mark Struberg : > > GIT repos can be requested by ASF members via https://reporeq.apache.org/ > > You can also create an INFRA ticket with the according coordinates. > > Or you simply t

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-21 Thread Mark Struberg
GIT repos can be requested by ASF members via https://reporeq.apache.org/ You can also create an INFRA ticket with the according coordinates. Or you simply tell me the following data and I’ll request it. * Repository name: incubator-netbeans.git ? * commit notifications sent to: comm...@netbeans

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-21 Thread Geertjan Wielenga
OK, sorry to ask again, where are the instructions needed for requesting or setting up a Git repo? (And then we'll link those instructions here https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Transition so we won't need to ask again. :-) ) Gj On Fri, Oct 21, 2016 at 9:36 AM, Geertjan

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-21 Thread Geertjan Wielenga
Ah, OK. Great. So, let's set up a repo called 'temp' and put in there a new NetBeans Platform project, i.e., a few modules and some kind of structure that resembles hg.netbeans.org/releases. Once we have done that, how do we hook that into Jenkins and the release process in general? Gj On Fri, O

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-20 Thread Bertrand Delacretaz
On Fri, Oct 21, 2016 at 8:04 AM, Geertjan Wielenga wrote: > ...But that bit of similar code in order to test the infrastructure would also > need a software grant to be able to import it into an Apache repository?.. No, if you write original code you just commit it yourself covered by your iCLA.

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-20 Thread Geertjan Wielenga
But that bit of similar code in order to test the infrastructure would also need a software grant to be able to import it into an Apache repository? Gj On Thu, Oct 20, 2016 at 11:27 AM, Bertrand Delacretaz < bdelacre...@apache.org> wrote: > Hi, > > On Thu, Oct 20, 2016 at 11:11 AM, Geertjan Wiel

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-20 Thread Bertrand Delacretaz
Hi, On Thu, Oct 20, 2016 at 11:11 AM, Geertjan Wielenga wrote: > ...Is there really > no way we can do that without the software grant? I.e., set up some kind of > test repo or temp repo so we can work through a process as he describes,.. That''s possible of course. > ...push there http://hg.ne

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-20 Thread Geertjan Wielenga
The problem that we're facing is that we'd like to experiment and see whether we can set up our code base and work through a process, e.g., exactly as Jaroslav describes at the start of this thread. Is there really no way we can do that without the software grant? I.e., set up some kind of test rep

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-20 Thread Bertrand Delacretaz
Hi, On Thu, Oct 20, 2016 at 8:26 AM, Geertjan Wielenga wrote: > ...if you have your own personal code that is not licensed under > Oracle, e.g., some plugin code for example that you have made yourself and > is in your own personal repo, then that could be moved to Apache Git, > though even then

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-20 Thread Bertrand Delacretaz
On Thu, Oct 20, 2016 at 10:35 AM, Wade Chandler wrote: > On Oct 20, 2016 3:16 AM, "Bertrand Delacretaz" > wrote: >> ...I think it's quite easy now via https://reporeq.apache.org/ but as I >> said I haven't used that myself so far. >> > So, to double check, on GitHub auto mirroring, is that then a

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-20 Thread Wade Chandler
On Oct 20, 2016 3:16 AM, "Bertrand Delacretaz" wrote: > > On Wed, Oct 19, 2016 at 12:24 PM, Wade Chandler > wrote: > > ...how difficult is it to setup many small repos for a project through the Apache processes?... > > I think it's quite easy now via https://reporeq.apache.org/ but as I > said I

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-20 Thread Bertrand Delacretaz
On Wed, Oct 19, 2016 at 12:24 PM, Wade Chandler wrote: > ...how difficult is it to setup many small repos for a project through the > Apache processes?... I think it's quite easy now via https://reporeq.apache.org/ but as I said I haven't used that myself so far. -Bertrand

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Geertjan Wielenga
Only once we have the software grant can we migrate anything from hg.netbeans.org. However, if you have your own personal code that is not licensed under Oracle, e.g., some plugin code for example that you have made yourself and is in your own personal repo, then that could be moved to Apache Git,

Re: Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Geertjan Wielenga
On Thu, Oct 20, 2016 at 7:51 AM, Jaroslav Tulach wrote: > The code in the repo would remain under the current NetBeans license, but > I don't think it matters, we are incubating - the goal is to test the > infrastructure and re-licensing can wait. Exactly, I had assumed the above was true, but i

Jenkins & Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Jaroslav Tulach
19. 10. 2016 v 11:00, Bertrand Delacretaz : > On Wed, Oct 19, 2016 at 10:50 AM, Geertjan Wielenga > wrote: >> ...there's nothing stopping us right now from setting up our Git >> repo and having it mirrored on GitHub... > > Definitely - just choose a repository name that you won't need to > overw

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Wade Chandler
I suggest we don’t bundle such things into a single repo from the start. Maybe the historic contrib, for a start, and even that broken apart later, but IMO, each plugin or set of them (in some cases) should have its/their own repo; make things specific. Too, we should discuss what contrib means

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Bertrand Delacretaz
On Wed, Oct 19, 2016 at 11:32 AM, Geertjan Wielenga wrote: > ...Though I guess every Apache project using Git has one single Apache Git > repo, with substructures below that, and not multiple Apache Git repos?... As Daniel says it's not like that, see https://git-wip-us.apache.org/repos/asf Slin

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Daniel Gruno
On 10/19/2016 11:32 AM, Geertjan Wielenga wrote: > Great though I think we need to plan/design our repo structure first. > Though I guess every Apache project using Git has one single Apache Git > repo, with substructures below that, and not multiple Apache Git repos? If > so, we could already requ

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Geertjan Wielenga
Great though I think we need to plan/design our repo structure first. Though I guess every Apache project using Git has one single Apache Git repo, with substructures below that, and not multiple Apache Git repos? If so, we could already request that repo? We should definitely look at other Apache

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Bertrand Delacretaz
On Wed, Oct 19, 2016 at 10:50 AM, Geertjan Wielenga wrote: > ...there's nothing stopping us right now from setting up our Git > repo and having it mirrored on GitHub... Definitely - just choose a repository name that you won't need to overwrite when migrating the NetBeans code later. -Bertrand

Re: Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Geertjan Wielenga
Even while we don't have the SGA yet (in process in Oracle at the moment), we could already set up our Git repo and somewhere I imagine we'll have a place where anyone can commit plugin code, i.e., a subfolder called 'contrib', where ultimately the NetBeans contrib repo will be migrated. Until that

Git @apache (was: [PROPOSAL] Split the main NetBeans repo)

2016-10-19 Thread Bertrand Delacretaz
Hi, On Wed, Oct 19, 2016 at 1:21 AM, Wade Chandler wrote: > ...Does the Apache git infra support pull requests?... I'll describe the current status, a more integrated experimental workflow is used by a few projects but AFAIK not ready for more widespread use right now. The general idea is that