Wed, Apr 24
I've now adjusted the submission controls to have two boxes - one for VE, one for code. This has propagated to all the Spaces. Not the prettiest, but it gets the job done! Thank you all. https://wikimania.wikimedia.org/wiki/Template:Submission_Controls
Apr 19 2019
The poster session page - for ease of reference - is this: https://wikimania.wikimedia.org/wiki/2019:Poster_session
Apr 16 2019
@Urbanecm I'm sorry if the "2019" namespace is confusing the system... this was the method that @Eric_Luth_WMSE and I came up with to make the wiki "future proof" for being able to handle future wikimanias. Previously every wikimania gets its own wiki, which is an unnecessary duplication in the opinion of many, but which does create the problem of how to deal with previous wikimania's content without merely overwriting it. We assumed a namespace which indicates the year is the best way to do that. e.g. 2019:Schedule, 2020:Schedule, 2021:Schedule...
If however there's a better solution that would mean some other bugs would become redundant and save time yourself and others - please say so. We are not ideologically-wedded to the 2019 namespace, it's just a solution to a problem we know will arise in the future. :-)
I confirm that the signature issue is resolve! It now works in VE by automatically converting ~~~~ AND also the button for 'insert signature' is enabled. Thank you for such quick action @Sebastian_Berlin-WMSE :-)
Apr 15 2019
I have now subst'ed the button and the form to the Poster session page, and then created a test page within it:
Apr 14 2019
I have greatly updated the generic submission form with many of the elements I mentioned in my comment on Friday: https://wikimania.wikimedia.org/wiki/Template:Submission_Form
- I have also created the associated "open submission" template, https://wikimania.wikimedia.org/wiki/Template:2019:Open_submission
- and the matching category https://wikimania.wikimedia.org/wiki/Category:2019:Submissions
Apr 12 2019
requested small adjustments to the Template:Submission Form:
- I think you can force no table of contents
- each 'space's submission form should categorise the submission to that space specifically e.g. "glam submissions". So the leaders of that space can find theirs, and only theirs.
- The top of each submission should also include some Wikimania equivalent of this template https://meta.wikimedia.org/wiki/Template:GLAMTLV2018_open_submission
- Each subheading should have some visible explanatory text. e.g. the 'type' should give a list of the allowed options. the 'relationship to theme' should have a short sentence that links to the [[theme]] page...
Apr 11 2019
With @Sebastian_Berlin-WMSE 's comment here, I'm thinking I have to agree with him...
While I vastly prefer the improved user interface of the formWizard, I think we should also not introduce more technical complexity for the 'leaders' . At least the preload system is something that Wikimedians are familiar with even if it is ugly. It is less ugly than it used to be, i see, because the test module you created loads directly into Visual Editor (I'd not seen that before, which is a nice touch).
Apr 9 2019
That certainly doesn't look user-friendly for the person setting up the form...
But are you (or @Sebastian_Berlin-WMSE ) able to bring this across today(?)
looks very user friendly on the user-side.
- How hard is it to set this tool up on the Wikimania wiki?
- How hard is it to adjust the text that appears in the form (for the leaders of the spaces to adjust to their needs)?
Apr 8 2019
Dec 10 2018
Those are viable options for making the results of a query “permanent” @abian - thank you for putting the time into thinking about the problem. The second option is quit clever and solves 90% of what I’m suggesting. However...
Dec 4 2018
Dec 3 2018
Dec 2 2018
Relatedly: @Lea_Lacroix_WMDE & @johl recommended FRAB - http://frab.github.io/frab/ - which has many of the desired features above (but not oAUth) and seems to have fewer technical dependencies compared to Indico (see a summary of these done by @JeanFred over on T210952) Also, we have connection to the developers (including Jens himself) as it's built by and for the Chaos Computer Club at their conference (Chaos Communication Congress).
With Ellie, Irene, JamesF, Phoebe, we have identified several options to do this. A summary is:
- MediaWiki (which was used for most wikimanias in the past, but has been deemed not fit for the logistical needs of wikimania and the templates managing submissions etc are not easy to operate. It also requires lots of secondary systems (spreadsheets) to track private info, conversations, acceptances...
- third party hosted and paid software “EasyChair” has been used twice (esino Lario, Cape Town) and is very cumbersome, not tailored or tailorable to our needs. Very difficult to export from. However, as a hosted solution it was at least “ready to go” when we wanted to start.
- some kind of “build our own from scratch” option - which might be ideal but not viable for the 2019 wikimania
- Indico is a floss, host your own, system built by CERN for their own conference needs. Theoretically it can handle the whole conference lifecycle - from submission through reviewing, registration, scheduling and presenting - and with oAuth should mean we don’t need separate logins than the existing MediaWiki user accounts. However, it may require a lot of tweaking and database management to set up.
- there are many other paid solutions out there, but they can become very expensive and are not future-proof because you can’t extract the data necessarily.
Nov 11 2018
Aug 20 2018
Mar 13 2018
Nov 3 2017
Oct 22 2017
Jul 19 2017
Jul 11 2017
@Jdlrobson if you would like to close this ticket, please close it as "won't fix" rather than '"resolved". It is not resolved at all - the question has simply been declared invalid.
This is not a request for major renovations - it was just a small bug!
Mar 1 2017
Not specifically related to WLM, but Europeana leadership - who are already discussing potential ideas with Europea-Nostra and others - have recently asked me to identify if there's a major Wikimedia campaign (or proposed campaign) they could be part of or lead. It seems everyone is interested in doing *something* but no one is super-sure what that thing should be. But, at the very least - Europeana is willing and able to try to build a project that has Wikimedia at its centre, if we can come up with a project that makes sense for all stakeholders.
Feb 13 2017
I'm not sure if this is the best place to ask this - but did the people interested in this bug know about the 2017 IIIF conference happening in June at the Vatican? http://iiif.io/event/2017/vatican/#iiif-conference---the-vatican---2017 Calls for proposals close on 23 February (in 10 days from when I'm writing this comment),
If I understand correctly, IIIF would be something that could be highly relevant to the Structured Data On Commons project, and therefore potentially worth pursuing under that frame of reference?
Dec 7 2016
@MusikAnimal yes, that is a specific case, but it's just a case that I know of.
The hashtag function is a potentially good one for tracking an editathon (especially a distributed event) because it allows people to self-identify individual edits across any page that the editor themself says are related to the topic - even if the event coordinator didn't think of that.
Dec 5 2016
@MusikAnimal My specific use-case for this request is based on this project: https://www.wikidata.org/wiki/Wikidata:Europeana_Art_History_Challenge/Data
Which is tracking 280 specific paintings (ten per E.U. country) and encouraging people to write about their own country's paintings & translate articles about each others'. As you can see from that big table of translations there are a fixed number of languages being tracked, and a fixed number of Wikidata items. However there is NOT any one Wikipedia language edition in which ALL of the paintings exist as an article. The ONLY place where they ALL exist is in Wikidata.
Nov 29 2016
Thank you very much. Yes - that does work.
Oddly though, my computer is NOT set to US english standard - it is DD/MM/YYYY. But that's not your problem I suspect :-)
Aug 4 2016
The other discussion - T94298 - is about redesigning the layout of the mobile footer to remove the 'last edited by' section. I am not expressing an opinion on that issue. THIS bug is about indicating that something which is a link, is somehow identifiable as a link. That could be underlined, blue, chevron, some kind of shading to indicate a button, whatever.
But, since linking is apparently no longer a thing on the internet, I guess that means you can close this bug as 'wontfix'.
@Nirzar I think either of those two mockups are fine concepts - my only point is that when there's something that's a link, the fact that it is clickable should be made evident. For example, in the first mockup you provided the "edited by 72 members" doesn't pass this test because there's no way to know that it goes to the history page.
Jul 13 2016
I've just tested the new change with the person who reported the problem to me in the first place. When logged in (even after logging out and back in again) the problem persisted on English and Catalan Wikipedias (not any other language WP).
Jun 13 2016
Thigks like these:
A) "map of the the current location of the artworks in the virtual exibition"
B) "map of birthplaces of artists in the virtual exihibition"
Jun 9 2016
Apr 14 2016
This task was listed months ago, and the project starts tomorrow.
Mar 17 2016
This is now a higher priority (for me at least :-) ) because have the drafts of the country pages of the project and need to build the tables to encourage people to "click here to translate this article".
Mar 3 2016
To clarify what is actually being requested:
Is there any progress on this please?
Feb 10 2016
Really good point @Elitre. I'd forgotten about pages where "signup" was the primary activity. Another good example is the wikidata weekly status newsletter subscription page. People are requested to leave not only their name, but also the specific wiki (since we don't yet have 'global user/talk pages yet): https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Wikidata
I'm NOT trying to be pushy, but I'm just wondering what the status is of this task?
@Jdlrobson - I do indeed the new direct link to the userpage with the 'contribs' link at the top helps a LOT. Thank you.
@Esanders, yes I'm aware that you can create a signature (or other mediawiki things like italics or links) by putting in the code into VE... But that's not really the point here...
Feb 4 2016
Feb 3 2016
The actual 'competition' component will begin in April. However, as you can see at the Dynamic list of items I've already tagged with the relevant propoerty - https://tools.wmflabs.org/listeria/dynamic.html#list=53 - I have about 200 items marked up already and I am currently building the project homepage https://www.wikidata.org/wiki/User:Wittylama/280
Feb 2 2016
Feb 1 2016
Jan 29 2016
That indeed fixed it. Don't know how or why...
Jan 20 2016
Jan 18 2016
Just came here to report the exact same bug. I just made a VE edit in en.wp and the related articles then came up appearing on top. This was the edit - https://en.wikipedia.org/w/index.php?title=Anu_Singh&type=revision&diff=700491912&oldid=686000746 See attached screenshot for how it appeared on my screen.
Jan 11 2016
Dec 23 2015
My only position on this issue would be not to "reinvent the wheel'. I prefer if you choose "logged in" rather than "autoconfirmed" as the measurement of whether someone is sufficiently "interested" to warrant showing them more features - because it is the lower bar for entry and is also a feature that is a standard binary option across all wikis (whereas the level at which autoconfirmed is set can be adjusted on a per-wiki basis [I think]).
Dec 18 2015
Dec 16 2015
Dec 14 2015
As requested over on T116676, I've now added my various comments on the talkpage of the project: https://www.mediawiki.org/wiki/Talk:Reading/Web/Projects/Read_more
I've now added my various comments on that talkpage. Cheers.
As mentioned in: T116676#1877895
My mistake - didn't see that this feature was called "read more", was looking for "related articles" instead. Yes, the beta-features tool is working correctly. This is just user error (though, putting the phrase "related articles" in the beta feature description might help others who are similarly dim.
hi @bmansurov. I created T121402 specifically for this issue as I wasn't sure if this phabricator ticket was the correct place to put things. In it, I added some more detail (like that when I tried to see how it displayed for a different user I couldn't get it to load on ANY page.
I am now seeing "related articles" appear at the bottom of english Wikipedia articles.
Dec 8 2015
Dec 7 2015
This no longer seems to be a problem.
I can now create a statement AND add a reference for that statement at the same time.
Fair enough @Quiddity ;-) Cross-wiki notifications/watchlists is very important!
Dec 4 2015
There's a related discussion on MediaWiki.org about beta features: https://www.mediawiki.org/wiki/Topic:Ss54yq1w3twctqsj
TheDJ and Jdforrester are suggesting that the Beta Features system would need to be completely rebuilt to be able to scale anyway and that it wouldn't catch the kind of bugs I'm suggesting it ought to.
Dec 3 2015
Thank you @CCogdill_WMF!
Dec 1 2015
Probably pertinent to this discussion is the fact that a user who has opted in to the " Automatically enable all new beta features" mode will not know when a new Beta feature has been added to their interface. Equally, if a feature's behaviour has changed since it was enabled the user might not know either.