On Mon, Nov 6, 2017 at 3:26 AM, Sriram Ramkrishna wrote:
>> We did have something that was called the [commit
>> digest](https://blogs.gnome.org/commitdigest/), a weekly blog post
>> highlighting the most interesting code changes, and it was good.
>> That’s what you should aim at. Twitter or blog
On Sat, Nov 4, 2017 at 6:00 AM Alexandre Franke wrote:
> On Fri, Nov 3, 2017 at 6:46 PM, Umang Jain
> wrote:
> > Hi there,
>
> Hello,
>
> I apologize in advance for sounding like a buzzkill, but I do not
> share the enthusiasm about this. I do agree with the general idea,
> just not the proposed
On Fri, Nov 3, 2017 at 6:46 PM, Umang Jain wrote:
> Hi there,
Hello,
I apologize in advance for sounding like a buzzkill, but I do not
share the enthusiasm about this. I do agree with the general idea,
just not the proposed form.
> We have come up with an idea in the area of social media outrea
On Sat, Nov 4, 2017 at 10:50 AM, Sriram Ramkrishna
wrote:
>
>
> On Fri, Nov 3, 2017 at 4:26 PM Bastian Ilso
> wrote:
>
>> Hey,
>>
>>
>> I love the idea! If there are graphical attachments (fx mockups) on a
>> bug, it might also be interesting to attach those too in the automated
>> message to cr
On Fri, Nov 3, 2017 at 4:26 PM Bastian Ilso
wrote:
> Hey,
>
>
> I love the idea! If there are graphical attachments (fx mockups) on a bug,
> it might also be interesting to attach those too in the automated message
> to create some visual interest.
>
>
>
Yes, definitely something we can add there
Hey,
I love the idea! If there are graphical attachments (fx mockups) on a
bug, it might also be interesting to attach those too in the automated
message to create some visual interest.
-Bastian
On Sat, Nov 4, 2017 at 3:46 AM, Umang Jain
wrote:
Hi there,
We have come up with an idea in
