Re: [Engagement] Relaying out bug fixes news via social media

[Alexandre Franke]

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 posts doesn’t really
>> matter, but the curation aspect is key to make it good. Unfortunately,
>> Frédéric Peters was the only one putting in the time that requires and
>> after quite a while he moved to other things.
>
>
> What made it good?  What was the work involved around it?

It was good because:
* it was once a week, that’s often enough to keep informed but not too
much so one manages to keep up with the amount of info
* it was a one line summary for what could be several bug reports
closed, or a huge amount of commits
* that summary was high level and human readable

The work involved reading commits-list, picking interesting bits
manually and writing a good summary.

As a side note, the fact it was on a blog meant there was an RSS feed
and people could follow along without being on one of those silos… I
get that Twitter, Facebook and co are a way to reach out to people
outside our community, but there are also good reasons for people not
to be on there and we should cater to them as well, so hopefully
whatever you implement addresses this.

> How about we do this as the first step then? That would give the curated
> content, and also the ability for newcomers to share something.  It should
> address most of your concerns, yes?

I don’t really get what “this” is in this context.

-- 
Alexandre Franke
GNOME Hacker & Foundation Director
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: [Engagement] Relaying out bug fixes news via social media

[Sriram Ramkrishna]

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 form.
>

That's fine, a good idea should be able to stand up to a challenge
otherwise how would we know it is any good?


> > We have come up with an idea in the area of social media outreach and
> > it would be glad if you can share your views on it. The idea is to
> > relay news out in the social media whenever any bug/issue is fixed via
> > dedicated GNOME Bugs' Social Media Channels (thereafter referred as
> > SMC).
>
> With some curation? Because otherwise I really don’t see any value in
> this and people that want to see everything should just subscribe to
> commits-list.
>

Well, if it was not curated we would create a GNOME Bugs twitter that
people can subscribe to.  We would not use the GNOME account for this at
all as it would be total spam.


> > GNOME Bugs' SMC are not created yet and will be separate from main
> > GNOME handles. You can take a look at LibreOffice's bug channel [1].
> > [1] https://twitter.com/LibreOfficeBugs
>
> That LO channel is noisy. I would take it as an example of what not to aim
> for.
>

Only if you want to subscribe to the LibreOfficeBugs, not necessarily LO.
If that is noisy that is a different issue.


> > Although, based on the severity of the bug/issue, the main GNOME
> > handle can retweet/relay the link on it's own account. The idea is to
> > keep a separate bug SMC is:
> >
> > * Not to make main GNOME handle very noisy
> > * To have automated GNOME bugs SMC
>
> Please don’t make it automatic. That’s a sure way to make it noisy and
> uninteresting.
>

We could add some parameters that might could make it more interesting to
publish.


> > I think that most of us agree that social media is the fastest way to
> > get information out.
>
> Can we also agree that social media are flooded with content and that
> people waste a lot of time on them skimming through it to find
>
>
Sure, we can agree on that as well.

> Therefore, as far as code development is
> > concerned, it takes a while till the information is actually relayed
> > out. Mostly, until someone blogs about it and then pick up by other
> > blogs and so on..
>
> You need to find balance between the current lack of communication and
> the overwhelming flood of an automated feed.
>

I agree, we definitely can discuss this further.


> > We can get fast here and be more verbose about the work that goes into
> > everyday. In addition to that, we want it to be automated; similar to
> > [1]
>
> Again, this is a bad idea.
>
> 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 posts doesn’t really
> matter, but the curation aspect is key to make it good. Unfortunately,
> Frédéric Peters was the only one putting in the time that requires and
> after quite a while he moved to other things.
>

What made it good?  What was the work involved around it?


> > Now comes the most interesting part. It would be really great if we
> > can mention "Newcomers" and their internet handle in the bug SMC link;
> > That should really make them feel special as they can show to the
> > world that they have done something great and brag!
>
> Sure, that is a good idea.
>

How about we do this as the first step then?  That would give the curated
content, and also the ability for newcomers to share something.  It should
address most of your concerns, yes?

sri


>
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: [Engagement] Relaying out bug fixes news via social media

