[libre-riscv-dev] [Bug 307] look at installing a kan-ban board on top of bugzilla

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Fri Jun 12 16:54:42 BST 2020


--- Comment #10 from Cole Poirier <colepoirier at 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 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.

More information about the libre-riscv-dev mailing list