Trying image attachment again.
I didn't start out to be a naysayer though. I am really replying to to
>> share some team practices with the group based on experience with the
>> #Scap3 project.
>>
>
> https://phabricator.wikimedia.org/project/board/1449/ is the parent
> project. It could be a
On Wed, 2017-01-11 at 10:40 -0800, Joel Aufrecht wrote:
> [image: Inline image 1]
Seems like the image supposed to be displayed here did not make it.
andre
--
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/
___
teampractices
>
> I didn't start out to be a naysayer though. I am really replying to to
> share some team practices with the group based on experience with the
> #Scap3 project.
>
> https://phabricator.wikimedia.org/project/board/1449/ is the parent
> project. It could be a sub-project under our team project
Thanks, Mukunda! Good stuff. :)
I try to very gently discourage using herald to tag everything with a
> parent project. It hasn't become a problem yet but ultimately herald rules
> do not scale.
Thanks for the reminder. I definitely guilty of thinking about this stuff
more theoretically
If my years of programming taught me anything, it is the evil of
duplication. There needs to be one authoritative source of information. Any
copy is at high risk of being out-of-date or out-of-synch, either of which
make it misleading. For me, misleading information is (much) worse than
none at
