[Dune-devel] Is it intentional that user forks are private?

[Ospina De Los Rios, Santiago]

No, forks are not private by default. When forking a project, the default option is the same as the repository that you are forking. This means that in the case of dune-common, the owner of the fork had to intentionally opt for a private fork in the moment of forking, or manually changing the visibility later on. Best, Santiago

________________________________
From: Dune-devel <dune-devel-bounces at lists.dune-project.org> on behalf of Markus Blatt <markus at dr-blatt.de>
Sent: Friday, March 10, 2023 7:42:36 PM
To: dune-devel at lists.dune-project.org
Subject: Re: [Dune-devel] Is it intentional that user forks are private?

Am Fri, Mar 10, 2023 at 05:34:36PM +0000 schrieb Ospina De Los Rios, Santiago:
>GitLab manages permissions by projects, groups or roles within a project. Your core developer credentials are only valid to the core group and private forks (like this one) are private even for the owners of the original repository.

Interesting. Was that the way before, too? At least on github default is public.
Private by defaults means any further development is hidden unless the user
takes action. I think this is a bit unfortunate.

You guys should tell your students that they have to make forks public or you
risk that paid work will be lost.

BTW at least https://gitlab.dune-project.org/help/user/project/merge_requests/reviews/index.md#checkout-merge-requests-locally-through-the-head-ref
works for an existing MR.

Markus

_______________________________________________
Dune-devel mailing list
Dune-devel at lists.dune-project.org
https://lists.dune-project.org/mailman/listinfo/dune-devel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.dune-project.org/pipermail/dune-devel/attachments/20230313/cbc69fbb/attachment.htm>