Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index


Hi all,

Cor Nouws wrote on 14-10-16 20:37:
Hi Jan,

Jan Iversen wrote on 14-10-16 19:53:

Following our good discussion in the last ESC meeting, we have another
example [...]

[...] 
I hope my view on the situation does help a bit in our mutual effort :)


So it's good that there is a clear procedure * and that based on that we
can say: if an easyHack is done and closed, it should not have
unexpected unwanted side effects. In the unexpected case that there
appears to be a need for a follow-up, that should be done in a new
issue/easyHack.

May I take the freedom to suggest three things to further enhance this
situation?

- It might well be that in the existing easyHacks, there are some that
didn't go through the now set careful procedure.
To check if there are issues overseen, maybe we can ask 'UX' to do a
review of the existing (older) easyHacks with relation to UI?

- Since we want to be maximal encouraging to new hackers, it is unsure
who follow-up issues will be handled of course.
To prevent that (in some rare cases) favoring more devs will result in
poor UX, maybe we can ask 'dev' to commit themselves to fixing those, if
these are not picked up in reasonable time by an easyHacker?

- In the end we can not prevent that someone reopens a fixed easyHack.
Might that happen, let 'us' react soon and friendly (maybe via direct
mail) explaining and such.

Does that make sense?

Ciao - Cor


*) quoting jani:
1) somebody add keyword “easyhack” to a bug
2) next morning, it is in my mail (automatically), and I look at it and
    - needUIEval, if the change has anything to do with the UI or the
workflow
    - needDevEval, if there are no code pointers or I am unsure if the
suggestion is a valid development way.
3) needUIEval is removed only by the UI team
4) needDevEval is normally removed by me or a core developer.
5) At this point the easyhack is public


-- 
Cor Nouws
GPD key ID: 0xB13480A6 - 591A 30A7 36A0 CE3C 3D28  A038 E49D 7365 B134 80A6
- vrijwilliger http://nl.libreoffice.org
- volunteer http://www.libreoffice.org
- The Document Foundation Membership Committee Member

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.