Re: Telcon action: Task management proposal

Thanks for looking into this, Garbee (and for setting up a demo version,
Frozenice)!

Let's plan to talk about this in the call tomorrow, if you're able.
Switching bug tracking systems is a big decision and there are a lot of
aspects to consider.

What's your thinking around what types of things we'd track in buggenie? In
a world where we used this system, what would we use Flags/Editorial
Notes/Comments for ("nothing" is a reasonable answer)?

On Sat, Nov 3, 2012 at 4:10 PM, frozenice <frozenice@frozenice.de> wrote:

> To take a closer look, I created a test install (no demo reset timer!).
>
> URL: http://webplatform.frozenice.**de/bugs/thebuggenie/<http://webplatform.frozenice.de/bugs/thebuggenie/>
>
> Logins are:
> admin / testing
> user / testing
>
> Notes: SSO seems possible to include, uploads can be enabled/disabled,
> data can be imported (CSV), multiple projects / single project, fine
> grained permissions, seems to use %2f in some URLs (project permission
> AJAX) -> maybe AllowEncodedSlashes On necessary, odd directory setup, issue
> types / fields customizable, custom workflows seem nice and complex (has
> custom flows, including linking back to earlier steps as it seems),
> included wiki can be disabled (at least the links), has components (even
> editions, but we don't need those I guess), VCS integration possible
> (commit messages update bugs, github supported)
>
>
>
> On 03.11.2012 02:41, Jonathan Garbee wrote:
>
>> tl;dr:
>>
>> Bug Genie [1] is what we should use for task and bug tracking.  Any
>> objections?
>>
>> Long version:
>>
>> So, I tested a handful of software today that we could use to track tasks
>> and manage bugs along with any other possible Project Management things we
>> could need.  I'm very happy to
>> say, I have found one awesome solution for us.  That solution is Bug
>> Genie [1].
>>
>>   We can use it for:
>>   * Bug Tracking
>>   * Tracking major content edits/additions.
>>   * Tracking actions produced through telcons (perhaps even the telcon
>> discussion points themselves).
>>   * Perhaps more if anything else comes up that we need to track.
>>
>>   Pros:
>>   * Super granular ACL (Access Control Lists).
>>   * Decent UI by default.
>>   * Very customizable.
>>   * OpenID support.
>>
>>   Cons:
>>   * Pretty intricate setup.
>>   * Lots of features that aren't too useful to us since we aren't
>> developing software.
>>   * UX is tricky at first to figure out (I will try to help by creating
>> exact guides to help with tasks being done in the tracker).
>>   * Wiki "module" that is required.  So there is wasted links around
>> going into the Wiki that aren't needed.
>>
>> We can use the software to track just about anything we want to do. I am
>> confident that by hosting this we can streamline all suggestions, bugs,
>> requests, and tasks into one
>> unified area. Keeping things very centralized, easy to administrate, and
>> super simple to keep track of things.
>>
>> It would remove the use/need of discussion pages, comments, and these
>> random pages that we have scattered about for tracking tasks along with the
>> bugtracker hosted by W3.
>>
>>   I am going to setup a test install on a public server early next week
>> and import most of the bugs from one or two sections of the current tracker
>> as example data.  This way
>> everyone can try it out and see if it is worth pursuing to use.  I really
>> think that we can use it for full project management for WPD and centralize
>> a lot of information that is
>> currently spread out among duplicated areas.
>>
>>   If anyone has any questions about the software, or how exactly I think
>> we would be using it, please ask.  I really think this is the best solution
>> for us that fits the Open
>> Source requirement.  If you also know of something you think would be
>> better, please let me know so I can review it.
>>
>> Thanks,
>>   -Garbee
>>
>>   [1] http://www.thebuggenie.com/
>>
>>
>>
>