[WikimediaMobile] Prepare your small tasks to mentor a new contributor! (Google Code-in early heads-up)

2019-09-11 Thread Andre Klapper
(Note: This is only an early heads-up, to be prepared. Google Code-in
has NOT been announced yet, but last year, GCI mentors asked for more
time in advance to identify tasks to mentor. Here you are. :)

* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?

Google Code-in (GCI) is an annual contest for 13-17 year old students.
GCI 2019 has not yet been announced but usually takes place from late
October to December. It is not only about coding: We also need tasks
about design, docs, outreach/research, QA.

Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors , add
your name to the mentors table, and start tagging tasks in Wikimedia
Phabricator by adding the #gci-2019 project tag.
We will need MANY mentors and MANY tasks, otherwise we cannot make it.

Last year, 199 students successfully worked on 765 tasks supported by
39 mentors. For some achievements from the last round, see
https://wikimediafoundation.org/news/2019/02/20/partnerships-make-it-possible-behind-our-role-in-google-code-in-2018/

Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and replace 2 uses of
Linker::link() from the list in T223010" style).

We also have more than 400 unassigned open #good-first-bug tasks:
https://phabricator.wikimedia.org/maniphest/query/3YnDUWYJfXSo/#R
Can and would you mentor some of these tasks in your area?

Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
   https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2019#List_of_Wikimedia_mentors

Thanks (as we will not be able to run this without your help),
andre
-- 
Andre Klapper (he/him) | Bugwrangler / Developer Advocate
https://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Google Code-in 2018: Mentor some smaller tasks for young contributors!

2018-09-07 Thread Andre Klapper
: Read https://www.mediawiki.org/wiki/Google_Code-in/Mentors and
add your name to the mentors table and start tagging #GCI-2018 tasks.
We'll need MANY mentors and MANY tasks, otherwise we cannot make it.


Google Code-in is an annual contest for 13-17 year old students. It
will take place from Oct23 to Dec13. It's not only about coding: 
we also need tasks about design, docs, outreach/research, QA.

Last year, 300 students worked on 760 tasks supported by 51 mentors.
For some achievements from last round, see
https://blog.wikimedia.org/2018/03/20/wikimedia-google-code-in-2017/

While we wait whether Wikimedia will get accepted:
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has some smaller design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?

