From: bugzilla-daemon@libre-soc.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla
Date: Fri, 12 Jun 2020 15:54:42 +0000
Message-ID: <bug-307-13-Twpv6GMLqw@https.bugs.libre-soc.org/> (raw)
In-Reply-To: <bug-307-13@https.bugs.libre-soc.org/>
https://bugs.libre-soc.org/show_bug.cgi?id=307
--- Comment #10 from Cole Poirier <colepoirier@gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #9)
> (In reply to Cole Poirier from comment #8)
> > I like bugzilla and think it's fit for purpose,
>
> i like it other than it's centralised (has no option to store its data in a
> git repository).
Interesting... What is required for such decentralization? In other words why
can't bugzilla be backed by a git data store?
> > but I'd also like to be able to view some of the information on a much more
> > structured (visually) form,
>
> yes me too. i installed graphviz on the server (xdot) so that dependency
> graphs now work.
>
> however a kanban board is much superior.
Saw that, it's cool, but not quite as useful as the board as it does not show
that >300 of the <400 total bugs are assigned to you... among other things :)
> alain sent something a few days ago. he was able to ascertain that apache2
> fastcgi redirection works perfectly, where nginx does not.
>
> rather than waste time working out why i am inclined to recommend a
> deployment where apache2 operates on port 8080 120.0.0.1 and nginx does a
> transparent proxy for bugs.libre-soc.org
Sure, I think apache via nginx is fine. Alain, should the kanban board work
after this is done?
> yes.
>
> example: not having a visual tracker stops people from appreciating that of
> the 370 bugs on here, well over 300 of them are specifically assigned to me.
Indeed. I think we need a space separate from the "libre-riscv website"
bugzilla product do discuss the specifics of these organizational matters. Can
you please create a new component "Libre-SOC Organizational" for "Product:
Libre-SOC's first SoC". Or would it be better to create a new bugzilla
'Product' "Libre-SOC Organization and Planning" like we have "Product
Libre-riscv website"?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
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: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-11 12:28 [libre-riscv-dev] [Bug 307] New: " bugzilla-daemon
2020-05-11 12:28 ` [libre-riscv-dev] [Bug 307] " bugzilla-daemon
2020-05-11 12:43 ` bugzilla-daemon
2020-05-11 17:52 ` bugzilla-daemon
2020-05-12 20:56 ` bugzilla-daemon
2020-05-12 21:58 ` bugzilla-daemon
2020-05-12 22:03 ` bugzilla-daemon
2020-05-21 21:01 ` bugzilla-daemon
2020-05-21 21:12 ` bugzilla-daemon
2020-06-12 15:09 ` bugzilla-daemon
2020-06-12 15:39 ` bugzilla-daemon
2020-06-12 15:54 ` bugzilla-daemon [this message]
2020-06-12 16:37 ` Alain D D Williams
2020-06-12 16:28 ` bugzilla-daemon
2020-06-12 16:41 ` bugzilla-daemon
2020-06-12 16:58 ` bugzilla-daemon
2020-06-12 17:05 ` bugzilla-daemon
2020-06-12 17:15 ` bugzilla-daemon
2020-06-12 17:56 ` bugzilla-daemon
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=bug-307-13-Twpv6GMLqw@https.bugs.libre-soc.org/ \
--to=bugzilla-daemon@libre-soc.org \
--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