[Alexandre Franke]

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 outreach and
> it would be glad if you can share your views on it. The idea is to
> relay news out in the social media whenever any bug/issue is fixed via
> dedicated GNOME Bugs' Social Media Channels (thereafter referred as
> SMC).

With some curation? Because otherwise I really don’t see any value in
this and people that want to see everything should just subscribe to
commits-list.

> GNOME Bugs' SMC are not created yet and will be separate from main
> GNOME handles. You can take a look at LibreOffice's bug channel [1].
> [1] https://twitter.com/LibreOfficeBugs

That LO channel is noisy. I would take it as an example of what not to aim for.

> Although, based on the severity of the bug/issue, the main GNOME
> handle can retweet/relay the link on it's own account. The idea is to
> keep a separate bug SMC is:
>
> * Not to make main GNOME handle very noisy
> * To have automated GNOME bugs SMC

Please don’t make it automatic. That’s a sure way to make it noisy and
uninteresting.

> I think that most of us agree that social media is the fastest way to
> get information out.

Can we also agree that social media are flooded with content and that
people waste a lot of time on them skimming through it to find

> Therefore, as far as code development is
> concerned, it takes a while till the information is actually relayed
> out. Mostly, until someone blogs about it and then pick up by other
> blogs and so on..

You need to find balance between the current lack of communication and
the overwhelming flood of an automated feed.

> We can get fast here and be more verbose about the work that goes into
> everyday. In addition to that, we want it to be automated; similar to
> [1]

Again, this is a bad idea.

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 posts doesn’t really
matter, but the curation aspect is key to make it good. Unfortunately,
Frédéric Peters was the only one putting in the time that requires and
after quite a while he moved to other things.

> Now comes the most interesting part. It would be really great if we
> can mention "Newcomers" and their internet handle in the bug SMC link;
> That should really make them feel special as they can show to the
> world that they have done something great and brag!

Sure, that is a good idea.

-- 
Alexandre Franke
GNOME Hacker & Foundation Director
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: [Engagement] Relaying out bug fixes news via social media

[Biraj Karmakar]

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 create some visual interest.
>>
>>
>>
>
Firefox Nightly team actually does this. Here is one example [0].




> Yes, definitely something we can add there as well.
>
> sri
>
> -Bastian
>>
>> On Sat, Nov 4, 2017 at 3:46 AM, Umang Jain 
>> wrote:
>>
>> Hi there, We have come up with an idea in the area of social media
>> outreach and it would be glad if you can share your views on it. The idea
>> is to relay news out in the social media whenever any bug/issue is fixed
>> via dedicated GNOME Bugs' Social Media Channels (thereafter referred as
>> SMC). GNOME Bugs' SMC are not created yet and will be separate from main
>> GNOME handles. You can take a look at LibreOffice's bug channel [1].
>> Although, based on the severity of the bug/issue, the main GNOME handle can
>> retweet/relay the link on it's own account. The idea is to keep a separate
>> bug SMC is: * Not to make main GNOME handle very noisy * To have automated
>> GNOME bugs SMC I think that most of us agree that social media is the
>> fastest way to get information out. Therefore, as far as code development
>> is concerned, it takes a while till the information is actually relayed
>> out. Mostly, until someone blogs about it and then pick up by other blogs
>> and so on.. We can get fast here and be more verbose about the work that
>> goes into everyday. In addition to that, we want it to be automated;
>> similar to [1] Now comes the most interesting part. It would be really
>> great if we can mention "Newcomers" and their internet handle in the bug
>> SMC link; That should really make them feel special as they can show to the
>> world that they have done something great and brag! Again making that
>> automated would require some thought in organizing that kind of process so
>> Carlos Soriano would give better perspective. But all in all, this stuff is
>> great for newcomers engagement and outreach. This discussion actually
>> happened in Telegram "GNOME Engagement" channel this evening. So, it would
>> be great if you can share your views/consensus here. [1]
>> https://twitter.com/LibreOfficeBugs Thank you Cheers, uajain
>> ___ engagement-list mailing
>> list engagement-list@gnome.org https://mail.gnome.org/
>> mailman/listinfo/engagement-list
>>
>> ___
>> engagement-list mailing list
>> engagement-list@gnome.org
>> https://mail.gnome.org/mailman/listinfo/engagement-list
>>
>
> ___
> engagement-list mailing list
> engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list
>
>

