Re: [Wikitech-l] Maps
One foundation to rule them all? :P On Wed, Mar 18, 2015 at 10:06 AM, Max Semenik maxsem.w...@gmail.com wrote: Hi, just a quick note: as part of general search and discovery work, me and Yuri are resurrecting the project to have OpenStreetMap in Wikimedia starting in April. Because the initial part of this work will include researching options which will influence precise goals and this is yet to be done, we still can't commit to a precise timeline, but as a ballpark estimate I personally want to aim for serving PNG tiles at a reasonable, though not necessarily dynamic maps on every WP page scale by the end of Q4. Vector/multilingual maps would be the next stage. We will be mostly using Phabricator for planning, https://phabricator.wikimedia.org/tag/openstreetmap/ is my first pass on the outline of things to be done. Your comments and suggestions would be highly appreciated, please share your thoughts, ideas of projects that might use these maps, or just merciless critique! :D -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org
On Wed, Mar 18, 2015 at 5:42 AM, Kevin Wayne Williams kwwilli...@kwwilliams.com wrote: Danny Horn schreef op 2015/03/17 om 21:08: And I'm glad to hear that this thread has come close to almost inspiring optimism. That's what I'm here for. In a sample of one. Still, I guess one finds solace where one can. While this feature has encountered and keeps encountering resistance and opposition, it is also collecting adoption and enthusiasm, both in the editing [1] and technical communities. Looking only at the dark or the bright side of the picture helps nobody. mediawiki.org has always been a place for technical experimentation and for eating our own food. This is why LiquidThreads became a thing there, and this is also why it makes sense to keep pushing Flow in that space. I really care about newcomers and I think Flow is an essential piece for onboarding them [1], but as a self-proclaimed experienced user of online discussion tools, I also like Flow by its own merit. I praised wikitext discussions, and I praised LQT discussions, but each on their own decade so to say. Even if Flow is not perfect today, it improves every month, and I'd rather help improving it than stopping it. [2] This thread is clearly not a sample of one. I am personally delighted (and I'm choosing carefully this word) with the work the Flow/Collaboration team has been doing identifying what is an objective problem, pushing firmly but flexibly a vision, and communicating (listening/speaking/acting) with all their surroundings, release after release. They are listening and responsive in an array of channels that probably none of us can enumerate. I don't think there is any single relevant piece of feedback in all these conversations that hasn't been translated to a Phabricator task, and I don't think there is any relevant comment in any Flow task of Phabricator that the maintainers haven't replied to, explaining their thoughts and plans. [1] For instance, last Autumn I participated with my volunteer hat in Amical Wikimedia's annual meeting. This is a small but very active and well organized community, and reaching out to new editors is their top priority. They said that VisualEditor is now the essential piece in the many workshops they organize, and they explaned that the new moment of confusion is when they introduce the importance of discussions and collaboration. Having to move from VisualEditor's familiar features and UI to a blank space where equal signs, colons, and tildes are an essential requirement, systematically confuses new editors. For this reason, and because experienced editors can get away with some details when their primary goal is to onboard future experienced editors, ca.wiki has been testing Flow for a few months now, and they want it deployed to more pages and namespaces. There, it's basically the Flow maintainers who are pushing the break. [2] https://phabricator.wikimedia.org/maniphest/query/OouIbfQn0iB8/#R ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] RFC meeting this week
In the next RFC meeting we will discuss the following RFC: * Master slave datacenter strategy for MediaWiki https://www.mediawiki.org/wiki/Requests_for_comment/Master_%26_slave_datacenter_strategy_for_MediaWiki The meeting will be on the IRC channel #wikimedia-office on chat.freenode.net at the following time: * UTC: Wednesday 21:00 * US PDT: Wednesday 14:00 * Europe CET: Wednesday 22:00 * Australia AEDT: Thursday 08:00 -- Tim Starling ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
[Wikitech-l] Maps
Hi, just a quick note: as part of general search and discovery work, me and Yuri are resurrecting the project to have OpenStreetMap in Wikimedia starting in April. Because the initial part of this work will include researching options which will influence precise goals and this is yet to be done, we still can't commit to a precise timeline, but as a ballpark estimate I personally want to aim for serving PNG tiles at a reasonable, though not necessarily dynamic maps on every WP page scale by the end of Q4. Vector/multilingual maps would be the next stage. We will be mostly using Phabricator for planning, https://phabricator.wikimedia.org/tag/openstreetmap/ is my first pass on the outline of things to be done. Your comments and suggestions would be highly appreciated, please share your thoughts, ideas of projects that might use these maps, or just merciless critique! :D -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Maps
Looks like just a collaboration :-) https://www.mediawiki.org/wiki/OpenStreetMap https://meta.wikimedia.org/wiki/OpenStreetMap https://wiki.openstreetmap.org/wiki/Collaboration_with_Wikipedia Obviously we should be doing our own tile rendering and serving, for example. On 18 March 2015 at 09:09, Petr Bena benap...@gmail.com wrote: One foundation to rule them all? :P On Wed, Mar 18, 2015 at 10:06 AM, Max Semenik maxsem.w...@gmail.com wrote: Hi, just a quick note: as part of general search and discovery work, me and Yuri are resurrecting the project to have OpenStreetMap in Wikimedia starting in April. Because the initial part of this work will include researching options which will influence precise goals and this is yet to be done, we still can't commit to a precise timeline, but as a ballpark estimate I personally want to aim for serving PNG tiles at a reasonable, though not necessarily dynamic maps on every WP page scale by the end of Q4. Vector/multilingual maps would be the next stage. We will be mostly using Phabricator for planning, https://phabricator.wikimedia.org/tag/openstreetmap/ is my first pass on the outline of things to be done. Your comments and suggestions would be highly appreciated, please share your thoughts, ideas of projects that might use these maps, or just merciless critique! :D -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] regarding gsoc 2015
Hi Arindam, On Tue, Mar 17, 2015 at 8:58 PM, Arindam Padhy b113...@iiit-bh.ac.in wrote: hello i am a b.tech student pursuing my carrer at iiit bhubaneswar,india. i am deeply interested in gsoc 2015 and wanted to do a project under this organization. how should i proceed..?? Please go to https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015 and check the project ideas proposed. do we need to solve any bugs..?? Yes, we are requiring candidates to solve microtasks as part of their evaluation. Every project idea proposed has a list of suggested microtasks. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org
On Wed, Mar 18, 2015 at 10:12 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org wrote: On Tue, Mar 17, 2015 at 8:27 PM, Danny Horn dh...@wikimedia.org wrote: So we've figured out a new reply/indentation model that separates those two functions. We've been testing it out on the flow-tests server [1], and we're going to release it to Mediawiki soon. I ran some tests at http://flow-tests.wmflabs.org/wiki/Topic:Sdrqdcffddyz0jeo. Here are my observations: - Posts B, C, and I all reply to A, but the ordering is C, I, B. I'd expect replies to the same parent to be ordered chronologically (and I'd personally expect earliest first). - Posts B and C both reply to A, but are confusingly at different indentation levels. I'd expect replies to the same parent to be indented the same. - Posts I and E are at the same indentation level, despite I being a direct reply to A while E is at the end of the chain A→C→D→E. Similar confusion exists elsewhere. I'd expect two posts at the first indentation level under the same parent to both be replies to that parent. - Things are even weirder with post J: Even though D and its reply E are at the same indentation level, J is suddenly indented more because of an unrelated post I. - Things go completely wrong once we hit the maximum depth, it's impossible to have (or only to be seen as having?) tangents at all. The reply box doesn't even show up under the post where I actually clicked Reply. All in all, I personally find the resulting structure to be very confusing as to what's actually replying to what since the same reply-structure might be displayed in different ways (depending on the order the replies were entered) and different reply-structures can give rise to the same display-structure. (sorry for the self-reply) Some of these might be solved by simply abandoning the idea that first reply = main thread, all others = tangent in favor of displaying flat if this post and its parent both have no sibling post. That /would/ mean, though, that a single reply could result in a major change to display-structure. For example, a reply-chain A→B→C→D→E→F→G would be displayed flat, and then when someone posts B2 as a reply to A we'd have A, then indented under it B and B2, then indented under B we'd have C→D→E→F→G (which might still be displayed flat). And there'd still be the case that a chain of replies and a single post with multiple direct replies (none of which were replied to) could be displayed the same in some cases, but that seems less likely to be confusing to a reader. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org
Also, some nice-to-have features:
* provide View Source (showing the wikitext) of someone's post
https://phabricator.wikimedia.org/T62465
* post-edit diffs need a Thank link
https://phabricator.wikimedia.org/T85846
* Have WhatLinksHere show full information for Flow content
https://phabricator.wikimedia.org/T92571
Il 17/03/2015 11:05, Ricordisamoa ha scritto:
Hi Nick,
I'm glad the Foundation is finally valuing a usable discussion system.
Unfortunately, there are some serious issues with Flow which will
prevent my use of it in production if not addressed in full:
* Administrators *must* be able to to see a deleted Flow board without
undeleting it (T90972 https://phabricator.wikimedia.org/T90972)
* Ordinary users *must* be able to move topics between boards (T88140
https://phabricator.wikimedia.org/T88140)
* Ordinary users *must* be able to edit AND move AND indent AND dedent
other users' comments (T78253
https://phabricator.wikimedia.org/T78253)
* An arbitrary indentation level *must* be allowed, with optional
facilitations for adding an {{outdent}}-like marker
* Every basic functionality (including but not limited to the
preview button) *must* work without relying on JavaScript (T60019
https://phabricator.wikimedia.org/T60019)
I see that the implementation of many features was delayed at the
initial stage of development, but they can't be ignored when trying to
deploy such a software in production. Thank you.
Il 17/03/2015 01:51, Nick Wilson (Quiddity) ha scritto:
LiquidThreads (LQT) has not been well-supported in a long time. Flow
is in active development, and more real-world use-cases will help
focus attention on the higher-priority features that are needed. To
that end, LQT pages at mediawiki.org will start being converted to
Flow in the next couple of weeks.
There are about 1,600 existing LQT pages on Mediawiki, and the three
most active pages are VisualEditor/Feedback, Project:Support_desk, and
Help_talk:CirrusSearch.[1] The Collaboration team has been running
test conversions of those three pages, and fixing issues that have
come up. Those fixes are almost complete, and the team will be ready
to start converting LQT threads to Flow topics soon. (If you’re
interested in the progress, check out phab:T90788[2] and linked
tasks.) The latest set is visible at a labs test server.[3] See an
example topic comparison here: Flow vs LQT.[4])
The VisualEditor/Feedback page will be converted first (per James'
request), around the middle of next week. We’ll pause to assess any
high-priority changes required. After that, we will start converting
more pages. This process may take a couple of weeks to fully run.
The last page to be converted will be Project:Support_desk, as that is
the largest and most active LQT Board.
LQT Threads that are currently on your watchlist, will still be
watchlisted as Flow Topics. New Topics created at Flow Boards on your
watchlist will appear in your Echo notifications, and you can choose
whether or not to watchlist them.
The LQT namespaces will continue to exist. Links to posts/topics will
redirect appropriately, and the LQT history will remain available at
the original location, as well as being mirrored in the Flow history.
There’s a queue of new features in Flow that will be shipped over the
next month or so:
* Table of Contents is done
* Category support for Flow Header and Topics is done
* VE with editing toolbar coming last week of March (phab:T90763) [5]
* Editing other people’s comments coming last week of March
(phab:T91086)
* Ability to change the width side rail in progress, probably out in
April (phab:T88114])
* Search is in progress (no ETA yet) (phab:T76823)
* The ability to choose which Flow notifications end up in Echo,
watchlist, or both, and other more powerful options, will be coming up
next (no ETA yet)
That being said -- there are some LiquidThreads features that don’t
exist in Flow yet.
We’d like to hear which features you use on the current LQT boards,
and that you’re concerned about losing in the Flow conversion. At the
same time, we’d like further suggestions on how we could improve upon
that (or other) features from LQT.
Please give us feedback at
https://www.mediawiki.org/wiki/Topic:Sdoatsbslsafx6lw to keep it
centralized, and test freely at the sandbox.[6]
Much thanks, on behalf of the Collaboration Team,
Quiddity (WMF)
[1] https://www.mediawiki.org/wiki/VisualEditor/Feedback and
https://www.mediawiki.org/wiki/Help_talk:CirrusSearch and
https://www.mediawiki.org/wiki/Project:Support_desk
[2] https://phabricator.wikimedia.org/T90788
[3] http://flow-tests.wmflabs.org/wiki/Testwiki:Support_desk and
http://flow-tests.wmflabs.org/wiki/VisualEditor/Feedback
[4] http://flow-tests.wmflabs.org/wiki/Topic:Qmkwqmp0wfcazy9c and
https://www.mediawiki.org/wiki/Thread:Project:Support_desk/Error_creating_thumbnail:_Unable_to_save_thumbnail_to_destination
[5] https://phabricator.wikimedia.org/T90763 ,
Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org
On Tue, Mar 17, 2015 at 8:27 PM, Danny Horn dh...@wikimedia.org wrote: So we've figured out a new reply/indentation model that separates those two functions. We've been testing it out on the flow-tests server [1], and we're going to release it to Mediawiki soon. I ran some tests at http://flow-tests.wmflabs.org/wiki/Topic:Sdrqdcffddyz0jeo. Here are my observations: - Posts B, C, and I all reply to A, but the ordering is C, I, B. I'd expect replies to the same parent to be ordered chronologically (and I'd personally expect earliest first). - Posts B and C both reply to A, but are confusingly at different indentation levels. I'd expect replies to the same parent to be indented the same. - Posts I and E are at the same indentation level, despite I being a direct reply to A while E is at the end of the chain A→C→D→E. Similar confusion exists elsewhere. I'd expect two posts at the first indentation level under the same parent to both be replies to that parent. - Things are even weirder with post J: Even though D and its reply E are at the same indentation level, J is suddenly indented more because of an unrelated post I. - Things go completely wrong once we hit the maximum depth, it's impossible to have (or only to be seen as having?) tangents at all. The reply box doesn't even show up under the post where I actually clicked Reply. All in all, I personally find the resulting structure to be very confusing as to what's actually replying to what since the same reply-structure might be displayed in different ways (depending on the order the replies were entered) and different reply-structures can give rise to the same display-structure. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Maps
Glad to hear of this idea. We've discussed potential collaborations with OSM in Cascadia Wikimedians meetings. Pine On Mar 18, 2015 2:08 AM, Max Semenik maxsem.w...@gmail.com wrote: Hi, just a quick note: as part of general search and discovery work, me and Yuri are resurrecting the project to have OpenStreetMap in Wikimedia starting in April. Because the initial part of this work will include researching options which will influence precise goals and this is yet to be done, we still can't commit to a precise timeline, but as a ballpark estimate I personally want to aim for serving PNG tiles at a reasonable, though not necessarily dynamic maps on every WP page scale by the end of Q4. Vector/multilingual maps would be the next stage. We will be mostly using Phabricator for planning, https://phabricator.wikimedia.org/tag/openstreetmap/ is my first pass on the outline of things to be done. Your comments and suggestions would be highly appreciated, please share your thoughts, ideas of projects that might use these maps, or just merciless critique! :D -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org
On Wed, Mar 18, 2015 at 11:12 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org wrote: On Tue, Mar 17, 2015 at 8:27 PM, Danny Horn dh...@wikimedia.org wrote: So we've figured out a new reply/indentation model that separates those two functions. We've been testing it out on the flow-tests server [1], and we're going to release it to Mediawiki soon. I ran some tests at http://flow-tests.wmflabs.org/wiki/Topic:Sdrqdcffddyz0jeo. Here are my observations: ... These look like the same problems reported last week on this thread: https://pt.wikipedia.org/w/index.php?title=WP:Esplanada/propostas/Flow_na_Wikip%C3%A9dia:Contato_%285mar2015%29oldid=41541009 Best regards, Helder ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] looking for unit testing resources for bot development
Il 17/03/2015 20:45, Frances Hocutt ha scritto: I'm working on cleaning up the code[1] for GrantsBot[2] and generally getting it into better and more robust shape. I've started writing basic unit tests to assist in the refactoring process. Since it interacts so heavily with the MediaWiki API, however, this isn't a straightforward process, and it's even more complicated because I'll be rewriting it to use a different client library (so any mocks/stubs I include will need to be rewritten). Does anyone have thoughts on the best strategy for this, or, more generally, pointers to good resources for writing unit tests for API clients? -Frances [1] dev branch: https://github.com/fhocutt/grantsbot/tree/dev [2] a bot run by Community Resources to maintain the IdeaLab on MetaWiki: https://meta.wikimedia.org/wiki/User:GrantsBot If you're using Pywikibot, you may want to have a look at its extensive unit tests :) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Maps
On Wed, Mar 18, 2015 at 4:01 PM, MZMcBride z...@mzmcbride.com wrote: I believe OpenStreetMap previously had a relationship with Wikimedia Germany and the Toolserver(?). I'm not sure if that endeavor is related to this one. And I'm not sure what the scopes of these projects are. Toolserver's gone, right? It looks like this new project would be the Wikimedia Foundation acting as both the (tile)server and the client, using data from OpenStreetMap. Is that correct? Yes. If so, will the tileserver be considered a public service for use outside of Wikimedia wikis? TBD. And will this service be hosted on Wikimedia Labs? No, on real hardware. Expanding the mediawiki.org and Meta-Wiki pages to include more information about the history here would be great. Hey, we're still working on fulfilling our previous commitments. Everything will come, just not instantaneously;) -- Best regards, Max Semenik ([[User:MaxSem]]) ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Starting conversion of LiquidThreads to Flow at mediawiki.org
Brad: unfortunately, it's really hard to tell very much from a conversation with messages like 3: Post C: reply to Post A. You could do that with the old model, the new model or the perfect magic Nobel-Prize-winning discussion threading still to be discovered, and it would probably look like nonsense in all three. We've tried in our testing to pretend that we're having real conversations, so we could see whether there's any logical way to get to eight levels of nested threading. It's not easy to organize make-believe conversations, but if you want to start a thread, I'd be happy to fire up a few sockpuppets and pretend to talk about something with you. On Wed, Mar 18, 2015 at 7:35 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org wrote: On Wed, Mar 18, 2015 at 10:12 AM, Brad Jorsch (Anomie) bjor...@wikimedia.org wrote: On Tue, Mar 17, 2015 at 8:27 PM, Danny Horn dh...@wikimedia.org wrote: So we've figured out a new reply/indentation model that separates those two functions. We've been testing it out on the flow-tests server [1], and we're going to release it to Mediawiki soon. I ran some tests at http://flow-tests.wmflabs.org/wiki/Topic:Sdrqdcffddyz0jeo. Here are my observations: - Posts B, C, and I all reply to A, but the ordering is C, I, B. I'd expect replies to the same parent to be ordered chronologically (and I'd personally expect earliest first). - Posts B and C both reply to A, but are confusingly at different indentation levels. I'd expect replies to the same parent to be indented the same. - Posts I and E are at the same indentation level, despite I being a direct reply to A while E is at the end of the chain A→C→D→E. Similar confusion exists elsewhere. I'd expect two posts at the first indentation level under the same parent to both be replies to that parent. - Things are even weirder with post J: Even though D and its reply E are at the same indentation level, J is suddenly indented more because of an unrelated post I. - Things go completely wrong once we hit the maximum depth, it's impossible to have (or only to be seen as having?) tangents at all. The reply box doesn't even show up under the post where I actually clicked Reply. All in all, I personally find the resulting structure to be very confusing as to what's actually replying to what since the same reply-structure might be displayed in different ways (depending on the order the replies were entered) and different reply-structures can give rise to the same display-structure. (sorry for the self-reply) Some of these might be solved by simply abandoning the idea that first reply = main thread, all others = tangent in favor of displaying flat if this post and its parent both have no sibling post. That /would/ mean, though, that a single reply could result in a major change to display-structure. For example, a reply-chain A→B→C→D→E→F→G would be displayed flat, and then when someone posts B2 as a reply to A we'd have A, then indented under it B and B2, then indented under B we'd have C→D→E→F→G (which might still be displayed flat). And there'd still be the case that a chain of replies and a single post with multiple direct replies (none of which were replied to) could be displayed the same in some cases, but that seems less likely to be confusing to a reader. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] Maps
David Gerard wrote: Looks like just a collaboration :-) https://www.mediawiki.org/wiki/OpenStreetMap https://meta.wikimedia.org/wiki/OpenStreetMap https://wiki.openstreetmap.org/wiki/Collaboration_with_Wikipedia Obviously we should be doing our own tile rendering and serving, for example. Thanks for these links. I believe OpenStreetMap previously had a relationship with Wikimedia Germany and the Toolserver(?). I'm not sure if that endeavor is related to this one. And I'm not sure what the scopes of these projects are. It looks like this new project would be the Wikimedia Foundation acting as both the (tile)server and the client, using data from OpenStreetMap. Is that correct? If so, will the tileserver be considered a public service for use outside of Wikimedia wikis? And will this service be hosted on Wikimedia Labs? Expanding the mediawiki.org and Meta-Wiki pages to include more information about the history here would be great. MZMcBride ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Re: [Wikitech-l] regarding gsoc 2015
Hello Arindam, There are 3 different ideas listed under Mediawiki extensions on https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects https://www.mediawiki.org/wiki/Outreach_programs/Possible_projects If you click on these, you’ll see a Phabricator task which explains the idea and suggests some microtasks that a prospective student should work on. You can start working on the one(s) you find interesting. Also, you can start writing a proposal for the project you want to work on. How to write a proposal is explained on the page linked above itself. Thank you! Niharika. On Mar 18, 2015, at 9:57 PM, Arindam Padhy b113...@iiit-bh.ac.in wrote: i am interested in the mediawiki extensions idea proposed by the org. what should i do next...?? On Wed, Mar 18, 2015 at 5:56 PM, Quim Gil q...@wikimedia.org wrote: Hi Arindam, On Tue, Mar 17, 2015 at 8:58 PM, Arindam Padhy b113...@iiit-bh.ac.in wrote: hello i am a b.tech student pursuing my carrer at iiit bhubaneswar,india. i am deeply interested in gsoc 2015 and wanted to do a project under this organization. how should i proceed..?? Please go to https://www.mediawiki.org/wiki/Google_Summer_of_Code_2015 and check the project ideas proposed. do we need to solve any bugs..?? Yes, we are requiring candidates to solve microtasks as part of their evaluation. Every project idea proposed has a list of suggested microtasks. ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l ___ Wikitech-l mailing list Wikitech-l@lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/wikitech-l
