Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

On 6 May 2018 at 09:01, Hervé BOUTEMY  wrote:
> uh, the move to trunk discarded the whole history before!
>
> That's not what I expected for a a svn2git mirror

Yes, I already noted that in the related issue:

https://issues.apache.org/jira/browse/INFRA-16355

> I'm not proficient enough in Git and svn2git, I hope infra can help, but it
> would be good if we could have the new trunk history appended after the whole
> pre-trunk history...

I think it's essential to preserve history.

It was preserved for the other repos.

> Regards,
>
> Hervé
>
> Le dimanche 29 avril 2018, 09:40:08 CEST sebb a écrit :
>> Top-posting
>>
>> I have moved SVN down a level to trunk/ and updated the workspace on
>> projects.a.o to use it.
>> Its pubsub seems to be working.
>>
>> The next set of cronjobs run from midnight to 4am (UTC) so we shall
>> see tomorrow if anything needs to be tweaked.
>>
>> S.
>>
>> On 29 April 2018 at 07:04, sebb  wrote:
>> > On 26 April 2018 at 01:02, sebb  wrote:
>> >> Looks like there is a bit more to it.
>> >>
>> >> asf-auth template needs to be updated to give projects_role access to
>> >> the new directory.
>> >> This can be done by adding the new directory name and later dropping
>> >> the old one.
>> >
>> > The asf-auth update has been applied, so the code will be able to
>> > update SVN in the new location.
>> >
>> >> I don't yet know how to update projects-vm safely.
>> >>
>> >> On 25 April 2018 at 12:43, Hervé BOUTEMY  wrote:
>> >>> no objection for me: what is important is to keep the machine running
>> >>> the web server synchronized with the change
>> >>>
>> >>> Regards,
>> >>>
>> >>> Hervé
>> >>>
>> >>> Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
>>  It looks like we need to move the contents of
>> 
>>  https://svn.apache.org/repos/asf/comdev/projects.apache.org
>> 
>>  to
>> 
>>  https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
>> 
>>  [No need to do the same for reporter, as it already uses a trunk
>>  directory]
>> 
>>  AFAICT this should not affect the projects.a.o site.
>>  The pubsub script that pulls in updates only looks for the
>>  comdev/projects.apache.org prefix.
>>  (As it does for reporter)
>> 
>>  Moving projects to the trunk directory would give it the same layout
>>  as reporter.
>>  It would also allow the use of tags/ and branches/ sibling directories.
>> 
>>  Are there objections to moving projects.a.o down a level?
>> 
>>  On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
>>  > Jira issue created:
>>  > https://issues.apache.org/jira/browse/INFRA-16355
>>  >
>>  > Regards,
>>  >
>>  > Hervé
>>  >
>>  > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
>>  >> ok, I don't see any remaining objection
>>  >>
>>  >> I'll ask for svn2git read-only Git+GitHub mirrors.
>>  >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the
>>  >> git
>>  >> repo "comdev-community.apache.org" to match other
>>  >> "comdev-*.apache.org"
>>  >>
>>  >> This will ease people understanding that comdev's site is
>>  >> community.apache.org (and not comdev.apache.org...)
>>  >>
>>  >> Regards,
>>  >>
>>  >> Hervé
>>  >>
>>  >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
>>  >> > What about creating a Git/GitHub svn2git mirror for
>>  >> > projects.apache.org?
>>  >> > This would be our first Git repo for community/comdev: I don't
>>  >> > know
>>  >> > which
>>  >> > prefix we should use...
>>  >> >
>>  >> > Any objection?
>>  >> >
>>  >> > Perhaps we can do the same for the 3 other locations in svn
>>  >> > https://projects.apache.org/project.html?comdev-community_developm
>>  >> > ent
>>  >> >
>>  >> > Regards,
>>  >> >
>>  >> > Hervé
>>  >> >
>>  >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a
> écrit :
>>  >> > > Vincent Tuybens created COMDEV-288:
>>  >> > > --
>>  >> > >
>>  >> > >  Summary: Request "Projects Directory" migration to
>>  >> > >  GIT
>>  >> > >
>>  >> > >  Key: COMDEV-288
>>  >> > >  URL:
>>  >> > >  https://issues.apache.org/jira/browse/COMDEV-28
>>  >> > >  8
>>  >> > >
>>  >> > >  Project: Community Development
>>  >> > >
>>  >> > >   Issue Type: SVN->GIT Migration
>>  >> > >   Components: Projects Tool
>>  >> > >
>>  >> > > Reporter: Vincent Tuybens
>>  >> > >
>>  >> > > Dear all,
>>  >> > >
>>  >> > > is it possible for you to plan SVN to GIT migration for
>>  >> > > 

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

uh, the move to trunk discarded the whole history before!

That's not what I expected for a a svn2git mirror

I'm not proficient enough in Git and svn2git, I hope infra can help, but it 
would be good if we could have the new trunk history appended after the whole 
pre-trunk history...

Regards,

Hervé

Le dimanche 29 avril 2018, 09:40:08 CEST sebb a écrit :
> Top-posting
> 
> I have moved SVN down a level to trunk/ and updated the workspace on
> projects.a.o to use it.
> Its pubsub seems to be working.
> 
> The next set of cronjobs run from midnight to 4am (UTC) so we shall
> see tomorrow if anything needs to be tweaked.
> 
> S.
> 
> On 29 April 2018 at 07:04, sebb  wrote:
> > On 26 April 2018 at 01:02, sebb  wrote:
> >> Looks like there is a bit more to it.
> >> 
> >> asf-auth template needs to be updated to give projects_role access to
> >> the new directory.
> >> This can be done by adding the new directory name and later dropping
> >> the old one.
> > 
> > The asf-auth update has been applied, so the code will be able to
> > update SVN in the new location.
> > 
> >> I don't yet know how to update projects-vm safely.
> >> 
> >> On 25 April 2018 at 12:43, Hervé BOUTEMY  wrote:
> >>> no objection for me: what is important is to keep the machine running
> >>> the web server synchronized with the change
> >>> 
> >>> Regards,
> >>> 
> >>> Hervé
> >>> 
> >>> Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
>  It looks like we need to move the contents of
>  
>  https://svn.apache.org/repos/asf/comdev/projects.apache.org
>  
>  to
>  
>  https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
>  
>  [No need to do the same for reporter, as it already uses a trunk
>  directory]
>  
>  AFAICT this should not affect the projects.a.o site.
>  The pubsub script that pulls in updates only looks for the
>  comdev/projects.apache.org prefix.
>  (As it does for reporter)
>  
>  Moving projects to the trunk directory would give it the same layout
>  as reporter.
>  It would also allow the use of tags/ and branches/ sibling directories.
>  
>  Are there objections to moving projects.a.o down a level?
>  
>  On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
>  > Jira issue created:
>  > https://issues.apache.org/jira/browse/INFRA-16355
>  > 
>  > Regards,
>  > 
>  > Hervé
>  > 
>  > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
>  >> ok, I don't see any remaining objection
>  >> 
>  >> I'll ask for svn2git read-only Git+GitHub mirrors.
>  >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the
>  >> git
>  >> repo "comdev-community.apache.org" to match other
>  >> "comdev-*.apache.org"
>  >> 
>  >> This will ease people understanding that comdev's site is
>  >> community.apache.org (and not comdev.apache.org...)
>  >> 
>  >> Regards,
>  >> 
>  >> Hervé
>  >> 
>  >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
>  >> > What about creating a Git/GitHub svn2git mirror for
>  >> > projects.apache.org?
>  >> > This would be our first Git repo for community/comdev: I don't
>  >> > know
>  >> > which
>  >> > prefix we should use...
>  >> > 
>  >> > Any objection?
>  >> > 
>  >> > Perhaps we can do the same for the 3 other locations in svn
>  >> > https://projects.apache.org/project.html?comdev-community_developm
>  >> > ent
>  >> > 
>  >> > Regards,
>  >> > 
>  >> > Hervé
>  >> > 
>  >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a 
écrit :
>  >> > > Vincent Tuybens created COMDEV-288:
>  >> > > --
>  >> > > 
>  >> > >  Summary: Request "Projects Directory" migration to
>  >> > >  GIT
>  >> > >  
>  >> > >  Key: COMDEV-288
>  >> > >  URL:
>  >> > >  https://issues.apache.org/jira/browse/COMDEV-28
>  >> > >  8
>  >> > >  
>  >> > >  Project: Community Development
>  >> > >   
>  >> > >   Issue Type: SVN->GIT Migration
>  >> > >   Components: Projects Tool
>  >> > >   
>  >> > > Reporter: Vincent Tuybens
>  >> > > 
>  >> > > Dear all,
>  >> > > 
>  >> > > is it possible for you to plan SVN to GIT migration for
>  >> > > "Projects
>  >> > > Directory" project ?
>  >> > > 
>  >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects
>  >> > > .apac
>  >> > > he.
>  >> > > or
>  >> > > g/ {color}]
>  >> > > 
>  >> > > Thank you,
>  >> > > 
>  >> > > Regards.
>  >> > 

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

