1 On Thursday 25 June 2009 16:23:04 Steve Losh wrote:
2 > On Jun 25, 2009, at 10:02 AM, Chris Ball <cjb@laptop.org> wrote:
3 > >> Oh, and obviously there must still be bugs in BE. Please submit
6 > > Perhaps it's a good time to merge Steve Losh's CherryPy web interface?
8 > > http://void.printf.net/pipermail/be-devel/2009-February/000095.html
9 > > http://bitbucket.org/sjl/cherryflavoredbugseverywhere/
11 > Hey, I haven't touched the web interface in a while, but I should have
12 > some time to fix some stuff up tonight and tomorrow. Hold off on
13 > merging it in until then.
15 > I'm still curious as to what people think the role of a web interface
16 > like this should be. When I wrote it I meant it as a single-user
17 > interface like the command line one. It could definitely work as a
18 > public, read-only interface too.
20 I'd really like to have some sort of web interface for BE, also in read-only
23 I am thinking to write (actually I wrote some test code) a tool to parse a BE
24 repository to output a set of static html pages to put online, like the "ditz
25 html" command, but this was before I start to play with BE sourcecode, so now
26 I ma thinking to implement it as a BE command.
28 > If the goal is to allow more than one person to add issues, how should
29 > commits go? One commit per change? Commit every X minutes if necessary?
31 I think that a simple web interface should be read-only.
33 Eventually, to allow to add issues also from the web interface, it should be
34 done to a specific branch, one commit per change.
40 _______________________________________________
42 Be-devel@bugseverywhere.org
43 http://void.printf.net/cgi-bin/mailman/listinfo/be-devel