On Wed, 22 Dec 2010 14:26:27 +0800
"Zhang, Vivian" <[email protected]> wrote:

> It is a business decision of reversion PA to 0.9.19 for integrating
> voice call features on handset,

While I don't doubt the veracity of the decision, I wonder why, yet
again, it seems that a PROJECT impacting change was discussed and
decided behind the "closed doors" of a PRODUCT schedule and
requirements?  I am probably just being naive...

> which is announced on Meego Weekly Newsletter (ww50) from Imad.

That's nice but, since that newsletter is sent only to Intel recipients
(AFAICS), it does nothing with respect to keeping the MeeGo community
informed.

Clearly I failed to read the Newsletter in details and missed the one
bullet item that mentioned this decision in the "Core 1.2 Execution
Update" section.

Never-the-less, the newsletter makes no mention of how or why the
decision was made... which I would never think to expect for PRODUCT
specific communications, but since this decision impacts the PROJECT as
a whole, it ought to have been proposed and vetted out publicly (maybe
as an RFC) so the full extent of both the technical and perceptual
impacts can be exposed and considered.  Again, I am probably just being
naive still...

> I have revoked the submission and we are still talking about the
> detailed reversion plan.

Could I beg of you and others involved in this to please hold these
conversations on the mailing lists (meego-dev at least I would think)
rather than behind closed doors?

> I will do the local test before submitting it later, any existing
> apps/libraries will be affected by the PA reversion as you know? 

Personally, no, but that is why we need this vetted public ally, because
there are many others who do know if/how this reversion will be an
impact.  Similarly, it would likely help for the community to know WHY
the reversion is needed.  Exposing the full cost/benefit analysis for
all to see could temper perceptions if it's clear that what we get for
going back to 0.9.19 is better than staying at 0.9.21.  Even better
would be to also share to roadmap for getting back in sync with
upstream PulseAudio stable releases so everyone knows we're not stuck
at (AKA, forked) version 0.9.19 indefinitely.

Respectfully,

Shane...
_______________________________________________
MeeGo-packaging mailing list
[email protected]
http://lists.meego.com/listinfo/meego-packaging

Reply via email to