[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Social-mediagoblin] floating ideas of infrastructure

From: will kahn-greene
Subject: [Social-mediagoblin] floating ideas of infrastructure
Date: Mon, 30 May 2011 19:40:02 -0400
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv: Gecko/20110424 Thunderbird/3.1.10

At some point in the next month or two, I want to solve a few
infrastructure issues.

For each of these issues, it's likely we won't get a consensus for a
solution, so mostly I'm floating these ideas to get more feedback in
case there are pros and cons I'm not aware of and also other solutions
I'm not aware of.

Problem 1: we need a useful wiki

We need a wiki for documentation that doesn't quite fit on the web-site
because it really helps to have it updated by a large community of
people and documentation that doesn't quite fit in the docs/ directory
of the repository because it helps to have it updated by a large
community of people and it's not necessarily related to versions of
MediaGoblin.  I also don't feel like dealing with wiki spam.

Whatever we choose has to have the following properties:

1. easy to use for contributors

2. minimized spam

3. minimized administration (if I'm administrating, then this is very
related to my skill set and experience)

Redmine and gitorious both have wikis, but they both suck in different ways.

At PCF, we're using MediaWiki and a plugin Asheesh and I wrote that
allows contributors to drop in and contribute things without a lot of
hassle while still reducing the various vectors of spam.

I'm loathe to use a hosted wiki solution.

I really like the MediaWiki setup we have at PCF, so I'm proposing we
switch to that.

Problem 2: issue tracker

We need an issue tracker that has the following properties:

1. easy to use for contributors

2. minimized spam

3. minimized administration

4. maximized usefulness in terms of slicing the bug data to be able to
see where we're at, what's going on, and what's happened recently

At PCF we use Bugzilla.  I like it, but I think it fails item 1 and
given that MediaGoblin is geared towards artsy people, I think that's a
bad idea.

I've used Trac and don't like it because the resulting bug data sucks
unless someone is actively triaging and massaging the bug data.  That's
a lot of work to deal with warts for a bug system.

I don't particularly like Redmine.  It has a pretty interface and it
seems easy to use, but the search facilities totally suck, it doesn't
look like it'll scale well to groups much larger than ours, and I don't
like the permission/group system.  I do like that you can edit the
title/description after submitting the bug and the roadmap/milestone
bits are ok.

I'm using Roundup for PyBlosxom now with some changes I got from
OpenHatch.  There are some things I like (search is way better, it's
very configurable/modifyable, it's written in Python which makes it
easier for me to configure/modify, you can edit titles, ...) and things
I don't (the urls for views/searches are so unbelievably awful, it's not
easy to set up, it's not pretty, ...)

I'm on the fence about this.  I've never really liked any of the bug
trackers I've seen.  Part of me thinks that since I'm using Roundup for
PyBlosxom and Asheesh uses it at OpenHatch that it's more likely between
the three projects we can eventually get a Roundup setup that's useful.
 The other part of me thinks that setting up Bugzilla like we're using
at PCF might be ok, too.

What are other people thinking about wikis and bug trackers?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]