[0] https://twitter.com/FirefoxNightly/status/914822050858008576
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: [Engagement] Relaying out bug fixes news via social media

[Sriram Ramkrishna]

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 as well.

sri

-Bastian
>
> On Sat, Nov 4, 2017 at 3:46 AM, Umang Jain 
> wrote:
>
> Hi there, We have come up with an idea in the area of social media
> outreach and it would be glad if you can share your views on it. The idea
> is to relay news out in the social media whenever any bug/issue is fixed
> via dedicated GNOME Bugs' Social Media Channels (thereafter referred as
> SMC). GNOME Bugs' SMC are not created yet and will be separate from main
> GNOME handles. You can take a look at LibreOffice's bug channel [1].
> Although, based on the severity of the bug/issue, the main GNOME handle can
> retweet/relay the link on it's own account. The idea is to keep a separate
> bug SMC is: * Not to make main GNOME handle very noisy * To have automated
> GNOME bugs SMC I think that most of us agree that social media is the
> fastest way to get information out. Therefore, as far as code development
> is concerned, it takes a while till the information is actually relayed
> out. Mostly, until someone blogs about it and then pick up by other blogs
> and so on.. We can get fast here and be more verbose about the work that
> goes into everyday. In addition to that, we want it to be automated;
> similar to [1] Now comes the most interesting part. It would be really
> great if we can mention "Newcomers" and their internet handle in the bug
> SMC link; That should really make them feel special as they can show to the
> world that they have done something great and brag! Again making that
> automated would require some thought in organizing that kind of process so
> Carlos Soriano would give better perspective. But all in all, this stuff is
> great for newcomers engagement and outreach. This discussion actually
> happened in Telegram "GNOME Engagement" channel this evening. So, it would
> be great if you can share your views/consensus here. [1]
> https://twitter.com/LibreOfficeBugs Thank you Cheers, uajain
> ___ engagement-list mailing
> list engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list
>
> ___
> engagement-list mailing list
> engagement-list@gnome.org
> https://mail.gnome.org/mailman/listinfo/engagement-list
>
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list

Re: [Engagement] Relaying out bug fixes news via social media

[Bastian Ilso]

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 the area of social media outreach and
it would be glad if you can share your views on it. The idea is to
relay news out in the social media whenever any bug/issue is fixed via
dedicated GNOME Bugs' Social Media Channels (thereafter referred as
SMC).

GNOME Bugs' SMC are not created yet and will be separate from main
GNOME handles. You can take a look at LibreOffice's bug channel [1].

Although, based on the severity of the bug/issue, the main GNOME
handle can retweet/relay the link on it's own account. The idea is to
keep a separate bug SMC is:

* Not to make main GNOME handle very noisy
* To have automated GNOME bugs SMC

I think that most of us agree that social media is the fastest way to
get information out. Therefore, as far as code development is
concerned, it takes a while till the information is actually relayed
out. Mostly, until someone blogs about it and then pick up by other
blogs and so on..

We can get fast here and be more verbose about the work that goes into
everyday. In addition to that, we want it to be automated; similar to
[1]

Now comes the most interesting part. It would be really great if we
can mention "Newcomers" and their internet handle in the bug SMC link;
That should really make them feel special as they can show to the
world that they have done something great and brag! Again making that
automated would require some thought in organizing that kind of
process so Carlos Soriano would give better perspective. But all in
all, this stuff is great for newcomers engagement and outreach.

This discussion actually happened in Telegram "GNOME Engagement"
channel this evening. So, it would be great if you can share your
views/consensus here.


[1] https://twitter.com/LibreOfficeBugs

Thank you
Cheers,
  uajain
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list
___
engagement-list mailing list
engagement-list@gnome.org
https://mail.gnome.org/mailman/listinfo/engagement-list