Return-path: Envelope-to: publicinbox@libre-riscv.org Delivery-date: Tue, 16 Jun 2020 13:33:13 +0100 Received: from localhost ([::1] helo=libre-riscv.org) by libre-soc.org with esmtp (Exim 4.89) (envelope-from ) id 1jlAm8-0003Jk-Hi; Tue, 16 Jun 2020 13:33:12 +0100 Received: from vps2.stafverhaegen.be ([85.10.201.15]) by libre-soc.org with esmtp (Exim 4.89) (envelope-from ) id 1jlAm7-0003Je-Oi for libre-riscv-dev@lists.libre-riscv.org; Tue, 16 Jun 2020 13:33:11 +0100 Received: from hpdc7800 (hpdc7800 [10.0.0.1]) by vps2.stafverhaegen.be (Postfix) with ESMTP id 176BC11C05AB for ; Tue, 16 Jun 2020 14:33:11 +0200 (CEST) Message-ID: From: Staf Verhaegen To: libre-riscv-dev@lists.libre-riscv.org Date: Tue, 16 Jun 2020 14:33:04 +0200 In-Reply-To: References: <6FD98A7F-B751-48AE-8829-0CBD38F1CFF6@gmail.com> Organization: FibraServi bvba X-Mailer: Evolution 3.28.5 (3.28.5-8.el7) Mime-Version: 1.0 X-Content-Filtered-By: Mailman/MimeDel 2.1.23 Subject: Re: [libre-riscv-dev] Introduction X-BeenThere: libre-riscv-dev@lists.libre-riscv.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Libre-RISCV General Development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Reply-To: Libre-RISCV General Development Content-Type: multipart/mixed; boundary="===============3050155510950342251==" Errors-To: libre-riscv-dev-bounces@lists.libre-riscv.org Sender: "libre-riscv-dev" --===============3050155510950342251== Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-W+lPbr90WU5Q8LoDnHm4" --=-W+lPbr90WU5Q8LoDnHm4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Luke Kenneth Casson Leighton schreef op di 16-06-2020 om 11:59 [+0100]: > On Tue, Jun 16, 2020 at 9:51 AM Staf Verhaegen wrote= : > > Cole Poirier schreef op ma 15-06-2020 om 18:09 [-0700]: > > >=20 > > > Yes that=E2=80=99s precisely what inspired this idea, Luke and I were= talking about Kanban and I started to think of ways we could enhance it to= use all of the data from the bugzilla rest API. > >=20 > > Have you guys validated gitlab ? >=20 > yes we evaluated gitlab. > * from a security perspective it is a nightmare (vast amounts of codeand = involving arbitrary code execution) What security implication are you considering for a fully open source proje= ct ? You could not use the release feature of gitlab for example. > > It seems you guys are trying to reinvent the wheel. gitlab for exampleh= as issue boards, supports check lists in issues etc. >=20 > yes it does. the hassle associated with it unfortunately has alreadyelim= inated it from consideration. Isn't it time to reevaluate if people are planning to implement kanban boar= ds and other things on top of the bugzilla REST API? Developing, maintaining, auditing that code will also have cost implication= s. greets, Staf. --=-W+lPbr90WU5Q8LoDnHm4-- --===============3050155510950342251== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbGlicmUtcmlz Y3YtZGV2IG1haWxpbmcgbGlzdApsaWJyZS1yaXNjdi1kZXZAbGlzdHMubGlicmUtcmlzY3Yub3Jn Cmh0dHA6Ly9saXN0cy5saWJyZS1yaXNjdi5vcmcvbWFpbG1hbi9saXN0aW5mby9saWJyZS1yaXNj di1kZXYK --===============3050155510950342251==--