On 28 April 2018 at 11:15, Hervé BOUTEMY <herve.bout...@free.fr> wrote:
> creating a GitBox/GitHub test repository is easy: it's self service [1]

I looked at that, and one can only create empty repos for projects
that are registered to use GitBox - see INFRA-16456.

> You'll get an empty Git repository that is read/write both from GitBox and
> GitHub: you'll be able to do the tests you want. The only little issue is that
> future delete of this test repo won't be self service...
>
> Independently from GitBox/GitHub tests, you can ask INFRA to get a read-only
> svn2git mirror, that will prepare the whole Attic site svn history as Git
> history, to not loose the history if you decide to finally migrate fully to 
> Git
>
> Regards,
>
> Hervé
>
> [1] https://gitbox.apache.org/
>
> Le samedi 28 avril 2018, 00:09:08 CEST sebb a écrit :
>> On 27 April 2018 at 17:57, Jan Iversen <j...@apache.org> wrote:
>> > Sent from my iPad
>> >
>> >> On 27 Apr 2018, at 17:17, sebb <seb...@gmail.com> wrote:
>> >>
>> >> I think it would be useful to have an Attic GitBox test instance so we
>> >> can try out things like Buildbot scripts and online editing.
>> >>
>> >> It might also be a good way to evaluate the pros and cons of the
>> >> various redesigns.
>> >> Sort of like a Wiki page.
>> >
>> > I am not sure what a gitbox test instance consist of, so I tend to be
>> > neutral, but considering our site have not changed for a very long time I
>> > have to ask is it really needed ? and will someone be responsible for
>> > whatever needs to be maintained over time ?
>> I thought you wanted to move to Git?
>> If so, then it will have to be moved to an ASF GitBox as git-wip is
>> being withdrawn.
>>
>> Having a test instance will allow us to try out Buildbot etc. before
>> any possible move.
>>
>> In any case, the whole point was to have a test instance that can be
>> thrown away if we no longer need it.
>>
>> > In short if you all agree it is a something worth doing, then I will not
>> > stand in the way.
>> >
>> > rgds
>> > jan I
>
>

Reply via email to