On 30 April 2018 at 13:41, sebb  wrote:
> On 29 April 2018 at 08:40, sebb  wrote:
>> Top-posting
>>
>> I have moved SVN down a level to trunk/ and updated the workspace on
>> projects.a.o to use it.
>> Its pubsub seems to be working.
>>
>> The next set of cronjobs run from midnight to 4am (UTC) so we shall
>> see tomorrow if anything needs to be tweaked.
>
> There were some references to the old SVN location in the source.
>
> I hope I have fixed them all.
>
> Also it turns out that one project (Brooklyn) was using the full URL
> to the PMC RDF file instead of the shorthand:
>
> 
>
> They have been asked to fix it.

This was done.

I have not noticed any other issues following the move.

>> S.
>> On 29 April 2018 at 07:04, sebb  wrote:
>>> On 26 April 2018 at 01:02, sebb  wrote:
 Looks like there is a bit more to it.

 asf-auth template needs to be updated to give projects_role access to
 the new directory.
 This can be done by adding the new directory name and later dropping
 the old one.
>>>
>>> The asf-auth update has been applied, so the code will be able to
>>> update SVN in the new location.
>>>
 I don't yet know how to update projects-vm safely.


 On 25 April 2018 at 12:43, Hervé BOUTEMY  wrote:
> no objection for me: what is important is to keep the machine running the 
> web
> server synchronized with the change
>
> Regards,
>
> Hervé
>
> Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
>> It looks like we need to move the contents of
>>
>> https://svn.apache.org/repos/asf/comdev/projects.apache.org
>>
>> to
>>
>> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
>>
>> [No need to do the same for reporter, as it already uses a trunk 
>> directory]
>>
>> AFAICT this should not affect the projects.a.o site.
>> The pubsub script that pulls in updates only looks for the
>> comdev/projects.apache.org prefix.
>> (As it does for reporter)
>>
>> Moving projects to the trunk directory would give it the same layout
>> as reporter.
>> It would also allow the use of tags/ and branches/ sibling directories.
>>
>> Are there objections to moving projects.a.o down a level?
>>
>> On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
>> > Jira issue created:
>> > https://issues.apache.org/jira/browse/INFRA-16355
>> >
>> > Regards,
>> >
>> > Hervé
>> >
>> > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
>> >> ok, I don't see any remaining objection
>> >>
>> >> I'll ask for svn2git read-only Git+GitHub mirrors.
>> >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the 
>> >> git
>> >> repo "comdev-community.apache.org" to match other 
>> >> "comdev-*.apache.org"
>> >>
>> >> This will ease people understanding that comdev's site is
>> >> community.apache.org (and not comdev.apache.org...)
>> >>
>> >> Regards,
>> >>
>> >> Hervé
>> >>
>> >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
>> >> > What about creating a Git/GitHub svn2git mirror for
>> >> > projects.apache.org?
>> >> > This would be our first Git repo for community/comdev: I don't know
>> >> > which
>> >> > prefix we should use...
>> >> >
>> >> > Any objection?
>> >> >
>> >> > Perhaps we can do the same for the 3 other locations in svn
>> >> > https://projects.apache.org/project.html?comdev-community_development
>> >> >
>> >> > Regards,
>> >> >
>> >> > Hervé
>> >> >
>> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit 
>> >> > :
>> >> > > Vincent Tuybens created COMDEV-288:
>> >> > > --
>> >> > >
>> >> > >  Summary: Request "Projects Directory" migration to 
>> >> > > GIT
>> >> > >
>> >> > >  Key: COMDEV-288
>> >> > >  URL:
>> >> > >  https://issues.apache.org/jira/browse/COMDEV-288
>> >> > >
>> >> > >  Project: Community Development
>> >> > >
>> >> > >   Issue Type: SVN->GIT Migration
>> >> > >   Components: Projects Tool
>> >> > >
>> >> > > Reporter: Vincent Tuybens
>> >> > >
>> >> > > Dear all,
>> >> > >
>> >> > > is it possible for you to plan SVN to GIT migration for "Projects
>> >> > > Directory" project ?
>> >> > >
>> >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apac
>> >> > > he.
>> >> > > or
>> >> > > g/ {color}]
>> >> > >
>> >> > > Thank you,
>> >> > >
>> >> > > Regards.
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> 

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

On 29 April 2018 at 08:40, sebb  wrote:
> Top-posting
>
> I have moved SVN down a level to trunk/ and updated the workspace on
> projects.a.o to use it.
> Its pubsub seems to be working.
>
> The next set of cronjobs run from midnight to 4am (UTC) so we shall
> see tomorrow if anything needs to be tweaked.

There were some references to the old SVN location in the source.

I hope I have fixed them all.

Also it turns out that one project (Brooklyn) was using the full URL
to the PMC RDF file instead of the shorthand:



They have been asked to fix it.

> S.
> On 29 April 2018 at 07:04, sebb  wrote:
>> On 26 April 2018 at 01:02, sebb  wrote:
>>> Looks like there is a bit more to it.
>>>
>>> asf-auth template needs to be updated to give projects_role access to
>>> the new directory.
>>> This can be done by adding the new directory name and later dropping
>>> the old one.
>>
>> The asf-auth update has been applied, so the code will be able to
>> update SVN in the new location.
>>
>>> I don't yet know how to update projects-vm safely.
>>>
>>>
>>> On 25 April 2018 at 12:43, Hervé BOUTEMY  wrote:
 no objection for me: what is important is to keep the machine running the 
 web
 server synchronized with the change

 Regards,

 Hervé

 Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
