From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Libre-RISCV General Development <libre-riscv-dev@lists.libre-riscv.org>
Subject: Re: [libre-riscv-dev] Broken build notification from debian salsa
Date: Tue, 7 Apr 2020 16:00:06 +0100
Message-ID: <CAPweEDzD3y7YXGu=L5B4Voi0WXaYFy2CctzzgpJtugyULHaJmA@mail.gmail.com> (raw)
In-Reply-To: <CAC2bXD6wXSz+NWMwOhgxosKnLtTMJXzCNt9NY-qe1X80gCLVqg@mail.gmail.com>
---
crowd-funded eco-conscious hardware: https://www.crowdsupply.com/eoma68
On Tue, Apr 7, 2020 at 3:37 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
>
> Checking to see if you saw this Luke:
> https://salsa.debian.org/Kazan-team/soc/-/jobs/652909
no, i don't see anything from that because it's not sent to a public
mailing list / resource.
> If you don't have email notifications enabled, you probably should.
the implications of relying on and reacting to something that's sent
via a *private message* - even one that comes from an automated system
- are that we are "hiding something".
that seriously violates the goals of the project and undermines the
basis of the funding that we receive from NLNet.
although it's fantastic that you've done them, none of the rest of the
team have any idea why those bugs were fixed in the unit tests, except
when reviewing the "final result" - the commit.
this is a huge alarm-bell.
> We
> should probably figure out how to get salsa build failures sent to the
> mailing list as well,
build failures, job runs - everything.
this is important, jacob.
i didn't realise what was going to be involved in the deployment of
CI, otherwise i would have raised it as a proper discussion for
evaluation, long before the time and effort was spent on getting it
set up.
including properly evaluating alternatives, and how to ensure that
everything is archived and transparent.
l.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-07 14:37 Jacob Lifshay
2020-04-07 15:00 ` Luke Kenneth Casson Leighton [this message]
2020-04-07 15:13 ` Jacob Lifshay
2020-04-07 15:47 ` Luke Kenneth Casson Leighton
2020-04-07 15:52 ` Luke Kenneth Casson Leighton
2020-04-07 16:00 ` Jacob Lifshay
2020-04-07 16:41 ` Jacob Lifshay
2020-04-07 16:52 ` Luke Kenneth Casson Leighton
2020-04-08 15:42 ` [libre-riscv-dev] GitLab CI Archiver Jacob Lifshay
2020-04-08 16:15 ` Luke Kenneth Casson Leighton
2020-04-09 20:25 ` Jacob Lifshay
2020-04-07 15:03 ` [libre-riscv-dev] Broken build notification from debian salsa Immanuel, Yehowshua U
2020-04-07 15:10 ` Luke Kenneth Casson Leighton
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPweEDzD3y7YXGu=L5B4Voi0WXaYFy2CctzzgpJtugyULHaJmA@mail.gmail.com' \
--to=lkcl@lkcl.net \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git