Sat, Jun 2
For some reason @Aklapper is on most task I create (I guess for triage reasons) but not on this one. Please let me know if I should or not add you manually in that kind of case.
I looked at the Probox documentation but didn't saw anything related to the "join" button and the role list.
The list of activity is given on Commons:
I set up the probox template
So either someone already skilled on this installation process should claim/be-assigned this task, or it will wait that I can have time to read the documentation, and possibly get sufficient privileges on corresponding targeted wikis.
Hi @Denny any news regarding this? What's your mind concerning my additional more precise questions on lexical data?
Sun, May 27
May 25 2018
May 23 2018
Sorry, I've been busy on other activities lately, I'll catch up and give feed back as soon as I can.
May 19 2018
To give more context, the goal would be to enable archiving this discussion on Meta, where the license is a requirement.
May 18 2018
Seems that https://meta.wikimedia.org/wiki/Template:Probox is exacltly what we need :)
I just endorsed a project on Meta with a button which already do what we should aim: https://meta.wikimedia.org/wiki/Grants:Project/Rapid/UG_ELiSo/Outreach_leaflets_2018
May 14 2018
Hi @Denny, here are a small set questions that are hopefully simple and concrete:
May 13 2018
T115691 have something about the white line
@Ivanhercaz any news on this?
May 12 2018
May 8 2018
Also I think that if we want to really expand our community outside Europe and North America, it would be important to provide an infrastructure that ease contribution and reuse without too much legal concerns in places where we expect to make serious outreach to improve our community diversity.
Thank you @Tgr for bringing more clarification through distinction in the discussion. (also I'm not sure if thanks messages are welcome on phabricator tickets, but on the other hand I see no way to "thank" an individual answer…
May 7 2018
For 3. we might promote it in a different manner that don't limit the topic to Valentine day, but also other day of love. Actually, we could turn it to "day dedicated to love".
We could have also
Book covers is tricky, we have to be sure the book cover is not a ongoing copyrighted material. But >100 books are probably ok. So I would say, we promote that as "cover of ancient books related to love" and we give more information in details:)
Whatever list we come from at the end, I think we should keep one or two extra "yet to determine" categories in mind, and take care to have resource for prizes on it. We don't really what to expect, so it's better if we can give ourself a bit of flexibility.
May 5 2018
The current indication to edit this section would no work anymore if the section is just moved to the subpage, at minimun, the link that invite to edit the support section should be changed.
https://meta.wikimedia.org/wiki/User:Ivanhercaz/Tests seems perfect to me as far as the appearance goes, than you @Ivanhercaz we only need to add the functional part edit the page, possibly first checking if user is logged.
Until we have a wll at wikimedia dot org or something like that, @Wikilover90 created wikiloveslove at gmail dot com
I think that before we launch that, it would be better to have a simple "support" blue button, that directly edit the page, without requiring to type any wikitext.
I started something on the second point, see https://commons.wikimedia.org/wiki/Commons:Wiki_Loves_Love/Appreciation
May 4 2018
The second point is purely about writing some promotional, isn't it?
Ok. So far I thanked people who signed the support section on Meta through the Mediawiki "thank" feature.
May 3 2018
I'm not sure to understand the exact feature exposed here.
As a first comment, please let me make clear that I'm open to any change on the ticket description if it is judged too partial. The goal is to resolve the issue stated in the title, title which was validated by @Lea_Lacroix_WMDE. But the extensive description of the issue wasn't through this validation process. So feel free to edit it (if you do have edit rights for that), or ask me to make all the changes you think appropriate.
Apr 30 2018
Please highlight anything you think relevant for our WLL project in
So far, discussion mainly happened in Telegram. It's fine to discuss around, but not very handy for project management. We possibly will divide with sub-contest if some chapter want to take care of more local specific nurturing. But so far we didn't arrested the processes and scope. At some point in the telegram conversation it was suggested that we move to phabricator so we benefit from its feature for our organisational needs.
Apr 13 2018
Feb 28 2018
Thank @Nuria for the ticket. I'm not sure the description is clear here. My initial demand, which conducted to this ticket, was to have a the number of active Wikisource contributors, regardless of locale versions. This, in order to evaluate number of attendees we might target for the next Wikisource conference.
Jan 8 2018
To make sure that what I'm talking about is clear, here is a screenshot:
Hi @Nikerabbit thank you for taking care and put attention on that. :)
Jan 2 2018
Ok, thank you @Nikerabbit. Then it would be good to add this shortcut inter parentheses. :)
Dec 31 2017
Dec 25 2017
So I started to play with discourse. One thing I wonder is what scope should this new discussion tool should target to have good chances to be complementary rather than a competitor with existing canal – if there is no long term goal to close some of them.
Dec 23 2017
I didn't thought of the possible abuse, thank you @MarcoAurelio and @matmarex for relieving the potential problems. I agree with @Urbanecm that potential abuse should be taken into consideration without abandoning completely the feature.
Dec 20 2017
Dec 8 2017
See https://www.mediawiki.org/wiki/User:Psychoslave/generic_glossary/eo for some related works
Nov 12 2017
I replied to https://meta.wikimedia.org/wiki/2017_Community_Wishlist_Survey/Wikidata/Add_en-us_as_a_separate_language which is linking here as follow:
Nov 1 2017
It would also be useful to be able to use a set of possible values provided by some template/module.
Support of a dark skin was not really my point, although I would welcome such a proposal. I would expect the development of a skin to be a far more huge effort than proposing the icons in both dark and light flavour.
Oct 31 2017
I will just have one question: are this icon designed with non-white background use in mind?
Oct 30 2017
Oct 28 2017
For draft template I'm working on for the Wikitionary, I came with things like |définition.1.4.exemple.2.description =. That is description of 2nd example of the 4th subdefinition of the first main definition. That might be a somewhat extreme example, but that would be nice to take it into account while treating this ticket.