Hi,
I have addressed the issues in my talk page and added a 'Future Project
Maintenance' section to address maintenance needs.
https://www.mediawiki.org/wiki/User:Gautham_shankar/Gsoc
Kindly let me know if there are any other changes i have to make.
Thank you for your support,
Regards,
Gautham Shankar
One thing I've noticed in the last couple of days of madly reviewing things
in gerrit is that merge conflicts in the RELEASE-NOTES-1.20 file are very
common.
Because of the delay between submission and post-review merge, there's a
high probability that a new entry in one of the sections of
RELEASE-NOTES-1.20 will "conflict" with entries added by other commits that
have been merged in the meantime. Git doesn't understand that it can just
slip the line in at the end of the section, alas. :)
Do we really need to be maintaining these release notes files this way,
though?
Now that we have pre-commit review, we can more aggressively police commit
messages so that the first line is more consistently "release-notes-ready",
and we can generate release-notes files from commit logs instead, and avoid
the make-work of manually adding to and merging RELEASE-NOTES files on
every change.
Thoughts? Concerns? Threats? :)
-- brion
If you want to help us grow the MediaWiki developer community, there's a
quick thing you can do today. You can give feedback to one of these
three proposals:
* Automatic Taxobox Usability and Feature Enhancements - Have the
automatic taxobox's main and most used features exposed as a GUI
https://www.mediawiki.org/wiki/User:Baconprime/GSoC2012
* Grouping, a new UI for the watchlist page, and modifying the raw
watchlist page
https://www.mediawiki.org/wiki/User:Blackjack48/GSOC_proposal_for_watchlist…
* Revamping the watchlist structure to incorporate groups and shared
watchlists https://www.mediawiki.org/wiki/User:Bagariavivek/GSoC_Application
Right now, none of these students has found a mentor who's enthusiastic
about the proposal, so they're unlikely to be accepted into the summer
program (Google Summer of Code). But if they improve their proposals by
tomorrow (deadline) and can appeal to some mentors by the end of next
week, their chances go up.
And maybe you can suggest to the two students who are interested in
watchlists how they could decrease the overlap in their proposals.
--
Sumana Harihareswara
Volunteer Development Coordinator
Wikimedia Foundation
cross-posting to wikitech-l
On Thu, Mar 29, 2012 at 8:34 AM, Jon Robson <jrobson(a)wikimedia.org> wrote:
> I've been experimenting with the api that Max Semenik has been working
> on and the html5 history interface [1] to add javascript to the
> MobileFrontend extension so that any searches, link to other articles
> and section expansions go via the api. It's something I'm very
> interested to do both from a usability and site performance
> perspective. The best example of what I'm trying to do can be seen on
> http://github.com . It's worth pointing out that this is not currently
> on the roadmap but it is something I'm very interested in us doing.
>
> The resulting prototype [2] has a few quirks (and a few things I
> haven't paid attention to e.g. page titles do not change) but I think
> is interesting as it is noticeably faster (please bear in mind this is
> a slow server) and reduces the load on the server in that any page
> loads after the first load will go via the api. Note devices which do
> not support the history api or jQuery are not effected by this code.
>
> It throws up some interesting challenges.
> 1) It enables sub section expansion for which the existing design
> doesn't really seem to work. Also it means pages like History of China
> [3] look different when viewed normally to when retrieved via the api
> (the normal version only has expansion on the top level sections)
> 2) Also the back button (at the moment) has no memory of which
> sections were opened/closed and instead goes back to the last loaded
> page.
> 3) The first page is still wastefully loaded. It would be good if we
> could load all sections dynamically on the first page whilst not give
> a crummy experience to non-javascript users.
> 4) Some sections just contain sub sections. So if I click a section
> with heading 'Section 1' that only contains 'Section 1.1' and 'Section
> 1.2' there is a brief flash whilst it tries to load any text for
> section 1 (Please load-> empty string). To see what I mean load the
> Japan page [4], load History of China via the link 'Chinese history
> texts' and click 'Prehistory' (observe 'loading content'). I guess it
> would be useful if the api let me know beforehand if a section was
> empty of any text so I didn't try to retrieve it.
> 5) The api returns the heading in the text. For example in [5] the
> line Prehistory includes the heading in the text. This is unnecessary
> as I can determine this from toclevel and line. In my code I'm
> currently scrubbing this out every time I load.
>
> Feel free to have a play [6] locally as the mobile-geo server is very
> very slow and improve on it.
> Let me know if this interests anyone other than me :-)
>
> ~Jon
>
> [1] http://www.w3.org/TR/html5/history.html#the-history-interface
> [2] http://mobile-geo.wmflabs.org/w/index.php/Millet
> [3] http://mobile-geo.wmflabs.org/w/index.php/History_of_China
> [4] http://mobile-geo.wmflabs.org/w/index.php/Japan
> [5]
> http://en.wikipedia.org/w/api.php?action=mobileview&page=History+of+China&f…
> [6] https://gerrit.wikimedia.org/r/#change,3894
>
> _______________________________________________
> Mobile-l mailing list
> Mobile-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
>
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Hey,
I ran into a git review issue after doing a fresh Ubuntu install with the
packages from the regular sources, asked for help at several places and
googled for 2 hours, all to no avail.
git review
Errors running git rebase -i remotes/gerrit/master
/usr/lib/git-core/git-rebase--interactive: 1: arithmetic expression:
expecting primary: "+"
Reinstalled git, git review and did a clean clone of the repo. I can rebase
stuff just fine for my github repos.
So right now I cannot commit to core or extensions and have no idea how to
fix this. Help would be appreciated.
Cheers
--
Jeroen De Dauw
http://www.bn2vs.com
Don't panic. Don't be evil.
--
For MediaWiki 1.18, we had a really beautiful page that had a good, easy
to read, easy to scan, summary of the things in 1.18. I'm not sure we
can make the 1.19 page (http://www.mediawiki.org/wiki/MediaWiki_1.19) as
nice as that, but I would like something a little better than what we
have right now.
YOU CAN HELP! If you have done any work that is new in 1.19, please
take the time to add a short paragraph describing the changes.
I'm not too worried right now about the appearance or organisation of
the page -- I'd like to get the information on the page and then set
about organizing it.
Today, I'll be working on updating the page. I'm going to start by
scanning the Release Notes (http://hexm.de/h8) and finding things
there. Please join in.
Thanks!
FYI
---------- Forwarded message ----------
From: "Dan Bode" <dan(a)puppetlabs.com>
Date: Apr 5, 2012 12:24 AM
Subject: [Puppet Users] openstack-puppet mailing list
To: "public puppet users" <puppet-users(a)googlegroups.com>
Hi all,
I have been working to create a community around a set of modules for
configuring and deploying OpenStack.
For folks who are interested in our openstack efforts, I created a
separate mailing list.
http://groups.google.com/group/puppet-openstack
I plan to be pretty verbose about the code as it progresses and I
didn't want to flood the puppet users group with openstack specific
messages.
- Dan
Context: https://www.mediawiki.org/wiki/Wikimedia_engineering_20%25_policy
> Tim Starling wrote:
>> "20% time" is an attempt to correct broader related trends, but
>> perhaps we need a more project-oriented approach within our 20% time
>> policy in order to encourage mentoring and start the pipeline of
>> contributed extensions moving again.
> MZMcBride wrote:
>> I asked about this "policy" a few months ago:
>> <http://lists.wikimedia.org/pipermail/wikitech-l/2012-March/058665.html>.
>>
>> Rob never replied and the thread died. There's a difference between having a
>> page on MediaWiki.org and having a policy. From what I've seen, it's mostly
>> the former, though I'd be thrilled if someone can prove me wrong.
> Antoine Musso wrote:
>> Which is an entirely different subject. You might want to send a new
>> message just for that :-] Then I will happily reply about my specific case.
MZMcBride
Hello,
This week we will be testing the new search infrastructure that has been
spun up in our Ashburn data center. Search is currently running on some of
our oldest hardware, so this should provide both better performance and
reliability.
The first wiki that we will be testing is eswiki. We will start this test
at 15:00 UTC, tomorrow, 4/4/12. (Or 4/4/12, for those not using American
date formatting.) If that seems to run smoothly, we will rotate through the
other shards, with enwiki and the "everything else" shard being last.
Please respond to this thread if you see anything amiss, or let me know via
irc (my nick is notpeter). Due to mostly speaking English, personally, help
with other languages would be greatly appreciated!
Best,
Peter