caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Blair Zajac <blair@orcaware.com>
To: Aleksey Nogin <nogin@cs.caltech.edu>
Cc: caml-list@inria.fr
Subject: Re: [Caml-list] Using Bugzilla for OCaml - will be willing to host or  help settingup.
Date: Mon, 08 Dec 2003 19:49:27 -0800	[thread overview]
Message-ID: <3FD54647.BCA9E2E9@orcaware.com> (raw)
In-Reply-To: <3FD52C14.4090608@cs.caltech.edu>

Aleksey Nogin wrote:
> 
> 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.

Well, as the author of referenced link, I'm all for this :)  Must
be the Caltech background (I'm an alum).

However, some questions that I think may be relavent this being
used as a core Ocaml development tool.

How many people would manage this system?
Would it be just you?
What happens if you get tired of managing the bugzilla system?

For this to be considered, I think there'd have to be a way of
showing the longevity of the bugzilla repository.  No point of
putting effort into a bug repository to see it disappear later.

Which leads me to this thought:

It may be good to have a team of people that could manage this box.

There are a number of people setting up different resources on
the Internet for Ocaml (me for Mailman for ocaml-pxp and ocaml-i18n,
Gerd for Godi).  Most of the time its a single developer.  If
something happens to that person (loss of interest, lack of time,
etc), then the resource becomes stagnant, is hard to move to a new
site.

It would be good if there were some "community" ocaml boxes on the
internet that a team of people would administer for the good of the
community.  These boxes could hold mailing lists, bugzilla, be a
COAN (ala CPAN) repository, etc.

Management of the box could be done initially by people with
demonstrated experience, and then a voting method where good
work gets additional access to the repository.  This is similar to
the method where by new developers to open source projects get
commit access as their patches demonstrate good work and forward
the project.

The only thing we would need is some contributed hardware and
bandwidth, which sounds perfect for an educational institution :)

Best,
Blair

-- 
Blair Zajac <blair@orcaware.com>
Plots of your system's performance - http://www.orcaware.com/orca/

-------------------
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  3:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-09  1:57 [Caml-list] Using Bugzilla for OCaml - will be willing to host or help setting up Aleksey Nogin
2003-12-09  3:49 ` Blair Zajac [this message]
2003-12-09  4:27   ` [Caml-list] Using Bugzilla for OCaml - will be willing to host or help settingup 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=3FD54647.BCA9E2E9@orcaware.com \
    --to=blair@orcaware.com \
    --cc=caml-list@inria.fr \
    --cc=nogin@cs.caltech.edu \
    /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).