Some additional Redmine plug-ins

9 views
Skip to first unread message

James Turnbull

unread,
Jun 1, 2009, 9:37:41 AM6/1/09
to Luke Kanies, puppe...@googlegroups.com
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Luke et al

I came across two plug-ins for Redmine that might interest people:

1. An issue voting plug-in that allows you to vote for issues.
2. A sub-task plug-in that allows you to create sub-tasks for an issue.

If either of these interest anyone let me know and I can install.

Regards

James Turnbull

- --
Author of:
* Pro Linux Systems Administration
(http://www.amazon.com/gp/product/1430219122/)
* Pulling Strings with Puppet
(http://www.amazon.com/gp/product/1590599780/)
* Pro Nagios 2.0
(http://www.amazon.com/gp/product/1590596099/)
* Hardening Linux
(http://www.amazon.com/gp/product/1590594444/)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFKI9ml9hTGvAxC30ARAhtkAJ48D3S/t5GtgVdMDR4Bor0LquiUrACdFbSn
hpdaFEayqlL5N4Hx8GPksGI=
=jnCg
-----END PGP SIGNATURE-----

Sam Rowe

unread,
Jun 1, 2009, 9:49:27 AM6/1/09
to puppe...@googlegroups.com
On Mon, Jun 1, 2009 at 9:37 AM, James Turnbull <ja...@lovedthanlost.net> wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Luke et al
>
> I came across two plug-ins for Redmine that might interest people:
>
> 1.  An issue voting plug-in that allows you to vote for issues.

Bugzilla has voting. I asked a mozilla dev about a bug I'd submitted
that had a ton of votes and he explained to me that the voting system
was "management entertainment."

Would someone with commit access act differently if an issue got more votes?

Luke Kanies

unread,
Jun 1, 2009, 10:33:04 AM6/1/09
to puppe...@googlegroups.com

In general, yes.

And really, in the cases where the community really wanted a feature
that I wasn't willing to implement, I'd be more likely to reject the
ticket rather than not implement it. That is, if I know that the
community really wants it and I don't want it done, then I should have
a good enough reason to just reject it outright rather than passively
refuse to do the ticket.

Obviously I can't make guarantees one way or another, but I've always
maintained that I'm a squeaky wheel developer and I tend to work on
(or toward) the things that get the most attention from the community,
even if it's not obvious.

--
Yesterday upon the stair
I met a man who wasn't there.
He wasn't there again today --
I think he's from the CIA.
---------------------------------------------------------------------
Luke Kanies | http://reductivelabs.com | http://madstop.com

Nigel Kersten

unread,
Jun 1, 2009, 10:51:56 AM6/1/09
to puppe...@googlegroups.com
On Mon, Jun 1, 2009 at 7:33 AM, Luke Kanies <lu...@madstop.com> wrote:

> And really, in the cases where the community really wanted a feature
> that I wasn't willing to implement, I'd be more likely to reject the
> ticket rather than not implement it.  That is, if I know that the
> community really wants it and I don't want it done, then I should have
> a good enough reason to just reject it outright rather than passively
> refuse to do the ticket.
>
> Obviously I can't make guarantees one way or another, but I've always
> maintained that I'm a squeaky wheel developer and I tend to work on
> (or toward) the things that get the most attention from the community,
> even if it's not obvious.

So the primary advantage I see of the voting option is that it widens
the group of people who are expressing interest. Not everyone is
willing to break out of lurker mode on mailing lists, but they will
click a button semi-anonymously to vote for/against a feature.

--
Nigel Kersten
nig...@google.com
System Administrator
Google, Inc.

Luke Kanies

unread,
Jun 1, 2009, 11:04:13 AM6/1/09
to puppe...@googlegroups.com

I think voting has many more advantages than that. I agree that
people don't do much to make their voices heard, and this is
especially true in the sysadmin community -- if I had a hundred bucks
for every time I found someone hacking around some wicked bug rather
than reporting it or trying to fix it, I'd retire.

But it also provides a lot more visibility into what people are
actually using and what's affecting people's lives. Most Puppet users
seem to consider its flaws to just be a fixed landscape that can't
really be changed; giving them a means of voting for the most
important flaws gives us a window into what they're using and what
they care about.

--
Don't tell me how hard you work. Tell me how much you get done.
-- James Ling

Luke Kanies

unread,
Jun 1, 2009, 11:06:41 AM6/1/09
to puppe...@googlegroups.com
On Jun 1, 2009, at 8:37 AM, James Turnbull wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Luke et al
>
> I came across two plug-ins for Redmine that might interest people:
>
> 1. An issue voting plug-in that allows you to vote for issues.
> 2. A sub-task plug-in that allows you to create sub-tasks for an
> issue.
>
> If either of these interest anyone let me know and I can install.

Note sure how useful the subtask plugin is, but it's mostly a question
of implementation. I don't really want to get into building gantt
charts or whatever (although maybe I should), but it might be that
adding a bit more structure would be good.

As already mentioned, I like the voting plugin idea (as I've expressed
before).


--
The truth is that there is nothing noble in being superior to somebody
else. The only real nobility is in being superior to your former self.
-- Whitney Young

James Turnbull

unread,
Jun 1, 2009, 5:14:57 PM6/1/09
to puppe...@googlegroups.com
Luke Kanies wrote:
> On Jun 1, 2009, at 8:37 AM, James Turnbull wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Luke et al
>>
>> I came across two plug-ins for Redmine that might interest people:
>>
>> 1. An issue voting plug-in that allows you to vote for issues.
>> 2. A sub-task plug-in that allows you to create sub-tasks for an
>> issue.
>>
>> If either of these interest anyone let me know and I can install.
>
> Note sure how useful the subtask plugin is, but it's mostly a question
> of implementation. I don't really want to get into building gantt
> charts or whatever (although maybe I should), but it might be that
> adding a bit more structure would be good.
>
> As already mentioned, I like the voting plugin idea (as I've expressed
> before).
>
>

I'll have a bit more of a play with the sub-task one.

The voting plug-in, however, is installed. It's very simple:

1. Each issue has a green and a red arrow - use logically.
2. You can only vote for an issue once.
3. You can see the tally in the Issues tab. Click on the Votes column
to sort by it.

You can currently vote for closed/rejected/etc issues - I've made a note
to patch that at some point.

Luke - happy for you to announce on the -user list - suspect people read
your emails more than mine... :) Or I can. Not fussed.

Regards

James Turnbull

signature.asc

Luke Kanies

unread,
Jun 1, 2009, 5:51:41 PM6/1/09
to puppe...@googlegroups.com

Cool. Weird that you can't query or select based on votes, but having
it sortable by tally is sufficient.

>
> Luke - happy for you to announce on the -user list - suspect people
> read
> your emails more than mine... :) Or I can. Not fussed.

Sure, I'll announce.

How should it get documented?

--
Health is merely the slowest possible rate at which one can die.

Reply all
Reply to author
Forward
0 new messages