[Dune] Git repositories on gitlab.dune-project.org

[Steffen Müthing]

And another hint: If the colored menu bar on the left hand side only consists of cryptic
icons, try increasing the width of your browser window - at some point the menu bar will
expand and show text entries.

Steffen

> Am 29.10.2015 um 11:58 schrieb Steffen Müthing <steffen.muething at iwr.uni-heidelberg.de>:
> 
> One more little thing:
> 
> If you are also using the local Heidelberg GitLab at conan2.iwr.uni-heidelberg.de, you should
> definitely pick different color schemes for the two - I have really confused myself quite a bit with
> those before, changing stuff on the wrong server...
> 
> Steffen
> 
>> Am 29.10.2015 um 11:50 schrieb Steffen Müthing <steffen.muething at iwr.uni-heidelberg.de>:
>> 
>> Dear DUNE users and developers,
>> 
>> there are some important changes to our development infrastructure. PLEASE READ THIS
>> MAIL COMPLETELY, that will make life a lot easier for all us… ;-)
>> 
>> as decided at this year’s developer meeting, our development infrastructure will be moved
>> to a GitLab instance. GitLab is similar to GitHub, but can be hosted on our own server here
>> in Heidelberg.
>> 
>> This server is now online and can be found at https://gitlab.dune-project.org. Before we can
>> actually move the development activities over to that server, everybody will have to create a
>> new account (except for people who have already used the local GitLab in Heidelberg, e.g.
>> for PDELab - in that case, skip the following instructions). To do so,
>> 
>> * go to https://gitlab.dune-project.org and use the sign-up form at the bottom right of the page.
>> Please enter your real name and use the convention "firstname.lastname“ for your username.
>> 
>> * you will then receive an email with a confirmation link that you have to click.
>> 
>> * Afterwards, GitLab will say that your account is blocked. This is normal and not an error: One
>> of the GitLab administrators still has to manually approve your account, which should happen
>> within a few minutes.
>> 
>> * You will get another email once your account has been unblocked and can be used.
>> 
>> The manual approval process is a little annoying, but as every GitLab user can create repositories
>> on the server, we really want to be able to block spam.
>> 
>> If you have already used the GitLab instance in Heidelberg, you will already have an account
>> on gitlab.dune-project.org with the same username and password you used for the other instance.
>> 
>> After your first sign-in, you should take the time to customize your settings. To get there, click
>> on your username in the bottom left of the screen. On the following page, click on „Profile Settings“
>> (the last menu entry in the bar on the left). On the main settings page, you can update your name
>> and other personal details and decide whether your email should be visible. There are a few more
>> interesting settings:
>> 
>> * Under „Account“, you can link your account with GitHub, which will allow you to log in using your
>> GitHub credentials (click the little GitHub icon on the sign in page). That way, you can cut down
>> on the number of passwords if you want…
>> 
>> * Please add any additional email addresses that you use / have used in Git commits under „Emails“.
>> That way, GitLab will know that these commits have also been made by you.
>> 
>> * Under „Notifications“, you can tell GitLab for what it should send you notifications (also on a per-group
>> basis) and to which of your email addresses it should send those notifications.
>> 
>> * GitLab allows pushing over SSH in addition to HTTPS - yeah! Before you can use it, you will have to
>> upload your public SSH key(s).
>> 
>> * The „Preferences“ allow you to change the way GitLab looks. You can pick a different color scheme,
>>  which mostly changes the color of the left-hand menu bar, a code highlighting scheme, what to show
>>  on your dashboard and on the project pages and - very important - the layout width. This defauilts to
>>  fixed. If you have a wide screen, you should definitely switch this to „fluid“, as it will show you a lot more
>>  information on screen.
>>  You can also play around with the dashboard in combination with starred projects. If you are only interested
>>   in a small number of DUNE modules, you can star them on their project page and set the dashboard to
>>   „Starred Projects“ or „Starred Project’s Activity“ to hide all the other projects.
>> 
>> 
>> Please create your account as soon as possible, as I would like to keep the transition period rather short
>> to keep the unavoidable synchronization problems to a minimum.
>> 
>> 
>> Best,
>> Steffen
>> 
>> PS: @PDELab users: We will move PDELab development from the GitLab instance in Heidelberg to
>>      gitlab.dune-project.org sometime later today - there will be a separate email on how to update your
>>      remotes on the PDELab mailing list.
>> _______________________________________________
>> Dune mailing list
>> Dune at dune-project.org
>> http://lists.dune-project.org/mailman/listinfo/dune
> 
> _______________________________________________
> Dune mailing list
> Dune at dune-project.org
> http://lists.dune-project.org/mailman/listinfo/dune

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <https://lists.dune-project.org/pipermail/dune/attachments/20151029/0a5a2aa9/attachment.sig>