While CNN covers presidential campaigns, news about the Flash Player election is sadly being lost. Polls are open and candidates are sitting there hoping for your vote. Write-in candidates are already lurking in the back of your mind waiting to be added to race!
“What race is this?” you ask?
Today, Flash Player has joined Flex and Blaze DS as participants in Adobe’s public bug tracking system. While it may not actually be a real campaign, it is certainly inspired by the democratic process. In addition to searching for and reporting new issues, you can vote on issue that are important to you and influence the decisions of what goes into the next Flash Player.

As a product manager, the real treat for me though is the feature request section. If there is something you want from Flash Player, be it a small enhancement or a major new feature, you can enter a request on the site. It is product management GOLD to be able to have direct numbers on what the community wants and why (if you leave comments).
My job is to understand and anticipate your challenges and the sort of work that you want to do and work within Adobe to make the best product we can to serve your needs. Right now I do this through customer visits, talking to people at conferences, monitoring trends in the industry, and doing lots of other behind-the-scenes things. Most of this type of data is qualitative and has proven to be a successful methodology through the history of Flash. However, every time I can get my hands on some quantitative data like a vote count on a feature request it means that I can do a reality check and make sure that we are really going the direction the community needs us to go.
So, do Flash Player (and me) a favor and Vote early, vote often!
Digg this!
April 8th, 2008 at 12:06 pm
Player bugbase
Player bugbase: Now live. Justin Everett-Church has more info….
April 8th, 2008 at 12:08 pm
This is really cool! However do you know if this is also planned for AIR? I`ve tons of feature requests for AIR. Sometimes it`s hard to say if it`s a fetaure request for air or the core flash player. So should AIR requests be posted there or wait for a AIR JIRA?
Thanks
Benz
April 8th, 2008 at 12:30 pm
Hi Benz,
If you have a feature that you think would be beneficial to Flash Player running in the context of a web browser or if it would be good for both AIR and Flash Player, please do add it to the Flash Player JIRA site.
If it is a feature that is more specifically geared to AIR, we want to hear about it, but the Flash Player site, will probably not be the best home for it.
Unfortunately I can’t talk about AIRs plans much myself.
April 8th, 2008 at 1:15 pm
[…] esmo. Mais um passo da Adobe que confirma o seu empenho em colaborar com a comunidade.
[…]
April 8th, 2008 at 3:42 pm
Damn, that @adobe twitter user sure has some pull:
http://twitter.com/alucking/statuses/782508212
I’m going to ping him / her with all my requests in the future
Cheers,
A.
April 8th, 2008 at 4:36 pm
Glad to see the public bugbase for FP. Now I won’t have to resort influence peddling (as much). Anyway, this is great news.
April 9th, 2008 at 1:32 am
This is really useful, both for Adobe’s planing and people who find bugs or want to track new features.
Are there plans to import the existing (internal) bug list into the public system ? For instance I know there is an internal bug about the print dialogue on Linux (no landscape/portrait option) - should I reenter this ?
April 9th, 2008 at 2:15 am
[…] now log it in Adobes bug tracking system and watch it’s progress. More info over at Justin’s blog. This entry was […]
April 9th, 2008 at 2:55 pm
Tom,
The public bugbase will remain separate from the internal bugbase. It is important to respect the privacy of our customers who may have provided contact information or sensitive files during the process of tracking down a bug.
If you would like the bug you mentioned to be viewable publicly, please feel free to re-enter it.
April 9th, 2008 at 8:05 pm
Justin,
That’s a little odd, isn’t it? Maybe you could explain the two bug base system a little better. I bought CS3, should my bugs go in the internal or public bugbase?
April 9th, 2008 at 10:49 pm
Andrew,
There is an internal web application for tracking bugs for Flash Player and Flash Professional. These bugs are entered by Adobe employees that have received the reports from various sources such as customer visits, reports from customers, automated testing, customer support, etc.
There is now also this new, public bug application where the community can enter in bugs. This does mean that we have two concurrent bug applications, but our QE folks have heroically taken on the task of managing both.
April 10th, 2008 at 10:12 am
Thanks Justin. I realize my comment yesterday had a bit of a facetious tone; my apologies.
To put some sober second thought on my concerns… I was thrilled to hear that you were opening up the bugbase, something many people have been asking for for a long time now. And I still think it’s awesome so my thanks to all the “heros” who are making it happen (yes QE too)
However, as a developer on the platform, I can’t help but feel that a comprehensive bugbase would be useful for us all.
Obviously you need to track bugs that could be used maliciously and I would agree those entries should remain at a “need to know” basis. Atleast until the threat is resolved. As you said, maintaining the public and internal bugbases separately is going to mean extra work for you guys and it sure seems like the privacy concerns you cite as the impetous for it all could be resolved in a different way. Then we all win, no?
Anyhow, my intention is not to dismiss the signficance of the public database.
Cheers,
A.
April 12th, 2008 at 4:13 am
[…] But you can. Both options are cool ones ??” let’s just use them in right way. It is Justin Everett-Church who told us about this new Adobe JIRA F […]
April 17th, 2008 at 12:29 pm
This is just spin public relations. Something to keep the kids occupied. It’s meaningless.
April 17th, 2008 at 3:45 pm
lala,
I can only ask that you reserve judgment until we see how well Flash Player responds to the community through its player releases.