[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-kimageshop
Subject: Re: Moving to gitlab, which features to use.
From: "L. E. Segovia" <lsg () amyspark ! me>
Date: 2019-04-15 13:42:42
Message-ID: 00480a25-b963-9c0d-47d6-53b9623bfde3 () amyspark ! me
[Download RAW message or body]
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.)
* Not workflow-related, but some serious CI integration would be helpful
to let them know if their patch is acceptable.
* 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 .
Another question-- can we keep using tasks? I found them particularly
useful to review ideas without involving code.
Best regards,
Leonardo
--
Leonardo E. Segovia
https://www.amyspark.me
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic