Hm, but it is already deployed on MWW and Test wikis, isn't it? It was in recent's section in all the issues before so I don't quite understand need to change the location. But I'm not a great fun of any changes of things I'm used to at all :) Perhaps others should leave a comment about that piece.

Well if the changes you don't want to put in future's yet are really quite minor then I think it's OK for me. Thought I can't see how it'd harm to advance notify about them and then announce the changes after deployment again either. Latter way could be useful for users who read tech news on tech forums and do it quite irregularly.

But any way there will be always topics with panic about what happened right next to the section with tech news which explains it :)

---Base 22.08.2014 18:44, Guillaume Paumier написав(ла):

Hi Bohdan,

On Fri, Aug 22, 2014 at 4:46 PM, Bohdan Melnychuk base-w@yandex.ru wrote:

...

brr, somewhat confusing. Why the news about MW version is on Future changes section?

Tech News is sent on Monday, and the new version is deployed on Tuesday and Thursday, so it makes more sense to call it a "future change".

...

And there are no other recent changes? Sad( I didn't quite understand about "moved some of the non-urgent items to next week, so that people learn about them when they can actually see the changes and test the new features " you mean that they'd be already deployed at the time of puplication next issue? Or just nearer in future?

Yes, I mean that the changes will be already deployed at the time of publication. There are no "Recent changes" this week, but they'll be in the "Recent changes" next week. That way, users who read Tech News can test the new features as soon as they learn about them. Otherwise, they need to wait several days before testing, and they might forget about it.

Note that this is only for things that don't disrupt people's workflow. For disruptive changes, we still want to give them advance warning.

I hope this is clearer; let me know if it isn't :)

2014. 8. 23. 오전 12:30에 "Philippe Verdy" verdy_p@wanadoo.fr님이 작성:

I think that the choice of Meta-Wiki for fosting cross-wiki personal CSS

and javascript is not a good choice. All wikis are already linked to Commons that scales far better for all users, rather than Meta-Wiki which is still small and not made for hosting these personal contents for millions users

Commons is for media repository (images, videos, etc) , not for personal contents like global.js/css. Also, Meta is probably chosen for global.js/css storing location because already a number of users (including me) uses global.js/css on Meta, not Commons.

In addition there are far lot more admns and people helping on Commons

than on Meta-Wiki, and there are also some good translations in this multilingual site.

(but maybe developers think that the exploding growth of Commons causes

some long term risks for users as Commons has now difficulties to find backuping mirrors due to its volume)

Now we can expect many more users visiting Meta-Wiki and helping to

develop its content (notably pages about policies, chapters, groups; strategic development; grants...)

2014-08-22 16:15 GMT+02:00 Guillaume Paumier gpaumier@wikimedia.org:

...

Greetings,

The latest tech newsletter is ready for early translation: https://meta.wikimedia.org/wiki/Tech/News/2014/35

I'm planning to send the newsletter on Monday morning (UTC), as usual. The existing translations will be posted on the wikis in that language.

This week's issue is very short because I've moved some of the non-urgent items to next week, so that people learn about them when they can actually see the changes and test the new features. It's so short that it took me only 5 minutes to do the French translation :)

I may make a few edits tomorrow (and remove empty sections), but the content should generally remain fairly stable. I'll let you know tomorrow in any case.

Let me know if you have any questions, comments or concerns. As always, I appreciate your help and feedback.

Thanks!

-- Guillaume Paumier

---

Translators-l mailing list Translators-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/translators-l

---

Translators-l mailing list Translators-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/translators-l

-- Yena Hong (Revi) http://www.revi.pe.kr -- Sent from Android --

I didn't understand what your statement has to do with translation or the tech news issue itself but if saying about these news it seems to be good choice for me. Metawiki is common place for global.js and global.css of many global users. As well as e.g. global settings for some tools. Not saying about the fact that it's steward's nest with all actions and request pages that some of that :) Commons' community is global in some way but not in the same way as is needed imho. Also if consider not Meta then why actually commons? Scripts and styles are more sort of content expected on mww than on commons, imho. What do you mean about linking? Are there many wikis without a ling to Meta-wiki? All somewhat experienced local wikimedians know that Meta's central coordination place, imho. --Base

22.08.2014 18:29, Philippe Verdy написав(ла):

I think that the choice of Meta-Wiki for fosting cross-wiki personal CSS and javascript is not a good choice. All wikis are already linked to Commons that scales far better for all users, rather than Meta-Wiki which is still small and not made for hosting these personal contents for millions users

In addition there are far lot more admns and people helping on Commons than on Meta-Wiki, and there are also some good translations in this multilingual site.

(but maybe developers think that the exploding growth of Commons causes some long term risks for users as Commons has now difficulties to find backuping mirrors due to its volume)

Now we can expect many more users visiting Meta-Wiki and helping to develop its content (notably pages about policies, chapters, groups; strategic development; grants...)

2014-08-22 16:15 GMT+02:00 Guillaume Paumier <gpaumier@wikimedia.org mailto:gpaumier@wikimedia.org>:

Greetings,

The latest tech newsletter is ready for early translation:
https://meta.wikimedia.org/wiki/Tech/News/2014/35

I'm planning to send the newsletter on Monday morning (UTC), as usual.
The existing translations will be posted on the wikis in that
language.

This week's issue is very short because I've moved some of the
non-urgent items to next week, so that people learn about them when
they can actually see the changes and test the new features. It's so
short that it took me only 5 minutes to do the French translation :)

I may make a few edits tomorrow (and remove empty sections), but the
content should generally remain fairly stable. I'll let you know
tomorrow in any case.

Let me know if you have any questions, comments or concerns. As
always, I appreciate your help and feedback.

Thanks!

--
Guillaume Paumier

_______________________________________________
Translators-l mailing list
Translators-l@lists.wikimedia.org
<mailto:Translators-l@lists.wikimedia.org>
https://lists.wikimedia.org/mailman/listinfo/translators-l

---

Translators-l mailing list Translators-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/translators-l