Apache Flex :: Flex-Dev summaries 4
Hi,
I really think what I am doing here is healthy for the Apache Flex community that reads it. I have for the most part tried to keep opinions out of these summaries, not always.
If I have any parents, animal lovers etc, you will know that when a new child enters the house there is, no sleep for some, hectic communication to family and friends, and an understanding that in the beginning life requires your to give “a little” bit more to your new born baby.
Yeah, I’m a sentimental guy and love my children, I also love the fact that I now know others in the community have an investment into Apache Flex like we have had with the renegades of Flash back in early 2000s.
Apache Flex Logo Contest
The Apache Flex logo contest was the PPMC members first vote on a draft document. It was approved unanimously and will be published on the site I would guess Monday morning (pending).
There is one requirement that will need to be upheld for your image to even appear on the site with other applicants;
Do not use anything the even resembles the Adobe Flex logo of past, present or future. This is the easiest way to get a “thanks but no thanks“.
Spoon Visibility
Jonathan Campos reminded the community that there are already active Spoon members on the list, Garth, Kevin and Nick some others are on vacation.
He also noted that Spoon is preparing for an open public call for the community.
Again what is Spoon?
Spoon is a nonprofit corporation created by some community members to promote, educate, and contribute to the Flex framework.
Coding conventions
This topic is still going and from reading every post that has come through the doors, I would say that 3/4 of community members want to keep the standards close to what already exists here;
http://opensource.adobe.com/wiki/display/flexsdk/Coding+Conventions
Once the conventions are agreed upon, Jonathan suggests that they should be committed by svn and are protected by the votes of the PMC.
Basically all this means is, if you have problems with them in the future, bring it up on the list for discussion, we don’t want the community changing them at their will on the wiki. (this would negate the meaing of convention anyway)
BlazeDS
Continuing on the topic of BlazeDS and where it’s home will be Alex commented on that fact that there is little to no initial committers for the project.
Anne pointed out that without a core development team (initial committers), she cannot see how BlazeDS would survive as an Apache project.
“To graduate from incubation the project needs, among others, to show that it has an active community. (this doesn’t have to consist of committers only)”
Alex did point out that the rpc.swc is included in the Flex contribution.
Flex Road map
This was something that in a round about way was brought up at the beginning of the week and I have more information written about in the Flex-Dev summaries.
I would like to post a link here of Sebastian Mohr who is a PPMC member and initial committer. He has put a huge amount of time into this information and I think it’s worth your time checking it out and giving him some feedback.
http://code.google.com/p/masuland/wiki/WhatsWrongWithFlex
JIRA
JIRA will be up when it’s up. As noted earlier in the week, there is a HUGE amount of migration happening and it’s not as easy as just flipping a switch like wordpress or something.
I’ll let the community know on this blog the moment Apache Flex JIRA is online. Then kill the server with more bug and feature requests!
Conclusion
Hey it was Saturday and we voted, if that doesn’t say something then you don’t want to listen to what we are all saying.
Happy Sunday,
Mike









Recent Comments