Moving to gitlab, which features to use.

[Wolthera]

Hey everyone,

The gitlab instance is up! https://invent.kde.org/kde/krita

Now, tomorrow(friday), there's a good chance a lot of developers are
away, this is due to a variety of reasons, the least of which that all
of us have been working very hard on bugfixes past week, so please do
not run into the krita chat with fifteen thousand questions, because
likely noone there might be able to give any authorative answer :D

That said, I have updated the intro to hacking krita page [1]
(partially because scott was hoping that the developer page on
krita.org could be merged into it so there's less duplicate sources of
information, I have done this too), and I have written down the bare
basics that I know about gitlab. Jenkins might still be building the
page if you see nothing new.

Ben says that direct pushes should now be done via the gitlab url, so
this weekend do the following:

1. Login into invent.kde.org, configure your settings, add in avatars,
all the good stuff.
2. Reupload your ssh keys if you have made them. The instance cannot
get them from identity.kde.org. Ben's direct words are 'Contributors
will need to login on invent.kde.org and upload their SSH keys before
they're able to push for the first time.'
3. In your source directory, do... git remote set-url origin
git at invent.kde.org:kde/krita
    (anongit will still be able to be used for pulling, of course.)
4. Tasks have not been ported, please keep using phabricator for these.

This is all we know right now(no info on CI right now), hopefully
you'll enjoy the new interface and merge requests and forking and web
ides and what else :)

[1] : https://docs.krita.org/en/untranslatable_pages/intro_hacking_krita.html

On Thu, Apr 18, 2019 at 2:53 PM Scott Petrovic <scottpetrovic at gmail.com> wrote:
>
> I think we will have to play around with it to see what it is capable of. There definitely seems to be forking and merge requests available in gitlab.
>
> In about 5 minutes, I forked Kdenlive, made a change and committed it all from the invent site. I then submitted a merge request from my master branch to their master branch. I wouldn't be surprised if they could merge my change with a single button from the web UI.
>
> https://invent.kde.org/kde/kdenlive/merge_requests/35
>
>
>
>
>
>
>
>
>
> On Mon, Apr 15, 2019 at 10:21 AM Wolthera <griffinvalley at gmail.com> wrote:
>>
>> On Mon, Apr 15, 2019 at 3:42 PM L. E. Segovia <lsg at amyspark.me> wrote:
>> >
>> > Hey all, hey Wolthera,
>> >
>> > I'm glad to hear we're moving out of Phabricator. Having said this, as a
>> > GitHub user, I'm more used to the merge request approach. Ideas:
>> >
>> > * We'd need to document how to fork/clone, download the repo, change
>> > branch, etc. (University experience tells me this is not straightforward
>> > for beginners.)
>>
>> Yes, we'll need to wait till the migration is complete to see how this
>> will work in the end.
>>
>> >
>> > * Not workflow-related, but some serious CI integration would be helpful
>> > to let them know if their patch is acceptable.
>>
>> Ben says sysadmin intends to use gitlab's ci instead of jenkins ci(but
>> nightlies will still be done on jenkins) but they haven't finalized
>> the plans yet.
>>
>> >
>> > * Merge-by-email seems a far lower entry barrier than the proposed
>> > merge-request workflow, and also more similar to the current Phabricator
>> > approach. I think we could expand a bit on the Git-email docs from
>> > https://git-scm.com/book/en/v2/Appendix-C%3A-Git-Commands-Email .
>>
>> Ooh, thanks!
>>
>> >
>> > Another question-- can we keep using tasks? I found them particularly
>> > useful to review ideas without involving code.
>>
>> Yes, we will keep using tasks/issues. There's just too much pre-coding
>> design going on in Krita to not have them :)
>>
>> >
>> > Best regards,
>> > Leonardo
>> >
>> > --
>> > Leonardo E. Segovia
>> > https://www.amyspark.me
>>
>>
>>
>> --
>> Wolthera



-- 
Wolthera