[Paraview-developers] Migrating Git repository to Gitlab

[Utkarsh Ayachit]

If only it was easy to fix :). I've requested our sysadmins to see if
they can fix this. Initial feedback  hasn't been very promising. Let's
wait and see.

Utkarsh

On Mon, Mar 16, 2015 at 7:01 PM, Moreland, Kenneth <kmorel at sandia.gov> wrote:
> Ah, yes. That's good. But still, the home page shouldn't give the error "You
> need to sign in before continuing."
>
> -Ken
>
> From: Berk Geveci <berk.geveci at kitware.com>
> Date: Monday, March 16, 2015 at 2:01 PM
> To: Kenneth Moreland <kmorel at sandia.gov>
> Cc: Brad King <brad.king at kitware.com>, "paraview-developers at paraview.org"
> <paraview-developers at paraview.org>
> Subject: [EXTERNAL] Re: [Paraview-developers] Migrating Git repository to
> Gitlab
>
> It seems to be an interface thing. If I click on the creature (cat?) on the
> upper left, it takes me to an Explore page with which I can get to projects
> even if I am not signed it.
>
> -berk
>
> On Mon, Mar 16, 2015 at 3:58 PM, Moreland, Kenneth <kmorel at sandia.gov>
> wrote:
>>
>> I notice after clicking this link that I have to create an account and
>> sign in to see anything in the gitlab system. Is there a reason not to
>> give read-only access to those not logged in. I imagine there will be
>> users who will want to clone and browse the repository without necessarily
>> making modifications.
>>
>> -Ken
>>
>>
>>
>> On 3/16/15, 11:09 AM, "Brad King" <brad.king at kitware.com> wrote:
>>
>> >On 03/11/2015 03:26 PM, Utkarsh Ayachit wrote:
>> >> If you have been monitoring the VTK-developers list, this shouldn't
>> >> come as a surprise to you, but we're working on migrating our
>> >> development workflow to use Gitlab (a Github clone) to manage
>> >> reviewing, merging  and testing of changes. This means we'll replace
>> >> our current Stage and Gerrit based development workflow with one that
>> >> uses Gitlab merge requests instead.
>> >
>> >FYI, https://gitlab.kitware.com is now visible publicly.
>> >
>> >We are in the process of moving VTK's development over to it,
>> >but ParaView is not moving quite yet.
>> >
>> >We've marked all the placeholder ParaView repositories as "private"
>> >on this GitLab to avoid confusion, including user forks.  Please keep
>> >them that way until we officially announce that ParaView has moved.
>> >
>> >Thanks,
>> >-Brad
>> >
>> >_______________________________________________
>> >Powered by www.kitware.com
>> >
>> >Visit other Kitware open-source projects at
>> >http://www.kitware.com/opensource/opensource.html
>> >
>> >Search the list archives at:
>> >http://markmail.org/search/?q=Paraview-developers
>> >
>> >Follow this link to subscribe/unsubscribe:
>> >http://public.kitware.com/mailman/listinfo/paraview-developers
>>
>> _______________________________________________
>> Powered by www.kitware.com
>>
>> Visit other Kitware open-source projects at
>> http://www.kitware.com/opensource/opensource.html
>>
>> Search the list archives at:
>> http://markmail.org/search/?q=Paraview-developers
>>
>> Follow this link to subscribe/unsubscribe:
>> http://public.kitware.com/mailman/listinfo/paraview-developers
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Search the list archives at:
> http://markmail.org/search/?q=Paraview-developers
>
> Follow this link to subscribe/unsubscribe:
> http://public.kitware.com/mailman/listinfo/paraview-developers
>