> It looks like we need to move the contents of
>
> https://svn.apache.org/repos/asf/comdev/projects.apache.org
>
> to
>
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
>
> [No need to do the same for reporter, as it already uses a trunk 
> directory]
>
> AFAICT this should not affect the projects.a.o site.
> The pubsub script that pulls in updates only looks for the
> comdev/projects.apache.org prefix.
> (As it does for reporter)
>
> Moving projects to the trunk directory would give it the same layout
> as reporter.
> It would also allow the use of tags/ and branches/ sibling directories.
>
> Are there objections to moving projects.a.o down a level?
>
> On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
> > Jira issue created:
> > https://issues.apache.org/jira/browse/INFRA-16355
> >
> > Regards,
> >
> > Hervé
> >
> > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
> >> ok, I don't see any remaining objection
> >>
> >> I'll ask for svn2git read-only Git+GitHub mirrors.
> >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the 
> >> git
> >> repo "comdev-community.apache.org" to match other "comdev-*.apache.org"
> >>
> >> This will ease people understanding that comdev's site is
> >> community.apache.org (and not comdev.apache.org...)
> >>
> >> Regards,
> >>
> >> Hervé
> >>
> >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
> >> > What about creating a Git/GitHub svn2git mirror for
> >> > projects.apache.org?
> >> > This would be our first Git repo for community/comdev: I don't know
> >> > which
> >> > prefix we should use...
> >> >
> >> > Any objection?
> >> >
> >> > Perhaps we can do the same for the 3 other locations in svn
> >> > https://projects.apache.org/project.html?comdev-community_development
> >> >
> >> > Regards,
> >> >
> >> > Hervé
> >> >
> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> > > Vincent Tuybens created COMDEV-288:
> >> > > --
> >> > >
> >> > >  Summary: Request "Projects Directory" migration to GIT
> >> > >
> >> > >  Key: COMDEV-288
> >> > >  URL:
> >> > >  https://issues.apache.org/jira/browse/COMDEV-288
> >> > >
> >> > >  Project: Community Development
> >> > >
> >> > >   Issue Type: SVN->GIT Migration
> >> > >   Components: Projects Tool
> >> > >
> >> > > Reporter: Vincent Tuybens
> >> > >
> >> > > Dear all,
> >> > >
> >> > > is it possible for you to plan SVN to GIT migration for "Projects
> >> > > Directory" project ?
> >> > >
> >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apac
> >> > > he.
> >> > > or
> >> > > g/ {color}]
> >> > >
> >> > > Thank you,
> >> > >
> >> > > Regards.
> >> > >
> >> > >
> >> > >
> >> > > --
> >> > > This message was sent by Atlassian JIRA
> >> > > (v7.6.3#76005)
> >> > >
> >> > > -
> >> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> > > For additional commands, e-mail: dev-h...@community.apache.org

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

Top-posting

I have moved SVN down a level to trunk/ and updated the workspace on
projects.a.o to use it.
Its pubsub seems to be working.

The next set of cronjobs run from midnight to 4am (UTC) so we shall
see tomorrow if anything needs to be tweaked.

S.
On 29 April 2018 at 07:04, sebb  wrote:
> On 26 April 2018 at 01:02, sebb  wrote:
>> Looks like there is a bit more to it.
>>
>> asf-auth template needs to be updated to give projects_role access to
>> the new directory.
>> This can be done by adding the new directory name and later dropping
>> the old one.
>
> The asf-auth update has been applied, so the code will be able to
> update SVN in the new location.
>
>> I don't yet know how to update projects-vm safely.
>>
>>
>> On 25 April 2018 at 12:43, Hervé BOUTEMY  wrote:
>>> no objection for me: what is important is to keep the machine running the 
>>> web
>>> server synchronized with the change
>>>
>>> Regards,
>>>
>>> Hervé
>>>
>>> Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
 It looks like we need to move the contents of

 https://svn.apache.org/repos/asf/comdev/projects.apache.org

 to

 https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk

 [No need to do the same for reporter, as it already uses a trunk directory]

 AFAICT this should not affect the projects.a.o site.
 The pubsub script that pulls in updates only looks for the
 comdev/projects.apache.org prefix.
 (As it does for reporter)

 Moving projects to the trunk directory would give it the same layout
 as reporter.
 It would also allow the use of tags/ and branches/ sibling directories.

 Are there objections to moving projects.a.o down a level?

 On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
 > Jira issue created:
 > https://issues.apache.org/jira/browse/INFRA-16355
 >
 > Regards,
 >
 > Hervé
 >
 > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
 >> ok, I don't see any remaining objection
 >>
 >> I'll ask for svn2git read-only Git+GitHub mirrors.
 >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git
 >> repo "comdev-community.apache.org" to match other "comdev-*.apache.org"
 >>
 >> This will ease people understanding that comdev's site is
 >> community.apache.org (and not comdev.apache.org...)
 >>
 >> Regards,
 >>
 >> Hervé
 >>
 >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
 >> > What about creating a Git/GitHub svn2git mirror for
 >> > projects.apache.org?
 >> > This would be our first Git repo for community/comdev: I don't know
 >> > which
 >> > prefix we should use...
 >> >
 >> > Any objection?
 >> >
 >> > Perhaps we can do the same for the 3 other locations in svn
 >> > https://projects.apache.org/project.html?comdev-community_development
 >> >
 >> > Regards,
 >> >
 >> > Hervé
 >> >
 >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
 >> > > Vincent Tuybens created COMDEV-288:
 >> > > --
 >> > >
 >> > >  Summary: Request "Projects Directory" migration to GIT
 >> > >
 >> > >  Key: COMDEV-288
 >> > >  URL:
 >> > >  https://issues.apache.org/jira/browse/COMDEV-288
 >> > >
 >> > >  Project: Community Development
 >> > >
 >> > >   Issue Type: SVN->GIT Migration
 >> > >   Components: Projects Tool
 >> > >
 >> > > Reporter: Vincent Tuybens
 >> > >
 >> > > Dear all,
 >> > >
 >> > > is it possible for you to plan SVN to GIT migration for "Projects
 >> > > Directory" project ?
 >> > >
 >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apac
 >> > > he.
 >> > > or
 >> > > g/ {color}]
 >> > >
 >> > > Thank you,
 >> > >
 >> > > Regards.
 >> > >
 >> > >
 >> > >
 >> > > --
 >> > > This message was sent by Atlassian JIRA
 >> > > (v7.6.3#76005)
 >> > >
 >> > > -
 >> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
 >> > > For additional commands, e-mail: dev-h...@community.apache.org
 >> >
 >> > -
 >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
 >> > For additional commands, e-mail: dev-h...@community.apache.org
 >>
 >> -
 >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
 >> For additional commands, e-mail: dev-h...@community.apache.org
 

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

On 26 April 2018 at 01:02, sebb  wrote:
> Looks like there is a bit more to it.
>
> asf-auth template needs to be updated to give projects_role access to
> the new directory.
> This can be done by adding the new directory name and later dropping
> the old one.

The asf-auth update has been applied, so the code will be able to
update SVN in the new location.

> I don't yet know how to update projects-vm safely.
>
>
> On 25 April 2018 at 12:43, Hervé BOUTEMY  wrote:
>> no objection for me: what is important is to keep the machine running the web
>> server synchronized with the change
>>
>> Regards,
>>
>> Hervé
>>
>> Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
>>> It looks like we need to move the contents of
>>>
>>> https://svn.apache.org/repos/asf/comdev/projects.apache.org
>>>
>>> to
>>>
>>> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
>>>
>>> [No need to do the same for reporter, as it already uses a trunk directory]
>>>
>>> AFAICT this should not affect the projects.a.o site.
>>> The pubsub script that pulls in updates only looks for the
>>> comdev/projects.apache.org prefix.
>>> (As it does for reporter)
>>>
>>> Moving projects to the trunk directory would give it the same layout
>>> as reporter.
>>> It would also allow the use of tags/ and branches/ sibling directories.
>>>
>>> Are there objections to moving projects.a.o down a level?
>>>
>>> On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
>>> > Jira issue created:
>>> > https://issues.apache.org/jira/browse/INFRA-16355
>>> >
>>> > Regards,
>>> >
>>> > Hervé
>>> >
>>> > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
>>> >> ok, I don't see any remaining objection
>>> >>
>>> >> I'll ask for svn2git read-only Git+GitHub mirrors.
>>> >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git
>>> >> repo "comdev-community.apache.org" to match other "comdev-*.apache.org"
>>> >>
>>> >> This will ease people understanding that comdev's site is
>>> >> community.apache.org (and not comdev.apache.org...)
>>> >>
>>> >> Regards,
>>> >>
>>> >> Hervé
>>> >>
>>> >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
>>> >> > What about creating a Git/GitHub svn2git mirror for
>>> >> > projects.apache.org?
>>> >> > This would be our first Git repo for community/comdev: I don't know
>>> >> > which
>>> >> > prefix we should use...
>>> >> >
>>> >> > Any objection?
>>> >> >
>>> >> > Perhaps we can do the same for the 3 other locations in svn
>>> >> > https://projects.apache.org/project.html?comdev-community_development
>>> >> >
>>> >> > Regards,
>>> >> >
>>> >> > Hervé
>>> >> >
>>> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
>>> >> > > Vincent Tuybens created COMDEV-288:
>>> >> > > --
>>> >> > >
>>> >> > >  Summary: Request "Projects Directory" migration to GIT
>>> >> > >
>>> >> > >  Key: COMDEV-288
>>> >> > >  URL:
>>> >> > >  https://issues.apache.org/jira/browse/COMDEV-288
>>> >> > >
>>> >> > >  Project: Community Development
>>> >> > >
>>> >> > >   Issue Type: SVN->GIT Migration
>>> >> > >   Components: Projects Tool
>>> >> > >
>>> >> > > Reporter: Vincent Tuybens
>>> >> > >
>>> >> > > Dear all,
>>> >> > >
>>> >> > > is it possible for you to plan SVN to GIT migration for "Projects
>>> >> > > Directory" project ?
>>> >> > >
>>> >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apac
>>> >> > > he.
>>> >> > > or
>>> >> > > g/ {color}]
>>> >> > >
>>> >> > > Thank you,
>>> >> > >
>>> >> > > Regards.
>>> >> > >
>>> >> > >
>>> >> > >
>>> >> > > --
>>> >> > > This message was sent by Atlassian JIRA
>>> >> > > (v7.6.3#76005)
>>> >> > >
>>> >> > > -
>>> >> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> >> > > For additional commands, e-mail: dev-h...@community.apache.org
>>> >> >
>>> >> > -
>>> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> >> > For additional commands, e-mail: dev-h...@community.apache.org
>>> >>
>>> >> -
>>> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> >> For additional commands, e-mail: dev-h...@community.apache.org
>>> >
>>> > -
>>> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> > For additional commands, e-mail: dev-h...@community.apache.org
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>>> For additional commands, e-mail: dev-h...@community.apache.org
>>
>>
>>
>> 

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

Looks like there is a bit more to it.

asf-auth template needs to be updated to give projects_role access to
the new directory.
This can be done by adding the new directory name and later dropping
the old one.

I don't yet know how to update projects-vm safely.


On 25 April 2018 at 12:43, Hervé BOUTEMY  wrote:
> no objection for me: what is important is to keep the machine running the web
> server synchronized with the change
>
> Regards,
>
> Hervé
>
> Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
>> It looks like we need to move the contents of
>>
>> https://svn.apache.org/repos/asf/comdev/projects.apache.org
>>
>> to
>>
>> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
>>
>> [No need to do the same for reporter, as it already uses a trunk directory]
>>
>> AFAICT this should not affect the projects.a.o site.
>> The pubsub script that pulls in updates only looks for the
>> comdev/projects.apache.org prefix.
>> (As it does for reporter)
>>
>> Moving projects to the trunk directory would give it the same layout
>> as reporter.
>> It would also allow the use of tags/ and branches/ sibling directories.
>>
>> Are there objections to moving projects.a.o down a level?
>>
>> On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
>> > Jira issue created:
>> > https://issues.apache.org/jira/browse/INFRA-16355
>> >
>> > Regards,
>> >
>> > Hervé
>> >
>> > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
>> >> ok, I don't see any remaining objection
>> >>
>> >> I'll ask for svn2git read-only Git+GitHub mirrors.
>> >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git
>> >> repo "comdev-community.apache.org" to match other "comdev-*.apache.org"
>> >>
>> >> This will ease people understanding that comdev's site is
>> >> community.apache.org (and not comdev.apache.org...)
>> >>
>> >> Regards,
>> >>
>> >> Hervé
>> >>
>> >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
>> >> > What about creating a Git/GitHub svn2git mirror for
>> >> > projects.apache.org?
>> >> > This would be our first Git repo for community/comdev: I don't know
>> >> > which
>> >> > prefix we should use...
>> >> >
>> >> > Any objection?
>> >> >
>> >> > Perhaps we can do the same for the 3 other locations in svn
>> >> > https://projects.apache.org/project.html?comdev-community_development
>> >> >
>> >> > Regards,
>> >> >
>> >> > Hervé
>> >> >
>> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
>> >> > > Vincent Tuybens created COMDEV-288:
>> >> > > --
>> >> > >
>> >> > >  Summary: Request "Projects Directory" migration to GIT
>> >> > >
>> >> > >  Key: COMDEV-288
>> >> > >  URL:
>> >> > >  https://issues.apache.org/jira/browse/COMDEV-288
>> >> > >
>> >> > >  Project: Community Development
>> >> > >
>> >> > >   Issue Type: SVN->GIT Migration
>> >> > >   Components: Projects Tool
>> >> > >
>> >> > > Reporter: Vincent Tuybens
>> >> > >
>> >> > > Dear all,
>> >> > >
>> >> > > is it possible for you to plan SVN to GIT migration for "Projects
>> >> > > Directory" project ?
>> >> > >
>> >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apac
>> >> > > he.
>> >> > > or
>> >> > > g/ {color}]
>> >> > >
>> >> > > Thank you,
>> >> > >
>> >> > > Regards.
>> >> > >
>> >> > >
>> >> > >
>> >> > > --
>> >> > > This message was sent by Atlassian JIRA
>> >> > > (v7.6.3#76005)
>> >> > >
>> >> > > -
>> >> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> >> > > For additional commands, e-mail: dev-h...@community.apache.org
>> >> >
>> >> > -
>> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> >> > For additional commands, e-mail: dev-h...@community.apache.org
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> >> For additional commands, e-mail: dev-h...@community.apache.org
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> > For additional commands, e-mail: dev-h...@community.apache.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: 

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

no objection for me: what is important is to keep the machine running the web 
server synchronized with the change

Regards,

Hervé

Le dimanche 22 avril 2018, 10:50:28 CEST sebb a écrit :
> It looks like we need to move the contents of
> 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org
> 
> to
> 
> https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk
> 
> [No need to do the same for reporter, as it already uses a trunk directory]
> 
> AFAICT this should not affect the projects.a.o site.
> The pubsub script that pulls in updates only looks for the
> comdev/projects.apache.org prefix.
> (As it does for reporter)
> 
> Moving projects to the trunk directory would give it the same layout
> as reporter.
> It would also allow the use of tags/ and branches/ sibling directories.
> 
> Are there objections to moving projects.a.o down a level?
> 
> On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
> > Jira issue created:
> > https://issues.apache.org/jira/browse/INFRA-16355
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
> >> ok, I don't see any remaining objection
> >> 
> >> I'll ask for svn2git read-only Git+GitHub mirrors.
> >> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git
> >> repo "comdev-community.apache.org" to match other "comdev-*.apache.org"
> >> 
> >> This will ease people understanding that comdev's site is
> >> community.apache.org (and not comdev.apache.org...)
> >> 
> >> Regards,
> >> 
> >> Hervé
> >> 
> >> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
> >> > What about creating a Git/GitHub svn2git mirror for
> >> > projects.apache.org?
> >> > This would be our first Git repo for community/comdev: I don't know
> >> > which
> >> > prefix we should use...
> >> > 
> >> > Any objection?
> >> > 
> >> > Perhaps we can do the same for the 3 other locations in svn
> >> > https://projects.apache.org/project.html?comdev-community_development
> >> > 
> >> > Regards,
> >> > 
> >> > Hervé
> >> > 
> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> > > Vincent Tuybens created COMDEV-288:
> >> > > --
> >> > > 
> >> > >  Summary: Request "Projects Directory" migration to GIT
> >> > >  
> >> > >  Key: COMDEV-288
> >> > >  URL:
> >> > >  https://issues.apache.org/jira/browse/COMDEV-288
> >> > >  
> >> > >  Project: Community Development
> >> > >   
> >> > >   Issue Type: SVN->GIT Migration
> >> > >   Components: Projects Tool
> >> > >   
> >> > > Reporter: Vincent Tuybens
> >> > > 
> >> > > Dear all,
> >> > > 
> >> > > is it possible for you to plan SVN to GIT migration for "Projects
> >> > > Directory" project ?
> >> > > 
> >> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apac
> >> > > he.
> >> > > or
> >> > > g/ {color}]
> >> > > 
> >> > > Thank you,
> >> > > 
> >> > > Regards.
> >> > > 
> >> > > 
> >> > > 
> >> > > --
> >> > > This message was sent by Atlassian JIRA
> >> > > (v7.6.3#76005)
> >> > > 
> >> > > -
> >> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> > > For additional commands, e-mail: dev-h...@community.apache.org
> >> > 
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> > For additional commands, e-mail: dev-h...@community.apache.org
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

It looks like we need to move the contents of

https://svn.apache.org/repos/asf/comdev/projects.apache.org

to

https://svn.apache.org/repos/asf/comdev/projects.apache.org/trunk

[No need to do the same for reporter, as it already uses a trunk directory]

AFAICT this should not affect the projects.a.o site.
The pubsub script that pulls in updates only looks for the
comdev/projects.apache.org prefix.
(As it does for reporter)

Moving projects to the trunk directory would give it the same layout
as reporter.
It would also allow the use of tags/ and branches/ sibling directories.

Are there objections to moving projects.a.o down a level?


On 13 April 2018 at 16:59, Hervé BOUTEMY  wrote:
> Jira issue created:
> https://issues.apache.org/jira/browse/INFRA-16355
>
> Regards,
>
> Hervé
>
> Le samedi 7 avril 2018, 09:36:56 CEST Hervé BOUTEMY a écrit :
>> ok, I don't see any remaining objection
>>
>> I'll ask for svn2git read-only Git+GitHub mirrors.
>> Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git
>> repo "comdev-community.apache.org" to match other "comdev-*.apache.org"
>>
>> This will ease people understanding that comdev's site is
>> community.apache.org (and not comdev.apache.org...)
>>
>> Regards,
>>
>> Hervé
>>
>> Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
>> > What about creating a Git/GitHub svn2git mirror for projects.apache.org?
>> > This would be our first Git repo for community/comdev: I don't know which
>> > prefix we should use...
>> >
>> > Any objection?
>> >
>> > Perhaps we can do the same for the 3 other locations in svn
>> > https://projects.apache.org/project.html?comdev-community_development
>> >
>> > Regards,
>> >
>> > Hervé
>> >
>> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
>> > > Vincent Tuybens created COMDEV-288:
>> > > --
>> > >
>> > >  Summary: Request "Projects Directory" migration to GIT
>> > >
>> > >  Key: COMDEV-288
>> > >  URL: https://issues.apache.org/jira/browse/COMDEV-288
>> > >
>> > >  Project: Community Development
>> > >
>> > >   Issue Type: SVN->GIT Migration
>> > >   Components: Projects Tool
>> > >
>> > > Reporter: Vincent Tuybens
>> > >
>> > > Dear all,
>> > >
>> > > is it possible for you to plan SVN to GIT migration for "Projects
>> > > Directory" project ?
>> > >
>> > > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.
>> > > or
>> > > g/ {color}]
>> > >
>> > > Thank you,
>> > >
>> > > Regards.
>> > >
>> > >
>> > >
>> > > --
>> > > This message was sent by Atlassian JIRA
>> > > (v7.6.3#76005)
>> > >
>> > > -
>> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> > > For additional commands, e-mail: dev-h...@community.apache.org
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> > For additional commands, e-mail: dev-h...@community.apache.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

ok, I don't see any remaining objection

I'll ask for svn2git read-only Git+GitHub mirrors.
Regarding /repos/asf/comdev/site/trunk/, I'll see if we can name the git repo 
"comdev-community.apache.org" to match other "comdev-*.apache.org"

This will ease people understanding that comdev's site is community.apache.org 
(and not comdev.apache.org...)

Regards,

Hervé

Le mercredi 4 avril 2018, 08:09:46 CEST Hervé BOUTEMY a écrit :
> What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> This would be our first Git repo for community/comdev: I don't know which
> prefix we should use...
> 
> Any objection?
> 
> Perhaps we can do the same for the 3 other locations in svn
> https://projects.apache.org/project.html?comdev-community_development
> 
> Regards,
> 
> Hervé
> 
> Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> > Vincent Tuybens created COMDEV-288:
> > --
> > 
> >  Summary: Request "Projects Directory" migration to GIT
> >  
> >  Key: COMDEV-288
> >  URL: https://issues.apache.org/jira/browse/COMDEV-288
> >  
> >  Project: Community Development
> >   
> >   Issue Type: SVN->GIT Migration
> >   Components: Projects Tool
> >   
> > Reporter: Vincent Tuybens
> > 
> > Dear all,
> > 
> > is it possible for you to plan SVN to GIT migration for "Projects
> > Directory" project ?
> > 
> > [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.or
> > g/ {color}]
> > 
> > Thank you,
> > 
> > Regards.
> > 
> > 
> > 
> > --
> > This message was sent by Atlassian JIRA
> > (v7.6.3#76005)
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

yes, they are not mergeable at Git level (since it will be read-only)
but they are mergeable at svn level, the same way that we merge patches 
attached to Jira issues (when people take time to create such patches and 
attach, which nowadays does not happen much): every GitHub PR can be seen as a 
patch or diff (I don't remember if one is best suited than the other)

example:
PR: https://github.com/apache/maven-wagon/pull/47
patch: https://github.com/apache/maven-wagon/pull/47.patch
diff: https://github.com/apache/maven-wagon/pull/47.diff

not as convenient for the Comdev team as if we fully switch to Git, but like 
explained to Sebb, svn2git mirror is a necessary first step that lowers impact 
before thinking about doing next steps or not.
For the team, it really behaves as if we totally stay with svn: this Git 
mirror is just a new source of patches that are easier for contributors to 
create and submit (through Pull Requests)

But for sure, fully switching to Git to get Git-mergeable Pull Requests for 
the team can be useful in the future: we'll see that later, seeing also other 
side impacts (on hosts for example)

Regards,

Hervé

Le jeudi 5 avril 2018, 03:00:40 CEST Maxim Solodovnik a écrit :
> The PRs created for read-only hit are not "mergeable"
> 
> WBR, Maxim
> (from mobile, sorry for the typos)
> 
> On Thu, Apr 5, 2018, 05:34 Hervé BOUTEMY  wrote:
> > there is a little misunderstanding: I'm not talking about fully switching
> > from
> > svn to git
> > I'm talking about keeping svn as canonical repository but adding a
> > read-only
> > git mirror like done on many svn repositories [1]
> > 
> > This does not change anything to the host configuration, but adds a GitHub
> > mirror for external people to contribute through GitHub Pull Requests,
> > which
> > are so much easier to submit than svn patch attached to a Jira issue: this
> > will give a chance to get more contributions.
> > 
> > Later on, we can decide to switch to Git (with gitwcsub acting like
> > currently
> > svnwcsub), but that will be another choice to do in another time.
> > 
> > Regards,
> > 
> > Hervé
> > 
> > [1] http://git.apache.org/
> > 
> > Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> > > On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
> > > > What about creating a Git/GitHub svn2git mirror for
> > 
> > projects.apache.org?
> > 
> > > > This would be our first Git repo for community/comdev: I don't know
> > 
> > which
> > 
> > > > prefix we should use...
> > > > 
> > > > Any objection?
> > > 
> > > What are the benefits to using Git over SVN?
> > > Do they outweigh the costs?
> > > Who gets the benefit, and who pays the costs?
> > > 
> > > ==
> > > 
> > > Note that projects.a.o actually updates its own code repo using a role
> > > account. I don't know if that can be done in Git.
> > > It took quite a bit of work to ensure that the updates did not result
> > > in a locked workspace.
> > > (This used to happen regularly at the beginning)
> > > 
> > > Also, the projects.a.o and reporter.a.o hosts share the same VM.
> > > They would need to move together.
> > > 
> > > And of course the VM puppet definition will need to be updated.
> > > It's more complicated than a simple pubsub operation.
> > > 
> > > > Perhaps we can do the same for the 3 other locations in svn
> > > > https://projects.apache.org/project.html?comdev-community_development
> > > > 
> > > > Regards,
> > > > 
> > > > Hervé
> > > > 
> > > > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> > > >> Vincent Tuybens created COMDEV-288:
> > > >> --
> > > >> 
> > > >>  Summary: Request "Projects Directory" migration to GIT
> > > >>  
> > > >>  Key: COMDEV-288
> > 
> > > >>  URL:
> > https://issues.apache.org/jira/browse/COMDEV-288
> > 
> > > >>  Project: Community Development
> > > >>   
> > > >>   Issue Type: SVN->GIT Migration
> > > >>   Components: Projects Tool
> > > >>   
> > > >> Reporter: Vincent Tuybens
> > > >> 
> > > >> Dear all,
> > > >> 
> > > >> is it possible for you to plan SVN to GIT migration for "Projects
> > > >> Directory" project ?
> > > >> 
> > > >> [{color:#0066cc}
> > 
> > https://svn.apache.org/repos/asf/comdev/projects.apache.o
> > 
> > > >> rg/ {color}]
> > > >> 
> > > >> Thank you,
> > > >> 
> > > >> Regards.
> > > >> 
> > > >> 
> > > >> 
> > > >> --
> > > >> This message was sent by Atlassian JIRA
> > > >> (v7.6.3#76005)
> > > >> 
> > > >> -
> > > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > >> For additional commands, e-mail: dev-h...@community.apache.org
> > > > 
> > > > -
> > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > > For 

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

Le jeudi 5 avril 2018, 00:42:57 CEST sebb a écrit :
> On 4 April 2018 at 23:34, Hervé BOUTEMY  wrote:
> > there is a little misunderstanding: I'm not talking about fully switching
> > from svn to git
> > I'm talking about keeping svn as canonical repository but adding a
> > read-only git mirror like done on many svn repositories [1]
> 
> The JIRA said otherwise...
yes, external people nowadays just think "switch to Git" et voilà.
But I have a long experience on Maven (more than 5 years to to the near full 
migration [2]), and I know that it does not happen like this: there are steps 
to have the team find advantages along the journey, letting time to learn and 
do progressive adoption
This is how I naturally transformed the initial typical request: into the 
typical first step

[2] https://cwiki.apache.org/confluence/display/MAVEN/Git+Migration

> 
> > This does not change anything to the host configuration, but adds a GitHub
> > mirror for external people to contribute through GitHub Pull Requests,
> > which are so much easier to submit than svn patch attached to a Jira
> > issue: this will give a chance to get more contributions.
> 
> OK, fine.
> 
> > Later on, we can decide to switch to Git (with gitwcsub acting like
> > currently svnwcsub), but that will be another choice to do in another
> > time.
> 
> That will be a lot of work.
We'll see it later: for sure, it's more impact, then requires to be prepared.
svn 2 git mirror is a good first step, that is required if we do the next steps 
or not

> 
> > Regards,
> > 
> > Hervé
> > 
> > [1] http://git.apache.org/
> > 
> > Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> >> On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
> >> > What about creating a Git/GitHub svn2git mirror for
> >> > projects.apache.org?
> >> > This would be our first Git repo for community/comdev: I don't know
> >> > which
> >> > prefix we should use...
> >> > 
> >> > Any objection?
> >> 
> >> What are the benefits to using Git over SVN?
> >> Do they outweigh the costs?
> >> Who gets the benefit, and who pays the costs?
> >> 
> >> ==
> >> 
> >> Note that projects.a.o actually updates its own code repo using a role
> >> account. I don't know if that can be done in Git.
> >> It took quite a bit of work to ensure that the updates did not result
> >> in a locked workspace.
> >> (This used to happen regularly at the beginning)
> >> 
> >> Also, the projects.a.o and reporter.a.o hosts share the same VM.
> >> They would need to move together.
> >> 
> >> And of course the VM puppet definition will need to be updated.
> >> It's more complicated than a simple pubsub operation.
> >> 
> >> > Perhaps we can do the same for the 3 other locations in svn
> >> > https://projects.apache.org/project.html?comdev-community_development
> >> > 
> >> > Regards,
> >> > 
> >> > Hervé
> >> > 
> >> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> >> Vincent Tuybens created COMDEV-288:
> >> >> --
> >> >> 
> >> >>  Summary: Request "Projects Directory" migration to GIT
> >> >>  
> >> >>  Key: COMDEV-288
> >> >>  URL: https://issues.apache.org/jira/browse/COMDEV-288
> >> >>  
> >> >>  Project: Community Development
> >> >>   
> >> >>   Issue Type: SVN->GIT Migration
> >> >>   Components: Projects Tool
> >> >>   
> >> >> Reporter: Vincent Tuybens
> >> >> 
> >> >> Dear all,
> >> >> 
> >> >> is it possible for you to plan SVN to GIT migration for "Projects
> >> >> Directory" project ?
> >> >> 
> >> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apach
> >> >> e.o
> >> >> rg/ {color}]
> >> >> 
> >> >> Thank you,
> >> >> 
> >> >> Regards.
> >> >> 
> >> >> 
> >> >> 
> >> >> --
> >> >> This message was sent by Atlassian JIRA
> >> >> (v7.6.3#76005)
> >> >> 
> >> >> -
> >> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> >> For additional commands, e-mail: dev-h...@community.apache.org
> >> > 
> >> > -
> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> > For additional commands, e-mail: dev-h...@community.apache.org
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional 

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Maxim Solodovnik]

The PRs created for read-only hit are not "mergeable"

WBR, Maxim
(from mobile, sorry for the typos)

On Thu, Apr 5, 2018, 05:34 Hervé BOUTEMY  wrote:

> there is a little misunderstanding: I'm not talking about fully switching
> from
> svn to git
> I'm talking about keeping svn as canonical repository but adding a
> read-only
> git mirror like done on many svn repositories [1]
>
> This does not change anything to the host configuration, but adds a GitHub
> mirror for external people to contribute through GitHub Pull Requests,
> which
> are so much easier to submit than svn patch attached to a Jira issue: this
> will give a chance to get more contributions.
>
> Later on, we can decide to switch to Git (with gitwcsub acting like
> currently
> svnwcsub), but that will be another choice to do in another time.
>
> Regards,
>
> Hervé
>
> [1] http://git.apache.org/
>
> Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> > On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
> > > What about creating a Git/GitHub svn2git mirror for
> projects.apache.org?
> > > This would be our first Git repo for community/comdev: I don't know
> which
> > > prefix we should use...
> > >
> > > Any objection?
> >
> > What are the benefits to using Git over SVN?
> > Do they outweigh the costs?
> > Who gets the benefit, and who pays the costs?
> >
> > ==
> >
> > Note that projects.a.o actually updates its own code repo using a role
> > account. I don't know if that can be done in Git.
> > It took quite a bit of work to ensure that the updates did not result
> > in a locked workspace.
> > (This used to happen regularly at the beginning)
> >
> > Also, the projects.a.o and reporter.a.o hosts share the same VM.
> > They would need to move together.
> >
> > And of course the VM puppet definition will need to be updated.
> > It's more complicated than a simple pubsub operation.
> >
> > > Perhaps we can do the same for the 3 other locations in svn
> > > https://projects.apache.org/project.html?comdev-community_development
> > >
> > > Regards,
> > >
> > > Hervé
> > >
> > > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> > >> Vincent Tuybens created COMDEV-288:
> > >> --
> > >>
> > >>  Summary: Request "Projects Directory" migration to GIT
> > >>
> > >>  Key: COMDEV-288
> > >>  URL:
> https://issues.apache.org/jira/browse/COMDEV-288
> > >>
> > >>  Project: Community Development
> > >>
> > >>   Issue Type: SVN->GIT Migration
> > >>   Components: Projects Tool
> > >>
> > >> Reporter: Vincent Tuybens
> > >>
> > >> Dear all,
> > >>
> > >> is it possible for you to plan SVN to GIT migration for "Projects
> > >> Directory" project ?
> > >>
> > >> [{color:#0066cc}
> https://svn.apache.org/repos/asf/comdev/projects.apache.o
> > >> rg/ {color}]
> > >>
> > >> Thank you,
> > >>
> > >> Regards.
> > >>
> > >>
> > >>
> > >> --
> > >> This message was sent by Atlassian JIRA
> > >> (v7.6.3#76005)
> > >>
> > >> -
> > >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > >> For additional commands, e-mail: dev-h...@community.apache.org
> > >
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > > For additional commands, e-mail: dev-h...@community.apache.org
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>
>

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

On 4 April 2018 at 23:34, Hervé BOUTEMY  wrote:
> there is a little misunderstanding: I'm not talking about fully switching from
> svn to git
> I'm talking about keeping svn as canonical repository but adding a read-only
> git mirror like done on many svn repositories [1]

The JIRA said otherwise...

> This does not change anything to the host configuration, but adds a GitHub
> mirror for external people to contribute through GitHub Pull Requests, which
> are so much easier to submit than svn patch attached to a Jira issue: this
> will give a chance to get more contributions.

OK, fine.

> Later on, we can decide to switch to Git (with gitwcsub acting like currently
> svnwcsub), but that will be another choice to do in another time.

That will be a lot of work.

> Regards,
>
> Hervé
>
> [1] http://git.apache.org/
>
> Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
>> On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
>> > What about creating a Git/GitHub svn2git mirror for projects.apache.org?
>> > This would be our first Git repo for community/comdev: I don't know which
>> > prefix we should use...
>> >
>> > Any objection?
>>
>> What are the benefits to using Git over SVN?
>> Do they outweigh the costs?
>> Who gets the benefit, and who pays the costs?
>>
>> ==
>>
>> Note that projects.a.o actually updates its own code repo using a role
>> account. I don't know if that can be done in Git.
>> It took quite a bit of work to ensure that the updates did not result
>> in a locked workspace.
>> (This used to happen regularly at the beginning)
>>
>> Also, the projects.a.o and reporter.a.o hosts share the same VM.
>> They would need to move together.
>>
>> And of course the VM puppet definition will need to be updated.
>> It's more complicated than a simple pubsub operation.
>>
>> > Perhaps we can do the same for the 3 other locations in svn
>> > https://projects.apache.org/project.html?comdev-community_development
>> >
>> > Regards,
>> >
>> > Hervé
>> >
>> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
>> >> Vincent Tuybens created COMDEV-288:
>> >> --
>> >>
>> >>  Summary: Request "Projects Directory" migration to GIT
>> >>
>> >>  Key: COMDEV-288
>> >>  URL: https://issues.apache.org/jira/browse/COMDEV-288
>> >>
>> >>  Project: Community Development
>> >>
>> >>   Issue Type: SVN->GIT Migration
>> >>   Components: Projects Tool
>> >>
>> >> Reporter: Vincent Tuybens
>> >>
>> >> Dear all,
>> >>
>> >> is it possible for you to plan SVN to GIT migration for "Projects
>> >> Directory" project ?
>> >>
>> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.o
>> >> rg/ {color}]
>> >>
>> >> Thank you,
>> >>
>> >> Regards.
>> >>
>> >>
>> >>
>> >> --
>> >> This message was sent by Atlassian JIRA
>> >> (v7.6.3#76005)
>> >>
>> >> -
>> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> >> For additional commands, e-mail: dev-h...@community.apache.org
>> >
>> > -
>> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> > For additional commands, e-mail: dev-h...@community.apache.org
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

there is a little misunderstanding: I'm not talking about fully switching from 
svn to git
I'm talking about keeping svn as canonical repository but adding a read-only 
git mirror like done on many svn repositories [1]

This does not change anything to the host configuration, but adds a GitHub 
mirror for external people to contribute through GitHub Pull Requests, which 
are so much easier to submit than svn patch attached to a Jira issue: this 
will give a chance to get more contributions.

Later on, we can decide to switch to Git (with gitwcsub acting like currently 
svnwcsub), but that will be another choice to do in another time.

Regards,

Hervé

[1] http://git.apache.org/

Le mercredi 4 avril 2018, 10:32:55 CEST sebb a écrit :
> On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
> > What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> > This would be our first Git repo for community/comdev: I don't know which
> > prefix we should use...
> > 
> > Any objection?
> 
> What are the benefits to using Git over SVN?
> Do they outweigh the costs?
> Who gets the benefit, and who pays the costs?
> 
> ==
> 
> Note that projects.a.o actually updates its own code repo using a role
> account. I don't know if that can be done in Git.
> It took quite a bit of work to ensure that the updates did not result
> in a locked workspace.
> (This used to happen regularly at the beginning)
> 
> Also, the projects.a.o and reporter.a.o hosts share the same VM.
> They would need to move together.
> 
> And of course the VM puppet definition will need to be updated.
> It's more complicated than a simple pubsub operation.
> 
> > Perhaps we can do the same for the 3 other locations in svn
> > https://projects.apache.org/project.html?comdev-community_development
> > 
> > Regards,
> > 
> > Hervé
> > 
> > Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> >> Vincent Tuybens created COMDEV-288:
> >> --
> >> 
> >>  Summary: Request "Projects Directory" migration to GIT
> >>  
> >>  Key: COMDEV-288
> >>  URL: https://issues.apache.org/jira/browse/COMDEV-288
> >>  
> >>  Project: Community Development
> >>   
> >>   Issue Type: SVN->GIT Migration
> >>   Components: Projects Tool
> >>   
> >> Reporter: Vincent Tuybens
> >> 
> >> Dear all,
> >> 
> >> is it possible for you to plan SVN to GIT migration for "Projects
> >> Directory" project ?
> >> 
> >> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.o
> >> rg/ {color}]
> >> 
> >> Thank you,
> >> 
> >> Regards.
> >> 
> >> 
> >> 
> >> --
> >> This message was sent by Atlassian JIRA
> >> (v7.6.3#76005)
> >> 
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> >> For additional commands, e-mail: dev-h...@community.apache.org
> > 
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> > For additional commands, e-mail: dev-h...@community.apache.org
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[sebb]

On 4 April 2018 at 07:09, Hervé BOUTEMY  wrote:
> What about creating a Git/GitHub svn2git mirror for projects.apache.org?
> This would be our first Git repo for community/comdev: I don't know which 
> prefix
> we should use...
>
> Any objection?

What are the benefits to using Git over SVN?
Do they outweigh the costs?
Who gets the benefit, and who pays the costs?

==

Note that projects.a.o actually updates its own code repo using a role account.
I don't know if that can be done in Git.
It took quite a bit of work to ensure that the updates did not result
in a locked workspace.
(This used to happen regularly at the beginning)

Also, the projects.a.o and reporter.a.o hosts share the same VM.
They would need to move together.

And of course the VM puppet definition will need to be updated.
It's more complicated than a simple pubsub operation.

> Perhaps we can do the same for the 3 other locations in svn
> https://projects.apache.org/project.html?comdev-community_development
>
> Regards,
>
> Hervé
>
> Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
>> Vincent Tuybens created COMDEV-288:
>> --
>>
>>  Summary: Request "Projects Directory" migration to GIT
>>  Key: COMDEV-288
>>  URL: https://issues.apache.org/jira/browse/COMDEV-288
>>  Project: Community Development
>>   Issue Type: SVN->GIT Migration
>>   Components: Projects Tool
>> Reporter: Vincent Tuybens
>>
>>
>> Dear all,
>>
>> is it possible for you to plan SVN to GIT migration for "Projects Directory"
>> project ?
>>
>> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/
>> {color}]
>>
>> Thank you,
>>
>> Regards.
>>
>>
>>
>> --
>> This message was sent by Atlassian JIRA
>> (v7.6.3#76005)
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
>> For additional commands, e-mail: dev-h...@community.apache.org
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>

-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org

Re: [jira] [Created] (COMDEV-288) Request "Projects Directory" migration to GIT

[Hervé BOUTEMY]

What about creating a Git/GitHub svn2git mirror for projects.apache.org?
This would be our first Git repo for community/comdev: I don't know which 
prefix 
we should use...

Any objection?

Perhaps we can do the same for the 3 other locations in svn
https://projects.apache.org/project.html?comdev-community_development

Regards,

Hervé

Le mardi 3 avril 2018, 09:20:00 CEST Vincent Tuybens (JIRA) a écrit :
> Vincent Tuybens created COMDEV-288:
> --
> 
>  Summary: Request "Projects Directory" migration to GIT
>  Key: COMDEV-288
>  URL: https://issues.apache.org/jira/browse/COMDEV-288
>  Project: Community Development
>   Issue Type: SVN->GIT Migration
>   Components: Projects Tool
> Reporter: Vincent Tuybens
> 
> 
> Dear all,
> 
> is it possible for you to plan SVN to GIT migration for "Projects Directory"
> project ?
> 
> [{color:#0066cc}https://svn.apache.org/repos/asf/comdev/projects.apache.org/
> {color}]
> 
> Thank you,
> 
> Regards.
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
For additional commands, e-mail: dev-h...@community.apache.org