> OK, how about David Goldfarb's video ringtone support patches? He > started working on those a long time ago. Originally the patches had > several issues with them, Google was quick to jump in and point out > what was wrong. He resolved the issues and submitted his patches again > (over a month ago). Once the patches lacked the issues pointed out, > what happens then? Nothing.
David had long discussions directly with the media team and myself by email about his patch. Last time I checked his work the UI he was proposing was still not acceptable for inclusion in the platform. > It seems you don't understand. The entire ecosystem is being strangled > by this. It's not a nice to have feature. It seems like if someone > over there did understand, this would be a feature in Donut. If you've > starred the feature request in the bug database you'd understand how > angry people are about this. But I don't think anybody is even > notified when people post "Wow! I am getting way too much email from > having this issue starred, so I'm unstarring it". Wanting this feature does not mean we will add it at this point of the development process. The same applies to all of the features the core Android team would like to add and know would be enjoyed by many. In this particular case, and I talked briefly with the author about it, we also need to take into account the binary size of this feature (at least if you guys want the final build to fit on an HTC Dream/T-Mobile G1), the added dependency (new library) and the extra QA. This just cannot happen for Donut. We also need to see if it's something that makes sense to support in Android. Yes this issue was starred by 80 people. But this number is (unfortunately) dwarfed by the number of users of Android and we need to question the fact whether this feature would be used by enough people to warrant its inclusion. That's true of all features we include. Now in this particular case an Android engineer has been actively participating on the bug report and even took measure of the impact on batter life. Not having this feature in Donut is not a question of us ignoring it, it's just about the fact that it's too late in the development cycle. Period. > That's what you say. > Name one significant user visible feature that > has made its way from a non OHA member contributor from the public > repository into Donut in Google's private repo. Not a bugfix, or a > typo. Something visible to the user in the way that FLAC support or > Video Ringtones or something of that ilk would be. My point is, how > many contributions do you expect to receive when the worthy ones so > far are still unattended to? FLAC was too late and video ringtones were still not in good enough state. I just told you I am committed to accepting features and bug fixes from the community in specific areas. I cannot point you to features that have been merged in these areas if I don't receive patches in the first place. I would also be happy to discuss potential changes and their impact and relevance. Also please remember that because a feature, even if great, is submitted it does not mean it will make it into Android. There should be little reason for a feature to not make it but accept the fact that we cannot accept just *any* feature, especially considering some constraints we have to deal with (like the firmware size limit on 1st generation phones.) -- Romain Guy Android framework engineer [email protected] Note: please don't send private questions to me, as I don't have time to provide private support. All such questions should be posted on public forums, where I and others can see and answer them --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Android Discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
