Task tracking

[Russell Greene]

I say anything someone should be working on should definitely be a task on
phabricator, then tracked on phabricator. Then, the meta page could maybe
have links to phabricator tasks?

What do you guys think?

On Sat, Jan 9, 2016, 07:33 Davide Valsecchi <valsecchi.davide94 at gmail.com>
wrote:

> The use of phabricator is therefore to intensify.
>
> What do you think about the structure of developers documentation on the
> meta website?
> We should find a way to document every decision or action done on the code
> or infrastructure in a clear way.
>
> Davide
>
> Il giorno mer 6 gen 2016 17:09 Riccardo Iaconelli <riccardo at kde.org> ha
> scritto:
>
>> On Wednesday, January 06, 2016 03:23:51 PM Alessandro Tundo wrote:
>> > Communication channels are very dispersive. If a person join every
>> Telegram
>> > group he/she spends some hours to read all daily messages. I should be
>> able
>> > to know the W2L "state of the art" without reading lots of messages. I
>> > think Meta pages + phab tasks with comments are a very good way.
>> >
>> > Alessandro
>>
>> +1
>>
>> The WikiToLearn news of the day is another effort in that direction... I
>> hope
>> it's useful!
>>
>> Bye,
>> -Riccardo
>>
>> _______________________________________________
>> WikiToLearn-Tech mailing list
>> WikiToLearn-Tech at kde.org
>> https://mail.kde.org/mailman/listinfo/wikitolearn-tech
>>
> _______________________________________________
> WikiToLearn-Tech mailing list
> WikiToLearn-Tech at kde.org
> https://mail.kde.org/mailman/listinfo/wikitolearn-tech
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/wikitolearn-tech/attachments/20160109/66a17f89/attachment-0001.html>