Received: by 10.236.178.3 with SMTP id e3mr14728503yhm.3.1338247680190;
        Mon, 28 May 2012 16:28:00 -0700 (PDT)
X-BeenThere: django-users@googlegroups.com
Received: by 10.236.121.148 with SMTP id r20ls4785097yhh.1.gmail; Mon, 28 May
 2012 16:27:28 -0700 (PDT)
Received: by 10.236.156.196 with SMTP id m44mr14666645yhk.9.1338247648896;
        Mon, 28 May 2012 16:27:28 -0700 (PDT)
Received: by 10.236.156.196 with SMTP id m44mr14666644yhk.9.1338247648884;
        Mon, 28 May 2012 16:27:28 -0700 (PDT)
Return-Path: <freakboy3...@gmail.com>
Received: from mail-gh0-f169.google.com (mail-gh0-f169.google.com [209.85.160.169])
        by gmr-mx.google.com with ESMTPS id d5si10508438yhj.7.2012.05.28.16.27.28
        (version=TLSv1/SSLv3 cipher=OTHER);
        Mon, 28 May 2012 16:27:28 -0700 (PDT)
Received-SPF: pass (google.com: domain of freakboy3...@gmail.com designates 209.85.160.169 as permitted sender) client-ip=209.85.160.169;
Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of freakboy3...@gmail.com designates 209.85.160.169 as permitted sender) smtp.mail=freakboy3...@gmail.com; dkim=pass header...@gmail.com
Received: by ghrr18 with SMTP id r18so1994468ghr.14
        for <django-users@googlegroups.com>; Mon, 28 May 2012 16:27:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:sender:in-reply-to:references:date
         :x-google-sender-auth:message-id:subject:from:to:content-type
         :content-transfer-encoding;
        bh=qg3+YFVa9djpwkXFd1Hd/+e/L/ZiEyF5y6ESdcBbIRU=;
        b=r3uRLSnvpvDetO2iHjiv4g8XktC3/pdBg8Uju1ZsUTvXJ2NDr0VPZrroAu3MLUzh14
         CSlVOXQr1i5cuf3EFtqm3/e3k2rcyNTUxHKkL/6ny6CoTMt2N1nLPS4l7+W53U8mRs7X
         kZRz8z9LsOm2aNN+u9XgpodfzwE+Wbn9f3dQv7qa8zexOpjSxZpS2n1WCoRnNRD0q5e6
         BgPruAlCKIN9JsnzDTCViGJFv8y0lZUhN97eo6eM1W8gtbYOSECZY5jc/rqltBs466zV
         hwTfiSd1pf1nuz8GpOm2pgobiWrl6a6vT/KsjihjalnsI6yNqJNOpxOo61k/uoN+fjz4
         TQjQ==
MIME-Version: 1.0
Received: by 10.50.207.36 with SMTP id lt4mr5654324igc.5.1338247648611; Mon,
 28 May 2012 16:27:28 -0700 (PDT)
Sender: freakboy3...@gmail.com
Received: by 10.231.0.75 with HTTP; Mon, 28 May 2012 16:27:28 -0700 (PDT)
In-Reply-To: <0b9d0218-604e-4ea7-9283-395c55eb4cee@googlegroups.com>
References: <0b9d0218-604e-4ea7-9283-395c55eb4cee@googlegroups.com>
Date: Tue, 29 May 2012 07:27:28 +0800
Message-ID: <CAJxq84-tvx3OfG-1GkGhQ2uXSxP+JZ0YWAohYFVrs8Xr+tJ...@mail.gmail.com>
Subject: Re: Taggit fragmentation (open letter)
From: Russell Keith-Magee <russ...@keith-magee.com>
To: django-users@googlegroups.com
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Hi Simon,

On Tue, May 29, 2012 at 1:39 AM, Simon B=E4chler <s...@feinheit.ch> wrote:
> I was just checking on github if there was a new version of django-taggit
> and was quite shocked what I saw. The original repository had not been
> updated for over a year. Yet there are 41 issues and 12 pull requests. Th=
ere
> are 114 forks, 17 of which had commits within the last month.
>
> Shortly, it is a big mess. I'm sure some of the forks have important
> bugfixes while other just add features required for a certain project. Bu=
t
> it is really necessary that either Alex Gaynor or someone else gets that =
app
> back on track.

At this point, I feel it necessary to point out that you've missed one
very important person off the list of people that can help get this
app back on track - YOU.

I'm sure this wasn't your intention, but your message sounds like
you're demanding that someone else volunteer to fix your problems.

If Alex isn't on top of his pull requests, there's a reason. Given
that he's just graduated from college and is starting full time work,
I'm going to guess that it's because he's busy with other projects,
and his personal use case for django-taggit isn't as strong as it once
was. And while that may be very disappointing to you personally, it is
ultimately *your* problem. If you're not happy with django-taggit, I'm
sure Alex will offer you a 100% refund of everything you paid for it.

So - if you're not happy with the state of django-taggit, then it's up
to *you* -- not anybody else -- to fix the problem. Roll up your
sleeves and get involved. Start addressing some of the tickets.
Generate a private branch that merges all the pull requests. You say
the hcarvalhoalves fork is the most maintained? Start submitting pull
requests to them, instead of Alex. If they don't respond, start
publicising your own fork. And when you've put in enough effort to
show that you're serious, consider contacting Alex directly and see if
he's interested in sharing ownership of the project, or passing the
project off to you completely.

This is the beauty of open source. You have all the tools you need to
solve any problem you have. However, you have to get involved.
Standing on the sidelines complaining doesn't get anything done.

Yours,
Russ Magee %-)