[libre-riscv-dev] [Bug 285] bugzilla to be made available "offline"

[bugzilla-daemon@libre-soc.org]

https://bugs.libre-soc.org/show_bug.cgi?id=285

--- Comment #3 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #1)
> was going to half jokingly suggest the impractical (and probably insecure)
> measure of putting the bugzilla installation in a public git repo --

sigh it'd involve dumping - then purging - parts of the bugzilla postgresql
dump.  bleh :)

> bugs-everywhere looks much better, though I'd be concerned that we need a
> working, secure, public https interface for those who don't want to install
> bugs-everywhere locally and figure out how to use it.

i'd want it anyway.

> I know bugs-everywhere has a interactive web interface, 

yes.  it's... "functional".

> I just don't know if it properly supports
> adding new users, authentication, etc.

wark-wark :)  not at all.  i believe it's there for "convenience", for
when you're running locally, and want to browse bugs, comment on them etc.
locally then "git push" out to merge with other users.

https://github.com/cherrypy/tools/blob/master/AuthenticationAndAccessRestrictions
or this
https://github.com/cherrypy/tools/blob/master/CASAuthentication

funfunfun...

sigh i kinda promised myself i wouldn't mess about with web frameworks any
more :)  however if my arm was sufficiently twisted i could likely throw
something together that's suitable for public use, maybe even (gosh)
using the bugzilla postgres user/pass to do it (!)

hm i wonder if we can justify putting in an NLNet Grant request specifically
for things like this, on the basis that, really, we do need full independence.
we could then find - and pay - someone to do these kinds of things.

-- 
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