Task tracking

[Riccardo Iaconelli]

On Tuesday, January 05, 2016 11:23:04 AM Davide Valsecchi wrote:
> > Hey everyone,
> > I agree in every aspect Davide has written.
> > Regarding the need of docs, it is a very important tip that could help
> > us spare a lot of time. In my opinion
> > it could be easier if we have someone that wants to behave like a
> > "interface" between the tech guys and the
> > wtl users guys and that can check if the documentation is ok to
> > complete, readable etc.
> 
> This role could be useful because a lot of times people outside development
> doesn't hear about new improvements or bug fixs, or simply new features
> avaiable.

What we can also do is educate users to ask and report if things are not 
working like they expect, instead of somebody doing an active polling.

On the other hand I encourage the dev team to take full advantage of:

http://notes.kde.org/p/w2l-daily

The promo team is working hard on that one :-) Once that content is 
effectively rolling, we'll think of other ways to distribute it.

> > Furthermore, I think we need phabricator not only for the tech team
> > and the improving communication,
> > but also for bug/issue tracking. For example, lots of people write on
> > telegram channel about bugs in the
> > layout of the site. If the bug is not tracked it is lost under the
> > huge amount of daily messages.
> > So, I will start considering to redirect people on phab when they
> > notice something to fix.
> 
> Ye must definitely use phabricator also as bug traker, I agree.

This is the role of a bug tracker (i.e. Phabricator) after all... ;-)
...so +1 also here!

Bye,
-Riccardo