Time for Change
Hi all, It is with mixed emotions that I must admit that it's time for me to step down from the Flex PMC. It was an honor to be a mentor to this project through incubation and I can say without reservation that this community has been fully integrated into Apache. It's time for me to recognize that I simply don't have the bandwidth to contribute as I had hoped I would. I need to leave things in other very capable hands. Flex is different from a lot of Apache projects in terms of how it got here and the community around it. I think that maybe the community is still trying to navigate how Apache is not only different from Adobe, but also different from GitHub, SourceForge, and other open source environments. In some ways I think those differences are good for the Flex community, but in other ways I think the Flex community brings something to Apache that will help Apache grow into the future. I look forward to seeing more of the Flex PMC become ASF members and having a greater impact on the foundation! I want to be clear that there is no bad blood between me and anybody on the PMC. I'd be happy to work with any of you again in the future. I'll stay subscribed to the private@ list so if there are mentor-like questions to be answered I'll be happy to do my best. I will probably unsubscribe from the dev@ list in a few days to reduce my daily email load. Thanks to everyone for allowing me to be a part of the community. I wish you all the best going forward! Greg
Re: [DRAFT] Apache Flex December 2013 Report
On Tue, Dec 3, 2013 at 4:52 PM, Alex Harui aha...@adobe.com wrote: I'm wondering if the board really does appoint the char as much as approves the PMC recommendation. If we change chairs, we only provide notice and wait 72 hours. AFAIK, there is no action from the board required. This could just be another copy/paste problem of bad text like the term lazy majority. No the chair is appointed by resolution of the board. The original resolution that created the project named a chair and it requires another resolution to change the chair. The board normally does approve what the PMC recommends, but I have seen a case or two where the board intervened. Greg
Re: LinkedIn requests
I agree. Reject. On Wed, Nov 6, 2013 at 2:57 PM, Justin Mclean jus...@classsoftware.com wrote: Hi, Every once in a while we get an Invitation to connect on LinkedIn email for moderation. Reject I say. They could be phishing spam or sent by someone just sending out blanket requests (connect to all my friends). Does it make sense have these mailing lists connected via LinkedIn? IMO no. Not unless we aded Apache Flex as an organisation/companies and listed all of the committer/PMC members under it. Thanks, Justin
Re: [DISCUSS] Apache Flex Bylaws
Hi all, I hate to muddy the waters here, but I'll add this: When Tiles became a TLP we had the bylaws clause in our resolution. I don't remember all the context, but I'm pretty sure the objections came from some board members at the time (2006). The objections were that the ASF bylaws are the bylaws of projects. Others argued that project bylaws were a way for projects to get more specific about how their projects are run within the ASF guidelines. If my memory serves me correctly, the bottom line was that projects are free to adopt bylaws if they wish but that they are not a requirement. Because of that I think Crossley's email on Incubator was a little too settled. I don't think it's a settled thing that projects must adopt bylaws. That said, I think the things you are trying to formalize through establishing bylaws are good things to formalize. It's good to have them in writing and pointed to in a board report. If objections are raised in the future, we can point back to the adopted document.. We may still have to change (If you've followed the discussions on other lists, you'll see that there is not always consensus about these rules), but at least we will have something in writing to discuss. So all of that is to say that I think this is a good thing and we should do it. But we may end up having to call them policies instead of bylaws once presented to the board and we may trigger some crazy discussion of them once they are presented to the board. Or they may fly completely under the radar and not be noticed. Greg
Re: [DISCUSS] Apache Flex Bylaws
On Tue, Oct 1, 2013 at 4:41 AM, Erik de Bruin e...@ixsoftware.nl wrote: I very much prefer to set a bar for active. The only time the inactive PMC members come out of the closet is if they are rallied to vote for a controversial issue. If you're not involved in the project (anymore), I don't think you should be allowed to have a binding vote. Erik There's a longstanding principle of Apache that merit never expires. The idea is that if a person has ever contributed something worthy of giving him or her a binding voice on the project, that contribution is permanent and the person always has a binding voice on the project. It's a recognition that people's priorities and interests change and that we should allow people to move in and out of the daily function of the project as their priorities drive them. So I think there are two things we should remember: 1) As a project we should make it easy for PMC members to move in and out of the PMC. If a PMC member resigns most projects consider them in emeritus status and that means they can rejoin the project simply by asking. We should also invite people to join the PMC recognizing it's a permanent status. 2) As individuals we should let the project know when our priorities have changed by resigning from the PMC, knowing that if our priorities change again, we can easily come back. Greg
Re: Swiz Donation: Next Steps (was Re: [VOTE][RESULTS] Oprtional MVC/IOC Frameworks Donation: Swiz Framework Donation)
On Thu, Jun 6, 2013 at 11:00 AM, Carlos Rovira carlos.rov...@codeoscopic.com wrote: hehe I only want to say that history is written in the internet so is easy to prove that Chris Scott is the author, but I see that he must prove it himself. We could not in good conscience accept a donation without written, clear intentions from the author. I suspect it will require a software grant and the author will need to go through some legal paperwork to assent that he has ownership of the code and is willing to donate it to the ASF. I need to get more familiar with the details of what is required for the ASF to accept software donations, but it's a complicated subject and time is short. I do know that we want to be very sure we have all the details in order so we can be confident in saying that we have the right to continue to produce the software. Greg
Re: [VOTE] Swiz Framework Donation to Apache Flex
+1 (binding) On Wed, May 29, 2013 at 4:43 AM, Carlos Rovira carlosrov...@apache.orgwrote: After proposal thread (http://markmail.org/message/jtedmmx5djqen52l),comes the vote thread. This thread is to decide if we finally adopt Swiz Framework under Apache Flex, since there is multiple opinions in the Apache Flex community. points to take into account: * Swiz is a great addition to Apache Flex since it complements de SDK with a microarquitecture for application MVC, IOC, DI very simple and well designed. * This will be a project like flexunit or utilities. So it's optional a NOT part of the main sdk. * Swiz is already in 1.4.0 stable version, under Apache License 2.0, has its community and right now there's no maintenance or upgrade since people behind the project is no longer working with Flex technology. * Donation will be 1.4.0 source code and wiki content. * Future plans: if donation is successful, Chris Scott (creator of Swiz) will want to donate experimental 2.0.0 branch that brings AOP support, a feature that could bring a great benefit to Apache Flex since it brings something very new to client web technologies and that will require evolution at compiler level (introducing compile time weaving). Points that some people argument to not accept the donation: * There is other frameworks like Swiz out there in the same situation and this donation could make Swiz the preferred/recommended IOC framework of use. Points to take into account: * Erik de bruin stated that maybe the problem is what to do with it under Apache Flex umbrella. Please make your vote. Thanks Carlos Rovira
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
On Tue, May 28, 2013 at 9:52 AM, Carlos Rovira carlosrov...@apache.orgwrote: Hi, I want to propose the donation of Swiz Framework to Apache Flex. This would be awesome in my opinion :-) Just remember that the donation process could get complicated if Chris doesn't hold the copyright to all the code to be donated. Greg
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
On Tue, May 28, 2013 at 10:33 AM, dude d...@atheist.com wrote: Good luck, but I'd rather see Parsley integrated into Apache Flex. That's the only concern I'd have about the donation. I know Swiz is one framework among several. So we'd have to manage it carefully to keep from alienating part of the community. Greg
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
On Tue, May 28, 2013 at 10:37 AM, Roland Zwaga rol...@stackandheap.comwrote: On 28 May 2013 17:33, dude d...@atheist.com wrote: Good luck, but I'd rather see Parsley integrated into Apache Flex. Personally, the above response shows exactly the reason why I think there shouldn't be any application framework integrated into Apache Flex. Too many opinions on the matter... But, there's no reason we can't integrate it as a sub-project or incubate it. If it develops a community it can become its own TLP.
Re: [PROPOSAL] Swiz Framework Donation to Apache Flex
On Tue, May 28, 2013 at 11:18 AM, Alex Harui aha...@adobe.com wrote: Greg, do you think donations like these need to have a goal of being integrated with Apache Flex or becoming its own project? Personally, I'd be ok with Apache Flex being a warehouse of all kinds of Flex-related code even if there is no active development for it. There's a couple of things to consider here: 1) The board does not favor umbrella projects. Jakarta was an umbrella project and it contained (at one time) Struts, Tomcat, Commons, JMeter, and a whole bunch of Java-related projects. It became clear that the Jakarta community was too fragmented to get consensus so it spun off all those projects into TLPs. That could easily start to happen here. 2) This mailing list is already too high-traffic to follow. Practically, we could probably already split up the Flex project into multiple projects. It seems to me that folks are starting to gel around different efforts, like getting new releases of the SDK, vs. compilers, etc. It could be that we need to form new PMCs or it could be that we just need to enact sub-projects. But we have to be careful with sub-projects to avoid point 1 above. It's hard to know where the breaking point is. Probably it has to do with whether the community is having a hard time pushing out releases or just whether it feels fragmented. I'm not proposing that we break up now, but we should probably be thinking about whether the Falcon project, for example, has its own distinct community from the SDK. Greg
Re: [DISCUSS] Github based Whiteboard proposal
Just wanted to note that I think this proposal alleviates my concerns about using github for whiteboards. If I can find time I'm going to search other apache archives to see if there are other things we need to consider. But for now I feel like this supports apache's desires for open development and code provenance. Thanks for going to all the trouble putting it together. Greg Sent from my mobile device. On May 6, 2013, at 6:03 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Mon, May 6, 2013 at 3:48 PM, Alex Harui aha...@adobe.com wrote: Om, Can you update the proposal as to whether you have to use your a.o email or if allowing aliases works? -Alex I have posted the proposal here: https://cwiki.apache.org/confluence/display/FLEX/Proposal+-+Github+based+Whiteboard All apache.org emails are configured to be aliases for committer's personal email ids. So, you will need to add the committer's personal email id to the commits@f.a.o list in any case. The only advantage of adding the apache.org email id in GitHub would be that the 'from' field will have the apache.org email id. This keeps it consistent with Apache Git's emails. So, I have updated the proposal to say that it is 'recommended, but not compulsory' for adding the apache.org email address as the default email in GitHub. Thanks, Om On 5/6/13 3:35 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: Any other thoughts regarding this process? If not, I would like to test this workflow with a couple of volunteer committers. Anyone wants to volunteer? :-) Thanks, Om On Thu, May 2, 2013 at 8:55 PM, Alex Harui aha...@adobe.com wrote: On 5/2/13 6:21 PM, Dasa Paddock dpadd...@esri.com wrote: 6. The committer adds their committerAlias@apache.org email address as their default email in their github account. Anyway around to do this? I assume this is so email to the mailing list re changes are not rejected. I'm not sure, but maybe it's enough to just add your apache.orgaddress to your Email Settings [1] and set the repo's user.email config so that the apache.org address is used as the commit author [2]. [1]: https://github.com/settings/emails [2]: https://help.github.com/articles/setting-your-email-in-git I'm ok adding aliases for the committers who don't want to use their apache.org. I think I did so for Om in order for him to try this. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Whiteboard on GitHub - update
I'm a moderator. Assuming the mails don't cause the spam filter to be engaged, I'll moderate them through. On Fri, Apr 26, 2013 at 2:25 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Fri, Apr 26, 2013 at 12:16 PM, Alex Harui aha...@adobe.com wrote: Om, Maybe I wasn't clear. I think a key aspect of whiteboards on GitHub is to have a commit to your whiteboard be seen on the commits@flex.a.o list by anyone subscribed to commits@f.a.o without other work on their part like signing up with GitHub or being added as a member of the an organization. We can't get an email to commits@f.a.o to happen for all activity on your whiteboard? Short answer: it is doable. Long answer: I can add an organization-wide notification setting to send emails to: comm...@flex.apache.org. The only problem is the list moderator for commits@f.a.o should manually add notificati...@github.com to the list so that the emails can go through. Who is the moderator of commits@f.a.o? Thanks, Om On 4/26/13 11:04 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Fri, Apr 26, 2013 at 10:51 AM, Alex Harui aha...@adobe.com wrote: Om, Thanks for working on this. Some questions: 1) do you have this actually setup? If so, can you commit something to your whiteboard so I can see what the notification email looks like? Yes, but with a private account. I can add you as a member of this test organization. We can 'watch' repos and notifications emails can be configured [1], [2] More details on Organiations available here [3] 2) When the contributor sends the pull request, how does the committer get notified? Can an email go to the commits list? Or does the committer only get notified off-list? We should be able to make the notifications go to any and multiple email ids [4]. We will have to add the notificati...@github.com email id to our list. Thanks, Om [1] https://help.github.com/articles/watching-repositories [2] https://help.github.com/articles/configuring-notification-emails [3] https://help.github.com/categories/2/articles [4] https://help.github.com/articles/notifications#per-organization-email-routing -Alex On 4/26/13 10:27 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: I have been experimenting with a GitHub based workflow for the whiteboard repos for our committers. Here is the workflow I would like to propose: * Apache Flex creates an 'Organization' account GitHub * Each Apache Flex committer is encouraged to create an account on GitHub * The committer then posts their GitHub id on dev@flex.apache.organd asks to be added to the ApacheFlex@GitHub account * The Apache Flex PMC will add the committer's GitHub id to the ApacheFlex@GitHub account. * In the contributing.md file [1] at the root of each committer's github project, there will be information about Apache's contribution guidelines including a link to the ICLA [2] * Any public contributor is free to fork an ApacheFlex committer's github project. * The contributor makes a few modifications and is ready to send a 'Pull request' to the Apache Flex committer * Before the 'Pull Request' can be sent, GitHub will automatically point the contributor to take a look at the contribution guidelines first. * Theoretically the contributor reads the contribution guidelines, agrees to it implicitly and clicks the 'Send Pull Request' button. * The Apache Flex Committer now will have a chance to peruse the commits and decide whether or not to accept the pull request. There is another alternative I have been working on as well. There is a CLAHub [3] plugin for GitHub. The workflow for this is described in the same link [3]. I have been experimenting with this plugin but have found various issues with it. I am currently working with the plugin's creator, Jason Morrison and support@GitHub to fix these issues. They have been very helpful so far. I hope to be able to fix all the issues soon and send out a demo. Please let me know if the above mentioned steps are sufficient or if something like CLAHub plugin would be better. Thanks, Om [1] https://github.com/blog/1184-contributing-guidelines [2] http://www.apache.org/licenses/icla.txt [3] http://www.clahub.com/ -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: Whiteboard on GitHub - update
I haven't seen any mod requests yet. I'm traveling this weekend and will have limited network access. I will try to look into it again next week if I don't see anything before. Sent from my mobile device. On Apr 26, 2013, at 4:42 PM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Fri, Apr 26, 2013 at 2:26 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Fri, Apr 26, 2013 at 12:28 PM, Greg Reddin gred...@gmail.com wrote: I'm a moderator. Assuming the mails don't cause the spam filter to be engaged, I'll moderate them through. Great! I just sent out a test notification to commits@flex.apache.orgfrom GitHub. Can you check if it came through? Another alternative would be to ask the committers to use their apache.orgemail ids for their GitHub email ids. And we can select the option of GitHub sending the email from the Author's email. This way there is no moderation required because commits@f.a.o seems to allow all apache.orgemail ids. GitHub validates the email addresses before it sends emails from those addresses. Thanks, Om I've sent another test email notification this time from my bigosma...@apache.org address. It did not automatically come through as I expected. Please take a look. Thanks, Om On Fri, Apr 26, 2013 at 2:25 PM, OmPrakash Muppirala bigosma...@gmail.comwrote: On Fri, Apr 26, 2013 at 12:16 PM, Alex Harui aha...@adobe.com wrote: Om, Maybe I wasn't clear. I think a key aspect of whiteboards on GitHub is to have a commit to your whiteboard be seen on the commits@flex.a.olist by anyone subscribed to commits@f.a.o without other work on their part like signing up with GitHub or being added as a member of the an organization. We can't get an email to commits@f.a.o to happen for all activity on your whiteboard? Short answer: it is doable. Long answer: I can add an organization-wide notification setting to send emails to: comm...@flex.apache.org. The only problem is the list moderator for commits@f.a.o should manually add notificati...@github.com to the list so that the emails can go through. Who is the moderator of commits@f.a.o? Thanks, Om On 4/26/13 11:04 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: On Fri, Apr 26, 2013 at 10:51 AM, Alex Harui aha...@adobe.com wrote: Om, Thanks for working on this. Some questions: 1) do you have this actually setup? If so, can you commit something to your whiteboard so I can see what the notification email looks like? Yes, but with a private account. I can add you as a member of this test organization. We can 'watch' repos and notifications emails can be configured [1], [2] More details on Organiations available here [3] 2) When the contributor sends the pull request, how does the committer get notified? Can an email go to the commits list? Or does the committer only get notified off-list? We should be able to make the notifications go to any and multiple email ids [4]. We will have to add the notificati...@github.com email id to our list. Thanks, Om [1] https://help.github.com/articles/watching-repositories [2] https://help.github.com/articles/configuring-notification-emails [3] https://help.github.com/categories/2/articles [4] https://help.github.com/articles/notifications#per-organization-email-routing -Alex On 4/26/13 10:27 AM, OmPrakash Muppirala bigosma...@gmail.com wrote: I have been experimenting with a GitHub based workflow for the whiteboard repos for our committers. Here is the workflow I would like to propose: * Apache Flex creates an 'Organization' account GitHub * Each Apache Flex committer is encouraged to create an account on GitHub * The committer then posts their GitHub id on dev@flex.apache.organd asks to be added to the ApacheFlex@GitHub account * The Apache Flex PMC will add the committer's GitHub id to the ApacheFlex@GitHub account. * In the contributing.md file [1] at the root of each committer's github project, there will be information about Apache's contribution guidelines including a link to the ICLA [2] * Any public contributor is free to fork an ApacheFlex committer's github project. * The contributor makes a few modifications and is ready to send a 'Pull request' to the Apache Flex committer * Before the 'Pull Request' can be sent, GitHub will automatically point the contributor to take a look at the contribution guidelines first. * Theoretically the contributor reads the contribution guidelines, agrees to it implicitly and clicks the 'Send Pull Request' button. * The Apache Flex Committer now will have a chance to peruse the commits and decide whether or not to accept the pull request. There is another alternative I have been working on as well. There is a CLAHub [3] plugin for GitHub. The workflow for this is described in the same link [3]. I have been experimenting with this plugin
Re: {DRAFT] April Board Report
Alex, I think I've seen comments from board members that they'd rather you not include the nothing to report sections. If I was producing the report I'd leave them out. Good report though. Thanks. Greg On Mon, Apr 8, 2013 at 10:03 AM, Alex Harui aha...@adobe.com wrote: BTW, I think we report quarterly after this report: Apache Flex is an application framework for easily building Flash-based applications for mobile devices, the browser and desktop. RELEASES Apache Flex 4.9.1 was released on 2/28/13. Apache Flex Installer 2.0.x was released on 1/9/13. The next version of the Installer is being voted on as of this writing. ACTIVITY Activity in Apache Flex continues to be in two main areas: improvements to the existing Adobe Flash Platform-dependent code base, including the releases listed above, and prototyping ways to create a version of Flex that is independent from the Adobe Flash Platform. There is another group working on Maven-related tools for the existing code base. We moved our code base from SVN to Git in mid-March. It has been a much more difficult transition than expected. Three weeks later, folks are still confused about how to use Git as it has many options for performing tasks that can have significant implications. Git¹s database model is not suited for partial checkouts like SVN, making the management of our whiteboard (a playground for committers) much more difficult as you have to download the entire whiteboard (currently 245MB) first. There is discussion of managing the whiteboard on GitHub, but others feel that it doesn't conform to the Apache way. The move to Git has slowed contributions from some committers as folks aren't sure they have the time to learn to use Git and are afraid of using the wrong options. Hopefully, the net benefit promised by the Git supporters will eventually be realized. COMMUNITY Harbs and Mark Kessler were added as committers. Frederic Thomas was added to the PMC. PRESS Per a request from the Apache Press VP, I was interviewed by a writer from InfoWorld in early February and the article was finally published in March. The link is: http://www.computerworld.com.au/slideshow/455802/pictures_15_high-impact_apa che_projects/?image=1 Nick Kwaitkowski presented on Apache Flex at the Flex Users Group in Chicago. Mike Labriola also presented on his Randori framework which uses compiler source from Apache Flex. LEGAL Nothing to report. TLP MIGRATION I don't know of any other remaining migration issues. INFRASTRUCTURE * Infra attempted to resolve INFRA-4380 but ran into problems. In the last report I thought we had a solution, but it appears that we are back to trying to devise a new solution. Tony has been helpful, but his time is limited. Every month we spend a few minutes discussing solutions. JIRA's migration tools are definitely insufficient, and Apache's desire to have one large centralized JIRA DB makes it difficult or impractical to experiment with custom solutions. BRANDING No issues at this time. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
Re: [MENTORS] Voting on code donations
On Sun, Mar 24, 2013 at 10:14 AM, Alex Harui aha...@adobe.com wrote: Hi Former Mentors, We’ve had some generous offers of code donations. I noticed that some projects have votes about whether to accept code donations, but we haven’t for any Adobe donations to Apache Flex. Is voting optional? I think there is some ambiguity with regard to how donations are accepted. Honestly, I'm not an expert on these matters. I believe this page is the canonical source for how to handle donations: http://incubator.apache.org/ip-clearance/index.html Unfortunately, I've been covered up with family and work matters and really haven't been able to follow things as I should around here recently. Sorry about that. So I'm not familiar with the specific scenarios you are speaking of. But, generally, I can see the following scenarios: 1) An individual develops code and donates that to Apache. 2) An open-source project decides to donate code to an Apache project. 3) A private company donates code to a project. Scenario 1 is easy. If the individual is a committer, he/she can simply commit the code. If the individual is not a committer he/she can submit the code via a Jira patch or through the IP Clearance process (it's usually safer to use the IP Clearance process in this case). Scenario 3 is not too hard. The company has legal ownership of the code so the onus is on them to decide whether they have provenance to donate it. This is the most common use of the page I linked to above and it's how the Flex code came in from Adobe. Scenario 2 is more complicated. Contributions to the code may have come from different sources and all owners must agree to the donation. That can be tricky. The IP Clearance form linked from the page above contains a line item for the PMC voting to accept responsibility for the code. We didn't do that with the Adobe code because the Adobe donation was part of the proposal for the Incubating project. Note that the page says it's not for new projects. The vote to accept that code came when the Incubator PMC voted to accept the project into the Incubator. I think the best approach if we are talking about scenario 2 or scenario 1 with a non-committer is to hold a formal vote. Even if scenario 1 comes from a committer, holding a vote makes everything clear to anyone who may come along wondering later. Either way, I think a significant code donation from an external party works best if it goes through the IP Clearance process. It just makes sure everything is in order as it should be. If it's just a few files that a committer drew up on his/her own, then there's nothing wrong with committing the code to the repo and holding a simple vote. But anything more than that would be better done through the IP Clearance process. And a formal vote is implied, if not required, by that process. Hope that helps. Greg
Re: AW: AW: Donation of Flexmojos
On Fri, Jan 25, 2013 at 3:35 AM, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: So ... does this have any impact on the plans to donate? Is it now harder to donate or does it make stuff even easier? To my knowledge the current licensing strategy of the product has no bearing on its donation. My assumption is that, by donating it, Velo asserts that he has intellectual property rights to the software, and he's passing those rights on to Apache. Apache can then relicense the software if/when we get ready to release it. Greg
Re: [VOTE] Allow tracking of download statistics on flex.apache.org
+1 Sent from my mobile device. On Jan 21, 2013, at 6:49 PM, Om bigosma...@gmail.com wrote: Please vote to allow the use of Google Analytics [1] to track download statistics of Apache Flex source, binaries and Installer artifacts. If you have any comments, please reply in this thread: [2] Here is the JIRA ticket that describes what needs to be done [3] Thanks, Om [1] http://www.google.com/analytics/ [2] http://markmail.org/thread/g3l6t7gt2guxh7qg [3] https://issues.apache.org/jira/browse/FLEX-33361
Re: [Marketing] - Telling the world that we are a TLP...
Thanks, Scott for helping with this! On Mon, Jan 14, 2013 at 10:39 AM, Guthmann, Scott sguthm...@on3solutions.com wrote: The Press Release is out. Please spread the word. Please tweet, Please Blog, Please share on your social networks. Please encourage others to join the mailing list and help in all the ways they feel comfortable. http://globenewswire.com/news-release/2013/01/14/516186/10017952/en/The-Apache-Software-Foundation-Announces-Apache-Flex-tm-as-a-Top-Level-Project.html The project improves IMO when there are more volunteers doing work for the project and donating code and time. Why I mention this is to provide you with a good reason to promote. If there are more volunteers, the support improves, the releases come more quickly, there are more wiki editors, and documentation editors, more examples are written, more provide reference applications. We should see many mentions and news articles written over the coming days. It is an exciting time!
Re: FlexUnit Location
On Fri, Jan 11, 2013 at 1:49 PM, Michael A. Labriola labri...@digitalprimates.net wrote: Do we know who owns it? Is that person willing to donate the code to the ASF? I own it. I donated it. The grant was filed with Apache last august. I'm sorry. I should've done the research :-) Ok, then I think we can go ahead and import it then. Greg
Re: [OT] Apache Flex twitter mentions up
That's good press :) Sent from my mobile device. On Jan 8, 2013, at 6:16 AM, Justin Mclean jus...@classsoftware.com wrote: Hi, Most of it seems to come from this article: http://www.internetnews.com/blog/skerner/open-source-flex-gets-top-project-status-at-apache.html Justin
