I'm happy to add links if somebody provides them. :)

I've linked Commons App to http://www.mediawiki.org/wiki/Commons_Mobile_upload_app but I don't know which other links you'd like to see here.
Maybe http://meta.wikimedia.org/wiki/Mobile_projects/Platforms_Support_Status ?

(In reply to comment #2)

I've linked Commons App to
http://www.mediawiki.org/wiki/Commons_Mobile_upload_app but I don't know which
other links you'd like to see here.
Maybe http://meta.wikimedia.org/wiki/Mobile_projects/Platforms_Support_Status ?

The problem is exactly that I don't even know what apps they are exactly...

That's something I cannot fix myself, hence CC'ing mobile team members.

There are so many apps now that it's hard to tell what's what

yuvipanda / preilly:
Are there "canonical" links that explain each mobile app?
Or is linking in Bugzilla to the generic page http://meta.wikimedia.org/wiki/Mobile_projects/Platforms_Support_Status considered enough to make users report their problems in the right place?

(In reply to comment #4)

That's something I cannot fix myself, hence CC'ing mobile team members.

There are so many apps now that it's hard to tell what's what

yuvipanda / preilly:
Are there "canonical" links that explain each mobile app?

As for the Wikipedia App, last time I spent some considerable time looking for a description page I found that the most complete one was https://translatewiki.net/wiki/Translating:WikipediaMobile (written by Brion).

[assigning to a random member of the Mobile team to get information]

So the Wiki Loves Monuments app product can be hidden / removed - all bugs have been autoclosed on it, and no further work is expected to happen.

So that leaves us with 4 apps. I believe that that can be reduced further down to two products

Wikipedia App - this can contain all of the current Products "Wikipedia App', 'Wiktionary App', and 'Wikisource App'. They all share the same base source code, with only minor modifications, and a bug in one is bound to be a bug in the others too. I asked Tpt, who maintains the Wikisource fork, and he had no objections. So can these be three be merged, with the description set to 'PhoneGap based mobile applications for Wikipedia / Wiktionary / Wikisource'?

Commons App - This can just stay as is.

Hi Yuvi,

(In reply to comment #7)

So the Wiki Loves Monuments app product can be hidden / removed - all bugs
have been autoclosed on it, and no further work is expected to happen.

We cannot remove products in Bugzilla for change history reasons, but edit products to close them "for new bug entry". Thanks for letting us now, and this is something that can be done immediately.

So that leaves us with 4 apps. I believe that that can be reduced further
down to two products

Wikipedia App - this can contain all of the current Products "Wikipedia App',
'Wiktionary App', and 'Wikisource App'. They all share the same base source
code, with only minor modifications, and a bug in one is bound to be a bug in
the others too. I asked Tpt, who maintains the Wikisource fork, and he had no
objections. So can these be three be merged, with the description set to
'PhoneGap based mobile applications for Wikipedia / Wiktionary / Wikisource'?

The argumentation is convincing, but as far as I know plans are to move from PhoneGap-based apps to native implementations, so what's the advantage of merging it all into product if the codebases will be totally different soon again?

Valerie.m.juarez wrote:

'WikiLoves Monuments Mobile' is now closed to new bugs.

http://www.mediawiki.org/wiki/Wikimedia_Apps is nominally the main page for mobile apps - at least the "official". As you see the page could receive a bit of improvement and connections to the rest of mobile efforts at the WMF and the community at large.

(In reply to comment #10)

http://www.mediawiki.org/wiki/Wikimedia_Apps is nominally the main page for
mobile apps - at least the "official". As you see the page could receive a
bit
of improvement and connections to the rest of mobile efforts at the WMF and
the
community at large.

That's the project/team page, it's surely not the page for the final products.
The thing closest to a master page was https://meta.wikimedia.org/?oldid=5183588 which recently got killed without getting a replacement; now it's apparently [[m:Wikimedia Apps]], judging from [[m:Mobile projects]].

(In reply to comment #8)

The argumentation is convincing, but as far as I know plans are to move from
PhoneGap-based apps to native implementations, so what's the advantage of
merging it all into product if the codebases will be totally different soon
again?

They'll be native, but the different implementations will differ in the same way. They'll have the same codebase with minor modifications (logo, i18n, etc) and not be too different.

Summarizing:

• https://meta.wikimedia.org/wiki/Wikimedia_Apps should get proper links to respective bugtrackers for each product
• Wiki Loves Monuments app: Closed already for new bug reports.
• Keep "Commons App" as is.
• Merge "Wikipedia App', 'Wiktionary App', 'Wikisource App' into "Wikipedia App", set description to 'Mobile applications for Wikipedia / Wiktionary / Wikisource'.

(In reply to comment #12)

They'll be native, but the different implementations will differ in the same
way. They'll have the same codebase with minor modifications (logo, i18n,
etc) and not be too different.

Yuvi: So would you like to have any subcomponents in that new "Wikipedia App" product at all? Does anybody else involved in developing mobile apps agree with this proposal? It's really up to the mobile team how they want to organize bug reports and what's the most effective way, and I'm happy to implement it then.

For now, components do not make sense. Some way of specifying which app was affected would be nice, but don't think components is the way to do it. I'm okay with just letting it be and having people specify it in the bug body.

(In reply to comment #14)

For now, components do not make sense. Some way of specifying which app was
affected would be nice

When playing with Mozilla Bugzilla yesterday I realized that we could set up a custom field with predefined values for a specific Bugzilla product. I'd have to explain how to search for this in the query interface though. :)

Yuvi: One last question as I don't want to step on anybody's feet: The rest of the mobile team is fine with these changes in Bugzilla (or just doesn't care)?

At the moment that'd be just brion (and perhaps tfinc?) so if you want you can wait on him to wake up (PST). I don't foresee problems, however.

And Michelle, CCed.

Proposal was also announced again in http://lists.wikimedia.org/pipermail/mobile-l/2013-March/005914.html

Proceeded:

• Merged 'Wikipedia App', 'Wiktionary App', 'Wikisource App' into "Wikipedia App" by moving all tickets (also closed ones) from 'Wiktionary App', 'Wikisource App' to 'Wikipedia App'. I've added a comment to all bug reports to filter bugmail: "[Merging 'Wiktionary App'&'Wikisource App' into 'Wikipedia App', see bug 41922]"
  • For those few open tickets, I manually added a prefix to the bug summary so it's easier to spot where they were originally filed.
• Deleted Bugzilla products 'Wiktionary App', 'Wikisource App' (that's only possible if no bug reports are left in there).
• Updated description of 'Wikipedia App' to 'Mobile applications for Wikipedia / Wiktionary / Wikisource' plus added a link to https://meta.wikimedia.org/wiki/Wikimedia_Apps .

Closing as FIXED, but https://meta.wikimedia.org/wiki/Wikimedia_Apps should still get updated to properly point to Bugzilla. Yuvi?

So I don't know anything about these Wiktionary and Wikisource apps, but the impression I get is they're forks of the old PhoneGap app for Android only?

I'd really like to put these in a separate product, or at least a component, or something, so they're not filling up the actionable bug reports for the Wikipedia app.

Otherwise I'll probably just close them all...

Ok I'm splitting them out as components, along with the unofficially semi-maintained Windows 8 and Firefox OS Wikipedia apps. Yay!