Sumana Harihareswara suma...@wikimedia.org writes:
Please leave your comments at bug 1450 so we can decide how to write
the rewrite rule.
Since Gerrit makes review possible and the relevant Apache config
(redirects.conf) is on noc and *should* be in git, I've gone ahead and
(after discussing
Brion thanks so much for the feedback
A few comments below...
Are more styles damaging or legit? How do we know? I'd encourage keeping
all styles by default except for ones known to cause trouble...
The problem is that styles can be extremely damaging render content
unreadable. I'd rather have
On Fri, Apr 20, 2012 at 8:01 AM, Mark A. Hershberger m...@wikimedia.orgwrote:
Sumana Harihareswara suma...@wikimedia.org writes:
Please leave your comments at bug 1450 so we can decide how to write
the rewrite rule.
Since Gerrit makes review possible and the relevant Apache config
I think you could use a multi-step process to solve this problem with the
help of the community.
1. Detect when inline styles are used on a page and add that page to a
list of pages that might have problems being rendered on mobile.
1. Make a special page that displays this list and
Yesterday, someone asked #wikipedia where was the separation between
style and content done on wikipedia. Users don't suddenly start to write
CSS rules in the pages themselves.
Most inline styles come from templates.
They don't write for a table:
border=2 cellpadding=4 cellspacing=0
Jpostlethwaite posted a comment on Wikimedia.r1651.
URL: http://www.mediawiki.org/wiki/Special:Code/Wikimedia/1651#c32711
Commit summary for Wikimedia.r1651:
Added civicrm_api3_contribution_status to API.
Jpostlethwaite's comment:
I think it is necessary to add a new option_group for recurring
Catrope changed the status of MediaWiki.r114995 to ok
URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/114995
Old status: new
New status: ok
Commit summary for MediaWiki.r114995:
Unbreak script args to mwscriptwikiset.
___
Chad wrote:
I think we should probably work on mediawiki.org (subpage of
RfC?). This is something that needs to be thought out properly,
and I think on-wiki would be more productive than on-list.
Okay. I will create an RFC page. Keep in mind that my time is limited
and I've only just started
On Fri, Apr 20, 2012 at 5:27 PM, Greg Sabino Mullane g...@endpoint.com wrote:
Krinkle wrote:
I'd say put it in Gerrit from the start (in a branch) so that everyone
can check it out and send suggestions (either as a commit or through the
feedback channels on the mailing list, wiki or Gerrit
On 20/04/12 23:27, Greg Sabino Mullane wrote:
Right. I've been thinking about this a lot, and the big picture plan
is to remove all the tables.sql files and create a single text file,
mediawiki.schema, which will have a generic schema, very similar to
the existing main tables.sql, but with
MZMcBride posted a comment on MediaWiki.r100315.
URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/100315#c32712
Commit summary for MediaWiki.r100315:
* Made ?contribs=user actually show the results for the *user* if 'newbies' was
given as the user.
* Added a link batch query to newbie
Following up on the earlier thread by Rob [1], Rob and I kicked around
the question what metrics/targets for code review we want to surface
on an ongoing basis. We're not going to invest in a huge dashboard
project right now, but we'll try to get at least some of the key
metrics generated and
Erik Moeller wrote:
Following up on the earlier thread by Rob [1], Rob and I kicked around
the question what metrics/targets for code review we want to surface
on an ongoing basis. We're not going to invest in a huge dashboard
project right now, but we'll try to get at least some of the key
Andrew Garrett wrote:
On Wed, Apr 11, 2012 at 12:24 AM, Niklas Laxström niklas.laxst...@gmail.com
wrote:
Solution 2:
Use the api.php to post to the user talk page.
* Has lots of failure cases:
** Connection error/Timeout
Try again.
** May need to create user account separately
14 matches
Mail list logo
