About not reading AIs

Sat Jan 18 06:33:41 BRST 2014

On Fri, Jan 17, 2014 at 12:38:49PM -0200, Daniel Tygel wrote:
> Hi all,
> 
> I've just read some suggestions from Colivre on how to send commit. I'd like to
> take this oportunity to again highlight another problem: the creation of new
> Action Items without reading existing ones (including those which are shared in
> this list).
> 
> Let me share one very recent example: some months ago (on November) I sent a
> message here in this list, alerting that the comment group plugin is crashing
> noosfero. After no one replied, we had to disable it in cirandas (this is so
> sad), and reported it here: http://noosfero.org/Development/ActionItem2930 . We
> sent the log of the error and some hint of what might be (javascript error
> conflicting with viewing articles with comments)
> 
> Then we sent another message in this list sharing this AI.
> 
> Then the developpers of this plugin created a new AI, called simply "fixes to
> comment group plugin" (http://noosfero.org/Development/ActionItem2931). I
> ***again*** sent a message here in the list, asking about what "fixes" were
> being considered, since the AI said nothing, and if they were looking at the
> bug that crashes the whole noosfero (which is something quite problematic, I
> guess).
> 
> And now, suddenly, another person "discovers" that very same bug and registers
> it here: http://noosfero.org/Development/ActionItem2952
> 
> I have always a feeling that sending messages here means a "black hole"
> experience.

I understand your frustration and I am sorry you feel that way.

However, we have to take into account that this is not problem that only
happens in Noosfero. Every non-trivial software project has problems
with duplicated bug reports. Dealing with them is just a fact of life.

One of the reasons for that is that it's _impossible_ for most human
beings to keep up with every single bit of information that comes
around, or remembering everything that already came around. It is also
not reasonable, in my opinion, to always scavenge the full list of bug
reports before reporting another one.

So, my suggestion is to accept this _will_ happen and not let it
frustrate you as if people were ignoring your bug reports just because
they don't care. x Think of how other bugs you reported that were _not_
duplicated and that will make you feel better. ;-)

When you discover that a bug was duplicated, please help the project by
marking duplicate bugs as "rejected" and adding a comment pointing to
the one that "actually" got fixed.

Bug triaging is a very useful contribution that even non-programmers can
make to the project, so whoever feel like doing that just go ahead and
do it.

-- 
Antonio Terceiro <terceiro at colivre.coop.br>
Colivre - Cooperativa de Tecnologias Livres
http://www.colivre.coop.br/

> 
>      Thank you,
> 
>            daniel
> 
> 
> 
> Em 15-01-2014 23:41, Joenio Costa escreveu:
> 
>     Gente,
> 
>     Tenho percebido que alguns commits não faz referência ao ActionItem.
>     Peço que vocês dêem atenção a isso e sempre adicionem ao final da
>     mensagem de commit o ActionItem em que estão trabalhando, exemplo:
> 
>     ------------------------------------
>     commit 9b87b01fa706c63b94e19ddc690a0dc302f98ebb
>     Author: Marcos Ramos <ms.ramos at outlook.com>
>     Date:   Wed Dec 11 18:15:33 2013 -0200
> 
>     recent_content_plugin: display the last articles published in...
> 
>     (ActionItem2848)
>     ------------------------------------
> 
>     Esse commit acima é referente ao ActionItem2848, isso facilita
>     o trabalho de rastrear as mudanças no projeto num futuro próximo
>     ou distante.
> 
>     É algo simples, que facilita a vida quando alguém tentar entender
>     o passado do projeto, entender como as decisões foram tomadas, e
>     uma infinidade de informações e estudos que podem ser feitos a partir
>     daí.
> 
>     No exemplo acima do ActionItem2848, eu consigo sem muito esforço
>     saber que esse commit entrou (ou vai entrar) na versão 0.46.0,
>     pois é o que diz no tracker do projeto:
> 
>     http://noosfero.org/Development/ActionItem2848
> 
>     Esse é o tipo de informação útil para mim como desenvolvedor
>     do projeto por exemplo.
> 
>     É isso, reforçando, adicionem ao final da mensagem de commit de
>     vocês o ActionItem que estão trabalhando.
> 
>     Obrigado!
> 
> 
> --
> (_.-~*´¨¯¨`*·~-.,-( •_•)-,.-~*´¨¯¨`*·~-._)
>           .
>     ,-. . |- ,-.          Educação,
>     |-' | |  ,-|          Informação e
>     `-' ' `' `-^          Tecnologia para
>  http://eita.org.br       Autogestão
> 
> (_.-~*´¨¯¨`*·~-.,-( •_•)-,.-~*´¨¯¨`*·~-._)
> 

> _______________________________________________
> Noosfero-dev mailing list
> Noosfero-dev at listas.softwarelivre.org
> http://listas.softwarelivre.org/cgi-bin/mailman/listinfo/noosfero-dev

-- 
Antonio Terceiro <terceiro at colivre.coop.br>
Colivre - Cooperativa de Tecnologias Livres
http://www.colivre.coop.br/

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20140118/4f6f04fa/attachment.pgp>