What is the purpose of this group ideas

[Tom Chiverton]

Please post your handy summaries here, and we'll try and agree a composite.

My thoughts are we should come up with an easily quotable few
sentences, the better for spreading around the blog sphere etc.

So, here's mine:

"The Flex SDK Community Committee is an interface between the wider
SDK Community and Adobe. It exists to present the communities views
with a single voice and point of contact. It will also promote best
practice and the communities views in areas such as patch submission,
new feature implementation and the future direction of the framework."

--
Tom

[Simeon Bateman]

I think this is a real nice mission statement. I think it points out
that we are here to help bridge the gap between the community and
Adobe.

The trick is of course trying to gather the thoughts of the 200 people
in the next open forum with adobe. I started http://flexsdk.uservoice.com
which I think is a great forum for allowing people to start topics and
discuss them. I think its also great that people can just vote for
issue that affect them. Its much less formal than a bug list but more
open to discussion. We can use this to take in input from the
community and use that to guide our directions for adobe.

There are some amazingly smart folks in this list, but my focus is on
getting the greater feedback of the community to adobe. So I think
finding a way to bridge the communication gap with the community is
just as important as bridging the gap to Adobe.

I have shared this url with a couple of you, but I figure this group
is the best place to start on if this user voice can be useful in
helping us cut the signal/noise ratio.

Thanks,
sim

[Ben Clinkinbeard]

How about this?


The mission of the Flex SDK Community Committee is to enhance and
focus communication between the wider Flex SDK Community and Adobe. It
exists to present the community's views

with a single voice and point of contact. It will also promote best

practices and the community's views in areas such as bug voting, patch

submission, new feature implementation and the future direction of the

framework. Finally, the Flex SDK Community Committee will attempt to
guide community adoption and acceptance of new features once they
become official.

[Tom Chiverton]

Fine here
--
Tom

[Ryan Campbell]

Yeah I think it's perfect.

On Sat, Feb 7, 2009 at 10:43 AM, Tom Chiverton <tom.ch...@gmail.com> wrote:

Fine here
--

Tom

[Brian Holmes]

I think it needs to be much simpler. 1 maybe 2 sentences. Take a look
at the Rails Activists mission statement. http://rubyonrails.org/activists
Short and to the point.

[Tom Chiverton]

2009/2/7 Brian Holmes <brian.j...@gmail.com>:

> I think it needs to be much simpler. 1 maybe 2 sentences. Take a look

Drop a sentance and rearragned to give:

The mission of the Flex SDK Community Committee is to enhance and
focus communication between the wider Flex SDK Community and Adobe.

It will promote best practices and the community's views in areas such

as bug voting, patch submission, new feature implementation and the
future direction of the
framework.

Finally, the Flex SDK Community Committee will attempt to
guide community adoption and acceptance of new features once they
become official.

--
Tom

[Brian Holmes]

Taking as many of the concepts out of statements already posted I came
up with the following two

The mission of the Flex SDK Community Committee is to advocate the
views of the Flex Community. We do this by
incubating ideas and concerns, communicating and mediating those views
to Adobe and finally promoting and guiding adoption.

or

The mission of the Flex SDK Community Committee is to advocate the
views of the Flex Community, incubate their ideas and concerns,
communicate and mediate those views to Adobe and finally facilitate
and guide adoption.

Not sure if I like them yet but thought I'd throw them out there anyways.

[Doug McCune]

