Issue tracking

[Arthur Del Esposte]

Hey guys,

This week we had a conflict of efforts to repair the Noosfero tests, all
due to the lack of communication in the community about what will be
developed or repaired.

Once, we used ActionItems. Now we do this through the Gitlab's issue
tracker, which is a great tool, by the way.

Let us all to recover the culture of issue creation for communicate what we
intend to do to avoid duplicate effort and loss of work.

So, before start programming something that is not trivial or you can't do
in 15 minutes, create a new issue explaining your new feauture, a bug or a
big refactoring you want to do. Everybody will be notified in noosfero-dev
list and will have the oportunity to discuss about what you proposed. In
fast changes,  the commit or MergeRequest are sufficient.

Below is a list of benefits that we haves to use issues:
- Avoid duplication
- Enhances community's communication
- Avoid you to lose your time building something that won't be accepted
- Help with Noosfero and it's releases' documantions.
- We can discuss about features and changes before they are made.
- Keep a better development track.

Let's start to do it again =)?

-- 
*Arthur de Moura Del Esposte*
Engenheiro de Software

Colivre - http://colivre.coop.br/
LAPPIS - http://fga.unb.br/lappis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listas.softwarelivre.org/pipermail/noosfero-dev/attachments/20150610/28fe4415/attachment.html>