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

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

[bugzilla-daemon]

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

            Bug ID: 285
           Summary: bugzilla to be made available "offline"
           Product: Libre-RISC-V Website
           Version: unspecified
          Hardware: PC
                OS: Linux
            Status: CONFIRMED
          Severity: enhancement
          Priority: ---
         Component: website
          Assignee: lkcl@lkcl.net
          Reporter: lkcl@lkcl.net
                CC: libre-riscv-dev@lists.libre-riscv.org
   NLnet milestone: ---

one of the important aspects of this project is it being possible to
replicate (for both offline real-time collaboration as well as legacy
archiving purposes) all resources.

bugzilla is one major piece of critical functionality that is also a
critical online resource.

about the only offline bugtracker that exists (and is any good) is
bugseverywhere.

that's interesting.
https://github.com/kalkin/be/blob/master/interfaces/email/interactive/be-handle-mail

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

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

[bugzilla-daemon]

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

Jacob Lifshay <programmerjake@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |programmerjake@gmail.com

--- Comment #1 from Jacob Lifshay <programmerjake@gmail.com> ---
was going to half jokingly suggest the impractical (and probably insecure)
measure of putting the bugzilla installation in a public git repo --
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 know bugs-everywhere
has a interactive web interface, I just don't know if it properly supports
adding new users, authentication, etc.

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

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

[bugzilla-daemon]

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

--- Comment #2 from Jacob Lifshay <programmerjake@gmail.com> ---
another option is fossil, which is a distributed version control system with a
wiki and bug tracker:
https://www.fossil-scm.org/home/doc/trunk/www/index.wiki

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

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

[bugzilla-daemon]

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

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

[bugzilla-daemon]

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

--- Comment #4 from Luke Kenneth Casson Leighton <lkcl@lkcl.net> ---
(In reply to Jacob Lifshay from comment #2)
> another option is fossil, which is a distributed version control system with
> a wiki and bug tracker:
> https://www.fossil-scm.org/home/doc/trunk/www/index.wiki

sigh i'd really like it... if they hadn't decided to reinvent git.
UNIX philosophy: do one thing, and do it well.  the majority of
other "project management" systems all allow alternative revision
control to be used.  an all-or-nothing approach does not inspire
confidence.

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