Re: issue tracking reorganisation proposal

On Wed, Feb 15, 2012 at 10:37 AM, Adriaan Moors <adriaan.moors@epfl.ch> wrote:

i don't mean to set the tipping point towards getting you a fresh well too high (just slightly above ground level),but let's see what we can do with some minimal, well-aimed, purification efforts first

I'll go along with this if we can agree that the lion's share of the effort should be put into purifying the data, not jira itself.   Fixing the data we have to do anyway, and I will reap immediate benefits.  "Fixing" jira only invests us further, and the last thing I need is for the sunk cost fallacy to sing any louder.

By the way, whatever tool is being looked at, first check if there's a
hook listed for it on github admin page.

On Thu, Feb 16, 2012 at 17:11, Daniel Sobral wrote:
> On Thu, Feb 16, 2012 at 16:09, Adriaan Moors wrote:
>> that looks pretty awesome! firsthand experiences, anyone? --a
>
> As a user, it never bothered me. The puppet stuff I use/contribute to
> use it, but that's very light. Also, I have no idea how it would
> behave when multiple people must have access to it, and I haven't
> looked into whatever tooling/API it might have. I'd be surprised if it
> didn't come down to git-based text files, however, which would be very
> amenable to scripting.
>
>>
>>
>> On Thu, Feb 16, 2012 at 6:56 PM, Erik Bruchez wrote:
>>>
>>> Then what about the github tracker? Simple, to the point, and Scala is
>>> already on github.
>>>
>>> See:
>>> https://github.com/blog/831-issues-2-0-the-next-generation
>>>
>>> API:
>>> http://develop.github.com/p/issues.html
>>>
>>> -Erik
>>>
>>> 2012/2/15 √iktor Ҡlang :
>>> > TBH,
>>> >
>>> > An issue tracker should have the following properties:
>>> >
>>> > 1) No "workflow" crap
>>> > 2) Be able to show code and stack traces in a non-disruptive way
>>> > 3) Have a REST API for creating and updating tickets
>>> > 4) Arbitrary tagging of tickets
>>> > 5) Absolute ordering of tickets, no "priority" BS
>>> > 6) Should support discussions regarding the ticket
>>> > 7) Have great search/filtering capabilities
>>> >
>>> > Almost everything else just complicates and makes working with the issue
>>> > tracker a painful exercise.
>>> >
>>> > An issue tracker should be a tool that helps in documenting the past,
>>> > illustrating the current and aids in planning the future of some
>>> > software
>>> > project. That means low overhead, no handwaving and no fluff.
>>> >
>>> > Cheers,
>>> > √
>>> >
>>> >
>>> > On Wed, Feb 15, 2012 at 8:58 PM, Alex Cruise wrote:
>>> >>
>>> >> Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to
>>> >> donate a license, then I saw
>>> >> this: http://www.jetbrains.com/youtrack/buy/buy.jsp:
>>> >>
>>> >>>
>>> >>> OS-Project License
>>> >>>
>>> >>>
>>> >>>
>>> >>> Who Qualifies
>>> >>>
>>> >>>
>>> >>>
>>> >>> Open Source Project license is available free to non-commercial open
>>> >>> source software development projects that meet the Open Source
>>> >>> definition,
>>> >>> have a dedicated website, and an active community.
>>> >>>
>>> >>>
>>> >>>
>>> >>> An Open Source Licenses entitles you to use YouTrack Unlimited User
>>> >>> Pack
>>> >>> and is valid for an initial period of one year. Annual renewals are
>>> >>> provided
>>> >>> on request, subject to JetBrains' approval.
>>> >>>
>>> >>>
>>> >>>
>>> >>> License Terms
>>> >>>
>>> >>>
>>> >>>
>>> >>> An Open Source Project license allows you to:
>>> >>>
>>> >>> use YouTrack for non-commercial, open source software development only
>>> >>> run a single instance of YouTrack Server
>>> >>> create an unlimited number of User Accounts
>>> >>
>>> >>
>>> >> -0xe1a
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Viktor Klang
>>> >
>>> > Akka Tech Lead
>>> > Typesafe - The software stack for applications that scale
>>> >
>>> > Twitter: @viktorklang
>>> >
>>
>>
>
>
>
> --
> Daniel C. Sobral
>
> I travel to the future all the time.

