nice picture!
B.
2006/5/9, Geoff Stearns <[EMAIL PROTECTED]>:
the devnet article that started all this went live today:
On May 9, 2006, at 9:57 AM, Andrew Eatherington wrote:
In total agreement. It was badly managed or maybe even not managed at all. It would make sense to have guidelines on how to use the name rather than not use it at all and the requirement perhaps for some footnote reference/disclaimer. This way Adobe could count on continued support for its product. Lets face it, the Flash® Community is valuable as a resource. It would be interesting to find out how other companies which have strong communities (for example Autodesk's 3D Studio Max) have handled this.
Andrew
On 28 Apr 2006, at 10:11, Aral Balkan wrote:
Hi guys,I hope to see you all at SWF Forward in september... and maybe atSWF in the Can next year!
If it sounds ridiculous to us, it will probably sound ridiculous to ourfriends at Adobe too (except perhaps the legal department, but that's alegal department, filled with lawyers -- 'nuff said.) Thus, I can onlyassume that Adobe will be making some concessions forfestivals/communities. It would be unthinkable for them to askFlashForward or Flash In The Can to change their names.
Remember, we're not trying to make Flash the next big secret. It alreadyis somewhat of a secret outside of its own community and we're trying toget the word out to other developers. One way of doing this is(drumroll) actually getting the word out there as much as possible.
If everything, from third-party tools to communities to conferences wereto be called SWF-this-or-that, it would make sense to refer to the SWFPlatform instead of the Flash Platform. I'm sure that's not what Adobeintends at all.
I'd say let's give them some time to sort this out internally and seewhat happens. Ideally, I'd like to see a simple, human-readable (notlawyer-speak -- although it can be backed up by one, ala CreativeCommonslicenses) page somewhere, created solely for the benefit of the Flashcommunity, that specifically states how/when the Flash trademark can beused.
It's unfortunate that this matter was not better managed by Adobe'slegal department who, IMHO, should have spoken to PR before making thispublic but I'm sure that this is something that we'll get sorted outeventually.
Aral
_______________________________________________osflash mailing list
_______________________________________________osflash mailing list
_______________________________________________
osflash mailing list
osflash@osflash.org
http://osflash.org/mailman/listinfo/osflash_osflash.org
_______________________________________________ osflash mailing list osflash@osflash.org http://osflash.org/mailman/listinfo/osflash_osflash.org