Note that "beginner tasks" (e.g. "Set up Vagrant") and generic
tasks are very welcome (like "Choose and fix 2 PHP7 issues from
the list in https://phabricator.wikimedia.org/T120336; style).

We also have more than 400 unassigned open #easy tasks listed:
https://phabricator.wikimedia.org/maniphest/query/HCyOonSbFn.z/#R
Can you mentor some of those tasks in your area?

Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Read
   https://www.mediawiki.org/wiki/Google_Code-in/Mentors
, ask if you have any questions, and add your name to
https://www.mediawiki.org/wiki/Google_Code-in/2018#List_of_Wikimedia_mentors

(If you have mentored before and have a good overview of our
infrastructure: We also need more organization admins! See 
https://www.mediawiki.org/wiki/Google_Code-in/Admins )

Thanks (as we cannot run this without your help),
andre

-- 
Andre Klapper  |  ak...@gmx.net
https://blogs.gnome.org/aklapper/



___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Google Code-in: Get your tasks for young contributors prepared!

2017-10-16 Thread Andre Klapper
Google Code-in is an annual contest for 13-17 year old students. It
will take place from Nov28 to Jan17 and is not only about coding tasks.

While we wait whether Wikimedia will get accepted:
* You have small, self-contained bugs you'd like to see fixed?
* Your documentation needs specific improvements?
* Your user interface has small design issues?
* Your Outreachy/Summer of Code project welcomes small tweaks?
* You'd enjoy helping someone port your template to Lua?
* Your gadget code uses some deprecated API calls?
* You have tasks in mind that welcome some research?

Also note that "Beginner tasks" (e.g. "Set up Vagrant" etc) and
"generic" tasks are very welcome (e.g. "Choose & fix 2 PHP7 issues
from the list in https://phabricator.wikimedia.org/T120336 ").
Because we will need hundreds of tasks. :)

And we also have more than 400 unassigned open 'easy' tasks listed:
https://phabricator.wikimedia.org/maniphest/query/HCyOonSbFn.z/#R
Would you be willing to mentor some of those in your area?

Please take a moment to find / update [Phabricator etc.] tasks in your
project(s) which would take an experienced contributor 2-3 hours. Check

   https://www.mediawiki.org/wiki/Google_Code-in/Mentors

and please ask if you have any questions!

For some achievements from last round, see
https://blog.wikimedia.org/2017/02/03/google-code-in/

Thanks!,
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/

___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Prague Pre-Hackathon - registration and travel scholarships open

2017-03-02 Thread Andre Klapper
On Thu, 2017-03-02 at 09:12 -0800, Pine W wrote:
> I'm glad to see that work is continuing on the Commons app. Just
> wondering, is there a chance of creating some kind of link between
> the Commons app and the Wikipedia app, or maybe even merging them at
> some point?

Could you elaborate why you're asking? Do you have some potential
improvements in mind, or problems that might get solved by merging?

Thanks,
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/

___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Wikimedia takes part in Google Code-in. Which small Mobile Apps tasks do you plan to mentor?

2016-11-07 Thread Andre Klapper
Wikimedia is among the 17 organizations in Google Code-in (GCI) 2016! 
GCI starts on November 28th. It's a contest for 13-17 year old students
working on small tasks and a great opportunity to let new contributors
make progress and help with smaller tasks on your To-Do list!

There are currently 13 open Mobile Apps tasks marked as easy:
https://phabricator.wikimedia.org/maniphest/query/0pQOZawilr3q/#R 

What we want you to do:

BECOME A MENTOR:

1. Go to https://www.mediawiki.org/wiki/Google_Code-in_2016 and add
yourself to the mentor's table.
2. Get an invitation email to register on the contest site.

PROVIDE SMALL TASKS:

We want your tasks in the following areas: code, outreach/research,
documentation/training, quality assurance, user interface/design.
(Please note that translation tasks are not allowed.)

1. Create a Phabricator task (which would take you 2-3h to complete) or
pick an existing Phabricator task you'd mentor.
2. Add the "Google-Code-In-2016" project tag.
3. Add a comment "I will mentor this in #GCI2016".

Looking for task ideas? Check the "easy" tasks in Phabricator:
https://www.mediawiki.org/wiki/Annoying_little_bugs offers links. 

Make sure to cover expectations and deliverables in your task.
And once the contest starts on Nov 28, be ready to answer and review
contributions quickly. 

Any questions? Just ask, we're happy to help.

Thank you for your help broadening our contributor base!
andre

-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/

___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] [Apps] Old open "Done"/"Ready for signoff" sprint tasks in Phabricator

2016-06-06 Thread Andre Klapper
On Mon, 2016-06-06 at 13:14 -0700, Max Binder wrote:
> Thanks, Andre. I'll bring these to the Android and iOS POs'
> attention.

Thank you a lot!

> Was the second link supposed to be one specific task, or a Maniphest
> query like the other links?

Only one task. (I should have used singular instead, sorry.)

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/



___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Reading goals for the quarter.

2015-11-02 Thread Andre Klapper
On Sun, 2015-11-01 at 19:08 -0800, Toby Negrin wrote:
> Our goals for Fiscal Year Q2 (Oct - Dec) are up on the wiki.
> Apologies for this taking so long.
> 
> https://www.mediawiki.org/wiki/Wikimedia_Engineering/2015-16_Q2_Goals
> #Reading

Should that be linked from the central team page on mw.org, like under
"Strategy and planning" of https://www.mediawiki.org/wiki/Reading ?

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/



___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Get those small bugs fixed by new contributors: It's Google Code-In time!

2015-11-01 Thread Andre Klapper
* Do you have small, self-contained, "easy" bugs you'd love to get fixed?
  (Also see https://www.mediawiki.org/wiki/Annoying_little_bugs )
* Does your documentation need improvements?
* Do your old bugs welcome some testing?
* Does your user interface have some small design issues?
* Does the Outreachy/GSoC project you finished welcome small tweaks?
* Would you enjoy helping someone port your template to Lua?
* Does your gadget use some deprecated API calls?
* Do you have some tasks that welcome some research?

Google Code-In (GCI) will take place again in Dec+Jan: a contest for
13-17 year old students to provide small contributions to free software
projects. 
Wikimedia will apply again to take part in GCI. The more tasks we can
offer the likelier the changes Wikimedia will get accepted.

Unsure about quality of contributions and effort?
Read about tgr's post about Multimedia achievements in GCI 2014:
https://lists.wikimedia.org/pipermail/multimedia/2015-January/001009.html

In short:
* Add the project "GCI2015" + a comment to Phabricator tasks you'd mentor.
* Tasks are welcome in five areas: Code; Outreach/Research; 
  Documentation/Training; Quality Assurance; User Interface.
* Make sure the task description provides pointers to help the student.
* Add yourself to the table of mentors on the wikipage.
* "Beginner tasks" (<30 min for an experienced contributor) also welcome.
* "Generic" tasks also welcome (e.g. "Fix two user interface messages from
  the "Blocked By" list in https://phabricator.wikimedia.org/T40638 ").
For all information, check 
https://www.mediawiki.org/wiki/Google_Code-in_2015#Mentors.27_corner

15 Mobile Apps "easy" tasks (are they still valid? are there more?):
https://phabricator.wikimedia.org/maniphest/query/3P9zM7vzlXCS/#R

Can you imagine providing a helping hand to someone fixing tasks?

Please ask if you have questions!

Thank you!
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/



___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Password alternative for mobile

2015-10-29 Thread Andre Klapper
On Thu, 2015-10-29 at 00:17 -0700, Pine W wrote:
> Maybe worth considering as an option for mobile Web and mobile apps?
> http://www.komonews.com/news/tech/Yahoos-updated-email-app-aims-to-ki
> ll-the-password-333096981.html

What is the actual difference to Two-Factor Authentication?

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/



___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Gerrit Cleanup Day on Wed 23rd: Are you ready?

2015-09-21 Thread Andre Klapper
Hi Reading,

the Gerrit Cleanup Day is only two days away (Wed 23rd).
More info: https://phabricator.wikimedia.org/T88531

Do you feel prepared and all Reading team members know what to do?
 
If not, what are you missing and how can we help?

Some Gerrit queries for each team are listed under "Gerrit queries per
team/area" in https://phabricator.wikimedia.org/T88531 
Are they helpful and a good start? Or do they miss some areas (or do
you have existing Gerrit team queries to use instead or to "integrate",
e.g. for parts of MediaWiki core you might work on)?

Also, which person will be the main team contact for the day (and
available in #wikimedia-dev on IRC) and help organize review work in
your areas, so other teams could easily reach out?
Some team plates are emptier than others so they're wondering where and
how to lend a helping hand (to find out in advance, due to timezones).

Thanks for your help to make the Gerrit Cleanup day a success!

andre

-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/



___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Old Wikipedia-App tasks in Phabricator

2015-08-11 Thread Andre Klapper
Hey Mobile Apps crew,

there are 58 open tasks in archived Wikipedia-App-* Phabricator
projects which do not have any active projects associated either:

https://phabricator.wikimedia.org/maniphest/query/s4y9prrcTSnQ/#R

What should happen to these tasks and what feedback should be given to
the folks who spent time to report those issues?

We can mass-{add comments, change statuses, change priorities} but I
don't know which message you'd like to send out here.

Thanks in advance!,
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Outdated Reading-Admin Phab project description

2015-07-22 Thread Andre Klapper
Hi,

could someone please update the description of Reading-Admin in
https://phabricator.wikimedia.org/project/profile/1199/ ?
Currently it talks about future plans to happen in April 2015.

Thanks in advance,
andre

PS: Sent this to mobile-l after starring at the numerous lists at
https://www.mediawiki.org/wiki/Reading#Mailing_Lists for a while.
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Mobile-Apps' Unbreak now tasks in Phabricator

2015-07-07 Thread Andre Klapper
On Mon, 2015-07-06 at 18:40 -0400, Brian Gerstle wrote:
 I closed the iOS ones, which were already in the Done column in 
 Phab 2 sprints ago.  Sorry for the confusion, still grappling w/ task 
 state transitions vs. columns.

Thanks a lot! No problem, I just look at open Unbreak now and High
priority tasks from time to time and ping... :)

(Regarding connecting the Done with the Resolved status
automatically, that's https://secure.phabricator.com/T5474 )

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Android app bug report template

2015-07-07 Thread Andre Klapper
On Tue, 2015-07-07 at 13:21 +0200, Joaquin Oltra Hernandez wrote:
 How are you generating the links? Sounds like a great way to make the
 template cards actually super useful.

If this question is about the URL parameters to prefill certain fields:
https://www.mediawiki.org/wiki/Phabricator/Help#Passing_certain_values_in_the_task_creation_URL

Cheers,
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Mobile-Apps' Unbreak now tasks in Phabricator

2015-07-06 Thread Andre Klapper
Hi,

could the Apps Team please update their open tasks with Unbreak Now!
priority [1] in Phabricator's Mobile-App-Sprint-58-iOS project? 

https://phabricator.wikimedia.org/maniphest/query/40ps.K.br_Ri/#R

That Sprint ended one month ago and all remaining tasks are in the
Done column.

Thanks in advance,
andre

[1] Something is broken and needs to be fixed immediately as per
https://www.mediawiki.org/wiki/Phabricator/Project_management#Setting_task_priorities
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Task/bug naming conventions

2015-06-09 Thread Andre Klapper
On Mon, 2015-06-08 at 10:36 -0700, Toby Negrin wrote:
 I've always used enhancement for this purpose -- does phabricator 
 actually support this?

Used where? Bugzilla, Mingle, Trello? :)

What is the underlying need to mark a task as enhancement?
Corey filed https://phabricator.wikimedia.org/T93499 to Add support
for task types and listed some reasons for differentation there. And
I'm waiting for some Team Practices Group input on that task...

We discussed having a Severity or Impact field before migrating
Bugzilla to Phabricator in T102 (as Bugzilla's Severity field offered a
value called enhancement). In the end we decided to not have that.


In general this might be a discussion to have on the teampractices
mailing list. I see nothing really mobile-specific in this discussion
and I'm usually concerned that teams end up discussing their needs in
their silos without the bigger picture and potentially finding a good
solution across teams, assuming that other teams have similar needs.
(And I hope this doesn't come across a rude or too blunt - I just can't
find a better wording in English language on this morning. Sorry.)

Cheers,
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Google Code-In 2014: Become a mentor and add tasks!

2014-11-03 Thread Andre Klapper
Hi,

Google Code-In (GCI) will soon take place again - a contest for 13-17
year old students to contribute to free software projects. 

Wikimedia wants to take part again. 
Last year's GCI results were surprisingly good - see
https://www.mediawiki.org/wiki/Google_Code-in_2013

We need your help:

1) Go to 
https://www.mediawiki.org/wiki/Google_Code-in_2014#Mentors.27_corner and
read the information there. If something is unclear, ask!

2) Add yourself to the table of mentors on 
https://www.mediawiki.org/wiki/Google_Code-in_2014#Contacting_Wikimedia_mentors
- the more mentors are listed the better our chances are that Google
accepts us.

3) Please take ten minutes and go through open recent tickets in
https://bugzilla.wikimedia.org in your area of interest. If you see
self-contained, non-controversial issues with a clear approach which you
can recommend to new developers and would mentor: Add the task to
https://www.mediawiki.org/wiki/Google_Code-in_2014#Proposed_tasks


