Hi all,
I like Magnus' suggestion of using the Dashboard. I look at it often and
it's usually my starting point before signing off patches. Now with
Jenkins status being back on it, it's even more useful for me RMaint.
Maybe we could add a section for the RM to post urgent messages? Most of
the Dashboard is data pulled in from difference sources, not sure how to
best add it to it.
Katrin
On 11.08.2017 11:03, Magnus Enger wrote:
Kia ora!
I agree that there should be *one* place to get an overview of the
health of the project and what needs doing (at least as far as bugs
go), and for me the natural place for that is the dashboard:
http://dashboard.koha-community.org/
We could probably do more with that, and the data behind it (from
Bugzilla). Like:
- display blockers/critical bugs in big red letters across the top.
(Or use tags to let the RM choose bugs that should be specially
highlighted.)
- make the favicon red when there are such blockers (developers could
have the dashboard always open in a pinned tab)
- highlight the people who helped signoff and qa those critical patches
As for what to work on and when: With a lot more customers there is a
lot less time to sign off patches. So if I am going to do it I need to
find one that
- fits in the time I have available
- is relevant to my customers
- is in a part of Koha I know, or it will take a lot more time
(signing off patches in unknown parts of Koha is great for learning,
of course, but it will take more time)
Just my NOK 0,02.
Best regards,
Magnus
Libriotech
On 11 August 2017 at 02:01, David Cook <dc...@prosentient.com.au> wrote:
I have Arduinos and Raspberry Pis at my desk. Maybe making a literal big red
warning light isn’t a bad idea… ;). We could call it “The Bug Signal” after
The Bat Signal. We could make a Kickstarter!
I’m joking about the Kickstarter, but I kind of like the idea of a little
physical Koha bug display :p.
David Cook
Systems Librarian
Prosentient Systems
72/330 Wattle St
Ultimo, NSW 2007
Australia
Office: 02 9212 0899
Direct: 02 8005 0595
From: koha-devel-boun...@lists.koha-community.org
[mailto:koha-devel-boun...@lists.koha-community.org] On Behalf Of Jonathan
Druart
Sent: Friday, 11 August 2017 1:14 AM
To: Indranil Das Gupta <indr...@gmail.com>
Cc: Koha-devel <koha-devel@lists.koha-community.org>
Subject: Re: [Koha-devel] FW: Where is the BIG RED WARNING button?
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 <indr...@gmail.com> wrote:
Hi
On Wed, Aug 9, 2017 at 7:25 PM, Jonathan Druart
<jonathan.dru...@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
WWW : http://www.l2c2.co.in
Blog : http://blog.l2c2.co.in
IRC : indradg on irc://irc.freenode.net
Twitter : indradg
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
_______________________________________________
Koha-devel mailing list
Koha-devel@lists.koha-community.org
http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/
