From: Staf Verhaegen <staf@fibraservi.eu>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: Re: [libre-riscv-dev] Introduction
Date: Tue, 16 Jun 2020 14:33:04 +0200
Message-ID: <f248aa42dfb0d4be598e3253eaf8c8ae6f98b59b.camel@fibraservi.eu> (raw)
In-Reply-To: <CAPweEDws6xaaAEMQGbQJmcM7obGfKrvREmyu7mqP96SWXaR9rg@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1218 bytes --]
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 <staf@fibraservi.eu> wrote:
> > Cole Poirier schreef op ma 15-06-2020 om 18:09 [-0700]:
> > >
> > > Yes that’s 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.
> >
> > Have you guys validated gitlab ?
>
> 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 project ?
You could not use the release feature of gitlab for example.
> > It seems you guys are trying to reinvent the wheel. gitlab for examplehas issue boards, supports check lists in issues etc.
>
> yes it does. the hassle associated with it unfortunately has alreadyeliminated it from consideration.
Isn't it time to reevaluate if people are planning to implement kanban boards and other things on top of the bugzilla REST API?
Developing, maintaining, auditing that code will also have cost implications.
greets,
Staf.
[-- Attachment #2: Type: text/plain, Size: 177 bytes --]
_______________________________________________
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: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:06 Anais Poirier
2020-06-15 20:16 ` Yehowshua
2020-06-15 20:27 ` Luke Kenneth Casson Leighton
2020-06-15 20:27 ` Yehowshua
2020-06-15 20:49 ` Luke Kenneth Casson Leighton
2020-06-15 20:55 ` Cole Poirier
2020-06-15 21:04 ` Luke Kenneth Casson Leighton
2020-06-15 21:08 ` Yehowshua
2020-06-15 21:13 ` Yehowshua
2020-06-15 21:16 ` Luke Kenneth Casson Leighton
2020-06-15 21:13 ` Luke Kenneth Casson Leighton
2020-06-15 22:20 ` [libre-riscv-dev] using debian on a mac Jacob Lifshay
2020-06-16 0:01 ` Luke Kenneth Casson Leighton
2020-06-15 20:58 ` [libre-riscv-dev] Introduction Yehowshua
2020-06-15 21:15 ` Hendrik Boom
2020-06-15 21:17 ` Luke Kenneth Casson Leighton
2020-06-15 22:51 ` Jacob Lifshay
2020-06-15 23:59 ` Luke Kenneth Casson Leighton
2020-06-16 1:09 ` Cole Poirier
2020-06-16 3:03 ` Jacob Lifshay
2020-06-16 3:30 ` Cole Poirier
2020-06-16 8:50 ` Staf Verhaegen
2020-06-16 10:59 ` Luke Kenneth Casson Leighton
2020-06-16 12:33 ` Staf Verhaegen [this message]
2020-06-16 13:13 ` Luke Kenneth Casson Leighton
2020-06-16 18:29 ` Cole Poirier
2020-06-17 6:17 ` Lauri Kasanen
2020-06-17 16:14 ` Cole Poirier
2020-06-16 12:42 ` Staf Verhaegen
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=f248aa42dfb0d4be598e3253eaf8c8ae6f98b59b.camel@fibraservi.eu \
--to=staf@fibraservi.eu \
--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