Until Sunday November 12th, we need at least five tasks from each of
these categories (plus some less technical beginner tasks as well):
* Code: Tasks related to writing or refactoring code
* Documentation/Training: Tasks related to creating/editing documents
and helping others learn more - no translation tasks
* Outreach/research: Tasks related to community management,
outreach/marketing, or studying problems and recommending solutions
* Quality Assurance: Tasks related to testing and ensuring code is of
high quality
* User Interface: Tasks related to user experience research or user
interface design and interaction

Google wants every organization to have 100+ tasks available on December
1st. Last year, we had 273 tasks in the end.

Note that you could also create rather generic tasks, for example fixing
two interface messages from the list of dependencies of
https://bugzilla.wikimedia.org/show_bug.cgi?id=38638


Helpful Bugzilla links:

* Reports that were proposed for GCI last year and are still open:
https://bugzilla.wikimedia.org/buglist.cgi?quicksearch=ALL%20whiteboard%3Agci2014

* Open Wikipedia Mobile App tickets created in the last six months (if I
got your products and components right):
https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=REOPENEDchfield=[Bug%20creation]chfieldfrom=-6mkeywords=easykeywords_type=nowordsresolution=---product=Wikipedia%20App

* 5 existing Wikipedia Mobile App easy tickets (are they still valid?
Are they really self-contained, non-controversial issues with a clear
approach? Could some of them be GCI tasks that you would mentor? If so,
please tag them as described above!):
https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=REOPENEDkeywords=easykeywords_type=allwordsresolution=---product=Wikipedia%20App

