Thanks for being on this list and helping communicate about technology on Wikimedia sites.
What kinds of discussions or notifications would you like to have on this list? Or in general, if you don't think they quite belong here?
In my perspective, there should be two things on this list:
* Invitations to test new features. "Testing" in this case is something that can be done by somebody who is an end user who has an "early adopter" character and who is curious about technologies, but who is not necessarily a developer. The new feature must be set up online somewhere: in labs, as an opt-in feature in an existing Wikipedia or Wikisource, in translatewiki.net or some other site. It usually shouldn't be needed to install software on your own computer to test features announced here - installing MediaWiki is too hard for non-developer users. Announcement of Visual Editor features deployments in Meta is a good example of this.
* Announcements about new features that break existing gadgets, templates, features or content in existing projects, and require change in their code. The change is not necessarily something that the ambassador can do himself or understand completely, because the ambassador is not necessarily a coder, but it must be something that the ambassador must be able to convey to the techie types in his community. The announcement of the $.browser deprecation by Krinkle a few days ago is a good example of this.
Of course, there can be other opinions.
-- Amir Elisha Aharoni · אָמִיר אֱלִישָׁע אַהֲרוֹנִי http://aharoni.wordpress.com “We're living in pieces, I want to live in peace.” – T. Moore
2012/11/10 Sumana Harihareswara sumanah@wikimedia.org:
Thanks for being on this list and helping communicate about technology on Wikimedia sites.
What kinds of discussions or notifications would you like to have on this list? Or in general, if you don't think they quite belong here?
-- Sumana Harihareswara Engineering Community Manager Wikimedia Foundation
Wikitech-ambassadors mailing list Wikitech-ambassadors@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-ambassadors
On Sat, Nov 10, 2012 at 1:06 PM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
In my perspective, there should be two things on this list:
- Invitations to test new features. "Testing" in this case is
something that can be done by somebody who is an end user who has an "early adopter" character and who is curious about technologies, but who is not necessarily a developer. The new feature must be set up online somewhere: in labs, as an opt-in feature in an existing Wikipedia or Wikisource, in translatewiki.net or some other site. It usually shouldn't be needed to install software on your own computer to test features announced here - installing MediaWiki is too hard for non-developer users. Announcement of Visual Editor features deployments in Meta is a good example of this.
- Announcements about new features that break existing gadgets,
templates, features or content in existing projects, and require change in their code. The change is not necessarily something that the ambassador can do himself or understand completely, because the ambassador is not necessarily a coder, but it must be something that the ambassador must be able to convey to the techie types in his community. The announcement of the $.browser deprecation by Krinkle a few days ago is a good example of this.
I would add announcements about new features which are available or can be requested (e.g. "from today wikis can request ArticleFeedback to be turned on").
I would prefer not to have discussions here (with the exception of meta-discussions about the list itself, like this one); there are several channels for that already, and keeping the list low-traffic, high-relevance is much more valuable. On the other hand, pointers to discussions in other places (about how upcoming features should work, for example) would be useful.
On Sat, 10 Nov 2012 14:09:21 +1100, Tisza Gergő gtisza@gmail.com wrote:
On Sat, Nov 10, 2012 at 1:06 PM, Amir E. Aharoni < amir.aharoni@mail.huji.ac.il> wrote:
In my perspective, there should be two things on this list:
- Invitations to test new features. "Testing" in this case is
something that can be done by somebody who is an end user who has an "early adopter" character and who is curious about technologies, but who is not necessarily a developer. The new feature must be set up online somewhere: in labs, as an opt-in feature in an existing Wikipedia or Wikisource, in translatewiki.net or some other site. It usually shouldn't be needed to install software on your own computer to test features announced here - installing MediaWiki is too hard for non-developer users. Announcement of Visual Editor features deployments in Meta is a good example of this.
- Announcements about new features that break existing gadgets,
templates, features or content in existing projects, and require change in their code. The change is not necessarily something that the ambassador can do himself or understand completely, because the ambassador is not necessarily a coder, but it must be something that the ambassador must be able to convey to the techie types in his community. The announcement of the $.browser deprecation by Krinkle a few days ago is a good example of this.
I would add announcements about new features which are available or can
be
requested (e.g. "from today wikis can request ArticleFeedback to be
turned
on").
I would prefer not to have discussions here (with the exception of meta-discussions about the list itself, like this one); there are
several
channels for that already, and keeping the list low-traffic,
high-relevance
is much more valuable. On the other hand, pointers to discussions in
other
places (about how upcoming features should work, for example) would be useful.
+1 x2
The purpose of the list over the wiki is that it is real time, and it is *push*, so ...
* Invitations / opportunities : including the priority of what is the next in the process, skills wanted, time requested, with whom you would be working : clear notices of where help or review is wanted by the general user and/or sysop, and clarity in the preferred means of reporting .. via bugzilla, via wikis, via ambassadors
* Context : wiki communities, as it would be great to see either languages and/or the sister communities represented, so there is some conduit through to the forums so they are kept informed. Sometimes the detail to understand the context of changes
I also agree about not wanting the list of NOTs that were expressed.
Regards, Andrew
Hi,
100 % agree with previous answers :-)
To sum it up in a few words: - new features (including features available on request) - future features (and demos) - breaking changes (and workarounds) - technical discussions go to wikitech-l, not here
Best regards,
On 11/10/2012 08:15 AM, Jérémie Roquet wrote:
Hi,
100 % agree with previous answers :-)
To sum it up in a few words:
- new features (including features available on request)
- future features (and demos)
- breaking changes (and workarounds)
- technical discussions go to wikitech-l, not here
Best regards,
I thank all of you for your thoughts on this topic (in this thread and in "Local discussions about how to improve communication between users and developers"), which have gone into Guillaume Paumier's thinking about improving Wikimedia technical communications. https://www.mediawiki.org/wiki/Technical_communications is where you can see the work he's doing on that.
Thank all of you for your ambassadorship this year, and happy 2013. :-)
Hi,
I'd like to add my thanks. Earlier in 2012, we considered turning this list into a more conversational venue to encourage 2-way communications instead of primarily announcements. This thread has proved that that's not what subscribers are after, and I completely understand why: there are other existing venues for that. I'm glad that you shared your opinions about how the list should and should not be used.
On Mon, Dec 31, 2012 at 11:25 PM, Sumana Harihareswara sumanah@wikimedia.org wrote:
I thank all of you for your thoughts on this topic (in this thread and in "Local discussions about how to improve communication between users and developers"), which have gone into Guillaume Paumier's thinking about improving Wikimedia technical communications. https://www.mediawiki.org/wiki/Technical_communications is where you can see the work he's doing on that.
https://www.mediawiki.org/wiki/Technical_communications/Fall_2012_consultati... is actually more specific, and I've also rewritten https://meta.wikimedia.org/wiki/Tech/Ambassadors . Opinions and feedback are appreciated (on the talk page or here).
wikitech-ambassadors@lists.wikimedia.org