I do like the two way street that this statement implies (I guess that's my argument for not simplifying too much further and dropping the last part completely). The goals are to influence Adobe in the interests of the community, and influence the community in the interests of Adobe. Both are useful, both are valuable for the product as a whole, and I think it's a good PR move to get the recommendations of the group respected by Adobe if they know that once things are decided we'll push for adoption and education (tutorial blog posts, video tutorials, vocal support on flexcoders, etc).

[Tom Chiverton]

Although I can't think of anything better, it sounds like management speak...

--
Tom

[Brian Holmes]

> I do like the two way street that this statement implies

> The goals are to influence Adobe in the interests of the community, and influence the community in the interests of Adobe.

My sentiments exactly. Not sure if the following is exactly what I'm
looking for but:

The mission of the Flex SDK Community Committee is to advocate the
views of the Flex Community. We do this

by communicating and mediating community ideas and concerns to Adobe
and promoting and guiding community adoption of
Adobe standards.

[Tom Chiverton]

How about:

The goals are to influence Adobe in the interests of the community,
and influence the community in the interests of Adobe.

We will mediate community ideas and concerns to Adobe, promoting and
guiding community adoption of Flex.

--
Tom

[Ben Clinkinbeard]

I don't think solidify is quite the word I am looking for, but what about this:


The mission of the Flex SDK Community Committee is to solidify the views of the Flex community and advocate for them to Adobe. Conversely, our mission includes driving community adoption and education once new features become official. We aim to influence topics such as bug voting, patch submission, feature implementation and the overall direction of the framework.

[Tom Chiverton]

2009/2/7 Ben Clinkinbeard <ben.clin...@gmail.com>:

> I don't think solidify is quite the word I am looking for, but what about
> this:

Good distillation.

--
Tom

[Doug McCune]

Just trying to synthesize some of the key points I see coming through in this thread. I'm not saying these items should be any kind of defined mission statement as they are, but these seem to be the main points everyone has brought up

represent the Flex community by presenting concrete and actionable recommendations about the Flex SDK for Adobe's consideration
advocate the community's adoption of finalized SDK features
coordinate community participation in bug voting and patch submission

[Ben Clinkinbeard]

Yea, I think we're all on board with what we're trying to say, now we just have to agree on a way to say it.

[Douglas Knudsen]

a suggestion incorporating Doug's keywords and making it concise and a bit more terse.  I leave out some of the 'how', as I feel this should really state the 'why' for now, leaving the 'how' for more descriptive communications :

The mission of the Flex SDK Community Committee is to coordinate the community's views and opinions and communicate them with solidarity to the Adobe Flex SDK Team thus representing the Flex community at large.  Conversely, our mission includes advocacy by driving community adoption and education once new features become official.


Douglas Knudsen
http://www.cubicleman.com
this is my signature, like it?

[Tom Chiverton]

Edited for flow:

The mission of the Flex SDK Community Committee is to coordinate the

community's views and opinions and communicate them to the

Adobe Flex SDK Team thus representing the Flex community at large.

Conversely, our mission includes driving community adoption and
education once new features become available.

--
Tom

[Ben Stucki]

This is reworked from Doug's input (I like it) and moved into paragraph form with some Ruby Activists inspiration thrown in. The first sentence might need some tweaking, but I'm feeling good about the second part (except it could be edited for length). Thoughts?

The mission of the Flex SDK Community Committee is to empower and engage the worldwide community of Flex developers in the interest of improving the Flex SDK. We do this by representing the community's needs with concrete and actionable recommendations about the Flex SDK for Adobe's consideration, coordinating community participation in bug voting and patch submissions, and advocating the adoption of finalized SDK features to the larger community.

-- Gratuitous Tag Line

-- The Flex SDK Community Committee - Represent, Advocate, Coordinate.

[Justin Reidy]

Bingo. I think this phrases things perfectly. It provides a strong definition for the Committee while maintaining that mission statement je ne sais quoi.

[Douglas Knudsen]

Here here. I agree. I motion to consider complete.

DK

--
Sent from my mobile device

[Tom Chiverton]

2009/2/7 Douglas Knudsen <douglas...@gmail.com>:

> Here here. I agree.  I motion to consider complete.

Seconded.
If this was BSG, it would be law now :-)

--
Tom

[Brian Holmes]

I'll 3rd it. It is a little long, but it incorporates the main
concepts that I feel are important, and if someone comes up with a
better one in the future we could always vote to change it.

[Tom Ortega]

Sounds good, though a bit clean if we want people to think McCune
really had input. ;)

Thanks,
Tom Ortega
360Conferences, Inc.
cell: 951.212.9686 | twitter/skype: lordbron
lordbron.wordpress.com | www.OurStartupStory.com |
www.360conferences.com | www.360flex.com | www.360iDev.com

[Tom Chiverton]

2009/2/7 Tom Ortega <tom.o...@gmail.com>:

> Sounds good, though a bit clean if we want people to think McCune
> really had input.  ;)

We can recut it for the post-watershed version later :-)

--
Tom