* Open Mobile platform tickets created in the last six months (if I got
your products and components right):
https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=REOPENEDchfield=[Bug%20creation]chfieldfrom=-6mkeywords=easykeywords_type=nowordsresolution=---product=MobileFrontendproduct=MediaWiki%20extensionscomponent=alphacomponent=betacomponent=stablecomponent=General/Unknowncomponent=Feature%20requestscomponent=Hygienecomponent=Uploadscomponent=PageImagescomponent=TextExtracts

* 4 existing Mobile platform easy tickets (are they still valid? Are
they really self-contained, non-controversial issues with a clear
approach? Could some of them be GCI tasks that you would mentor? If so,
please tag them as described above!):
https://bugzilla.wikimedia.org/buglist.cgi?bug_status=UNCONFIRMEDbug_status=NEWbug_status=REOPENEDkeywords=easykeywords_type=allwordsresolution=---product=MobileFrontendproduct=MediaWiki%20extensionscomponent=alphacomponent=betacomponent=stablecomponent=General/Unknowncomponent=Feature%20requestscomponent=Hygienecomponent=Uploadscomponent=PageImagescomponent=TextExtracts

Could you imagine mentoring some of these tasks?


Thank you for your help in reaching out to new contributors and making
GCI a success again! Please ask if you have questions.

