On Tue, May 6, 2014 at 1:56 AM, Nick Coghlan <ncogh...@gmail.com> wrote:
>
> On 6 May 2014 08:42, "Carol Willing" <willi...@willingconsulting.com> wrote:
>> Here's a write up of how I found the contribution process and how I would
>> explain the process to others based on my experience:
>> http://pastebin.com/iKhL5RvS
>
> Thanks Carol, that's a great write-up and definitely includes some good
> ideas for improvement.
>
> For folks with greater Roundup-fu than me: how hard does the "personal tags"
> idea sound? Alternatively, the front end could be more like a personal set
> of "issue lists".
>
I haven't read Carol's link yet, but if with "personal tags" you mean
tags hat a single user can add for himself to an issue and that are
not visible to others, then I think it might be somewhat difficult.
You could store them in a user field (e.g. user.personal_tags =
{issue123: [tag1, tag2], issue124: [tag3]}) but then it might not be
too easy to access them (e.g. while searching). Same goes if we keep
them in a separate table. In addition, we also have to write the code
to handle addition/deletion of both tags in a personal list, and on
the issue.
A possible compromise might be to add a way to "star" interesting issues.
I think there are 3 "levels", and we currently support only two:
1) If I know I'm going to fix an issue, I assign it to myself;
2) if I know how to fix an issue, or I would like to work on it, I
have to mark it on my mail client;
3) if I left a comment or a review or even if an issue is
"interesting", I add myself to nosy;
If you were referring to "a way to easily tag issues to return to as
promising possibilities", then a star/favorite feature might cover
case 2) and solve the issue, and even if it's not as fine grained as
a full personal tags system, it should be simpler to implement.
> Cheers,
> Nick.
>
>>
>> I'm not asking you to change or modify the process as it stands, but
>> merely to consider the process from the perspective of someone who would
>> like to contribute but is new to Python's specific workflow.
>>
>> Thanks,
>> Carol Willing
>>
>> --
>> Carol Willing
>> Developer
>> Willing Consulting
>>
>>
>> _______________________________________________
>> core-workflow mailing list
>> core-workflow@python.org
>> https://mail.python.org/mailman/listinfo/core-workflow
>> This list is governed by the PSF Code of Conduct:
>> https://www.python.org/psf/codeofconduct
>
>
> _______________________________________________
> core-workflow mailing list
> core-workflow@python.org
> https://mail.python.org/mailman/listinfo/core-workflow
> This list is governed by the PSF Code of Conduct:
> https://www.python.org/psf/codeofconduct
_______________________________________________
core-workflow mailing list
core-workflow@python.org
https://mail.python.org/mailman/listinfo/core-workflow
This list is governed by the PSF Code of Conduct:
https://www.python.org/psf/codeofconduct
