I've been trying to integrate Google products for a couple of years now and I have found it INCREDIBLY frustrating to work with Google products that combine a core product and APIs. Bugs reported in the main product Help Forums get lost in the noise of millions of users and ignored. My return on investment for identifying bugs, and reporting them has been ZERO, and bugs still remain after two and even three years with NO feedback/updates.
Buzz will be even worse because you will be integrating other products into the mix (picasa, Flickr, blogger, youtube). Where do buzz specific integration issues get reported and tracked? To each product group?.. that doesn't help me fix a Buzz specific issue. Trust me.. I've have had bug after bug break my overall integration. Waiting, tracking and monitoring to see when/if bugs have been fixed (and your product works again) is not fun!!
Where do I report Buzz product bugs? To the folder in gmail help, that is not individually searchable with status/feedback that I can't track? Sorry that doesn't work for me!!
Buzz needs it's own product help forum. Buzz needs a formal PRODUCT issue tracker and some sort of roadmap/idea when features and bug fixes are expected. When updates are made a DETAILED change log and release notes are critical (I've also had many hidden changes break a working flow).
I've heard the mantra "Release Early, Release Often" but you are missing the critical tight feedback loop that makes this whole methodology work. Without feedback, your products and APIs look buggy, unstable, and un-integrated. Without timing, change logs, release notes or a road map it becomes unusable, especially when I want/need to give my clients/customers feedback and timing; guessing doesn't cut it!!
Note. I've got a pretty big Buzz issues/bug list already but I'm not going to waste my time documenting them until the basic development issues above are addressed. Frankly it has been a complete waste of time for me.
On Thu, Feb 11, 2010 at 09:17, Chris Myles <svbillab...@gmail.com> wrote: > I've been trying to integrate Google products for a couple of years > now and I have found it INCREDIBLY frustrating to work with Google > products that combine a core product and APIs. Bugs reported in the > main product Help Forums get lost in the noise of millions of users > and ignored. My return on investment for identifying bugs, and > reporting them has been ZERO, and bugs still remain after two and even > three years with NO feedback/updates.
> Buzz will be even worse because you will be integrating other products > into the mix (picasa, Flickr, blogger, youtube). Where do buzz > specific integration issues get reported and tracked? To each product > group?.. that doesn't help me fix a Buzz specific issue. Trust me.. > I've have had bug after bug break my overall integration. Waiting, > tracking and monitoring to see when/if bugs have been fixed (and your > product works again) is not fun!!
> Where do I report Buzz product bugs? To the folder in gmail help, that > is not individually searchable with status/feedback that I can't > track? Sorry that doesn't work for me!!
> Buzz needs it's own product help forum. Buzz needs a formal PRODUCT > issue tracker and some sort of roadmap/idea when features and bug > fixes are expected. When updates are made a DETAILED change log and > release notes are critical (I've also had many hidden changes break a > working flow).
> I've heard the mantra "Release Early, Release Often" but you are > missing the critical tight feedback loop that makes this whole > methodology work. Without feedback, your products and APIs look buggy, > unstable, and un-integrated. Without timing, change logs, release > notes or a road map it becomes unusable, especially when I want/need > to give my clients/customers feedback and timing; guessing doesn't cut > it!!
> Note. I've got a pretty big Buzz issues/bug list already but I'm not > going to waste my time documenting them until the basic development > issues above are addressed. Frankly it has been a complete waste of > time for me.
-- Abraham Williams | Community Advocate | http://abrah.am Project | Out Loud | http://outloud.labs.poseurtech.com This email is: [ ] shareable [x] ask first [ ] private. Sent from Seattle, WA, United States
> Hopefully with the number of upstanding open web advocates participating in > this list feedback will be handled properly.
> Abraham
> On Thu, Feb 11, 2010 at 09:17, Chris Myles <svbillab...@gmail.com> wrote: > > I've been trying to integrate Google products for a couple of years > > now and I have found it INCREDIBLY frustrating to work with Google > > products that combine a core product and APIs. Bugs reported in the > > main product Help Forums get lost in the noise of millions of users > > and ignored. My return on investment for identifying bugs, and > > reporting them has been ZERO, and bugs still remain after two and even > > three years with NO feedback/updates.
> > Buzz will be even worse because you will be integrating other products > > into the mix (picasa, Flickr, blogger, youtube). Where do buzz > > specific integration issues get reported and tracked? To each product > > group?.. that doesn't help me fix a Buzz specific issue. Trust me.. > > I've have had bug after bug break my overall integration. Waiting, > > tracking and monitoring to see when/if bugs have been fixed (and your > > product works again) is not fun!!
> > Where do I report Buzz product bugs? To the folder in gmail help, that > > is not individually searchable with status/feedback that I can't > > track? Sorry that doesn't work for me!!
> > Buzz needs it's own product help forum. Buzz needs a formal PRODUCT > > issue tracker and some sort of roadmap/idea when features and bug > > fixes are expected. When updates are made a DETAILED change log and > > release notes are critical (I've also had many hidden changes break a > > working flow).
> > I've heard the mantra "Release Early, Release Often" but you are > > missing the critical tight feedback loop that makes this whole > > methodology work. Without feedback, your products and APIs look buggy, > > unstable, and un-integrated. Without timing, change logs, release > > notes or a road map it becomes unusable, especially when I want/need > > to give my clients/customers feedback and timing; guessing doesn't cut > > it!!
> > Note. I've got a pretty big Buzz issues/bug list already but I'm not > > going to waste my time documenting them until the basic development > > issues above are addressed. Frankly it has been a complete waste of > > time for me.
> -- > Abraham Williams | Community Advocate |http://abrah.am > Project | Out Loud |http://outloud.labs.poseurtech.com > This email is: [ ] shareable [x] ask first [ ] private. > Sent from Seattle, WA, United States
Buzz also need to provide an up-to-date known issues page (ASAP)
I am finding such a ridiculous number of bugs that users show be made aware of, searching the Help forum doesn't work (sub folder).
I am building a list of the minimum bug fixes and features I NEED before I return to Buzz, without the changelog and release notes how will I ever know. A Blog will never give me the level of detail I need to make that decision, and I'm certainly not going to keep trying every bug each day just to see if it has been fixed.
What exactly does "Please note that this will only remove the Buzz label from your Gmail account." mean?
> > Hopefully with the number of upstanding open web advocates participating in > > this list feedback will be handled properly.
> > Abraham
> > On Thu, Feb 11, 2010 at 09:17, Chris Myles <svbillab...@gmail.com> wrote: > > > I've been trying to integrate Google products for a couple of years > > > now and I have found it INCREDIBLY frustrating to work with Google > > > products that combine a core product and APIs. Bugs reported in the > > > main product Help Forums get lost in the noise of millions of users > > > and ignored. My return on investment for identifying bugs, and > > > reporting them has been ZERO, and bugs still remain after two and even > > > three years with NO feedback/updates.
> > > Buzz will be even worse because you will be integrating other products > > > into the mix (picasa, Flickr, blogger, youtube). Where do buzz > > > specific integration issues get reported and tracked? To each product > > > group?.. that doesn't help me fix a Buzz specific issue. Trust me.. > > > I've have had bug after bug break my overall integration. Waiting, > > > tracking and monitoring to see when/if bugs have been fixed (and your > > > product works again) is not fun!!
> > > Where do I report Buzz product bugs? To the folder in gmail help, that > > > is not individually searchable with status/feedback that I can't > > > track? Sorry that doesn't work for me!!
> > > Buzz needs it's own product help forum. Buzz needs a formal PRODUCT > > > issue tracker and some sort of roadmap/idea when features and bug > > > fixes are expected. When updates are made a DETAILED change log and > > > release notes are critical (I've also had many hidden changes break a > > > working flow).
> > > I've heard the mantra "Release Early, Release Often" but you are > > > missing the critical tight feedback loop that makes this whole > > > methodology work. Without feedback, your products and APIs look buggy, > > > unstable, and un-integrated. Without timing, change logs, release > > > notes or a road map it becomes unusable, especially when I want/need > > > to give my clients/customers feedback and timing; guessing doesn't cut > > > it!!
> > > Note. I've got a pretty big Buzz issues/bug list already but I'm not > > > going to waste my time documenting them until the basic development > > > issues above are addressed. Frankly it has been a complete waste of > > > time for me.
> > -- > > Abraham Williams | Community Advocate |http://abrah.am > > Project | Out Loud |http://outloud.labs.poseurtech.com > > This email is: [ ] shareable [x] ask first [ ] private. > > Sent from Seattle, WA, United States
