← Back to team overview

zim-wiki team mailing list archive

Re: wishlist?

 

Paulo,
would that have voting system? I think this is essential. I understand
developers have the right to do whatever they
want to (as they are not being paid for this), but the scores would at
least might have some influence on their decisions.
Agus

On Wed, Apr 26, 2017 at 9:38 AM, Paulo van Breugel
<p.vanbreugel@xxxxxxxxx> wrote:
> Hi Jaap,
>
> The issue tracker at github let's you label tickets as amongst others bug,
> enhancement, question, etc. You can also add your own labels, e.g., to
> separate between concrete actionable feature requests and ideas / outlines
> that are not yet actionable. These should be sufficient to separate feature
> requests and bug reports. The key to make this work (independent on the
> tool) lies i.m.h.o. in having one or more persons that monitor all issues,
> and assign the appropriate label (or re-assign if the issue reporter applied
> the wrong label).  I guess the most obvious persons would be the
> participating developers, as these would also know to whom to assign tasks,
> but others could step in as well (I for one wouldn't mind helping in this
> respect).
>
> Cheers,
>
> Paulo
>
>
> On 25-04-17 21:46, Jaap Karssenberg wrote:
>
> If we do use the issue tracker to also track feature requests, there is a
> need for a process for those as well. More specifically a process to ensure
> the quality of the open requests. What happened in the launchpad tracker is
> that we have hundreds of requests, some which are actionable, some which are
> just an idea or an outline of an idea. I haven;t been able to clean it up,
> because we have no process to refine or close requests.
>
> -- Jaap
>
>
> On Tue, Apr 25, 2017 at 9:29 PM Dimitrij Lisov <dmt.lsv@xxxxxxxxx> wrote:
>>
>> @Ale Great idea! I think it's quite easy to import the existing issues
>> from Launchpad into GitHub and label them appropriately to have a good
>> overview.
>>
>> Alessandro Sarretta <alessandro.sarretta@xxxxxxxxx> schrieb am Di., 25.
>> Apr. 2017 um 21:24 Uhr:
>>>
>>> On 25/04/2017 20:10, Jaap Karssenberg wrote:
>>>
>>> Not as such. We have captured a lot of wishlist requests in the bug
>>> tracker, but I'm afraid that that greatly diminished the usefulness of the
>>> bug tracker for real bugs. My intention for the github branch is to use the
>>> issue tracker purely for bugs and look elsewhere for keeping track of
>>> feature requests and discussion. Not decided yet how and where to do that -
>>> for now they can keep on living in the launchpad tracker. Any suggestions?
>>>
>>> I think you can easily keep track and manage bugs, feature requests and
>>> discussions in GitHub, using different and specific labels for issues or
>>> pull requests (e.g.
>>> https://medium.com/@dave_lunny/sane-github-labels-c5d2e6004b63).
>>>
>>> Ale
>>>
>>> --
>>> --
>>>
>>> Alessandro Sarretta
>>>
>>> skype/twitter: alesarrett
>>> Web: ilsarrett.wordpress.com
>>>
>>> Research information:
>>>
>>> Google scholar profile
>>> ORCID
>>> Research Gate
>>> Impactstory
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~zim-wiki
>>> Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~zim-wiki
>>> More help   : https://help.launchpad.net/ListHelp
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~zim-wiki
>> Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~zim-wiki
>> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~zim-wiki
> Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~zim-wiki
> Post to     : zim-wiki@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~zim-wiki
> More help   : https://help.launchpad.net/ListHelp
>

-- 
Agustin Lobo
aloboaleu@xxxxxxxxx


Follow ups

References