[Doug McCune]

The first draft I wrote was "We bitch at Adobe to get shit done."

[Tom Ortega]

Now that has the Doug stamp. :)

Tom Ortega
360Conferences, Inc.
cell: 951.212.9686 | twitter/skype: lordbron
lordbron.wordpress.com | www.OurStartupStory.com |
www.360conferences.com | www.360flex.com | www.360iDev.com

[Ben Clinkinbeard]

If another two members voice support I will join in to give it a
majority. (We have 14 active members I think). I personally think it's
too close to the Rails activists text.


On 2/7/09, Ben Stucki <bens...@gmail.com> wrote:
> *This is reworked from Doug's input (I like it) and moved into paragraph

> form with some Ruby Activists inspiration thrown in. The first sentence
> might need some tweaking, but I'm feeling good about the second part (except
> it could be edited for length). Thoughts?
>
> The mission of the Flex SDK Community Committee is to empower and engage the
> worldwide community of Flex developers in the interest of improving the Flex

> SDK. We do this by* representing the community's needs with concrete and

[Tom Gonzalez]

You got my vote

- Tom

*** Sent from my iPhone ***

On Feb 7, 2009, at 4:15 PM, Ben Clinkinbeard

[Doug McCune]

How about some more rewording to not use some similar phrases from the rails manifesto:

The Flex SDK Community Committee fights for the betterment of the Flex SDK. We represent the Flex community by proposing concrete and actionable recommendations for Adobe's consideration, we coordinate community participation in bug voting and patch submissions, and we advocate the adoption of finalized SDK features to the larger community.

Of course we could keep writing reworded drafts forever :)

Doug

[Ben Clinkinbeard]

I can definitely get behind that one.




On 2/7/09, Doug McCune <do...@dougmccune.com> wrote:
> *How about some more rewording to not use some similar phrases from the

> rails manifesto:
>
> The Flex SDK Community Committee fights for the betterment of the Flex SDK.

> We represent* the Flex community by proposing concrete and actionable

[Douglas Knudsen]

So let it be written, so let it be done.

DK

--
Sent from my mobile device

[Brian Holmes]

I like it. Would recommend replacing fights for the betterment with
something else. Although nothing comes directly to mind.

[Doug McCune]

it reminded me of Batman :)

[Tom Ortega]

And let's face it, if we ain't gonna fight, who will?

Tom Ortega
360Conferences, Inc.
cell: 951.212.9686 | twitter/skype: lordbron
lordbron.wordpress.com | www.OurStartupStory.com |
www.360conferences.com | www.360flex.com | www.360iDev.com

[Ben Clinkinbeard]

The Flex SDK Community Committee works for the betterment of the Flex SDK. We represent the Flex community by proposing concrete and actionable recommendations for Adobe's consideration, we coordinate community participation in bug voting and patch submissions, and we advocate the adoption of finalized SDK features to the community at large.


Can we chisel this into a stone tablet and call it official?

[Tom Chiverton]

2009/2/8 Ben Clinkinbeard <ben.clin...@gmail.com>:

> Can we chisel this into a stone tablet and call it official?

/me hands you a hammer

--
Tom

[Brian Holmes]

> Can we chisel this into a stone tablet and call it official?

Let's do it.

[Douglas Knudsen]

Roll baby roll

On 2/7/09, Brian Holmes <brian.j...@gmail.com> wrote:
>
>> Can we chisel this into a stone tablet and call it official?
>
> Let's do it.
>
> >
>

[Adam Flater]

Looks good everyone.. Sorry I've been off the thread.. nice work all
around.

Sent from my iPhone

On Feb 7, 2009, at 7:22 PM, Brian Holmes <brian.j...@gmail.com>
wrote:

>

[Ben Clinkinbeard]

Speak now or forever hold your peace. Piece? Like the Fx statement, I
will consider this approved and fit for publish unless I hear
otherwise by end of day Tuesday.

Ben

On Feb 8, 8:44 pm, Adam Flater <adamfla...@gmail.com> wrote:
> Looks good everyone.. Sorry I've been off the thread.. nice work all  
> around.
>
> Sent from my iPhone
>

> On Feb 7, 2009, at 7:22 PM, Brian Holmes <brian.josep...@gmail.com>