Last modified: 2013-03-11 07:33:01 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T47915, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 45915 - MediaWiki Developers, heads up: use "Twitter" for breaking news, software upgrades ("Some Sort of Notice for Breaking Changes")
MediaWiki Developers, heads up: use "Twitter" for breaking news, software upg...
Status: RESOLVED INVALID
Product: MediaWiki
Classification: Unclassified
General/Unknown (Other open bugs)
1.21.x
All All
: Unprioritized normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2013-03-08 23:00 UTC by T. Gries
Modified: 2013-03-11 07:33 UTC (History)
7 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description T. Gries 2013-03-08 23:00:48 UTC
Many OSS projects like ownCloud and Mailvelope and also security-issue related services like "Packetstorm" use "Twitter" for informing admins about 


+ new releases
+ breaking news
+ and so on

Only Wikimedia/MediaWiki does not use this, as far as I know.

See also mail discussion thread http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/68137


I suggest:

Use "Twitter" for breaking news, software upgrades ("Some Sort of Notice for Breaking Changes")
Comment 1 Alex Monk 2013-03-08 23:04:58 UTC
Seems we already do: https://twitter.com/mediawiki
Not sure who has access though.


BZ isn't the place for this.
Comment 2 T. Gries 2013-03-08 23:06:58 UTC
It's a good place - if the names of staff having access is added here.
Comment 3 T. Gries 2013-03-08 23:07:34 UTC
and to trigger some progress in that respect.
Comment 4 Chad H. 2013-03-08 23:16:06 UTC
I think we're trying to solve two things with one account. I don't think new releases necessarily should be announced at the same place we announce things that only affect developers (it's the reason we have the ultra-low-traffic mediawiki-announce, for comparison).

Announcing developer-esque changes reduces the usefulness of the main account. So if it's going to be done...it should be from a separate account.

But really, we have hard enough time getting people to follow the usual communication channels, so I doubt that adding *yet another* is a good idea.
Comment 5 Quim Gil 2013-03-09 18:45:06 UTC
I agree API breaks should be announced in advance, but I don't think including Twitter in some communication process is the answer for this. 

Then again if someone writes occasionally about API changes in a blog post or even a significant email and we get a heads up, I don't mind posting that through our social media channels. 

fwiw, info about Twitter et al can be found and discussed at https://www.mediawiki.org/wiki/Social_media
Comment 6 Krinkle 2013-03-11 07:33:01 UTC
(In reply to comment #4)
> But really, we have hard enough time getting people to follow the usual
> communication channels, so I doubt that adding *yet another* is a good idea.

For the record, these are primarily:
- https://lists.wikimedia.org/mailman/listinfo/mediawiki-announce
- https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce
- https://lists.wikimedia.org/mailman/listinfo/wikitech-announce

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links