kicad-developers team mailing list archive
Mailing list archive
Re: ideas to improve patch and CI integration
Maciej Sumiński <maciej.suminski@xxxxxxx>
Mon, 22 Oct 2018 11:59:19 +0200
spf=pass (sender IP is 184.108.40.206) smtp.mailfrom=cern.ch; lists.launchpad.net; dkim=none (message not signed) header.d=none;lists.launchpad.net; dmarc=bestguesspass action=none header.from=cern.ch;
addr=maciej.suminski@xxxxxxx; prefer-encrypt=mutual; keydata= xsBNBFKfmAwBCAC9tak+4mDO1WiNnAwegusPBMEdl+sV35XeaU4PGSt33mPSlXB2klamg4ih QUykvuWqNEg2KyTvCSKNfnHTpzeeFegEsIwWFdhbIc4uUAD6CHl4+uGTXQiMh1+IJkgLmwuD RCEx9mSKbdzzTKz05w+fzzT3mNfko8NICWlcmhFgo2RXnQRTqFg7CNNBpx4kr4+AWIvb+Rha AVMLVJj1s05+STGyFucu6sZmTmOC53ZtkV8HchJeGuQL0LPkjvX0VKGE3gkvuP4iLBcgFtNC Kcu/L6FmWd24m2IhWaHXoWLBiVFw7gGzUdB7gSAiNO1+SoWX+99rbud7RvqV49vOgoqbABEB AAHNKU1hY2llaiBTdW1pbnNraSA8bWFjaWVqLnN1bWluc2tpQGNlcm4uY2g+wsB5BBMBAgAj BQJSn5gMAhsDBwsJCAcDAgEGFQgCCQoLBBYCAwECHgECF4AACgkQFHAa7WGlsnU/JQf5AYW0 oFH+jOykZvlRkRZMoqw1vZGOHeRPK92vbjeiau/hALYX1FBvZMx+JMmVHN7DkRIY7bVoiJ6N n4Byn//BSd9F9eXjAphYVuBg2Xe5wp3/l9/z2Iw8KeLpfKAtfIybgpycvTuUxFIxm9mtpPt+ AoNFKBDhfLcpZLJTW7AwwpnzP+GDdjszjnW6rMt8Aq55liR+y/TZfz/tTEDcUcSPLlJBTmda TmkO5aPxPmeCeDMOT3YEd+bK57V5b7RgtqTdIT6CW7tjQKBPJbIGa8PQ0tUfz0yCBEPWghnY w+B/2JeArrRXDui78cGgTDy1ocQNAm3havk2WO2qykxziY6Owc7ATQRSn5gMAQgAxw+MRllT IPNnCeOAbRgX1KRzo7+7WpSIbmhrBzLY0O1SyIa7U05E6+4jDHDfDpSLqc61an1+M69e6l9Z E3ve3hymtj5ucXZQnveQ5klD6z5FBC/04of/YyrS+h6iRSM0nOmu1JOIqM0S2OzwsKRsS86r jCtRE5OxoBDCIB4xNPitezs4uvLoVfO3mVYUhiPRZMtTCInEi+tlM+AmaPjRkPAfhd0wsOjk oxkuJWEnZ8U8oHpeL0uqANZgLlIiT5yJMWsyyqlK01hdFbuIydIFFiyXJw1HDTXWX+tMxJrX VEvQJZALof9RU/jntqGltnQXArUgPMSGGu1f+7AH/CuMyQARAQABwsBfBBgBAgAJBQJSn5gM AhsMAAoJEBRwGu1hpbJ1maAH/RZPbvXaNIOouHZlnlkq/WORHxjkKfve+AbE62Ed8yFIwlAj tyZGKeEG9hDJl6f9BxDv+9qunTfWfXQuHxNIpdXstkxQIx4m043Kx3h7VdEmg53ybeGNgpvz BYk5HdgCH3yP6UbGNiel6xZOywmvpru3pEKNg4mJhzxm9JCG+djrvbRh+BZNOkDBgaSiCAuJ q6Ffo9Qk/qfl6Uim9G7GKSS4930ZQ2GoVObe+jXixOhWXFSDhGKX5meABmELJ9XTcW3Pp6XC 0KXOE2p0EHQPmFvXdU6OePI72jTgRzPJXRXbPkL0/NUfbZfxS/xnAG8jmODc2ufbtrvE2jPu INX35u4=
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.0
I like Gitlab, but it is a matter of taste and obviously the final word
belongs to Wayne. I think the main problem would be to transfer the bug
tracker and decide what to do regarding the mailing list.
Another point is a plan for a case when Gitlab turns evil. Currently
they offer Gold version to open source projects for free , but you
never know what will happen in a few years. Either we pay or host a
limited version (Community Edition) privately. I realize the same thing
may happen with Launchpad, the point is to decide whether we would be
satisfied with Gitlab Community Edition features.
You may also find insightful a discussion we head about moving KiCad
from Bazaar to Git .
On 10/21/18 7:11 PM, Thomas Pointhuber wrote:
> I think this topic will have many different point of views, but I think
> it is important to discuss it anyway.
> I'm now about 5 years on the project, started as library maintainer and
> now sometimes with code contributions as well. I experienced at least a
> few different types of how software projects can be design of a
> management perspective to get work done.
> Currently, there is the time where many big organizations (GNOME and
> freedesktop.org for example) moved their development to custom GitLab
> instances. And I would like to propose to think about that for KiCad as
> well. Not because everyone does it, but because it would benefit the
> project itself. There are various reasons I can think of right now:
> * patches are sometimes simply forgotten on the mailing list
> * it is pretty hard to find old patches on the mailing list unless you
> have the e-mails stored on your account. You cannot search on launchpad
> * CI integration of patches is missing. People need to run them explicit
> before merging, or the automated build will fail at some point
> * getting CI runs for various systems requires explicit request due to
> missing automatization
> * no automated linter checks (would require us to reformat the project)
> * it's hard to track changes of patches, especially when modified,
> * way better possibilities to view/edit/show history online
> * review tools on Launchpad are cumbersome and rarely used. This should
> be the standard in point of fact.
> * easier to handle a proper review than with e-mail
> * easier to keep track how discussions evolved
> * the project is currently split between Launchpad and GitHub, this
> would allow us to combine all parts on one platform
> * GitLab would theoretically allow us add custom differs for library review
> * new contributors likely know GitHub/Gitlab workflow and can join more
> I know this is quite some heavy proposal due to change of workflow and
> bug-migration. Nevertheless, we should at least discuss it.
> PS: A college built a working GitLab CI script with export of build
> artifacts. GitLab integration of Jenkins would be possible as well.
Description: OpenPGP digital signature