caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Aleksey Nogin <nogin@cs.caltech.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Using Bugzilla for OCaml - will be willing to host or help setting up.
Date: Mon, 08 Dec 2003 17:57:40 -0800	[thread overview]
Message-ID: <3FD52C14.4090608@cs.caltech.edu> (raw)

About a year ago there already was a discussion on using Bugzilla for 
tracking OCaml issues/patches. In 
http://caml.inria.fr/archives/200211/msg00275.html Xavier Leroy wrote

>> Would there be any way to get Bugzilla installed at Inria?
> 
> Bugzilla has a reputation of being awfully hard to install.

If this is indeed the main reason for not using Bugzilla, I would be 
willing to host OCaml Bugzilla at http://bugzilla.metaprl.org/ and/or 
help with setting up and configuring Bugzilla on another machine, as 
well as help finding a good way to move the current data over.

The reasons I dislike the current setup and would very much prefer to 
see Bugzilla used for OCaml are numerous:
(a) In current setup, there is no reliable way to post a followup on an 
existing issue. Most of the time when I try doing it, a new entry gets 
created.
(b) There is no easy way to attach files (patches/testcases/etc) to 
existing issues. One can only try to add things inline, but even if that 
works (see (a)), it is ugly and hard to manage.
(c) There is no easy "CC" list that one can subscribe to in order to get 
notified when something happens to a particular entry.
(d) The search function is very primitive
(e) As an "outsider", I feel like I am getting very little feedback on 
the things I submit (when they jut sit there and I do not know what is 
going on), Bugzilla's "NEW/ASSIGNED/REOPENED/RESOLVED/etc" bug status 
classification (together with an "assigned to" field!) does not require 
much more from the developers, but (in my experience) gives much better 
feedback to the reporters.
(f) Entries do not have permanent URLs. Every time an entry is 
re-classified (for example, when it is moved out of "incoming"), the URL 
changes. This means that I can not just point people to an entry 
directly, but instead they have to go through several steps to get there.

In short, I feel that having Bugzilla has a potential to enable me to be 
a better contributor to OCaml. Of course, I have no idea whether this is 
something OCaml team needs or wants.

-- 
Aleksey Nogin

Home Page: http://nogin.org/
E-Mail: nogin@cs.caltech.edu (office), aleksey@nogin.org (personal)
Office: Jorgensen 70, tel: (626) 395-2907

-------------------
To unsubscribe, mail caml-list-request@inria.fr Archives: http://caml.inria.fr
Bug reports: http://caml.inria.fr/bin/caml-bugs FAQ: http://caml.inria.fr/FAQ/
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners


             reply	other threads:[~2003-12-09  2:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09  1:57 Aleksey Nogin [this message]
2003-12-09  3:49 ` [Caml-list] Using Bugzilla for OCaml - will be willing to host or help settingup Blair Zajac
2003-12-09  4:27   ` Aleksey Nogin
2003-12-09  7:47 ` [Caml-list] Using Bugzilla for OCaml - will be willing to host or help setting up Sven Luther
2003-12-09  8:35   ` [Caml-list] Re: [OT] Bugzilla Sucks (WAS: Using Bugzilla for OCaml ..) N. Owen Gunden
2003-12-09  9:45     ` Sven Luther
2003-12-09 12:02   ` [Caml-list] Using Bugzilla for OCaml - will be willing to host or help setting up Yaron M. Minsky
2003-12-09 12:21     ` Nuutti Kotivuori
2003-12-09 13:38     ` Sven Luther
2003-12-09 13:52       ` Yaron M. Minsky
2003-12-09 14:18         ` Sven Luther

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=3FD52C14.4090608@cs.caltech.edu \
    --to=nogin@cs.caltech.edu \
    --cc=caml-list@inria.fr \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).