Last modified: 2014-08-26 22:26:20 UTC
Previously iOS and Android apps share the same codebase, but nowadays they're two completely different projects except for the same goal to read Wikipedia. Having them mixed makes bug list and other stuff difficult to navigate.
While this is true, I do not know if having them as separate products would make any sense. Perhaps make components something like: - Android App - iOS App - Extension:MobileApp (For CSS styling issues, which are common) - General/Unknown Thoughts? This should make filtering per platform easier. The 'versions' would still be useful for determining alpha/beta/stable.
Sounds a bit like https://bugzilla.wikimedia.org/describecomponents.cgi?product=Commons%20App to me :) Yuvi: Do the current components make any sense to you? How else are developers for this app and should be CC'ed here to discuss what works best? Also see https://bugzilla.wikimedia.org/describecomponents.cgi?product=MobileFrontend for an example for alpha/beta/stable as *components* (could of course also be versions as proposed here). Having this as components was requested by the mobile team about three months ago (see bug 61280); it might be good to ask on the mailing list if handling tickets in Bugzilla has become less cumbersome for them and what there experience has been so far if anybody wants to go ahead. In general I'm pretty open to trying stuff out, whatever works for the maintainers - if you want my thoughts I first need questions to answer though. :P
So this is different than MF in that the iOS and Android are entirely different codebases, so separating codebases by component makes sense (similar to Mediawiki Extensions, I guess). It would also make default cc's easier, I think. So, Components: 1. Android App 2. iOS App 3. Extension:MobileApp 4. General / Unknown Versions: 1. Alpha 2. Beta 3. Stable That should help, I think :)
In answer to who else is working on apps, I've added the ones I know of. In a related topic, mhurd should be on the default cc list for new iOS bugs, and dbrant for Android bugs.
I think keeping them together makes sense. Although bugs are tagged in the Component bit as being only on one platform, most bugs are actually checked by both the iOS and Android teams to make sure the bug isn't present in their app. Additionally, we are ultimately a single team (the Mobile Apps team), and some people like Brion Vibber actively work on both platforms. That said, as the product manager I'm not the primary consumer of Bugzilla. Ultimately I'll support whatever decision my engineers make.
We right now can't at all have anyone set to just have default cc on iOS *or* Android, while with components we can. And if we have components we can still have people on default cc for everything, so we don't lose that ability at all. So let's split the components to have slightly more flexibility? Searching also becomes easier then, I think.
I'm happy to set up the structure in comment 3 in a few days (if no comments get added here that create more discussion or a different proposal).
(In reply to Andre Klapper from comment #7) > I'm happy to set up the structure in comment 3 in a few days (if no comments > get added here that create more discussion or a different proposal). I've invited the other engineers (Dmitry, Brion, Monte) to comment on this.
Added Bernd as well. I assume he'd want to be on default cc for the Android component.
(In reply to Yuvi Panda from comment #3) > > So, > > Components: > 1. Android App > 2. iOS App > 3. Extension:MobileApp IMO this should be in MediaWiki extensions -> MobileApp > 4. General / Unknown > > Versions: > 1. Alpha > 2. Beta > 3. Stable > Where are we planning to put the bugs for the "legacy" apps? +1 to the general idea.
Thank you, Sage. Yes, I'd like to be on default cc for Android.
(In reply to Kunal Mehta (Legoktm) from comment #10) > > 3. Extension:MobileApp > IMO this should be in MediaWiki extensions -> MobileApp I have no opinion on that - we just moved MobileFrontend from the "MediaWiki extensions" to its own product to give it more visibility, and most users might not find it. And most users might not be able to know on which level the issue happens anyway, so this would need triaging. > Where are we planning to put the bugs for the "legacy" apps? There is the "Unofficial Apps" product already.
We should keep MobileApp in the Wikimedia Apps product, since it is completely unused elsehwere, and for easier visibility.
(In reply to Yuvi Panda from comment #3) > Components: > 1. Android App > 2. iOS App > 3. Extension:MobileApp > 4. General / Unknown I have created the components listed above. I have disabled creating new tickets or moving existing tickets into the following components: * Automated Builds * Generic * History * Localization/Translation/Language * Media Uploads * Near by * Save Article * Search * Settings * Share
> Versions: > 1. Alpha > 2. Beta > 3. Stable I've disabled the existing versions for bug entry or changing existing tickets to those versions. I've created above three versions. I won't try to move (open) tickets to new versions and components today anymore (it's getting late here); feel free to start with that...
(In reply to Yuvi Panda from comment #13) > We should keep MobileApp in the Wikimedia Apps product, since it is > completely unused elsehwere, and for easier visibility. That makes it hard to figure out where to fill bugs for MobileApp. I have just filled bug 65964 'Create a Bugzilla component for MobileApp MediaWiki extension' because I definitely expect mediawiki/extensions/MobileApp.git bugs to be filled under Bugzilla at MediaWiki Extensions > MobileApp. Please? :-(
I myself don't care where it is - up to mobile team how they want to organize things...
Andre: I would like to be added to the default cc for the android components as well. :)
(In reply to Sage Ross from comment #18) > Andre: I would like to be added to the default cc for the android components > as well. :) Added you to the default CC for the component ""Android App""
(In reply to Andre Klapper from comment #15) > I won't try to move (open) tickets to new versions and components today > anymore (it's getting late here); feel free to start with that... Is there an ETA when this will get done? Right now bugs are split between two components... (In reply to Andre Klapper from comment #17) > I myself don't care where it is - up to mobile team how they want to > organize things... No one has objected in the past 2 weeks since hashar suggested it, so lets just do it (putting MobileApp back in MediaWiki extensions).
(In reply to Kunal Mehta (Legoktm) from comment #20) > No one has objected in the past 2 weeks since hashar suggested it, so lets > just do it (putting MobileApp back in MediaWiki extensions). I'd like to see an explicit statement by Yuvi, Bernd, or Dan here.
Yuvi, Bernd, Dan: ping
(In reply to Andre Klapper from comment #22) > Yuvi, Bernd, Dan: ping I'd prefer one of the engineers to answer this with what they prefer, since Bugzilla is primarily for them.
Yuvi, Bernd: ping I'd prefer one of the engineers to answer this with what they prefer, since Bugzilla is primarily for them.
I'm fine with having Android and iOS as components. I think MobileApp should probably not be a separate component since most users are not aware of it when they submit a bug in the app. It's only used by Android and iOS. But it doesn't matter much since I don't think there would be many defects for this anyways. The few ones we currently have are hiding in the General/Unknown category right now. Long story short. Either way is fine with me. Dmitry probably should speak up as well since he's acting as tech lead for the Android team. For some reason I still don't get cc'd when a new Android bug gets submitted, though.
It really doesn't matter to me where the MobileApp component ends up. As Bernd mentioned, users of the apps are not aware of its existence, and will not file bugs against it. The patches that we push to it are usually associated with bugs filed under the app components (Android / iOS) anyway. If it makes more sense for the sake of consistency to have MobileApp be under MediaWiki Extensions, then by all means move it there! (The other components (Android, iOS) are fine as they are)
Alright, so we'll leave it here. We won't have Bugzilla around for too long anyway as we're heading towards Phabricator. (In reply to Bernd Sitzmann from comment #25) > For some reason I still don't get cc'd when a new Android bug gets > submitted, though. Uhm, sorry. Fixed now.
