@webcompat twitter account

[miketaylr]

So. We have twitter.com/webcompat and it's doing nothing.

What's a good use? Tweeting bug reports? Updates? Emoji?

[karlcow]

Tweeting Bug reports might become quickly overwhelming if the site becomes successful.
I guess you are the only one subscribed to the twitter account. So managing it might be difficult too.

What about tweeting a weekly summary of open bugs. We should be able to do a bit of stats on open bugs such as oldest bug, etc. :) This requires a bit of work too and a place to publish the summary.

To think a bit more.

[hallvors]

What about an automated tweet whenever a bug is closed? Should (unfortunately) be less overwhelming than tweeting all new bugs or updates, and is cooler.

[miketaylr]

karl wrote:

I guess you are the only one subscribed to the twitter account. So managing it might be difficult too.

Nah, Adam has the password too. PM me if you want it. :)

But Github has some nice twitter integration to automatically tweet events like commits, issues, etc. But I don't know if this is actually a good idea. People can just as easily "watch" a repo and get updates on bugs that way.

karl wrote:

What about tweeting a weekly summary of open bugs. We should be able to do a bit of stats on open bugs such as oldest bug, etc. :) This requires a bit of work too and a place to publish the summary.

This is an interesting idea. Seems like something we could automate at some point (as long as the generated output isn't "0 bugs reported, 0 bugs fixed..." every week. :P). Also some kind of update like this would be a good place to highlight contributors. I imagine a tiny "Latest News" or s/News/whatever/ widget or link on the homepage too.

hallvors wrote:

What about an automated tweet whenever a bug is closed? Should (unfortunately) be less overwhelming than tweeting all new bugs or updates, and is cooler.

I wonder how you could filter the wins from closing spam, invalid bugs, dupes, etc... I guess you could do something smarter than a "tweetthis" label. :P

[calexity]

I love these ideas. I'd love to see the power of twitter leveraged for
spreading this project. I think there's a bigger workflow here that could
involve the steps before of how a bug gets diagnosed and then sent to the
source.

I'd love to delve into this stuff because it's core of making this thing
sing. From when someone submits a bug through it being solved. It's
probable that Twitter could help us with this workflow.

On Friday, April 25, 2014, Mike Taylor notifications@github.com wrote:

karl wrote:

I guess you are the only one subscribed to the twitter account. So
managing it might be difficult too.

Nah, Adam has the password too. PM me if you want it. :)

But Github has some nice twitter integration to automatically tweet events
like commits, issues, etc. But I don't know if this is actually a good
idea. People can just as easily "watch" a repo and get updates on bugs that
way.

karl wrote:

What about tweeting a weekly summary of open bugs. We should be able to do
a bit of stats on open bugs such as oldest bug, etc. :) This requires a bit
of work too and a place to publish the summary.

This is an interesting idea. Seems like something we could automate at
some point (as long as the generated output isn't "0 bugs reported, 0 bugs
fixed..." every week. :P). Also some kind of update like this would be a
good place to highlight contributors. I imagine a tiny "Latest News" or
s/News/whatever/ widget or link on the homepage too.

hallvors wrote:

What about an automated tweet whenever a bug is closed? Should
(unfortunately) be less overwhelming than tweeting all new bugs or updates,
and is cooler.

I wonder how you could filter the wins from closing spam, invalid bugs,
dupes, etc... I guess you could do something smarter than a "tweetthis"
label. :P

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/63#issuecomment-41398521
.

Sent from Gmail Mobile

[tagawa]

+1 to @hallvors' suggestion, and I think it's important to say a public thanks to the sites in question.

[hallvors]

What about "if issue had contactready or sitewait label, tweet automatically when it gets closed"?

[magsout]

+1 @tagawa @hallvors

[miketaylr]

That's a cool idea. Will put on my list of things to hopefully get done next week during my "webcompat work week".

[magsout]

Maybe write a short bio on Twitter?

[tagawa]

Good idea @magsout - and we can have a link to webcompat.com as well.

[calexity]

Yes! Could be something like

An open source initiative to increase cross-browser compatibility. Report bugs from anywhere on the web.

Also, we could stand to use a higher res icon - I think that's my fault. Try this one @miketaylr or @karlcow

[miketaylr]

Great suggestions, I've updated the bio and avatar.

[tagawa]

Looks good. Thanks @miketaylr

[calexity]

Yes thank you!

Sent from Gmail Mobile

[karlcow]

see also #55 about notifications by email.

Possibilities:

• Automatically tweeting new bugs
• Automatically tweeting closed bugs
• Automatically tweeting about changelog

The issue with automatic tweets, is that it becomes quickly spammy for people. It makes it harder to have a dialog on this account. Maybe it could be a separate account. The webcompatFly account 🐦

[calexity]

What about a weekly round up? Have you seen SumAlls "how I did on Twitter this week?" https://twitter.com/YasmineMolavi/status/519926916279992321?s=09

We could do webcompat weekly stats:

X new bugs
X bugs closed
X new contributors

I think site updates/new features are OK to go out individually because they happen less often.

[karlcow]

@calexity. Yes it sounds like a good idea even for us as a dashboard. This I guess ties to notifications and logging on the server side. Issue #245

[miketaylr]

Karl is going to write a script to collect bugs that were fixed in the past week, and a bot to tweet (some of) those bugs will be cool.

[hallvors]

@karlcow is there a bug for "last week's fixes" script?

This feature can be added to the webhooks stuff we've moved to the webcompat.com server now.

[SemicolonExpected]

I'm not sure if you are still looking for suggestions, but you could also link to some relevant articles as well. I've seen a lot of "brands" tweet/share/etc articles that are relevant to the industry they're in. In this case you could share articles regarding web compatibility, which doesn't seem too narrow of a scope to focus in on.

[karlcow]

@SemicolonExpected We do time to time. But there are not that many ;)

[miketaylr]

I'm gonna close this as unactionnable and vague (the reporter is the worst). If anyone has suggestions, let's open specific issues for each type of info we might want to broadcast.