I will need to add them since I have been made co-owner by toby.
On Wed, Jan 15, 2014 at 6:01 PM, Raine M. Ekman <ra...@iki.fi> wrote:
> Here's some kind of starting point.
>
> Broad classifications: bug, crash, enhancement, discussion
> Resolutions: duplicate, invalid, question, wontfix, not our issue, later
> Components: zynaddsubfx, mixer, sf2player, vestige, midi, build system,
> automation, audio file processor
>
> BTW, I signed up for Github but can't see any obvious way to add labels to
> LMMS issues...
>
> Quoting Jonathan Aquilina <eagles051...@gmail.com>:
>
> Raine I am migrating the bugs from the SF bug tracker to the git hub issue
>> tracker.
>>
>> Can you provide me with a list of tags you would like to see I would more
>> the
>> happily include them. Seeing as Toby is busy I am going to take this by
>> the
>> horns instead of waiting for him to respond.
>>
>> Isnt this what the whole point of OSS and the software that is part of it
>> to
>> work as a community. I think its time i get on that bandwagon :D.
>>
>> As mentioned above provide me wiht a list of tags and I will get them up
>> asap
>> and If I am not mistaken any one can really add tags to issues. If someone
>> cannot please let me know.
>>
>> Thanks
>> Jonathan
>>
>> On Wednesday 15 January 2014 14:39:24 Raine M. Ekman wrote:
>>
>>> OK, I was thinking of how to leverage the new opportunities or
>>> something. My reasoning is that labels on github seem like a
>>> user-friendly way of categorizing the issues. You see immediately in
>>> the issue list what the issue relates to, and even get cool statistics
>>>
>>> :)
>>>
>>> Another thing is that searching finds only exactly what you search
>>> for, and false positives too. Think of a label "windows specific" vs.
>>> trying to skip those issues that don't apply to linux using only the
>>> search, in how many ways can you write it in text? "only on windows",
>>> "no problem on linux", "win8 doesn't like this" and so on.
>>>
>>> I'm fine with whatever way this goes, and labels can of course be made
>>> up along the way as needed. But I don't agree on the mistagging, it's
>>> way more likely that the labels will just be ignored when reporting
>>> issues. But those are matters of culture and gently beating sense into
>>> people :)
>>>
>>> Citerar Jonathan Aquilina <eagles051...@gmail.com>:
>>> > @toby see below on your thoughts.
>>> >
>>> > Raine I am going by the labels toby had initially setup. Its really
>>> > up to him.
>>> > The problem with too many labels is that things can easily get
>>> mistagged +
>>> > it would be easier to just classify them as a bug in general and
>>> specify
>>> > what part of the program. Then again that is my preference.
>>> >
>>> > On Wednesday 15 January 2014 11:56:26 Raine M. Ekman wrote:
>>> >> Citerar Jonathan Aquilina <eagles051...@gmail.com>:
>>> >> > Dont worry though if you arent seeing all the bugs yet from source
>>> >> > forge
>>> >> > im
>>> >> > working on migrating them as we speak. But for any new bugs or
>>> patches
>>> >> > go
>>> >> > ahead and create a new issue
>>> >> >
>>> >> > https://github.com/LMMS/lmms/issues?state=open
>>> >> >
>>> >> > and tag accordingly please.
>>> >>
>>> >> 1. The wiki should be updated to point people towards Github. The
>>> >> instructions for how to participate should be updated, too. (I know I
>>> >> read the wiki long before I joined these lists...)
>>> >>
>>> >> 2. The new issue tracker could do with better labels, my suggestion is
>>> >> something along these lines:
>>> >> - enhancement/patch -> split into enhancement and patch
>>> >> - crash! (even redder than "bug" if possible), maybe "important" too?
>>> >> - one label for each plugin
>>> >> - automation, pattern editor, midi, ui...
>>> >> - "not our bug" as a resolution for stuff external to LMMS (libs it
>>> >> depends on and so on)
>>>
>>
>>
>>
>
>
> --
> ra...@iki.fi
> 04 00 83 83 95
>
>
>
--
Jonathan Aquilina
------------------------------------------------------------------------------
CenturyLink Cloud: The Leader in Enterprise Cloud Services.
Learn Why More Businesses Are Choosing CenturyLink Cloud For
Critical Workloads, Development Environments & Everything In Between.
Get a Quote or Start a Free Trial Today.
http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk
_______________________________________________
LMMS-devel mailing list
LMMS-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lmms-devel