Cheers,
andre


PS: And in a future Phabricator world, Bugzilla tickets with the 'easy'
keyword will become Phabricator tasks with the 'easy' project.
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Pulling the Commons app

2014-09-17 Thread Andre Klapper
On Tue, 2014-09-16 at 13:32 -0700, Brion Vibber wrote:
 Ok, I've killed the iOS version as well.

There's a Commons App product in bugzilla.wikimedia.org with 213
tickets, 82 of them open.
There is also an Unofficial Apps product in Bugzilla:
https://bugzilla.wikimedia.org/describecomponents.cgi?product=Unofficial%20Apps

What would you like to see happen in Bugzilla? Move tickets from
'Commons App' to a new component under 'Unofficial'? All lowest
priority? Should Brion really be default assignee for all those
'Unofficial' tickets?

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] wikimediafoundation.org mobile site

2014-04-10 Thread Andre Klapper
On Thu, 2014-04-10 at 15:14 +0200, Željko Filipin wrote:
 I vaguely remember http://wikimediafoundation.org/ having a mobile site,
 but when I visit it from an Android or iOS device, desktop site opens. I
 also vaguely remember there was a mobile site link at the home page, but
 I do not see it now.
 
 If I visit http://m.wikimediafoundation.org/ desktop home page opens, or at
 least I see no difference.
 
 I am doing something wrong?

https://bugzilla.wikimedia.org/show_bug.cgi?id=56836#c2 

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Fwd: [Wiki Loves Monuments] WLM Android mobile app is back

2013-08-26 Thread Andre Klapper
On Mon, 2013-08-26 at 08:07 +0200, Maarten Dammers wrote:
 You can file bugs at 
 https://bugzilla.wikimedia.org/enter_bug.cgi?product=Wiki%20Loves%20Monuments 
 (for now component general, will ask for a mobile component)

Also see the discussion in
https://bugzilla.wikimedia.org/show_bug.cgi?id=5 as there is a
WikiLoves Monuments Mobile product in Bugzilla already, which got
closed due to being unmaintained.

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


Re: [WikimediaMobile] Caching Problem with Mobile Main Page?

2013-05-03 Thread Andre Klapper
On Fri, 2013-05-03 at 10:31 +0530, Yuvi Panda wrote:
 Encountered 
 https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Issue_with_Main_Page_on_mobile.2C_viz._it_hasn.27t_changed_since_Tuesday
 
 Some people seem to be having problems with the mobile main page being
 cached too much. Can someone look into it?

Also reported as https://bugzilla.wikimedia.org/show_bug.cgi?id=48062

andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l


[WikimediaMobile] Killing RESOLVED LATER in Bugzilla.

2012-12-12 Thread Andre Klapper
I'm aiming at killing RESOLVED LATER in Bugzilla as discussed in
http://lists.wikimedia.org/pipermail/wikitech-l/2012-November/064240.html
Recommendation is to use either RESOLVED WONTFIX (will not be fixed), or
to set lowest priority.

Mobile bugs affected:
* Monuments App:
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=38935,39714,39712,39907
* Wikipedia App:
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=31966,32913,33618
* Wikimedia Mobile (hence also needs to be moved *if* reopened):
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=33202,32541,17454
* MWextensions/MobileFrontend:
https://bugzilla.wikimedia.org/buglist.cgi?bug_id=19920,28528,30827,32098,32254,32290,32292,32320,33444,34233,3432535040,35525,36029,36407,36712,36838,37716,37944

Do you prefer if I mass-reopen them and set priority to Lowest, or
would you like to skim them in the next days to set
WONTFIX/FIXED/whatever?

Thanks,
andre
-- 
Andre Klapper | Wikimedia Bugwrangler
http://blogs.gnome.org/aklapper/


___
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l