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 di
Salvete!
>>
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
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 e
I can't think of something better for now, thx for finding out and
explaining!
On 10.08.2017 10:33, Marcel de Rooy wrote:
> Christopher got me thinking: For 260 and 264 are repeatable, as a side
effect of cataloguing rule changes, they might even appear both in a
record (even if they should
Hi
On Wed, Aug 9, 2017 at 7:25 PM, Jonathan Druart
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 sor
On Wed, 9 Aug 2017, Jonathan Druart wrote:
If you are a developer and you want to help, what do you do? Where do you
do? How to you prioritize your work? Are you all picking bugs randomly in
the queue?
I'm not a "developer" in that I don't work for a commercial Koha support
company, but as our
> Christopher got me thinking: For 260 and 264 are repeatable, as a side effect
> of cataloguing rule changes, they might even appear both in a record (even if
> they shouldn't). Which year will be given priority? For display purposes in
> the brief views, only one year should be displayed.
Tra