By the way, whatever tool is being looked at, first check if there's a
hook listed for it on github admin page.

On Thu, Feb 16, 2012 at 17:11, Daniel Sobral <dcsobral@gmail.com> wrote:
> On Thu, Feb 16, 2012 at 16:09, Adriaan Moors <adriaan.moors@epfl.ch> wrote:
>> that looks pretty awesome! firsthand experiences, anyone? --a
>
> As a user, it never bothered me. The puppet stuff I use/contribute to
> use it, but that's very light. Also, I have no idea how it would
> behave when multiple people must have access to it, and I haven't
> looked into whatever tooling/API it might have. I'd be surprised if it
> didn't come down to git-based text files, however, which would be very
> amenable to scripting.
>
>>
>>
>> On Thu, Feb 16, 2012 at 6:56 PM, Erik Bruchez <ebruchez@gmail.com> wrote:
>>>
>>> Then what about the github tracker? Simple, to the point, and Scala is
>>> already on github.
>>>
>>> See:
>>> https://github.com/blog/831-issues-2-0-the-next-generation
>>>
>>> API:
>>> http://develop.github.com/p/issues.html
>>>
>>> -Erik
>>>
>>> 2012/2/15 √iktor Ҡlang <viktor.klang@gmail.com>:
>>> > TBH,
>>> >
>>> > An issue tracker should have the following properties:
>>> >
>>> > 1) No "workflow" crap
>>> > 2) Be able to show code and stack traces in a non-disruptive way
>>> > 3) Have a REST API for creating and updating tickets
>>> > 4) Arbitrary tagging of tickets
>>> > 5) Absolute ordering of tickets, no "priority" BS
>>> > 6) Should support discussions regarding the ticket
>>> > 7) Have great search/filtering capabilities
>>> >
>>> > Almost everything else just complicates and makes working with the issue
>>> > tracker a painful exercise.
>>> >
>>> > An issue tracker should be a tool that helps in documenting the past,
>>> > illustrating the current and aids in planning the future of some
>>> > software
>>> > project. That means low overhead, no handwaving and no fluff.
>>> >
>>> > Cheers,
>>> > √
>>> >
>>> >
>>> > On Wed, Feb 15, 2012 at 8:58 PM, Alex Cruise <alex@cluonflux.com> wrote:
>>> >>
>>> >> Well, I asked @YouTrack/@JetBrains on twitter if they'd be willing to
>>> >> donate a license, then I saw
>>> >> this: http://www.jetbrains.com/youtrack/buy/buy.jsp:
>>> >>
>>> >>>
>>> >>> OS-Project License
>>> >>>
>>> >>>
>>> >>>
>>> >>> Who Qualifies
>>> >>>
>>> >>>
>>> >>>
>>> >>> Open Source Project license is available free to non-commercial open
>>> >>> source software development projects that meet the Open Source
>>> >>> definition,
>>> >>> have a dedicated website, and an active community.
>>> >>>
>>> >>>
>>> >>>
>>> >>> An Open Source Licenses entitles you to use YouTrack Unlimited User
>>> >>> Pack
>>> >>> and is valid for an initial period of one year. Annual renewals are
>>> >>> provided
>>> >>> on request, subject to JetBrains' approval.
>>> >>>
>>> >>>
>>> >>>
>>> >>> License Terms
>>> >>>
>>> >>>
>>> >>>
>>> >>> An Open Source Project license allows you to:
>>> >>>
>>> >>> use YouTrack for non-commercial, open source software development only
>>> >>> run a single instance of YouTrack Server
>>> >>> create an unlimited number of User Accounts
>>> >>
>>> >>
>>> >> -0xe1a
>>> >
>>> >
>>> >
>>> >
>>> > --
>>> > Viktor Klang
>>> >
>>> > Akka Tech Lead
>>> > Typesafe - The software stack for applications that scale
>>> >
>>> > Twitter: @viktorklang
>>> >
>>
>>
>
>
>
> --
> Daniel C. Sobral
>
> I travel to the future all the time.



--
Daniel C. Sobral

I travel to the future all the time.