29/02a56192277e3128b6bca06dd76c2c68a4a765

   1 Return-path: <libre-riscv-dev-bounces@lists.libre-riscv.org>
   2 Envelope-to: publicinbox@libre-riscv.org
   3 Delivery-date: Tue, 16 Jun 2020 13:33:13 +0100
   4 Received: from localhost ([::1] helo=libre-riscv.org)
   5         by libre-soc.org with esmtp (Exim 4.89)
   6         (envelope-from <libre-riscv-dev-bounces@lists.libre-riscv.org>)
   7         id 1jlAm8-0003Jk-Hi; Tue, 16 Jun 2020 13:33:12 +0100
   8 Received: from vps2.stafverhaegen.be ([85.10.201.15])
   9  by libre-soc.org with esmtp (Exim 4.89)
  10  (envelope-from <staf@fibraservi.eu>) id 1jlAm7-0003Je-Oi
  11  for libre-riscv-dev@lists.libre-riscv.org; Tue, 16 Jun 2020 13:33:11 +0100
  12 Received: from hpdc7800 (hpdc7800 [10.0.0.1])
  13  by vps2.stafverhaegen.be (Postfix) with ESMTP id 176BC11C05AB
  14  for <libre-riscv-dev@lists.libre-riscv.org>;
  15  Tue, 16 Jun 2020 14:33:11 +0200 (CEST)
  16 Message-ID: <f248aa42dfb0d4be598e3253eaf8c8ae6f98b59b.camel@fibraservi.eu>
  17 From: Staf Verhaegen <staf@fibraservi.eu>
  18 To: libre-riscv-dev@lists.libre-riscv.org
  19 Date: Tue, 16 Jun 2020 14:33:04 +0200
  20 In-Reply-To: <CAPweEDws6xaaAEMQGbQJmcM7obGfKrvREmyu7mqP96SWXaR9rg@mail.gmail.com>
  21 References: <CAC2bXD7coX-Y7fo=BDQ+_Ju3gsZqyJY3w1KS3SLy+UNE9o6Z9Q@mail.gmail.com>
  22  <6FD98A7F-B751-48AE-8829-0CBD38F1CFF6@gmail.com>
  23  <e4436780b9c80da269ddc9cc66ad8cb709d31183.camel@fibraservi.eu>
  24  <CAPweEDws6xaaAEMQGbQJmcM7obGfKrvREmyu7mqP96SWXaR9rg@mail.gmail.com>
  25 Organization: FibraServi bvba
  26 X-Mailer: Evolution 3.28.5 (3.28.5-8.el7)
  27 Mime-Version: 1.0
  28 X-Content-Filtered-By: Mailman/MimeDel 2.1.23
  29 Subject: Re: [libre-riscv-dev] Introduction
  30 X-BeenThere: libre-riscv-dev@lists.libre-riscv.org
  31 X-Mailman-Version: 2.1.23
  32 Precedence: list
  33 List-Id: Libre-RISCV General Development
  34  <libre-riscv-dev.lists.libre-riscv.org>
  35 List-Unsubscribe: <http://lists.libre-riscv.org/mailman/options/libre-riscv-dev>,
  36  <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=unsubscribe>
  37 List-Archive: <http://lists.libre-riscv.org/pipermail/libre-riscv-dev/>
  38 List-Post: <mailto:libre-riscv-dev@lists.libre-riscv.org>
  39 List-Help: <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=help>
  40 List-Subscribe: <http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev>,
  41  <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=subscribe>
  42 Reply-To: Libre-RISCV General Development
  43  <libre-riscv-dev@lists.libre-riscv.org>
  44 Content-Type: multipart/mixed; boundary="===============3050155510950342251=="
  45 Errors-To: libre-riscv-dev-bounces@lists.libre-riscv.org
  46 Sender: "libre-riscv-dev" <libre-riscv-dev-bounces@lists.libre-riscv.org>
  47
  48
  49 --===============3050155510950342251==
  50 Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
  51         boundary="=-W+lPbr90WU5Q8LoDnHm4"
  52
  53
  54 --=-W+lPbr90WU5Q8LoDnHm4
  55 Content-Type: text/plain; charset="UTF-8"
  56 Content-Transfer-Encoding: quoted-printable
  57
  58 Luke Kenneth Casson Leighton schreef op di 16-06-2020 om 11:59 [+0100]:
  59 > On Tue, Jun 16, 2020 at 9:51 AM Staf Verhaegen <staf@fibraservi.eu> wrote=
  60 :
  61 > > Cole Poirier schreef op ma 15-06-2020 om 18:09 [-0700]:
  62 > > >=20
  63 > > > Yes that=E2=80=99s precisely what inspired this idea, Luke and I were=
  64  talking about Kanban and I started to think of ways we could enhance it to=
  65  use all of the data from the bugzilla rest API.
  66 > >=20
  67 > > Have you guys validated gitlab ?
  68 >=20
  69 > yes we evaluated gitlab.
  70 > * from a security perspective it is a nightmare (vast amounts of codeand =
  71 involving arbitrary code execution)
  72
  73 What security implication are you considering for a fully open source proje=
  74 ct ?
  75 You could not use the release feature of gitlab for example.
  76
  77 > > It seems you guys are trying to reinvent the wheel. gitlab for exampleh=
  78 as issue boards, supports check lists in issues etc.
  79 >=20
  80 > yes it does.  the hassle associated with it unfortunately has alreadyelim=
  81 inated it from consideration.
  82
  83 Isn't it time to reevaluate if people are planning to implement kanban boar=
  84 ds and other things on top of the bugzilla REST API?
  85 Developing, maintaining, auditing that code will also have cost implication=
  86 s.
  87
  88 greets,
  89 Staf.
  90
  91
  92 --=-W+lPbr90WU5Q8LoDnHm4--
  93
  94
  95
  96 --===============3050155510950342251==
  97 Content-Type: text/plain; charset="utf-8"
  98 MIME-Version: 1.0
  99 Content-Transfer-Encoding: base64
 100 Content-Disposition: inline
 101
 102 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbGlicmUtcmlz
 103 Y3YtZGV2IG1haWxpbmcgbGlzdApsaWJyZS1yaXNjdi1kZXZAbGlzdHMubGlicmUtcmlzY3Yub3Jn
 104 Cmh0dHA6Ly9saXN0cy5saWJyZS1yaXNjdi5vcmcvbWFpbG1hbi9saXN0aW5mby9saWJyZS1yaXNj
 105 di1kZXYK
 106
 107 --===============3050155510950342251==--
 108
 109
 110