[Bug 57577] I18n issue in flow
https://bugzilla.wikimedia.org/show_bug.cgi?id=57577 Nemo changed: What|Removed |Added URL||https://translatewiki.net/w ||iki/Thread:Support/About_Me ||diaWiki:Flow-rev-message-re ||ply-bundle/en_%283%29 CC||federicol...@tiscali.it -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57577] I18n issue in flow
https://bugzilla.wikimedia.org/show_bug.cgi?id=57577 --- Comment #1 from Bingle --- The WMF core features team tracks this bug on Mingle card https://mingle.corp.wikimedia.org/projects/flow/cards/524, but people from the community are welcome to contribute here and in Gerrit. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 54514] 1= plural rule not working for Russian (and maybe other languages)
https://bugzilla.wikimedia.org/show_bug.cgi?id=54514 --- Comment #2 from Siebrand Mazeland --- This issue is being tracked in mingle at https://mingle.corp.wikimedia.org/projects/internationalization/cards/3855 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57577] New: I18n issue in flow
https://bugzilla.wikimedia.org/show_bug.cgi?id=57577 Web browser: --- Bug ID: 57577 Summary: I18n issue in flow Product: MediaWiki extensions Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: Flow Assignee: wikibugs-l@lists.wikimedia.org Reporter: niklas.laxst...@gmail.com CC: ebernhard...@wikimedia.org, oke...@wikimedia.org, sp...@wikimedia.org Classification: Unclassified Mobile Platform: --- Reporting here as I'm unsure how to get the attention: https://gerrit.wikimedia.org/r/#/c/96418 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 49088] Make archive table partially accessible on Wikimedia Labs
https://bugzilla.wikimedia.org/show_bug.cgi?id=49088 --- Comment #11 from Sean Pringle --- The archive table should now be replicating to labs with ar_text and ar_comment redacted. The views should be ready shortly. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41745] Remove ptwiki and ptwikinews from Emergency Captcha mode
https://bugzilla.wikimedia.org/show_bug.cgi?id=41745 --- Comment #44 from Nemo --- FYI, those looking for pretty compact graphs on the effects of this change can now use Erik Zachte's http://stats.wikimedia.org/EN/EditsRevertsPT.htm (updated more or less monthly). In particular http://stats.wikimedia.org/EN/PlotEditsPT.png shows the peak in unregistered (but also registered?) editing and http://stats.wikimedia.org/EN/PlotRevertsPT.png demonstrates how the amount of vandalism/reverts was not higher than the seasonal peak in 2012. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 56524] pywikibot transliteration should support more scripts
https://bugzilla.wikimedia.org/show_bug.cgi?id=56524 ebraminio changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #9 from ebraminio --- Reopened for Chinese transliteration -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 46212] Dump stats: update edit/revert stats monthly
https://bugzilla.wikimedia.org/show_bug.cgi?id=46212 Nemo changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Nemo --- (In reply to comment #4) > I see a problem in http://stats.wikimedia.org/EN/EditsRevertsPT.htm , > recently > updated: the graphs, generated 2013-07-23, show data only till January 2012, Graphs generated 2013-11-22 like http://stats.wikimedia.org/EN/PlotEditsPT.png with data till October seem to have everything again. I'm not so sure because the last section shows only 64 % of a year, but it's probably just some rounding and not like missing 18 months. Thanks! -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 22390] Purge foreign pages using an image/media file where this data is available
https://bugzilla.wikimedia.org/show_bug.cgi?id=22390 Gerrit Notification Bot changed: What|Removed |Added Status|NEW |PATCH_TO_REVIEW -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 22390] Purge foreign pages using an image/media file where this data is available
https://bugzilla.wikimedia.org/show_bug.cgi?id=22390 --- Comment #6 from Gerrit Notification Bot --- Change 97659 had a related patch set uploaded by Aaron Schulz: Added support for purging backlinks in the wiki farm https://gerrit.wikimedia.org/r/97659 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57491] Make betafeatures_user_counts table available
https://bugzilla.wikimedia.org/show_bug.cgi?id=57491 --- Comment #3 from Sean Pringle --- All fine I think. The betafeatures_user_counts table is not involved in the redaction process, so it should be already replicated normally to labs and need only the relevant views setup using Coren's perl scripts. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 56524] pywikibot transliteration should support more scripts
https://bugzilla.wikimedia.org/show_bug.cgi?id=56524 Amir Ladsgroup changed: What|Removed |Added Status|PATCH_TO_REVIEW |RESOLVED Resolution|--- |FIXED --- Comment #8 from Amir Ladsgroup --- Both of patches got merged. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 41363] Create simple interface for adding a page redirect to MediaWiki core
https://bugzilla.wikimedia.org/show_bug.cgi?id=41363 Nemo changed: What|Removed |Added CC||federicol...@tiscali.it --- Comment #6 from Nemo --- (In reply to comment #4) > Can someone elaborate on some of the most common use cases for creating > redirects to give a bit more background to this for new users not as > familiar. > > Also, is this a band aid? do we need to step back and think about the reason > redirects are created in the first place? Does mediawiki support the concept > of > page aliases? Does the redirected page need to continue to exist as a regular > wikipage after the redirect has happened? [[m:Help:Redirect]] contains the necessary educational material for the topic. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 55701] Using unchecked input as array keys may cause TypeErrors
https://bugzilla.wikimedia.org/show_bug.cgi?id=55701 Santhosh Thottingal changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Santhosh Thottingal --- https://gerrit.wikimedia.org/r/#/c/97068 ported this to MediaWiki. Marking fixed. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New feature for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #31 from Nemo --- This bug got hopelessly confusing with all these discussions about closures and whatnot, which should continue at bug 57569. If the outcome of this discussion is to work on this in core, this bug should be duplicated to bug 27311, which has clearer requirements, and other stuff added to its dependencies (as in, the "/managing" part of the summary, which was never asked so far; that can be blocked on bug 27311). -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 48835] Separate Cache-Control header for proxy and client
https://bugzilla.wikimedia.org/show_bug.cgi?id=48835
--- Comment #3 from Faidon Liambotis ---
We currently don't have a Client-Cache-Control header at all and I don't think
we should introduce it now with that name. Introducing just Surrogate-Control
and doing the VCL ping-pong you mentioned sounds more sensible to me. We'd need
a temporary header to store the client cache control, so we may end up using
Client-Cache-Control internally inside VCL as an interim header but I don't see
a reason for MediaWiki to use it. i.e. as I see it, the VCL could just be:
sub vcl_fetch {
if (beresp.http.Surrogate-Control) {
set beresp.http.Client-Cache-Control = beresp.http.Cache-Control
set beresp.http.Cache-Control = beresp.http.Surrogate-Control
unset beresp.http.Surrogate-Control
}
}
sub vcl_deliver {
if (resp.http.Client-Cache-Control) {
set resp.http.Cache-Control = resp.http.Client-Cache-Control
unset resp.http.Client-Cache-Control
}
}
I don't see any handling that we do now to preserve the backwards compatibility
you mentioned. Even if we do and I missed it, we can easily implement it as
"else" clauses above, no?
It's a pity that Varnish doesn't natively support Surrogate-Control natively,
indeed. Ironically, Squid 3 does in some form :) (so using it inside MediaWiki
may be generally useful). I guess we could provide patches to Varnish for the
long-term but VCL hacks seem viable in the short-term.
Note that the standard specifies a Surrogate-Capabilities request header to
signal the capability to handle Surrogate-Control. We could set it in Varnish
and MediaWiki could check for it, so you may avoid a configuration option.
Also note that the same Surrogate-Capabilities/Control mechanism could be also
used to signal ESI back and forth (this is defined in the spec). Yuri has used
X-Force-ESI (request) and X-Enable-ESI (response) for this purpose in the
mobile caches for his ESI testing. We could deprecate those in favor of a
unified Surrogate handling by core, especially while we move in the direction
of doing ESI.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 Nemo changed: What|Removed |Added Priority|Unprioritized |Normal CC||federicol...@tiscali.it --- Comment #13 from Nemo --- I've not read the discussion but I have to say the closure is quite straightforward: «the heart of the proposal: a new namespace for Drafts [...] This community discussion does not change the AfC process». It obviously doesn't entail any extension, nor special user permissions for the namespace for that matter; those can come later if wanted. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57528] Special:ListRedirects is missing some pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57528 --- Comment #8 from Ofra Hod --- (In reply to comment #0) > I have a wiki with Hebrew contents. There is a page titled "י. פרידמן" that > redirects to the page "יהושע פרידמן". The page "י. פרידמן" is missing from > the > list of redirects. > > Other pages, like "ל. גולדברג", "הנרי ו. לונגפלו" and "קריסטינה ג'. רוסתי", > are > also missing from the list of redirects. While all these examples contain > the > special character ".", some redirection pages with this character, such as > "א. > א. קאמינגס", do appear in the list. Having a "." in the redirection page > title > seems to be a necessary but not sufficient condition for the demonstration of > the bug. > > My wiki is in http://poetrans.shoutwiki.com. It turns out that having a "." in the redirection page title is NOT a necessary condition: the redicrection page "יוהן וולפגנג פון גתה" is missing from the redirect list, too. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57096] Uploading 605 MB file on Commons
https://bugzilla.wikimedia.org/show_bug.cgi?id=57096 Nitika changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #5 from Nitika --- Cannot access text of this book on Commons or Wikisource. The page does not download properly. I'm assuming this is due to heavy file size. For example: On Wikimedia Commons: https://commons.wikimedia.org/wiki/File:Konkani_Viswakosh_Vol2.pdf. Doesn't show the text of the page. On Wikisource: https://wikisource.org/w/index.php?title=Page:Konkani_Viswakosh_Vol2.pdf/390&action=edit&redlink=1. The page on right hand side is all black and doesn't download the page. Could you please look into this. Thanks Nitika -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 54606] Make tutorial video on how to use Bugzilla
https://bugzilla.wikimedia.org/show_bug.cgi?id=54606 Quim Gil changed: What|Removed |Added Assignee|q...@wikimedia.org |lettric...@gmail.com --- Comment #24 from Quim Gil --- It's a good first draft, but still needs more work. I have left my feedback. Andre and other readers of this report are encouraged to comment there as well. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New feature for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 Matthew Flaschen changed: What|Removed |Added Assignee|wikibugs-l@lists.wikimedia. |mflasc...@wikimedia.org |org | -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New feature for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 Matthew Flaschen changed: What|Removed |Added Summary|New extension for |New feature for |creating/managing new pages |creating/managing new pages --- Comment #30 from Matthew Flaschen --- Changing the title to reflect that we're going to look closer at where to put stuff, and a core feature flag is one possibility. It might allow easier and tighter integration/replacement of certain features (search pages, redlinks, etc), even though hooks remain an option. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57234] Override user-talk Echo notification with something more MassMessage-specific
https://bugzilla.wikimedia.org/show_bug.cgi?id=57234 Steven Walling changed: What|Removed |Added CC||bs...@wikimedia.org, ||rkald...@wikimedia.org, ||swall...@wikimedia.org --- Comment #2 from Steven Walling --- (In reply to comment #0) > Default notification looks something like "MediaWiki message delivery left a > message on your talk page in "subject line..."" > > We can probably make that more specific and relevant. Great idea. One of the nicer parts of MassMessage is that the Talk page message doesn't have to be signed by a bot. We should try and make Echo notifications do this as well. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 27935] squid cache of [[foo_(bar%29]] not purged
https://bugzilla.wikimedia.org/show_bug.cgi?id=27935 Tim Starling changed: What|Removed |Added Summary|Redirect to canonicalize|squid cache of |URLs (aka "squid cache of |[[foo_(bar%29]] not purged |[[foo_(bar%29]] not | |purged")| -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57500] Impossible to use https://www.mediawiki.org/wiki/Special:OAuth/initiate?format=&oauth_callback= style URL
https://bugzilla.wikimedia.org/show_bug.cgi?id=57500 Liangent changed: What|Removed |Added Blocks||57576 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57576] New: GET call to Special:OAuth/$par without query strings (but with Authorization header) shouldn't be redirected to pretty URLs
https://bugzilla.wikimedia.org/show_bug.cgi?id=57576 Web browser: --- Bug ID: 57576 Summary: GET call to Special:OAuth/$par without query strings (but with Authorization header) shouldn't be redirected to pretty URLs Product: MediaWiki extensions Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: OAuth Assignee: wikibugs-l@lists.wikimedia.org Reporter: liang...@gmail.com CC: aschulz4...@gmail.com, bjor...@wikimedia.org, cste...@wikimedia.org, dga...@wikimedia.org Depends on: 57500 Classification: Unclassified Mobile Platform: --- Because pretty URLs don't work. See bug 57500. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 48835] Separate Cache-Control header for proxy and client
https://bugzilla.wikimedia.org/show_bug.cgi?id=48835 --- Comment #2 from Tim Starling --- (In reply to comment #1) > We could do this the other way around and partially implement the > semi-standard (semi because it's from the W3C, not IETF) > Surrogate-Control header and leave Cache-Control intact for > end-users. Fastly, for example, seems to be suggesting users > to use this, so this may be a more compatible with the real world > alternative. Varnish uses the Cache-Control header in RFC2616_Ttl(), so I suppose it would be necessary to move the Cache-Control header out to some temporary pseudo-header in vcl_fetch, and to move it back into place in vcl_deliver. While the object is in the cache, Surrogate-Control would be copied into Cache-Control. Support for pass mode would theoretically be simpler with Surrogate-Control. Either way, there would have to be some backwards compatible handling in Varnish, to account for the progressive rollout of the new MW code. If Client-Cache-Control/Surrogate-Control is missing, Varnish would have to interpret Cache-Control in the old way. On the MW side, OutputPage could provide an interface allowing configuration of the mapping of headers: a) Old $wgUseSquid = false: * Client-Cache-Control -> Cache-Control * Surrogate-Control -> deleted b) Old $wgUseSquid = true; * Surrogate-Control -> Cache-Control * Client-Cache-Control -> deleted c) Surrogate-Control scheme: * Surrogate-Control -> Surrogate-Control * Client-Cache-Control -> Cache-Control d) Client-Cache-Control scheme: * Surrogate-Control -> Cache-Control * Client-Cache-Control -> Client-Cache-Control -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 56178] Security review of GLAM Wiki Toolkit
https://bugzilla.wikimedia.org/show_bug.cgi?id=56178 --- Comment #6 from dan --- • sanitized-exceptions: https://gerrit.wikimedia.org/r/#/c/97676/ -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 27935] Redirect to canonicalize URLs (aka "squid cache of [[foo_(bar%29]] not purged")
https://bugzilla.wikimedia.org/show_bug.cgi?id=27935 Tim Starling changed: What|Removed |Added Status|PATCH_TO_REVIEW |RESOLVED Resolution|--- |FIXED --- Comment #31 from Tim Starling --- Actually, this was probably fixed in May 2012, Ie38ae198b. Testing I did during the deployment of the above change supports this. But, the current patch was worth doing anyway, since after Ie38ae198b, all requests for non-canonical encodings were cache misses due to MW serving them with CC: private (this was confirmed in my testing today). The current patch makes them cache hits instead. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 22014] Caching problems with mobile_main_page
https://bugzilla.wikimedia.org/show_bug.cgi?id=22014 Bug 22014 depends on bug 27935, which changed state. Bug 27935 Summary: Redirect to canonicalize URLs (aka "squid cache of [[foo_(bar%29]] not purged") https://bugzilla.wikimedia.org/show_bug.cgi?id=27935 What|Removed |Added Status|PATCH_TO_REVIEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 --- Comment #12 from Gerrit Notification Bot --- Change 97675 had a related patch set uploaded by MZMcBride: Create "Draft" namespace on the English Wikipedia https://gerrit.wikimedia.org/r/97675 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 Gerrit Notification Bot changed: What|Removed |Added Status|NEW |PATCH_TO_REVIEW -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 Matthew Flaschen changed: What|Removed |Added See Also||https://bugzilla.wikimedia. ||org/show_bug.cgi?id=57315 --- Comment #11 from Matthew Flaschen --- (In reply to comment #6) > > We still need to specify things like: > > > > * who is allowed to create drafts. (e.g. Are anonymous users allowed to do > > so? > > I assume so but the proposal summary and closure don't specify.) > > * how to publish drafts > > * who is allowed to publish drafts > > * how do we tell users they can create/publish drafts, on search, redlinks, > > and other places > > * do we want to let people make drafts of pages that already exist? > > None of this is relevant to adding a new namespace and you know this. All of those questions are relevant. Some I certainly consider blockers. For example, I am strongly inclined to determine an initial permission model before we deploy it (that's not the only one). It is irrelevant how many lines it takes to create a dumb namespace. The questions are how it will function initially (which may include A/B testing multiple possibilities) and how it will relate to other features. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 Matthew Flaschen changed: What|Removed |Added See Also||https://bugzilla.wikimedia. ||org/show_bug.cgi?id=57569 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57575] updateCollation refers to $row when it is out of scope
https://bugzilla.wikimedia.org/show_bug.cgi?id=57575 --- Comment #2 from Gerrit Notification Bot --- Change 97670 merged by MarkAHershberger: Move reference to $row where it is in-scope and doesn't produce E_STRICT notices. https://gerrit.wikimedia.org/r/97670 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57575] updateCollation refers to $row when it is out of scope
https://bugzilla.wikimedia.org/show_bug.cgi?id=57575 Mark A. Hershberger changed: What|Removed |Added Status|PATCH_TO_REVIEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 27935] Redirect to canonicalize URLs (aka "squid cache of [[foo_(bar%29]] not purged")
https://bugzilla.wikimedia.org/show_bug.cgi?id=27935 --- Comment #30 from Gerrit Notification Bot --- Change 96941 merged by Tim Starling: Normalise the path part of URLs in the text frontend https://gerrit.wikimedia.org/r/96941 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #29 from Matthew Flaschen --- (In reply to comment #25) > The proposal to create the Draft namespace was partially to make things > easier on the homegrown solutions. It wasn't to render them unneeded through > software changes. It's true the closure said there was no immediate change to AFC. However, I don't agree that maintaining lots of bot- and userscript-based Draft processes is a key goal. The key goal is to "simplify the process of submitting draft articles" (as the closure put it). Steven was clear in the RFC comments: "I think we should take an experimental approach to this, objectively testing out how a new Drafts namespace should work." and "I want to test asking new article creators if they want to start a draft first before publishing to mainspace." There is a lot of MW software development that is not specifically requested by an RFC (including the original wiki software). It's always going to be a back and forth. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57575] updateCollation refers to $row when it is out of scope
https://bugzilla.wikimedia.org/show_bug.cgi?id=57575 Gerrit Notification Bot changed: What|Removed |Added Status|NEW |PATCH_TO_REVIEW -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57479] Unable to mount /public directories on queue nodes
https://bugzilla.wikimedia.org/show_bug.cgi?id=57479 Marc A. Pelletier changed: What|Removed |Added Status|UNCONFIRMED |ASSIGNED Ever confirmed|0 |1 --- Comment #4 from Marc A. Pelletier --- Yeah, I just checked and it's definitely broken. Annoyingly, autofs is really bad at restarting if any mounts are active, so there is little to do but drain the node from all jobs and wait for it to be idle before forcibly restarting it. I'm going to remove it from the queue allocation now and let it drain; it'll take a while before every job goes away (I don't want to disrupt running tools), but it won't get assigned for new jobs in the meantime so nothing will hit the broken /public -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57575] updateCollation refers to $row when it is out of scope
https://bugzilla.wikimedia.org/show_bug.cgi?id=57575 --- Comment #1 from Gerrit Notification Bot --- Change 97670 had a related patch set uploaded by MarkAHershberger: Move reference to $row where it is in-scope and doesn't produce E_STRICT notices. https://gerrit.wikimedia.org/r/97670 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57575] updateCollation refers to $row when it is out of scope
https://bugzilla.wikimedia.org/show_bug.cgi?id=57575 Mark A. Hershberger changed: What|Removed |Added Summary|updateCollation refers too |updateCollation refers to |$row when it is out of |$row when it is out of |scope |scope -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57575] New: updateCollation refers too $row when it is out of scope
https://bugzilla.wikimedia.org/show_bug.cgi?id=57575 Web browser: --- Bug ID: 57575 Summary: updateCollation refers too $row when it is out of scope Product: MediaWiki Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: Maintenance scripts Assignee: wikibugs-l@lists.wikimedia.org Reporter: m...@everybody.org Classification: Unclassified Mobile Platform: --- Today, while I was trying to enable profiling, I set $wgProfileToDatabase = true; and then ran php maintenance/update.php as suggested at [[mw:Manual:How_to_debug]]. I have error_reporting set to show E_STRICT and I noticed a few of the following: Notice: Undefined variable: row in maintenance/updateCollation.php on line 192 The reference to $row is outside of the foreach loop where $row is set, so I would expect it to often (if not always) be unset. I'm not sure if moving the reference to the inside of the foreach loop is the right fix, but it seems to work for me. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 56777] Cannot create account "Shinjiman" where formally had SVN access
https://bugzilla.wikimedia.org/show_bug.cgi?id=56777 Shinjiman changed: What|Removed |Added Status|NEW |RESOLVED Resolution|--- |FIXED --- Comment #4 from Shinjiman --- Hmmm, I can now log in to my account now after resetting onto the new password. Thanks Andrew for help to create the new account. :) -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #28 from Matthew Flaschen --- (In reply to comment #19) > Might I be so bold as to suggest such a feature for core, rather than an > extension. The see alsos suggest that. It's definitely possible that this will end up in core at some point. > We should keep detailed discussion there, but we're leaning toward an > extension, because not all wikis are going to want a Draft namespace right > away, necessarily. However, Chad is right that that doesn't necessarily require an extension. The namespace part can be done in wmf-config (that doesn't mean we necessarily will), and core variables can be gated. (In reply to comment #23) > Moving to core is always harder than just developing in core to begin with. > Case in point: Vector extension. You can look at that both ways. On the plus side, it enabled quicker experimentation (both in the code sense and the analytics sense). It successfully resulted in some good functionality that was moved to core. Other stuff was done in core in a significantly different way, after learning lessons from the extension implementation. I think it also kept some rejected functionality out of core. On the downside, there was definitely Vector functionality that should have been moved to core sooner. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 31369] Non-canonical HTTPS URLs quietly redirect to HTTP
https://bugzilla.wikimedia.org/show_bug.cgi?id=31369 --- Comment #62 from Gerrit Notification Bot --- Change 96438 merged by Tim Starling: Generate redirects.conf https://gerrit.wikimedia.org/r/96438 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57574] Special pages need entry in $specialPageAliases
https://bugzilla.wikimedia.org/show_bug.cgi?id=57574 --- Comment #2 from Jon --- A precommit hook would be useful as well to ensure ones added in future have them... -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 --- Comment #10 from Kunal Mehta (Legoktm) --- (In reply to comment #3) > (In reply to comment #2) > * who is allowed to create drafts. (e.g. Are anonymous users allowed to do > so? > I assume so but the proposal summary and closure don't specify.) I've left Tom Morris (the RfC closer) a note asking him to clarify - [[Special:Permalink/583319065]]. That said, I don't think that question specifically blocks the creation of the namespace, a hook can be added to userCan later on to allow anon's to create pages in it. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57479] Unable to mount /public directories on queue nodes
https://bugzilla.wikimedia.org/show_bug.cgi?id=57479 --- Comment #3 from Tim Landscheidt --- On tools-exec-01, /public is empty and /home looks rather sparse: | scfc@tools-login:~$ ssh tools-exec-01 ls -l /public | total 0 | scfc@tools-login:~$ ssh tools-exec-01 ls -l /home | total 20 | drwx-- 3 dapete wikidev 4096 Nov 24 17:43 dapete | drwxr-xr-x 2 gmetric gmetric 4096 Feb 27 2013 gmetric | drwx-- 4 marcwikidev 4096 Nov 22 17:09 marc | drwx-- 3 scfcwikidev 4096 Nov 26 01:16 scfc | drwxr-xr-x 3 ubuntu ubuntu 4096 Feb 27 2013 ubuntu | scfc@tools-login:~$ Also, on tools-exec-01 (at least) my home directory is not my "real" one: | scfc@tools-exec-01:~$ ll /home/scfc | total 32 | drwx-- 3 scfc wikidev 4096 Nov 26 01:16 ./ | drwxr-xr-x 7 root root4096 Nov 25 22:50 ../ | -rw--- 1 scfc wikidev 242 Nov 26 01:16 .bash_history | -rw--- 1 scfc wikidev 220 Nov 25 22:50 .bash_logout | -rw--- 1 scfc wikidev 3387 Nov 25 22:50 .bashrc | drwx-- 2 scfc wikidev 4096 Nov 25 22:50 .cache/ | -rw--- 1 root root 43 Nov 26 01:12 .lesshst | -rw--- 1 scfc wikidev 675 Nov 25 22:50 .profile | scfc@tools-exec-01:~$ I don't see any differences in /etc/auto* compared to tools-exec-02, but it looks like the automounts for /home and /public aren't working (/data/project is mounted fine). -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 Equazcion changed: What|Removed |Added Keywords|easy| --- Comment #9 from Equazcion --- (In reply to comment #7) > I'm not talking about articles for creation at all. That's a community > process, > not a software feature that has direct overlap with a drafts namespace, with > the exception of what we want to appear on search. The accepted proposal we seek to implement here doesn't concern any software feature. If you want one, propose one separately. You've stated nothing that couldn't also be applied without a draft namespace, or after it's already created. They are separate suggestions, and they may be useful ones, but still have no bearing on the implementation of this namespace. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 MZMcBride changed: What|Removed |Added Keywords||easy --- Comment #8 from MZMcBride --- (In reply to comment #6) > We're talking about a two-line configuration change here. Probably a few more than two lines to create the namespace, the talk namespace, and set noindex. Maybe a half-dozen to a dozen lines? In any case, this seems fairly easy to implement to me. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57574] Special pages need entry in $specialPageAliases
https://bugzilla.wikimedia.org/show_bug.cgi?id=57574 --- Comment #1 from Bingle --- Prioritization and scheduling of this bug is tracked on Mingle card https://wikimedia.mingle.thoughtworks.com/projects/mobile/cards/1453 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 --- Comment #7 from Steven Walling --- > None of this is relevant to adding a new namespace and you know this. > > If you want to improve the articles for creation process, great! I've filed > several bugs in this area. :-) No objections from me. > > But the two ideas (adding a new namespace on the English Wikipedia and > improving the articles for creation process) are not tied to each other in > any > meaningful way. We're talking about a two-line configuration change here. I'm not talking about articles for creation at all. That's a community process, not a software feature that has direct overlap with a drafts namespace, with the exception of what we want to appear on search. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57119] Non main namespace history pages show red link in header
https://bugzilla.wikimedia.org/show_bug.cgi?id=57119 Arthur Richards changed: What|Removed |Added Status|PATCH_TO_REVIEW |RESOLVED CC||aricha...@wikimedia.org Resolution|--- |FIXED --- Comment #3 from Arthur Richards --- Merged -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57574] New: Special pages need entry in $specialPageAliases
https://bugzilla.wikimedia.org/show_bug.cgi?id=57574 Web browser: --- Bug ID: 57574 Summary: Special pages need entry in $specialPageAliases Product: MediaWiki extensions Version: master Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: MobileFrontend Assignee: wikibugs-l@lists.wikimedia.org Reporter: aricha...@wikimedia.org CC: aricha...@wikimedia.org, jgon...@wikimedia.org, jrob...@wikimedia.org, kw...@wikimedia.org, maxsem.w...@gmail.com, mgro...@wikimedia.org, mpinc...@wikimedia.org, rkald...@wikimedia.org, tf...@wikimedia.org Classification: Unclassified Mobile Platform: --- From Siebrand in https://gerrit.wikimedia.org/r/#/c/96166/: All special pages should have an entry in $specialPageAliases['en']. Please do a complete check for MobileFrontend. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57119] Non main namespace history pages show red link in header
https://bugzilla.wikimedia.org/show_bug.cgi?id=57119 --- Comment #4 from Gerrit Notification Bot --- Change 96166 merged by jenkins-bot: Use prefixed title in Special:History banner https://gerrit.wikimedia.org/r/96166 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 56496] Provide way to page through previous/next media on the page in viewer lightbox
https://bugzilla.wikimedia.org/show_bug.cgi?id=56496 Mark Holmquist changed: What|Removed |Added Assignee|wikibugs-l@lists.wikimedia. |mtrac...@member.fsf.org |org | --- Comment #3 from Mark Holmquist --- OK, claiming, we're working on this now. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 --- Comment #6 from MZMcBride --- (In reply to comment #3) > This is not about consensus. We don't know basic things about how the > namespace would work. I'm pretty sure we know how namespaces work. :-) > We still need to specify things like: > > * who is allowed to create drafts. (e.g. Are anonymous users allowed to do > so? > I assume so but the proposal summary and closure don't specify.) > * how to publish drafts > * who is allowed to publish drafts > * how do we tell users they can create/publish drafts, on search, redlinks, > and other places > * do we want to let people make drafts of pages that already exist? None of this is relevant to adding a new namespace and you know this. If you want to improve the articles for creation process, great! I've filed several bugs in this area. :-) No objections from me. But the two ideas (adding a new namespace on the English Wikipedia and improving the articles for creation process) are not tied to each other in any meaningful way. We're talking about a two-line configuration change here. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 --- Comment #5 from Steven Walling --- (In reply to comment #4) > As I stated at the other bug, these are not questions that need to block > creation of the namespace. Deciding the basics of who can do what in a new namespace, and how, are things that block creating a new namespace. I really don't see why you're in such a huge hurry. This is quite a large new feature, so understanding the basics of how it will function in relation to regular page creation, the permissions involved, and so on seem quite obviously basic things we need to figure out before we deploy a major new namespace to English Wikipedia. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 56469] Viewer lightbox state can't be bookmarked or cut-n-pasted as a link
https://bugzilla.wikimedia.org/show_bug.cgi?id=56469 --- Comment #6 from Mark Holmquist --- The implementation is: 1. You can load with #mediaviewer/File:Test file.jpg/1 and it will auto-load that file for you IF File:Test file.jpg is the 1th (0-indexed) image on the page. If the page has changed, it will just ignore the hash fragment and load the page normally. 2. Your URL will change when you open the lightbox, and you can use the URL in the location bar to link to your current state. 3. You can press the back button in the lightbox to close the lightbox, and if you've closed the lightbox with the escape button or the close button, you can use the back button to reopen it. Hitting the back button more than once doesn't work currently and I have no idea why. 4. If there are weird characters in the file name, I have no idea what will happen. Yay uncertainty! For #1, I can stop checking if we prefer to just blindly load the nth image if we're given #mediaviewer/n as the hash fragment (as long as it's a number, of course). -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 54606] Make tutorial video on how to use Bugzilla
https://bugzilla.wikimedia.org/show_bug.cgi?id=54606 --- Comment #23 from Richard L --- The draft is finished if you're interested. Just going to clean it up and maybe add more details. Link again for CC:https://www.mediawiki.org/wiki/User:Richardusername/BugzillaScriptProject -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 --- Comment #4 from Equazcion --- As I stated at the other bug, these are not questions that need to block creation of the namespace. It rather seems apparent that you saw this proposal as something other than it was -- a more substantial change to AFC that you had already envisioned prior -- but it wasn't, and the closure states that pretty clearly. Anyone is allowed to create drafts because anyone was allowed to before. This is just a change to their location. Publishing drafts will continue to merely require a move to mainspace, because that's all that was required before. We don't need to tell anyone anything other than through altered documentation at AFC, because nothing other than that will be changing. Phrasing these added proposals as questions doesn't make them requirements that apply to this proposal. They are merely possible additions that should be proposed and discussed separately. As concerns this proposal, we need only create a draft namespace. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 49959] Add default styling for tables (CSS for file description page for "File history" and "Metadata" tables)
https://bugzilla.wikimedia.org/show_bug.cgi?id=49959 --- Comment #3 from Gerrit Notification Bot --- Change 97518 merged by jenkins-bot: Adding default styling for tables https://gerrit.wikimedia.org/r/97518 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 49959] Add default styling for tables (CSS for file description page for "File history" and "Metadata" tables)
https://bugzilla.wikimedia.org/show_bug.cgi?id=49959 Jon changed: What|Removed |Added Status|PATCH_TO_REVIEW |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 --- Comment #3 from Steven Walling --- (In reply to comment #2) > (In reply to comment #1) > > Like I said on bug 57315, there are still too many unanswered questions > > about > > this namespace to roll it out in a hasty way. > > Does anyone else share your view? This is not about consensus. We don't know basic things about how the namespace would work. We still need to specify things like: * who is allowed to create drafts. (e.g. Are anonymous users allowed to do so? I assume so but the proposal summary and closure don't specify.) * how to publish drafts * who is allowed to publish drafts * how do we tell users they can create/publish drafts, on search, redlinks, and other places * do we want to let people make drafts of pages that already exist? There are numerous other smaller details to work out as well. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57573] VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference
https://bugzilla.wikimedia.org/show_bug.cgi?id=57573 --- Comment #3 from ryasm...@wikimedia.org --- Test Environment: production Browser: FF 25 OS: MAC OS X 10. 8. 5 Example Page:https://en.wikipedia.org/wiki/User:RYasmeen_%28WMF%29/test_copy_and_paste?veaction=edit Click on the [1] reference of this page. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57573] VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference
https://bugzilla.wikimedia.org/show_bug.cgi?id=57573 --- Comment #2 from ryasm...@wikimedia.org --- Created attachment 13908 --> https://bugzilla.wikimedia.org/attachment.cgi?id=13908&action=edit Opening the same dialog box unlimited times -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57573] VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference
https://bugzilla.wikimedia.org/show_bug.cgi?id=57573 --- Comment #1 from ryasm...@wikimedia.org --- Created attachment 13907 --> https://bugzilla.wikimedia.org/attachment.cgi?id=13907&action=edit How it appears after step 13 -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57573] New: VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference
https://bugzilla.wikimedia.org/show_bug.cgi?id=57573 Web browser: --- Bug ID: 57573 Summary: VisualEditor:Unlimited cascade of references appear if an image with reference gets added as reference Product: VisualEditor Version: unspecified Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: Editing Tools Assignee: rm...@wikimedia.org Reporter: ryasm...@wikimedia.org CC: jforres...@wikimedia.org, krinklem...@gmail.com, rm...@wikimedia.org Classification: Unclassified Mobile Platform: --- Created attachment 13906 --> https://bugzilla.wikimedia.org/attachment.cgi?id=13906&action=edit The reference for the main page Steps to reproduce: 1.Click on the Edit button 2.Add a reference to a text 3.In the reference dialog add an image 4.Also type some text into that reference box (for example "The content" in this case.) 5.Now select the image 6.Go to Media Settings 7.Now add a reference to that image 8.Type anything for this second reference box 9.Apply changes in all three dialog boxes 10.Save the changes 11.Reopen the editor 12.Select the reference [1] 13.Open the reference dialog box Observed Result: The text "The content" appears as a template with a highlighted blue box around it.Now click on the [1] reference on the image by going to the media settings of the image. It opens the same content for the first reference and it keeps on opening the same window as you repeatedly do it for all the reference windows appears. Expected Result: The reference on the main page and the reference on the image should be different content.But since the reference in image [1] is pointing to the same [1] for the article ,this issue arises. See the screenshots attached -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #27 from Chad H. --- (In reply to comment #26) > Developing in core has a (necessarily) high barrier for quality Yes, I view this as a good thing. I hope this means you're not planning to cut corners and hide bad code in an extension ;-) > and an > implied > requirement that what you intend to commit is more or less intended to be > permanent. A draft namespace is a new idea that's somewhat experimental, and > we > intend to approach with an eye toward testing out what is going to work for > authors or not. Not true. We've done plenty of experimental things in core before. The trick is hiding them behind a feature flag so if we decide it's not such a great idea, we can nuke it later (case in point: HTMLDiff). I see how people may find developing core code daunting, but hiding in extensions isn't the way to make MediaWiki better, and I have insanely serious doubts about us ever moving extensions to core in a timely manner :) -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 56469] Viewer lightbox state can't be bookmarked or cut-n-pasted as a link
https://bugzilla.wikimedia.org/show_bug.cgi?id=56469 Gerrit Notification Bot changed: What|Removed |Added Status|NEW |PATCH_TO_REVIEW -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 --- Comment #2 from MZMcBride --- (In reply to comment #1) > Like I said on bug 57315, there are still too many unanswered questions about > this namespace to roll it out in a hasty way. Does anyone else share your view? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 56469] Viewer lightbox state can't be bookmarked or cut-n-pasted as a link
https://bugzilla.wikimedia.org/show_bug.cgi?id=56469 --- Comment #5 from Gerrit Notification Bot --- Change 97657 had a related patch set uploaded by MarkTraceur: Push history state to support links to media viewer https://gerrit.wikimedia.org/r/97657 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 54606] Make tutorial video on how to use Bugzilla
https://bugzilla.wikimedia.org/show_bug.cgi?id=54606 --- Comment #22 from Richard L --- Thanks for the video! It was exactly what I was thinking of, except doing this one more to the point. Also this is my main account, was accidentally logged in to wrong one when posting the last one. (I was going through the steps again) As for the brief sign-up , we can easily remove it if needed, so ill just leave it until final revisions. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57558] Can't create functions on p50380g50790__wanderwiki database
https://bugzilla.wikimedia.org/show_bug.cgi?id=57558
--- Comment #2 from joffrey.qu...@gmail.com ---
The database i'm refering to is named p50380g50790__wanderwiki and is
associated with project wanderwiki on the tool server.
I connect to it using my account on the tool lab : joffreyq
and doing the following:
- become wanderwiki
- mysql --defaults-file="${HOME}"/replica.my.cnf -h tools-db
p50380g50790__wanderwiki
After this if i run the following command :
DELIMITER $$
CREATE FUNCTION `new_function` ()
RETURNS INTEGER
BEGIN
RETURN 1;
END
I have this error:
"ERROR 1418: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA
in its declaration and binary logging is enabled (you *might* want to use the
less safe log_bin_trust_function_creators variable)"
So i tried the following command:
CREATE FUNCTION `new_function` ()
RETURNS INTEGER DETERMINISTIC NO SQL
BEGIN
RETURN 1;
END
And had this error:
"ERROR 1419: You do not have the SUPER privilege and binary logging is enabled
(you *might* want to use the less safe log_bin_trust_function_creators
variable)"
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
___
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 Steven Walling changed: What|Removed |Added CC||swall...@wikimedia.org --- Comment #1 from Steven Walling --- Like I said on bug 57315, there are still too many unanswered questions about this namespace to roll it out in a hasty way. Please be patient. It's only been a week since the RFC on enwiki was closed. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 52507] Mention notification text displays wiki markup if there is no section
https://bugzilla.wikimedia.org/show_bug.cgi?id=52507 --- Comment #5 from Gerrit Notification Bot --- Change 96656 merged by jenkins-bot: Mention: notify correctly if there is no section title https://gerrit.wikimedia.org/r/96656 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 45980] Implement HTML5 caching manifests
https://bugzilla.wikimedia.org/show_bug.cgi?id=45980 --- Comment #7 from Sam Wilson --- Appcache doesn't only cache the designated files, it also implicitly caches the page that has the 'manifest' attribute. That page could be included in the NETWORK section of the manifest, so that it's always pulled from remote, but that would be tricky if the manifest is to be present on every wiki page. I am currently using an application cache in an extension that makes SemanticForms available for offline data entry. To do this the manifest file is only loaded on particular pages, and lists all reasourceloader URLs along with the cache keys. It also lists all of the pages that need to be made available offline, and their last-modified dates. Basically, it seems that the tricky part of appcache is making sure it's refreshed at the appropriate time. -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #26 from Steven Walling --- (In reply to comment #23) > (In reply to comment #22) > > We should keep detailed discussion there, but we're leaning toward an > > extension, because not all wikis are going to want a Draft namespace right > > away, necessarily. > > Make it configurable. > > > We probably want to be able to turn it on selectively at > > first, even if we're aiming for something generally useful beyond English > > Wikipedia. > > Again, make it configurable (off by default, at first :)) > > > Migrating to Core in the future when it's more road-tested seems > > wise to me. > > Moving to core is always harder than just developing in core to begin with. > Case in point: Vector extension. My experience developing for account creation and login says otherwise. Quite simple and not at all outlandish design changes there took us way too long to get merged. Developing in core has a (necessarily) high barrier for quality and an implied requirement that what you intend to commit is more or less intended to be permanent. A draft namespace is a new idea that's somewhat experimental, and we intend to approach with an eye toward testing out what is going to work for authors or not. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57572] New: Setup linting / phpunit tests for wikimedia/wikimania-scholarships
https://bugzilla.wikimedia.org/show_bug.cgi?id=57572 Web browser: --- Bug ID: 57572 Summary: Setup linting / phpunit tests for wikimedia/wikimania-scholarships Product: Wikimedia Version: wmf-deployment Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: Continuous integration Assignee: wikibugs-l@lists.wikimedia.org Reporter: innocentkil...@gmail.com CC: has...@free.fr, innocentkil...@gmail.com, krinklem...@gmail.com Blocks: 57545 Classification: Unclassified Mobile Platform: --- New project, not MediaWiki-related at all. Mostly PHP/JS, so linting would be nice. Also have some rudimentary PHPUnit tests, so running those would be nice too. Normal gate-and-submit workflow is dandy. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57545] Review and deploy Wikimania Scholarship
https://bugzilla.wikimedia.org/show_bug.cgi?id=57545 Chad H. changed: What|Removed |Added Depends on||57572 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 48176] Requested Scribunto/Lua built-in methods/functions (tracking)
https://bugzilla.wikimedia.org/show_bug.cgi?id=48176 Rainer Rillke @commons.wikimedia changed: What|Removed |Added Depends on||57571 -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57571] New: Add MediaWiki's language fallback logic to Lua
https://bugzilla.wikimedia.org/show_bug.cgi?id=57571 Web browser: --- Bug ID: 57571 Summary: Add MediaWiki's language fallback logic to Lua Product: MediaWiki extensions Version: unspecified Hardware: All OS: All Status: NEW Keywords: i18n Severity: enhancement Priority: Unprioritized Component: Scribunto Assignee: wikibugs-l@lists.wikimedia.org Reporter: rainerril...@hotmail.com CC: bjor...@wikimedia.org, darkl...@gmail.com, tstarl...@wikimedia.org, vasi...@gmail.com Blocks: 48176 Classification: Unclassified Mobile Platform: --- As the title sais, I would like being able getting a fallback chain or similar from mediaWiki for a given language code. See [[:commons:Module:Fallbacklist]] for what an effort we currently have. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #25 from Equazcion --- (In reply to comment #21) > (In reply to comment #17) > > I don't think you're correct here. The closure says that AFC doesn't need to > change, not that we should continue to make all new article proposals > continue > to go through it. There's not actually a consensus that new articles must be > proposed through AFC. Also, search *does* link to AFC on English Wikipedia, > just log out and search for something. > > Part of the reason the Draft namespace was asked for was because the > homegrown > scripts, templates, and bots at AFC are not robust enough to handle the large > volume of page creations on English Wikipedia. Let's not make the same > mistake > twice, if we want really avoid creating a new backlog like the 40,000+ > abandoned drafts that still need to be cleaned up. > > Now that's clear there's support, let's work on defining what the absolute > minimum viable requirements are for the new namespace. Let's not be hasty in > adding a namespace we want to be successful and persist for a long time. > There's no deadline. The proposal to create the Draft namespace was partially to make things easier on the homegrown solutions. It wasn't to render them unneeded through software changes. The closure states: "... no challenge was made to the proviso that AfC would continue as it currently does. This community discussion does not change the AfC process—any such decisions should be ones that the AfC WikiProject should make through further consensus-based discussion if they deem it to be necessary." Steven said: "Now that's clear there's support, let's work on defining what the absolute minimum viable requirements are for the new namespace." The requirement was met. It was proposed and gained consensus. I understand that you want to create further requirements now because you personally think there should be some -- but that's not how this is supposed to work. Your suggestions may have merit, but can be discussed and implemented later. Implementing the draft space now does no harm to them. (In reply to comment #24) > (In reply to comment #18) > > I'd recommend filing a separate bug report for the creation of a "Draft" > > namespace on the English Wikipedia. > > Filed as bug 57569. Thank you, MZMcBride. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 54606] Make tutorial video on how to use Bugzilla
https://bugzilla.wikimedia.org/show_bug.cgi?id=54606 --- Comment #21 from Quim Gil --- Hi Richiell! Slides vs screencast, this video was well received here. Just in case it serves as source of inspiration: > http://blog.johnath.com/2010/02/04/bugzilla-for-humans/ There is another GCI task about title cards for videos, but they are not ready yet. Still, this task is about agreeing on the script, so never mind. Same for the link to the guided form. You are right, currently there is no way to reach it from Bugzilla itself. However, for your script we can assume that it will be in the home. About your script, feel free of reusing the very little I could do at https://www.mediawiki.org/wiki/Talk:How_to_report_a_bug#Screencast I also started thinking of the registration process. Then again, Bugzilla's registration is quite standard, so perhaps it is better to save that time to the viewers of the video and yourself. Mention in the script that users must be registered in order to file bugs, feel free spending 3 seconds to point to the Register link in the home and get directly to the stuff. This means that the beef of your script is "Examples". :) Sorry for not reaching to this conclusion before! Your draft helped reaching to this conclusion. This is how iterations work... -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57570] New: The "Previous" link in the review interface always points to the current application under review
https://bugzilla.wikimedia.org/show_bug.cgi?id=57570 Web browser: --- Bug ID: 57570 Summary: The "Previous" link in the review interface always points to the current application under review Product: Wikimedia Version: wmf-deployment Hardware: All OS: All Status: NEW Severity: normal Priority: Unprioritized Component: Wikimania Scholarship Assignee: wikibugs-l@lists.wikimedia.org Reporter: bda...@wikimedia.org CC: bda...@wikimedia.org Classification: Unclassified Mobile Platform: --- The review interface provides "Next" and "Previous" navigation links for reviewers that are intended to make it easy to quickly page through the applications that the current user has not yet reviewed. The "Next" link works as expected, but the "Previous" link has the URL of the current application. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57570] The "Previous" link in the review interface always points to the current application under review
https://bugzilla.wikimedia.org/show_bug.cgi?id=57570 Bryan Davis changed: What|Removed |Added Priority|Unprioritized |Normal -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 Kunal Mehta (Legoktm) changed: What|Removed |Added Severity|normal |enhancement -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 45470] Provide JSON library/module by default
https://bugzilla.wikimedia.org/show_bug.cgi?id=45470 Rainer Rillke @commons.wikimedia changed: What|Removed |Added CC||rainerril...@hotmail.com --- Comment #11 from Rainer Rillke @commons.wikimedia --- (In reply to comment #1) >Data passed in from templates should be formatted in a manner friendly to >non-technical users rather than being some blob of JSON Ha! Sure that's why TemplateData and Upload Wizard Campaigns force the user entering raw JSON-data-blobs. From the perspective of their developers and Mr. James Forrester that's totally okay. For me, it wasn't but when I tried to change that, I was accused of "derailing Commons" by them. (In reply to comment #5) > Could you clarify what "some data for JS" is, how it would be "used in > the module", and what you'd use it for in both Lua and JS? Curretnly I have data (only small that's why I do not complain) in JSON-format for JavaScript, in AbuseFilter format and in Lua format for some edit notice at Commons. JSON is a well-accepted standard and having a fast, native parser and generator would be pretty much useful. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #24 from MZMcBride --- (In reply to comment #18) > I'd recommend filing a separate bug report for the creation of a "Draft" > namespace on the English Wikipedia. Filed as bug 57569. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57569] New: Create "Draft" namespace on the English Wikipedia
https://bugzilla.wikimedia.org/show_bug.cgi?id=57569 Web browser: --- Bug ID: 57569 Summary: Create "Draft" namespace on the English Wikipedia Product: Wikimedia Version: wmf-deployment Hardware: All URL: https://en.wikipedia.org/w/index.php?title=Wikipedia:V illage_pump_%28proposals%29&oldid=582561035#Proposed_n ew_Draft_namespace OS: All Status: NEW Keywords: shell Severity: normal Priority: Unprioritized Component: Site requests Assignee: wikibugs-l@lists.wikimedia.org Reporter: b...@mzmcbride.com CC: benap...@gmail.com, bugzilla+org.wikime...@tuxmachine.com, dereck...@espace-win.org, g...@wikimedia.org, tom...@twkozlowski.net, wikimedia.b...@snowolf.eu Classification: Unclassified Mobile Platform: --- https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_%28proposals%29&oldid=582561035#Proposed_new_Draft_namespace I believe this discussion demonstrates sufficient community consensus to create a "Draft" namespace on the English Wikipedia. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #23 from Chad H. --- (In reply to comment #22) > We should keep detailed discussion there, but we're leaning toward an > extension, because not all wikis are going to want a Draft namespace right > away, necessarily. Make it configurable. > We probably want to be able to turn it on selectively at > first, even if we're aiming for something generally useful beyond English > Wikipedia. Again, make it configurable (off by default, at first :)) > Migrating to Core in the future when it's more road-tested seems > wise to me. Moving to core is always harder than just developing in core to begin with. Case in point: Vector extension. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #22 from Steven Walling --- (In reply to comment #19) > Might I be so bold as to suggest such a feature for core, rather than an > extension. The see alsos suggest that. > > We would help tons and tons more people that way. Matt F. and I have discussed this a little bit at https://www.mediawiki.org/wiki/Talk:Wikipedia_article_creation We should keep detailed discussion there, but we're leaning toward an extension, because not all wikis are going to want a Draft namespace right away, necessarily. We probably want to be able to turn it on selectively at first, even if we're aiming for something generally useful beyond English Wikipedia. Migrating to Core in the future when it's more road-tested seems wise to me. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #21 from Steven Walling --- (In reply to comment #17) > > The proposal states that new article proposals would still go through AFC. > There is no more reason to discuss further changes to search etc. than there > was prior to this proposal. We didn't add AFC links to search before, and we > don't need to now as a block to implementing the Draft namespace. > > These questions are not fundamental to the creation of a draft namespace, as > nothing would be changing in the AFC process besides the location of drafts. > They do not have to block its creation. They are all possible enhancements to > AFC that can be added on later. I don't think you're correct here. The closure says that AFC doesn't need to change, not that we should continue to make all new article proposals continue to go through it. There's not actually a consensus that new articles must be proposed through AFC. Also, search *does* link to AFC on English Wikipedia, just log out and search for something. Part of the reason the Draft namespace was asked for was because the homegrown scripts, templates, and bots at AFC are not robust enough to handle the large volume of page creations on English Wikipedia. Let's not make the same mistake twice, if we want really avoid creating a new backlog like the 40,000+ abandoned drafts that still need to be cleaned up. Now that's clear there's support, let's work on defining what the absolute minimum viable requirements are for the new namespace. Let's not be hasty in adding a namespace we want to be successful and persist for a long time. There's no deadline. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #20 from Equazcion --- (In reply to comment #18) > (In reply to comment #17) > > These questions are not fundamental to the creation of a draft namespace, as > > nothing would be changing in the AFC process besides the location of drafts. > > They do not have to block its creation. They are all possible enhancements > > to > > AFC that can be added on later. > > I'd recommend filing a separate bug report for the creation of a "Draft" > namespace on the English Wikipedia. There are instructions here: > [[m:Requesting > a wiki configuration change]]. I would do that immediately if this bug didn't concern the same proposal and contain the same Draft namespace creation (along with these other monkey wrenches). It might simply be marked as a duplicate. I rather hope we can correct this bug request so that it becomes what it was supposed to be. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57568] Link interface fails to appear (FF only)
https://bugzilla.wikimedia.org/show_bug.cgi?id=57568 --- Comment #1 from Chris McMahon --- Created attachment 13905 --> https://bugzilla.wikimedia.org/attachment.cgi?id=13905&action=edit link is pressed, 'Starting' should be highlighted, link UI should appear but does not -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57568] New: Link interface fails to appear (FF only)
https://bugzilla.wikimedia.org/show_bug.cgi?id=57568 Web browser: Firefox Bug ID: 57568 Summary: Link interface fails to appear (FF only) Product: VisualEditor Version: unspecified Hardware: All OS: All Status: NEW Keywords: browser-test-bug Severity: normal Priority: Unprioritized Component: Editing Tools Assignee: rm...@wikimedia.org Reporter: cmcma...@wikimedia.org CC: jforres...@wikimedia.org, jh...@wikimedia.org, krinklem...@gmail.com, rm...@wikimedia.org, ryasm...@wikimedia.org Classification: Unclassified Mobile Platform: --- Seen in Firefox on beta labs as of Nov 25 (Chrome behaves correctly): Login and navigate to some page with text, e.g. as Selenium_user/User:Selenium_user Without touching anything on the page, click the "Link" icon in the menu bar. Expected: First word in the page is highlighted and link UI appears, referring to highlighted text. Actual: Link icon shows being pressed, but no link UI appears. -- You are receiving this mail because: You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 Chad H. changed: What|Removed |Added CC||innocentkil...@gmail.com --- Comment #19 from Chad H. --- Might I be so bold as to suggest such a feature for core, rather than an extension. The see alsos suggest that. We would help tons and tons more people that way. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #18 from MZMcBride --- (In reply to comment #17) > These questions are not fundamental to the creation of a draft namespace, as > nothing would be changing in the AFC process besides the location of drafts. > They do not have to block its creation. They are all possible enhancements to > AFC that can be added on later. I'd recommend filing a separate bug report for the creation of a "Draft" namespace on the English Wikipedia. There are instructions here: [[m:Requesting a wiki configuration change]]. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
[Bug 57315] New extension for creating/managing new pages
https://bugzilla.wikimedia.org/show_bug.cgi?id=57315 --- Comment #17 from Equazcion --- (In reply to comment #16) > The proposal as written is not even close to describing all necessary details > of how a Draft namespace would operate. All it does is show English Wikipedia > supports a Draft namespace. > > For instance, it doesn't outline: > > * How publishing to mainspace would work. Is it the regular page move > function > which is hidden from view, or should we augment the editing toolbar to > include > publish actions? > * What is the entry point for draft creation? Do we still send all new users > to > AFC via Search? > * Do we include starting a draft as a secondary option when searching? > * Do we suggest creating a draft as an option when visiting a red link? Do we > do that for all users or just new ones? People said we should consider > strongly > suggesting drafts to new editors. So do we send users on a red link to create > Drafts first, if they new? > * Do we let new users publish to mainspace at any point they like? Or do we > strongly suggest secondary review like AFC, and prevent page moves by > non-autoconfirmed users in the Draft namespace? > > These fundamental questions and others need to be answered. As I said on the > RFC, the best way to do this is to test things. In any case, we're not ready > to > just whip out a new namespace that works exactly like the main namespace but > is > titled Draft. That's not enough. Otherwise the proposal will be worthless, > because new users and experienced ones alike will have a hard time finding > the > ability create drafts and publish them. The proposal states that new article proposals would still go through AFC. There is no more reason to discuss further changes to search etc. than there was prior to this proposal. We didn't add AFC links to search before, and we don't need to now as a block to implementing the Draft namespace. These questions are not fundamental to the creation of a draft namespace, as nothing would be changing in the AFC process besides the location of drafts. They do not have to block its creation. They are all possible enhancements to AFC that can be added on later. -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___ Wikibugs-l mailing list Wikibugs-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
