[Koha-devel] FW: Where is the BIG RED WARNING button?

[Jonathan Druart]

Hi Indranil,

Of course I was not talking about new contributors. My main goal for this
release is to help new people to come on-board.
We refreshed the wiki, wrote a step-by-step how-to "signoff and write
patches", etc.
I give personal answers to new contributors, guide them, give them quick
and early feedbacks on their patches in order to keep them motivated.

This button I am asking for is to alert support companies and regular
developers that something is (very) urgent and need their attention. I
would like to stop gesticulating to try getting this attention. I would
like a button I can push to make a red blinking light on some desks. Then
everybody is free to ignore it, but they saw it and I will not push it
again. It will be easier for me to know that people knows, than sending
emails, pinging on #koha, adding card to the kanban, CCing people on the
bug report, without never knowing if they are aware of the problem.

About the kanban: its goal is NOT to replace bugzilla, it has never been
and will never be.
We are talking about two different tools. One is a bug tracker, the other
one is a tool to manage/prioritize different tasks, group them under "Epic"
(big works), form working groups, etc. Moreover community tasks are not
always one entry in bugzilla, we want to track, discuss and keep history of
more stuffs than just bugs. Taiga answered this lack. Please re-read the
wiki page of the kanban if its goal is not clear (or ask me to update it).

Cheers,
Jonathan

On Thu, 10 Aug 2017 at 06:43 Indranil Das Gupta <indradg at gmail.com> wrote:

> Hi
>
> On Wed, Aug 9, 2017 at 7:25 PM, Jonathan Druart
> <jonathan.druart at bugs.koha-community.org> wrote:
>
> > I do not see the point to sign-off and QA trivial string patches when
> > blockers are in the queue for weeks (no need to tell me everybody does
> what
> > do they want, I still agree with that).
>
> I completely get that blockers need to be sorted out. But personally I
> got into Koha dev stream with string patches. How to write the tests
> was a mystery to me in the initial days and I was afraid to get in
> there. And when I did, I made mistakes which others helped clean up
> and that's how I learnt and I'm still learning.
>
> For a newbie, seeing their trivial patch being signed off and pushed
> is a shot of adrenaline and it gives them the confidence to bite into
> bigger pieces. I'm sure that we do not want Koha development to be
> seen as an oligarchy of expert devs, by not pushing the insignificant
> patches when there are blocker patches, especially when there is a
> call up for more "hands on the deck".
>
> Personally I was *not* happy with the shift to taiga. I knew my way
> around BZ. Kanban was a new format to me and having to spend time to
> learn a new pm tool was something that had me dragging my feet. But
> then its human nature.to resist  change. :-)  I will probably just get
> used to it in bit
>
> just my 2c
>
> indranil
>
> --
> Indranil Das Gupta
> L2C2 Technologies
>
> Phone : +91-98300-20971 <+91%2098300%2020971>
> WWW  : http://www.l2c2.co.in
> Blog    : http://blog.l2c2.co.in
> IRC     : indradg on irc://irc.freenode.net
> Twitter : indradg
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.koha-community.org/pipermail/koha-devel/attachments/20170810/7bdfeb79/attachment.html>