You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@flex.apache.org by Maurice Amsellem <ma...@systar.com> on 2014/03/20 14:41:36 UTC
RE: Third-party tools / solutions on Apache Flex website
ActiveMQ is a middleware, so it's rather obvious to have a connectivity section.
However, having a section in the website about Apache Flex "Ecosystem" (MVC frameworks, Back-ends, IDEs, etc...) seems an excellent idea to me.
I don't think you can contribute directly on the web site, because it requires an svn account, but you are more than welcome to contribute to the content.
I think a simple way of doing that is to create a JIRA ticket to support your initiative and provide content as attached files (HTML files are fine)
The web site is using a CMS Management system inspired from Django, but we can rather easily convert HTML content if you provide it.
Make a first draft of your content and submit it, so we can see how it integrates to the site, and then you can polish / complete it.
Thank you again for your offer to help...
Maurice
-----Message d'origine-----
De : Gary Yang [mailto:flashflexpro@gmail.com]
Envoyé : jeudi 20 mars 2014 14:28
À : dev@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
Franck, I can not agree more! -Gary
On Thu, Mar 20, 2014 at 8:33 AM, Franck Wolff <fr...@gmail.com> wrote:
> Hi,
>
> I'm wondering why there is no section about Flex related server
> solutions such as BlazeDS, AMFPHP, FluorineFx, Red5, WebOrb and
> GraniteDS (I'm of course especially interesting in seeing GraniteDS
> somewhere on the Apache Flex website ;)
>
> I think people landing on the Apache Flex website and looking for the
> required tools / solutions usually accompanying a client-side SDK
> (IDEs, frameworks and servers) can end up with Google and the feeling
> that a lot of solutions are discontinued or inactive. There is
> admittedly something about IDEs
> (http://flex.apache.org/about-features.html) but I couldn't find
> anything like a comprehensive list of frameworks and server-side solutions.
> The mention of the latest release of BlazeDS at the bottom of every
> page
> "4.6.0 (Nov 2011)" is a bit awkward in this respect and can even
> discourage potential adopters of Apache Flex...
>
> Apache ActiveMQ is, IMHO, doing the right thing with its "Connectivity"
> page (http://activemq.apache.org/connectivity.html): a long and
> comprehensive list of third-party solutions, open-source (from Apache
> or other players) or not (WebLogic for instance), which gives a quick
> overview of a large panel of related tools and solutions.
>
> Do you think you could add a section on third-party tools? Can I
> contribute (I'll try to be fair with everybody) if you don't have time
> to write this page?
>
> Thanks,
> Franck Wolff
> Granite Data Services.
>
> PS: we have just released GraniteDS 3.0.3.GA (
> http://www.granitedataservices.com/2014/03/20/graniteds-3-0-3-ga-is-ou
> t/) and it would be great if you could mention it in your "Latest
> Releases" or "Latest News" panel (or anywhere else). I remember
> osflash.org had a News section where related projects could register
> and announce their latest releases (osflash is from the neolithic
> period, I admit).
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Frédéric THOMAS <we...@hotmail.com>.
Hi,
Ariel Sommeria-Klein, the team lead for AmfPhp asked me too, I invited him
to join this list, maybe he will be interested to work with you on the
content.
--
View this message in context: http://apache-flex-development.2333347.n4.nabble.com/Third-party-tools-solutions-on-Apache-Flex-website-tp36116p36207.html
Sent from the Apache Flex Development mailing list archive at Nabble.com.
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Well, this comparative table comes from us, we asked Fred to let us publish
something about BlazeDS vs. LCDS vs. GraniteDS...
I think we shouldn't go into details in a general page about third-party
solutions. And we have to cover different kind of technologies such as
IDEs, client-side frameworks, code generators tools and server solutions. A
detailed comparative table wouldn't fit for this purpose.
Thanks,
Franck.
2014-03-20 17:59 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
> Fred recently added this page on the wiki [1]
> Maybe you can use this as a starting point and improve on it?
>
> Thanks,
> Om
>
> [1]
>
> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
>
>
> On Thu, Mar 20, 2014 at 9:54 AM, Franck Wolff <fr...@gmail.com> wrote:
>
> > 2014-03-20 17:03 GMT+01:00 Alex Harui <ah...@adobe.com>:
> > >
> > >
> > > On 3/20/14 8:37 AM, "Franck Wolff" <fr...@gmail.com> wrote:
> > >
> > > >3) Not sure to understand what you mean here... Do you want to make
> sure
> > > >that nobody is mentioning "Adobe Flex" anymore?
> > > No, you can still mention "Adobe Flex", but it is important that your
> web
> > > site use the Flex trademark correctly as per
> > > http://www.apache.org/foundation/marks/ and help to notify that world
> > that
> > > Flex is now at Apache.
> > >
> > > Adobe did not care as much about proper use of the Flex trademark, but
> > the
> > > Apache does.
> > >
> >
> > I can certainly make sure that GraniteDS website is linking back to
> Apache
> > Flex (we already do that) and following the Apache trademark policy (if I
> > understand what it is about ;)
> >
> > However, I can't verify that all related projects are complying to your
> > request and I'm certainly not the right person to ask them to do so...
> >
> > I should have a first draft next week.
> >
> > Thanks,
> > Franck.
> >
> >
> >
> > >
> > > -Alex
> > >
> > >
> >
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Well, this comparative table comes from us, we asked Fred to let us publish
something about BlazeDS vs. LCDS vs. GraniteDS...
I think we shouldn't go into details in a general page about third-party
solutions. And we have to cover different kind of technologies such as
IDEs, client-side frameworks, code generators tools and server solutions. A
detailed comparative table wouldn't fit for this purpose.
Thanks,
Franck.
2014-03-20 17:59 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
> Fred recently added this page on the wiki [1]
> Maybe you can use this as a starting point and improve on it?
>
> Thanks,
> Om
>
> [1]
>
> https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
>
>
> On Thu, Mar 20, 2014 at 9:54 AM, Franck Wolff <fr...@gmail.com> wrote:
>
> > 2014-03-20 17:03 GMT+01:00 Alex Harui <ah...@adobe.com>:
> > >
> > >
> > > On 3/20/14 8:37 AM, "Franck Wolff" <fr...@gmail.com> wrote:
> > >
> > > >3) Not sure to understand what you mean here... Do you want to make
> sure
> > > >that nobody is mentioning "Adobe Flex" anymore?
> > > No, you can still mention "Adobe Flex", but it is important that your
> web
> > > site use the Flex trademark correctly as per
> > > http://www.apache.org/foundation/marks/ and help to notify that world
> > that
> > > Flex is now at Apache.
> > >
> > > Adobe did not care as much about proper use of the Flex trademark, but
> > the
> > > Apache does.
> > >
> >
> > I can certainly make sure that GraniteDS website is linking back to
> Apache
> > Flex (we already do that) and following the Apache trademark policy (if I
> > understand what it is about ;)
> >
> > However, I can't verify that all related projects are complying to your
> > request and I'm certainly not the right person to ask them to do so...
> >
> > I should have a first draft next week.
> >
> > Thanks,
> > Franck.
> >
> >
> >
> > >
> > > -Alex
> > >
> > >
> >
>
Re: Third-party tools / solutions on Apache Flex website
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Fred recently added this page on the wiki [1]
Maybe you can use this as a starting point and improve on it?
Thanks,
Om
[1]
https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
On Thu, Mar 20, 2014 at 9:54 AM, Franck Wolff <fr...@gmail.com> wrote:
> 2014-03-20 17:03 GMT+01:00 Alex Harui <ah...@adobe.com>:
> >
> >
> > On 3/20/14 8:37 AM, "Franck Wolff" <fr...@gmail.com> wrote:
> >
> > >3) Not sure to understand what you mean here... Do you want to make sure
> > >that nobody is mentioning "Adobe Flex" anymore?
> > No, you can still mention "Adobe Flex", but it is important that your web
> > site use the Flex trademark correctly as per
> > http://www.apache.org/foundation/marks/ and help to notify that world
> that
> > Flex is now at Apache.
> >
> > Adobe did not care as much about proper use of the Flex trademark, but
> the
> > Apache does.
> >
>
> I can certainly make sure that GraniteDS website is linking back to Apache
> Flex (we already do that) and following the Apache trademark policy (if I
> understand what it is about ;)
>
> However, I can't verify that all related projects are complying to your
> request and I'm certainly not the right person to ask them to do so...
>
> I should have a first draft next week.
>
> Thanks,
> Franck.
>
>
>
> >
> > -Alex
> >
> >
>
Re: Third-party tools / solutions on Apache Flex website
Posted by OmPrakash Muppirala <bi...@gmail.com>.
Fred recently added this page on the wiki [1]
Maybe you can use this as a starting point and improve on it?
Thanks,
Om
[1]
https://cwiki.apache.org/confluence/display/FLEX/Flex+Server+Technologies+-+Comparative+table
On Thu, Mar 20, 2014 at 9:54 AM, Franck Wolff <fr...@gmail.com> wrote:
> 2014-03-20 17:03 GMT+01:00 Alex Harui <ah...@adobe.com>:
> >
> >
> > On 3/20/14 8:37 AM, "Franck Wolff" <fr...@gmail.com> wrote:
> >
> > >3) Not sure to understand what you mean here... Do you want to make sure
> > >that nobody is mentioning "Adobe Flex" anymore?
> > No, you can still mention "Adobe Flex", but it is important that your web
> > site use the Flex trademark correctly as per
> > http://www.apache.org/foundation/marks/ and help to notify that world
> that
> > Flex is now at Apache.
> >
> > Adobe did not care as much about proper use of the Flex trademark, but
> the
> > Apache does.
> >
>
> I can certainly make sure that GraniteDS website is linking back to Apache
> Flex (we already do that) and following the Apache trademark policy (if I
> understand what it is about ;)
>
> However, I can't verify that all related projects are complying to your
> request and I'm certainly not the right person to ask them to do so...
>
> I should have a first draft next week.
>
> Thanks,
> Franck.
>
>
>
> >
> > -Alex
> >
> >
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
BTW: I'm certainly NOT asking for any credits for the writing of this page.
It is purely "public domain" in my mind and you can do whatever you want
with it, with or without my permission.
Franck.
2014-03-31 16:33 GMT+02:00 Franck Wolff <fr...@gmail.com>:
> The new page is just a modification of an existing Apache Flex page, it
> follows the look & feel of the website and I believe it could be even
> published as is (hard to say without knowing which CMS you use).
>
> Anyway: can somebody who knows the website publication process do it for
> me?
>
> Franck.
>
>
> 2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>:
>
> I agree this should be a regular page.
>> However, the web site is not that easy to modify ( CMS content and
>> two-phase publication) + you need access to svn
>>
>> Maurice
>>
>>
>> -----Message d'origine-----
>> De : Franck Wolff [mailto:frawolff@gmail.com]
>> Envoyé : lundi 31 mars 2014 14:27
>> À : dev@flex.apache.org
>> Objet : Re: Third-party tools / solutions on Apache Flex website
>>
>> Thanks Justin.
>>
>> I don't think it should be just a Wiki page. In my mind, it should rather
>> be a regular page of the website, either in the "About Flex" or "Community"
>> section (your call).
>>
>> Can you grant me a (temporary) write access to the website? Where should
>> I put this new page?
>>
>> Franck.
>>
>>
>> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>:
>>
>> > HI,
>> >
>> > > Any chance to get this page published anytime soon (with Andrew's
>> > > modifications applied)?
>> >
>> > You don't have to be a committer to make wiki edits changes/ just ask
>> > for wiki access put the file there yourself may be the quickest way.
>> >
>> > Thanks,
>> > Justin
>> >
>> >
>>
>
>
RE: Third-party tools / solutions on Apache Flex website
Posted by Maurice Amsellem <ma...@systar.com>.
I spent some time trying to figure out why the page was empty except the title.
Finally, it was because of ANSI encoding. I changed it to UTF8, and it fixed it.
The CMS system does not support ANSI, but you have to know it :)
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com]
Envoyé : mardi 1 avril 2014 13:55
À : Maurice Amsellem
Cc : dev@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
Thanks Maurice! That was fast ;)
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Well, you're free to modify the page as you want.
Franck.
2014-04-01 13:48 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
Published.
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Otherwise, great stuff.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : mardi 1 avril 2014 11:41
À : dev@flex.apache.org<ma...@flex.apache.org>
Cc : Maurice Amsellem
Objet : Re: Third-party tools / solutions on Apache Flex website
Done: FLEX-34199<https://issues.apache.org/jira/browse/FLEX-34199>.
Franck.
2014-04-01 6:09 GMT+02:00 Alex Harui <ah...@adobe.com>>:
For record keeping purposes please submit the content in a jira issue.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Maurice Amsellem <ma...@systar.com>> wrote:
>Anyway: can somebody who knows the website publication process do it for me?
I can do it.
However, I wasn't following this thread, so is the team ok regarding the content ad location to publish?
If so, send me the content, I will format it, review it and get it published.
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : lundi 31 mars 2014 16:34
À : dev@flex.apache.org<ma...@flex.apache.org>
Objet : Re: Third-party tools / solutions on Apache Flex website
The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>] Envoyé : lundi 31 mars
> 2014 14:27 À : dev@flex.apache.org<ma...@flex.apache.org> Objet : Re: Third-party tools /
> solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should
> rather be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where
> should I put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just
> > ask for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Nicholas Kwiatkowski <ni...@spoon.as>.
A disclaimer might be good, but I don't think we need to put too much into
it -- this is clearly a 3rd party project page.
-Nick
On Tue, Apr 1, 2014 at 11:12 AM, Alex Harui <ah...@adobe.com> wrote:
> Hey guys,
>
> Thanks for getting this done. I'm tempted to add some sort of a
> disclaimer at the beginning that the list may not be complete or an
> endorsement. What do others think?
>
> -Alex
> ________________________________________
> From: Maurice Amsellem [maurice.amsellem@systar.com]
> Sent: Tuesday, April 1, 2014 4:59 AM
> To: Franck Wolff
> Cc: dev@flex.apache.org
> Subject: RE: Third-party tools / solutions on Apache Flex website
>
> >Well, you're free to modify the page as you want.
>
> I have extended the description on Parsley.
>
> Maurice
>
> De : Franck Wolff [mailto:frawolff@gmail.com]
> Envoyé : mardi 1 avril 2014 13:55
> À : Maurice Amsellem
> Cc : dev@flex.apache.org
> Objet : Re: Third-party tools / solutions on Apache Flex website
>
> Thanks Maurice! That was fast ;)
>
>
> Note: the testing section is not complete IMO.
> it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as
> LoadRunner].
>
> Parsley would deserver a better description.
>
> Well, you're free to modify the page as you want.
>
> Franck.
>
> 2014-04-01 13:48 GMT+02:00 Maurice Amsellem <maurice.amsellem@systar.com
> <ma...@systar.com>>:
> Published.
>
> Note: the testing section is not complete IMO.
> it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as
> LoadRunner].
>
> Parsley would deserver a better description.
>
> Otherwise, great stuff.
>
> Maurice
>
>
> De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
> Envoyé : mardi 1 avril 2014 11:41
> À : dev@flex.apache.org<ma...@flex.apache.org>
> Cc : Maurice Amsellem
>
> Objet : Re: Third-party tools / solutions on Apache Flex website
>
> Done: FLEX-34199<https://issues.apache.org/jira/browse/FLEX-34199>.
>
> Franck.
>
> 2014-04-01 6:09 GMT+02:00 Alex Harui <aharui@adobe.com<mailto:
> aharui@adobe.com>>:
> For record keeping purposes please submit the content in a jira issue.
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Maurice Amsellem <maurice.amsellem@systar.com<mailto:
> maurice.amsellem@systar.com>> wrote:
>
>
> >Anyway: can somebody who knows the website publication process do it for
> me?
>
> I can do it.
>
> However, I wasn't following this thread, so is the team ok regarding the
> content ad location to publish?
> If so, send me the content, I will format it, review it and get it
> published.
>
> Maurice
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
> Envoyé : lundi 31 mars 2014 16:34
> À : dev@flex.apache.org<ma...@flex.apache.org>
> Objet : Re: Third-party tools / solutions on Apache Flex website
>
> The new page is just a modification of an existing Apache Flex page, it
> follows the look & feel of the website and I believe it could be even
> published as is (hard to say without knowing which CMS you use).
>
> Anyway: can somebody who knows the website publication process do it for
> me?
>
> Franck.
>
>
> 2014-03-31 15:26 GMT+02:00 Maurice Amsellem <maurice.amsellem@systar.com
> <ma...@systar.com>>:
>
> > I agree this should be a regular page.
> > However, the web site is not that easy to modify ( CMS content and
> > two-phase publication) + you need access to svn
> >
> > Maurice
> >
> >
> > -----Message d'origine-----
> > De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
> Envoyé : lundi 31 mars
> > 2014 14:27 À : dev@flex.apache.org<ma...@flex.apache.org> Objet :
> Re: Third-party tools /
> > solutions on Apache Flex website
> >
> > Thanks Justin.
> >
> > I don't think it should be just a Wiki page. In my mind, it should
> > rather be a regular page of the website, either in the "About Flex" or
> "Community"
> > section (your call).
> >
> > Can you grant me a (temporary) write access to the website? Where
> > should I put this new page?
> >
> > Franck.
> >
> >
> > 2014-03-31 13:53 GMT+02:00 Justin Mclean <justin@classsoftware.com
> <ma...@classsoftware.com>>:
> >
> > > HI,
> > >
> > > > Any chance to get this page published anytime soon (with Andrew's
> > > > modifications applied)?
> > >
> > > You don't have to be a committer to make wiki edits changes/ just
> > > ask for wiki access put the file there yourself may be the quickest
> way.
> > >
> > > Thanks,
> > > Justin
> > >
> > >
> >
>
>
RE: Third-party tools / solutions on Apache Flex website
Posted by ma...@usmc.mil.
+1 Disclaimer
-----Original Message-----
From: Alex Harui [mailto:aharui@adobe.com]
Sent: Tuesday, April 01, 2014 11:12 AM
To: dev@flex.apache.org; Franck Wolff
Subject: RE: Third-party tools / solutions on Apache Flex website
Hey guys,
Thanks for getting this done. I'm tempted to add some sort of a disclaimer at the beginning that the list may not be complete or an endorsement. What do others think?
-Alex
________________________________________
From: Maurice Amsellem [maurice.amsellem@systar.com]
Sent: Tuesday, April 1, 2014 4:59 AM
To: Franck Wolff
Cc: dev@flex.apache.org
Subject: RE: Third-party tools / solutions on Apache Flex website
>Well, you're free to modify the page as you want.
I have extended the description on Parsley.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com]
Envoyé : mardi 1 avril 2014 13:55
À : Maurice Amsellem
Cc : dev@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
Thanks Maurice! That was fast ;)
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Well, you're free to modify the page as you want.
Franck.
2014-04-01 13:48 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
Published.
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Otherwise, great stuff.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : mardi 1 avril 2014 11:41
À : dev@flex.apache.org<ma...@flex.apache.org>
Cc : Maurice Amsellem
Objet : Re: Third-party tools / solutions on Apache Flex website
Done: FLEX-34199<https://issues.apache.org/jira/browse/FLEX-34199>.
Franck.
2014-04-01 6:09 GMT+02:00 Alex Harui <ah...@adobe.com>>:
For record keeping purposes please submit the content in a jira issue.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Maurice Amsellem <ma...@systar.com>> wrote:
>Anyway: can somebody who knows the website publication process do it for me?
I can do it.
However, I wasn't following this thread, so is the team ok regarding the content ad location to publish?
If so, send me the content, I will format it, review it and get it published.
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : lundi 31 mars 2014 16:34
À : dev@flex.apache.org<ma...@flex.apache.org>
Objet : Re: Third-party tools / solutions on Apache Flex website
The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>] Envoyé : lundi 31 mars
> 2014 14:27 À : dev@flex.apache.org<ma...@flex.apache.org> Objet : Re: Third-party tools /
> solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should
> rather be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where
> should I put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just
> > ask for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
RE: Third-party tools / solutions on Apache Flex website
Posted by Maurice Amsellem <ma...@systar.com>.
I agree for the disclaimer.
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : mardi 1 avril 2014 17:12
À : dev@flex.apache.org; Franck Wolff
Objet : RE: Third-party tools / solutions on Apache Flex website
Hey guys,
Thanks for getting this done. I'm tempted to add some sort of a disclaimer at the beginning that the list may not be complete or an endorsement. What do others think?
-Alex
________________________________________
From: Maurice Amsellem [maurice.amsellem@systar.com]
Sent: Tuesday, April 1, 2014 4:59 AM
To: Franck Wolff
Cc: dev@flex.apache.org
Subject: RE: Third-party tools / solutions on Apache Flex website
>Well, you're free to modify the page as you want.
I have extended the description on Parsley.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com] Envoyé : mardi 1 avril 2014 13:55 À : Maurice Amsellem Cc : dev@flex.apache.org Objet : Re: Third-party tools / solutions on Apache Flex website
Thanks Maurice! That was fast ;)
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Well, you're free to modify the page as you want.
Franck.
2014-04-01 13:48 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
Published.
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Otherwise, great stuff.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : mardi 1 avril 2014 11:41
À : dev@flex.apache.org<ma...@flex.apache.org>
Cc : Maurice Amsellem
Objet : Re: Third-party tools / solutions on Apache Flex website
Done: FLEX-34199<https://issues.apache.org/jira/browse/FLEX-34199>.
Franck.
2014-04-01 6:09 GMT+02:00 Alex Harui <ah...@adobe.com>>:
For record keeping purposes please submit the content in a jira issue.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Maurice Amsellem <ma...@systar.com>> wrote:
>Anyway: can somebody who knows the website publication process do it for me?
I can do it.
However, I wasn't following this thread, so is the team ok regarding the content ad location to publish?
If so, send me the content, I will format it, review it and get it published.
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : lundi 31 mars 2014 16:34
À : dev@flex.apache.org<ma...@flex.apache.org>
Objet : Re: Third-party tools / solutions on Apache Flex website
The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff
> [mailto:frawolff@gmail.com<ma...@gmail.com>] Envoyé : lundi
> 31 mars
> 2014 14:27 À : dev@flex.apache.org<ma...@flex.apache.org> Objet :
> Re: Third-party tools / solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should
> rather be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where
> should I put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just
> > ask for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
RE: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
Hey guys,
Thanks for getting this done. I'm tempted to add some sort of a disclaimer at the beginning that the list may not be complete or an endorsement. What do others think?
-Alex
________________________________________
From: Maurice Amsellem [maurice.amsellem@systar.com]
Sent: Tuesday, April 1, 2014 4:59 AM
To: Franck Wolff
Cc: dev@flex.apache.org
Subject: RE: Third-party tools / solutions on Apache Flex website
>Well, you're free to modify the page as you want.
I have extended the description on Parsley.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com]
Envoyé : mardi 1 avril 2014 13:55
À : Maurice Amsellem
Cc : dev@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
Thanks Maurice! That was fast ;)
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Well, you're free to modify the page as you want.
Franck.
2014-04-01 13:48 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
Published.
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Otherwise, great stuff.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : mardi 1 avril 2014 11:41
À : dev@flex.apache.org<ma...@flex.apache.org>
Cc : Maurice Amsellem
Objet : Re: Third-party tools / solutions on Apache Flex website
Done: FLEX-34199<https://issues.apache.org/jira/browse/FLEX-34199>.
Franck.
2014-04-01 6:09 GMT+02:00 Alex Harui <ah...@adobe.com>>:
For record keeping purposes please submit the content in a jira issue.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Maurice Amsellem <ma...@systar.com>> wrote:
>Anyway: can somebody who knows the website publication process do it for me?
I can do it.
However, I wasn't following this thread, so is the team ok regarding the content ad location to publish?
If so, send me the content, I will format it, review it and get it published.
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : lundi 31 mars 2014 16:34
À : dev@flex.apache.org<ma...@flex.apache.org>
Objet : Re: Third-party tools / solutions on Apache Flex website
The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>] Envoyé : lundi 31 mars
> 2014 14:27 À : dev@flex.apache.org<ma...@flex.apache.org> Objet : Re: Third-party tools /
> solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should
> rather be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where
> should I put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just
> > ask for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
RE: Third-party tools / solutions on Apache Flex website
Posted by Maurice Amsellem <ma...@systar.com>.
>Well, you're free to modify the page as you want.
I have extended the description on Parsley.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com]
Envoyé : mardi 1 avril 2014 13:55
À : Maurice Amsellem
Cc : dev@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
Thanks Maurice! That was fast ;)
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Well, you're free to modify the page as you want.
Franck.
2014-04-01 13:48 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
Published.
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Otherwise, great stuff.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : mardi 1 avril 2014 11:41
À : dev@flex.apache.org<ma...@flex.apache.org>
Cc : Maurice Amsellem
Objet : Re: Third-party tools / solutions on Apache Flex website
Done: FLEX-34199<https://issues.apache.org/jira/browse/FLEX-34199>.
Franck.
2014-04-01 6:09 GMT+02:00 Alex Harui <ah...@adobe.com>>:
For record keeping purposes please submit the content in a jira issue.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Maurice Amsellem <ma...@systar.com>> wrote:
>Anyway: can somebody who knows the website publication process do it for me?
I can do it.
However, I wasn't following this thread, so is the team ok regarding the content ad location to publish?
If so, send me the content, I will format it, review it and get it published.
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : lundi 31 mars 2014 16:34
À : dev@flex.apache.org<ma...@flex.apache.org>
Objet : Re: Third-party tools / solutions on Apache Flex website
The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>] Envoyé : lundi 31 mars
> 2014 14:27 À : dev@flex.apache.org<ma...@flex.apache.org> Objet : Re: Third-party tools /
> solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should
> rather be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where
> should I put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just
> > ask for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Thanks Maurice! That was fast ;)
Note: the testing section is not complete IMO.
> it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as
> LoadRunner].
>
> Parsley would deserver a better description.
Well, you're free to modify the page as you want.
Franck.
2014-04-01 13:48 GMT+02:00 Maurice Amsellem <ma...@systar.com>:
> Published.
>
>
>
> Note: the testing section is not complete IMO.
>
> it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as
> LoadRunner].
>
>
>
> Parsley would deserver a better description.
>
>
>
> Otherwise, great stuff.
>
>
>
> Maurice
>
>
>
>
>
> *De :* Franck Wolff [mailto:frawolff@gmail.com]
> *Envoyé :* mardi 1 avril 2014 11:41
> *À :* dev@flex.apache.org
> *Cc :* Maurice Amsellem
>
> *Objet :* Re: Third-party tools / solutions on Apache Flex website
>
>
>
> Done: FLEX-34199 <https://issues.apache.org/jira/browse/FLEX-34199>.
>
>
>
> Franck.
>
>
>
> 2014-04-01 6:09 GMT+02:00 Alex Harui <ah...@adobe.com>:
>
> For record keeping purposes please submit the content in a jira issue.
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
>
> Maurice Amsellem <ma...@systar.com> wrote:
>
>
> >Anyway: can somebody who knows the website publication process do it for
> me?
>
> I can do it.
>
> However, I wasn't following this thread, so is the team ok regarding the
> content ad location to publish?
> If so, send me the content, I will format it, review it and get it
> published.
>
> Maurice
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com]
> Envoyé : lundi 31 mars 2014 16:34
> À : dev@flex.apache.org
> Objet : Re: Third-party tools / solutions on Apache Flex website
>
> The new page is just a modification of an existing Apache Flex page, it
> follows the look & feel of the website and I believe it could be even
> published as is (hard to say without knowing which CMS you use).
>
> Anyway: can somebody who knows the website publication process do it for
> me?
>
> Franck.
>
>
> 2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>:
>
> > I agree this should be a regular page.
> > However, the web site is not that easy to modify ( CMS content and
> > two-phase publication) + you need access to svn
> >
> > Maurice
> >
> >
> > -----Message d'origine-----
> > De : Franck Wolff [mailto:frawolff@gmail.com] Envoyé : lundi 31 mars
> > 2014 14:27 À : dev@flex.apache.org Objet : Re: Third-party tools /
> > solutions on Apache Flex website
> >
> > Thanks Justin.
> >
> > I don't think it should be just a Wiki page. In my mind, it should
> > rather be a regular page of the website, either in the "About Flex" or
> "Community"
> > section (your call).
> >
> > Can you grant me a (temporary) write access to the website? Where
> > should I put this new page?
> >
> > Franck.
> >
> >
> > 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>:
> >
> > > HI,
> > >
> > > > Any chance to get this page published anytime soon (with Andrew's
> > > > modifications applied)?
> > >
> > > You don't have to be a committer to make wiki edits changes/ just
> > > ask for wiki access put the file there yourself may be the quickest
> way.
> > >
> > > Thanks,
> > > Justin
> > >
> > >
> >
>
>
>
RE: Third-party tools / solutions on Apache Flex website
Posted by Maurice Amsellem <ma...@systar.com>.
Published.
Note: the testing section is not complete IMO.
it's missing FlexMonkey, HP QTP (QuickTest Professional) [not the same as LoadRunner].
Parsley would deserver a better description.
Otherwise, great stuff.
Maurice
De : Franck Wolff [mailto:frawolff@gmail.com]
Envoyé : mardi 1 avril 2014 11:41
À : dev@flex.apache.org
Cc : Maurice Amsellem
Objet : Re: Third-party tools / solutions on Apache Flex website
Done: FLEX-34199<https://issues.apache.org/jira/browse/FLEX-34199>.
Franck.
2014-04-01 6:09 GMT+02:00 Alex Harui <ah...@adobe.com>>:
For record keeping purposes please submit the content in a jira issue.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Maurice Amsellem <ma...@systar.com>> wrote:
>Anyway: can somebody who knows the website publication process do it for me?
I can do it.
However, I wasn't following this thread, so is the team ok regarding the content ad location to publish?
If so, send me the content, I will format it, review it and get it published.
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>]
Envoyé : lundi 31 mars 2014 16:34
À : dev@flex.apache.org<ma...@flex.apache.org>
Objet : Re: Third-party tools / solutions on Apache Flex website
The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com<ma...@gmail.com>] Envoyé : lundi 31 mars
> 2014 14:27 À : dev@flex.apache.org<ma...@flex.apache.org> Objet : Re: Third-party tools /
> solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should
> rather be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where
> should I put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just
> > ask for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Done: FLEX-34199 <https://issues.apache.org/jira/browse/FLEX-34199>.
Franck.
2014-04-01 6:09 GMT+02:00 Alex Harui <ah...@adobe.com>:
> For record keeping purposes please submit the content in a jira issue.
> Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
>
> Maurice Amsellem <ma...@systar.com> wrote:
>
>
> >Anyway: can somebody who knows the website publication process do it for
> me?
>
> I can do it.
>
> However, I wasn't following this thread, so is the team ok regarding the
> content ad location to publish?
> If so, send me the content, I will format it, review it and get it
> published.
>
> Maurice
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com]
> Envoyé : lundi 31 mars 2014 16:34
> À : dev@flex.apache.org
> Objet : Re: Third-party tools / solutions on Apache Flex website
>
> The new page is just a modification of an existing Apache Flex page, it
> follows the look & feel of the website and I believe it could be even
> published as is (hard to say without knowing which CMS you use).
>
> Anyway: can somebody who knows the website publication process do it for
> me?
>
> Franck.
>
>
> 2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>:
>
> > I agree this should be a regular page.
> > However, the web site is not that easy to modify ( CMS content and
> > two-phase publication) + you need access to svn
> >
> > Maurice
> >
> >
> > -----Message d'origine-----
> > De : Franck Wolff [mailto:frawolff@gmail.com] Envoyé : lundi 31 mars
> > 2014 14:27 À : dev@flex.apache.org Objet : Re: Third-party tools /
> > solutions on Apache Flex website
> >
> > Thanks Justin.
> >
> > I don't think it should be just a Wiki page. In my mind, it should
> > rather be a regular page of the website, either in the "About Flex" or
> "Community"
> > section (your call).
> >
> > Can you grant me a (temporary) write access to the website? Where
> > should I put this new page?
> >
> > Franck.
> >
> >
> > 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>:
> >
> > > HI,
> > >
> > > > Any chance to get this page published anytime soon (with Andrew's
> > > > modifications applied)?
> > >
> > > You don't have to be a committer to make wiki edits changes/ just
> > > ask for wiki access put the file there yourself may be the quickest
> way.
> > >
> > > Thanks,
> > > Justin
> > >
> > >
> >
>
RE: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
For record keeping purposes please submit the content in a jira issue.
Sent via the PANTECH Discover, an AT&T 4G LTE smartphone.
Maurice Amsellem <ma...@systar.com> wrote:
>Anyway: can somebody who knows the website publication process do it for me?
I can do it.
However, I wasn't following this thread, so is the team ok regarding the content ad location to publish?
If so, send me the content, I will format it, review it and get it published.
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com]
Envoyé : lundi 31 mars 2014 16:34
À : dev@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com] Envoyé : lundi 31 mars
> 2014 14:27 À : dev@flex.apache.org Objet : Re: Third-party tools /
> solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should
> rather be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where
> should I put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just
> > ask for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
RE: Third-party tools / solutions on Apache Flex website
Posted by Maurice Amsellem <ma...@systar.com>.
>Anyway: can somebody who knows the website publication process do it for me?
I can do it.
However, I wasn't following this thread, so is the team ok regarding the content ad location to publish?
If so, send me the content, I will format it, review it and get it published.
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com]
Envoyé : lundi 31 mars 2014 16:34
À : dev@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
The new page is just a modification of an existing Apache Flex page, it follows the look & feel of the website and I believe it could be even published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com] Envoyé : lundi 31 mars
> 2014 14:27 À : dev@flex.apache.org Objet : Re: Third-party tools /
> solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should
> rather be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where
> should I put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just
> > ask for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
The new page is just a modification of an existing Apache Flex page, it
follows the look & feel of the website and I believe it could be even
published as is (hard to say without knowing which CMS you use).
Anyway: can somebody who knows the website publication process do it for me?
Franck.
2014-03-31 15:26 GMT+02:00 Maurice Amsellem <ma...@systar.com>:
> I agree this should be a regular page.
> However, the web site is not that easy to modify ( CMS content and
> two-phase publication) + you need access to svn
>
> Maurice
>
>
> -----Message d'origine-----
> De : Franck Wolff [mailto:frawolff@gmail.com]
> Envoyé : lundi 31 mars 2014 14:27
> À : dev@flex.apache.org
> Objet : Re: Third-party tools / solutions on Apache Flex website
>
> Thanks Justin.
>
> I don't think it should be just a Wiki page. In my mind, it should rather
> be a regular page of the website, either in the "About Flex" or "Community"
> section (your call).
>
> Can you grant me a (temporary) write access to the website? Where should I
> put this new page?
>
> Franck.
>
>
> 2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>:
>
> > HI,
> >
> > > Any chance to get this page published anytime soon (with Andrew's
> > > modifications applied)?
> >
> > You don't have to be a committer to make wiki edits changes/ just ask
> > for wiki access put the file there yourself may be the quickest way.
> >
> > Thanks,
> > Justin
> >
> >
>
RE: Third-party tools / solutions on Apache Flex website
Posted by Maurice Amsellem <ma...@systar.com>.
I agree this should be a regular page.
However, the web site is not that easy to modify ( CMS content and two-phase publication) + you need access to svn
Maurice
-----Message d'origine-----
De : Franck Wolff [mailto:frawolff@gmail.com]
Envoyé : lundi 31 mars 2014 14:27
À : dev@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
Thanks Justin.
I don't think it should be just a Wiki page. In my mind, it should rather be a regular page of the website, either in the "About Flex" or "Community"
section (your call).
Can you grant me a (temporary) write access to the website? Where should I put this new page?
Franck.
2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>:
> HI,
>
> > Any chance to get this page published anytime soon (with Andrew's
> > modifications applied)?
>
> You don't have to be a committer to make wiki edits changes/ just ask
> for wiki access put the file there yourself may be the quickest way.
>
> Thanks,
> Justin
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Thanks Justin.
I don't think it should be just a Wiki page. In my mind, it should rather
be a regular page of the website, either in the "About Flex" or "Community"
section (your call).
Can you grant me a (temporary) write access to the website? Where should I
put this new page?
Franck.
2014-03-31 13:53 GMT+02:00 Justin Mclean <ju...@classsoftware.com>:
> HI,
>
> > Any chance to get this page published anytime soon (with Andrew's
> > modifications applied)?
>
> You don't have to be a committer to make wiki edits changes/ just ask for
> wiki access put the file there yourself may be the quickest way.
>
> Thanks,
> Justin
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Justin Mclean <ju...@classsoftware.com>.
HI,
> Any chance to get this page published anytime soon (with Andrew's
> modifications applied)?
You don't have to be a committer to make wiki edits changes/ just ask for wiki access put the file there yourself may be the quickest way.
Thanks,
Justin
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Any chance to get this page published anytime soon (with Andrew's
modifications applied)?
Tell me how I can help.
Franck.
2014-03-26 17:26 GMT+01:00 Alex Harui <ah...@adobe.com>:
> Ended up in spam because of the zip attachment. Will try to look later.
>
> On 3/26/14 2:06 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>
> >Anyone?
> >
> >
> >2014-03-25 15:03 GMT+01:00 Franck Wolff <fr...@gmail.com>:
> >
> >> Hi,
> >>
> >> Here is the page about third-party tools and solutions (I don't know if
> >> attached files are accepted on this mailing list, tell me).
> >>
> >> I didn't try to create any comparison table, the projects listed having
> >> very different scope / kind of features. Each project / tool is listed
> >>with
> >> a link and a pitch which comes from their respective websites. Many of
> >>them
> >> are outdated and inactive, many of them are certainly not compliant with
> >> the Apache trademark policy.
> >>
> >> I have modified a page coming from the Apache Flex website and
> >>integration
> >> should be straightforward.
> >>
> >> Franck.
> >>
> >>
> >>
> >> 2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
> >>
> >>
> >>> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
> >>>
> >>>
> >>>>
> >>>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
> >>>>
> >>>> >I can certainly make sure that GraniteDS website is linking back to
> >>>> Apache
> >>>> >Flex (we already do that) and following the Apache trademark policy
> >>>>(if
> >>>> I
> >>>> >understand what it is about ;)
> >>>> Sounds great. Let us know when you think you've conformed to the
> >>>>policy
> >>>> and the Apache Flex PMC will review and make suggestions if needed.
> >>>>And
> >>>> feel free to ask questions on the dev@ list if you're unsure of how
> to
> >>>> implement the policy.
> >>>>
> >>>
> >>> I think we already comply with the policy: we refer to either "Flex" or
> >>> "Apache Flex" on our website and we link to http://flex.apache.org/ on
> >>> our main pages. You can certainly find "Adobe Flex" in some of our old
> >>>blog
> >>> posts and documentations. I have added a notice about "Apache", "Apache
> >>> Flex" and "Flex" trademarks at the bottom of our site terms &
> >>>conditions (
> >>>
> >>>
> http://www.granitedataservices.com/contact-us/site-terms-and-conditions-
> >>>of-use/).
> >>> We also have the full Apache 2 License in our distrib
> >>> (licenses/third-party/).
> >>>
> >>> BTW, according to this page:
> >>>http://www.apache.org/foundation/marks/list/,
> >>> Flex isn't listed as a trademark of Apache but just as a project...
> >>>
> >>> Anyway, I would be happy if somebody from the Apache Flex PMC can have
> >>>a
> >>> look at our website and make sure we are not infringing any Apache
> >>>policy.
> >>>
> >>>
> >>> >
> >>>> >However, I can't verify that all related projects are complying to
> >>>>your
> >>>> >request and I'm certainly not the right person to ask them to do
> >>>>so...
> >>>> Right, that's the job of the PMC. We should ask each technology owner
> >>>> that is going to be in the list to conform before we actually put
> >>>>them in
> >>>> the list (assuming they are still active).
> >>>>
> >>>
> >>> I will put everything I know related to Flex in the draft, you are free
> >>> to remove those who don't comply with the policy.
> >>>
> >>> Thanks,
> >>> Franck.
> >>>
> >>>
> >>>>
> >>>> -Alex
> >>>>
> >>>>
> >>>
> >>
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Any chance to get this page published anytime soon (with Andrew's
modifications applied)?
Tell me how I can help.
Franck.
2014-03-26 17:26 GMT+01:00 Alex Harui <ah...@adobe.com>:
> Ended up in spam because of the zip attachment. Will try to look later.
>
> On 3/26/14 2:06 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>
> >Anyone?
> >
> >
> >2014-03-25 15:03 GMT+01:00 Franck Wolff <fr...@gmail.com>:
> >
> >> Hi,
> >>
> >> Here is the page about third-party tools and solutions (I don't know if
> >> attached files are accepted on this mailing list, tell me).
> >>
> >> I didn't try to create any comparison table, the projects listed having
> >> very different scope / kind of features. Each project / tool is listed
> >>with
> >> a link and a pitch which comes from their respective websites. Many of
> >>them
> >> are outdated and inactive, many of them are certainly not compliant with
> >> the Apache trademark policy.
> >>
> >> I have modified a page coming from the Apache Flex website and
> >>integration
> >> should be straightforward.
> >>
> >> Franck.
> >>
> >>
> >>
> >> 2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
> >>
> >>
> >>> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
> >>>
> >>>
> >>>>
> >>>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
> >>>>
> >>>> >I can certainly make sure that GraniteDS website is linking back to
> >>>> Apache
> >>>> >Flex (we already do that) and following the Apache trademark policy
> >>>>(if
> >>>> I
> >>>> >understand what it is about ;)
> >>>> Sounds great. Let us know when you think you've conformed to the
> >>>>policy
> >>>> and the Apache Flex PMC will review and make suggestions if needed.
> >>>>And
> >>>> feel free to ask questions on the dev@ list if you're unsure of how
> to
> >>>> implement the policy.
> >>>>
> >>>
> >>> I think we already comply with the policy: we refer to either "Flex" or
> >>> "Apache Flex" on our website and we link to http://flex.apache.org/ on
> >>> our main pages. You can certainly find "Adobe Flex" in some of our old
> >>>blog
> >>> posts and documentations. I have added a notice about "Apache", "Apache
> >>> Flex" and "Flex" trademarks at the bottom of our site terms &
> >>>conditions (
> >>>
> >>>
> http://www.granitedataservices.com/contact-us/site-terms-and-conditions-
> >>>of-use/).
> >>> We also have the full Apache 2 License in our distrib
> >>> (licenses/third-party/).
> >>>
> >>> BTW, according to this page:
> >>>http://www.apache.org/foundation/marks/list/,
> >>> Flex isn't listed as a trademark of Apache but just as a project...
> >>>
> >>> Anyway, I would be happy if somebody from the Apache Flex PMC can have
> >>>a
> >>> look at our website and make sure we are not infringing any Apache
> >>>policy.
> >>>
> >>>
> >>> >
> >>>> >However, I can't verify that all related projects are complying to
> >>>>your
> >>>> >request and I'm certainly not the right person to ask them to do
> >>>>so...
> >>>> Right, that's the job of the PMC. We should ask each technology owner
> >>>> that is going to be in the list to conform before we actually put
> >>>>them in
> >>>> the list (assuming they are still active).
> >>>>
> >>>
> >>> I will put everything I know related to Flex in the draft, you are free
> >>> to remove those who don't comply with the policy.
> >>>
> >>> Thanks,
> >>> Franck.
> >>>
> >>>
> >>>>
> >>>> -Alex
> >>>>
> >>>>
> >>>
> >>
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
Ended up in spam because of the zip attachment. Will try to look later.
On 3/26/14 2:06 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>Anyone?
>
>
>2014-03-25 15:03 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>
>> Hi,
>>
>> Here is the page about third-party tools and solutions (I don't know if
>> attached files are accepted on this mailing list, tell me).
>>
>> I didn't try to create any comparison table, the projects listed having
>> very different scope / kind of features. Each project / tool is listed
>>with
>> a link and a pitch which comes from their respective websites. Many of
>>them
>> are outdated and inactive, many of them are certainly not compliant with
>> the Apache trademark policy.
>>
>> I have modified a page coming from the Apache Flex website and
>>integration
>> should be straightforward.
>>
>> Franck.
>>
>>
>>
>> 2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>>
>>
>>> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
>>>
>>>
>>>>
>>>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>>>>
>>>> >I can certainly make sure that GraniteDS website is linking back to
>>>> Apache
>>>> >Flex (we already do that) and following the Apache trademark policy
>>>>(if
>>>> I
>>>> >understand what it is about ;)
>>>> Sounds great. Let us know when you think you've conformed to the
>>>>policy
>>>> and the Apache Flex PMC will review and make suggestions if needed.
>>>>And
>>>> feel free to ask questions on the dev@ list if you're unsure of how to
>>>> implement the policy.
>>>>
>>>
>>> I think we already comply with the policy: we refer to either "Flex" or
>>> "Apache Flex" on our website and we link to http://flex.apache.org/ on
>>> our main pages. You can certainly find "Adobe Flex" in some of our old
>>>blog
>>> posts and documentations. I have added a notice about "Apache", "Apache
>>> Flex" and "Flex" trademarks at the bottom of our site terms &
>>>conditions (
>>>
>>>http://www.granitedataservices.com/contact-us/site-terms-and-conditions-
>>>of-use/).
>>> We also have the full Apache 2 License in our distrib
>>> (licenses/third-party/).
>>>
>>> BTW, according to this page:
>>>http://www.apache.org/foundation/marks/list/,
>>> Flex isn't listed as a trademark of Apache but just as a project...
>>>
>>> Anyway, I would be happy if somebody from the Apache Flex PMC can have
>>>a
>>> look at our website and make sure we are not infringing any Apache
>>>policy.
>>>
>>>
>>> >
>>>> >However, I can't verify that all related projects are complying to
>>>>your
>>>> >request and I'm certainly not the right person to ask them to do
>>>>so...
>>>> Right, that's the job of the PMC. We should ask each technology owner
>>>> that is going to be in the list to conform before we actually put
>>>>them in
>>>> the list (assuming they are still active).
>>>>
>>>
>>> I will put everything I know related to Flex in the draft, you are free
>>> to remove those who don't comply with the policy.
>>>
>>> Thanks,
>>> Franck.
>>>
>>>
>>>>
>>>> -Alex
>>>>
>>>>
>>>
>>
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
Ended up in spam because of the zip attachment. Will try to look later.
On 3/26/14 2:06 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>Anyone?
>
>
>2014-03-25 15:03 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>
>> Hi,
>>
>> Here is the page about third-party tools and solutions (I don't know if
>> attached files are accepted on this mailing list, tell me).
>>
>> I didn't try to create any comparison table, the projects listed having
>> very different scope / kind of features. Each project / tool is listed
>>with
>> a link and a pitch which comes from their respective websites. Many of
>>them
>> are outdated and inactive, many of them are certainly not compliant with
>> the Apache trademark policy.
>>
>> I have modified a page coming from the Apache Flex website and
>>integration
>> should be straightforward.
>>
>> Franck.
>>
>>
>>
>> 2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>>
>>
>>> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
>>>
>>>
>>>>
>>>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>>>>
>>>> >I can certainly make sure that GraniteDS website is linking back to
>>>> Apache
>>>> >Flex (we already do that) and following the Apache trademark policy
>>>>(if
>>>> I
>>>> >understand what it is about ;)
>>>> Sounds great. Let us know when you think you've conformed to the
>>>>policy
>>>> and the Apache Flex PMC will review and make suggestions if needed.
>>>>And
>>>> feel free to ask questions on the dev@ list if you're unsure of how to
>>>> implement the policy.
>>>>
>>>
>>> I think we already comply with the policy: we refer to either "Flex" or
>>> "Apache Flex" on our website and we link to http://flex.apache.org/ on
>>> our main pages. You can certainly find "Adobe Flex" in some of our old
>>>blog
>>> posts and documentations. I have added a notice about "Apache", "Apache
>>> Flex" and "Flex" trademarks at the bottom of our site terms &
>>>conditions (
>>>
>>>http://www.granitedataservices.com/contact-us/site-terms-and-conditions-
>>>of-use/).
>>> We also have the full Apache 2 License in our distrib
>>> (licenses/third-party/).
>>>
>>> BTW, according to this page:
>>>http://www.apache.org/foundation/marks/list/,
>>> Flex isn't listed as a trademark of Apache but just as a project...
>>>
>>> Anyway, I would be happy if somebody from the Apache Flex PMC can have
>>>a
>>> look at our website and make sure we are not infringing any Apache
>>>policy.
>>>
>>>
>>> >
>>>> >However, I can't verify that all related projects are complying to
>>>>your
>>>> >request and I'm certainly not the right person to ask them to do
>>>>so...
>>>> Right, that's the job of the PMC. We should ask each technology owner
>>>> that is going to be in the list to conform before we actually put
>>>>them in
>>>> the list (assuming they are still active).
>>>>
>>>
>>> I will put everything I know related to Flex in the draft, you are free
>>> to remove those who don't comply with the policy.
>>>
>>> Thanks,
>>> Franck.
>>>
>>>
>>>>
>>>> -Alex
>>>>
>>>>
>>>
>>
Re: Third-party tools / solutions on Apache Flex website
Posted by Andrew Wetmore <co...@gmail.com>.
This is very useful. I do have some small text notes:
- "Adobe® Flash® Builder® 4.7 software is a development environment..."
Don't need the word "software"
- Is it "Haxe" or "haXe"? Should be consistent
- for Cairngorm, this direct quote sounds like Apache Flex is certifying
the framework in some special way: "... but dependent on core principles we
believe are crucial to follow when developing enterprise RIAs." Should be
trimmed to "... but dependent on core principles crucial to follow when
developing enterprise RIAs."
- I would recommend cutting the whole first sentence about WebOrb, as it
is really the mission statement for Midnight Coders.
a
On Wed, Mar 26, 2014 at 6:06 AM, Franck Wolff <fr...@gmail.com> wrote:
> Anyone?
>
>
> 2014-03-25 15:03 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>
> > Hi,
> >
> > Here is the page about third-party tools and solutions (I don't know if
> > attached files are accepted on this mailing list, tell me).
> >
> > I didn't try to create any comparison table, the projects listed having
> > very different scope / kind of features. Each project / tool is listed
> with
> > a link and a pitch which comes from their respective websites. Many of
> them
> > are outdated and inactive, many of them are certainly not compliant with
> > the Apache trademark policy.
> >
> > I have modified a page coming from the Apache Flex website and
> integration
> > should be straightforward.
> >
> > Franck.
> >
> >
> >
> > 2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
> >
> >
> >> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
> >>
> >>
> >>>
> >>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
> >>>
> >>> >I can certainly make sure that GraniteDS website is linking back to
> >>> Apache
> >>> >Flex (we already do that) and following the Apache trademark policy
> (if
> >>> I
> >>> >understand what it is about ;)
> >>> Sounds great. Let us know when you think you've conformed to the
> policy
> >>> and the Apache Flex PMC will review and make suggestions if needed.
> And
> >>> feel free to ask questions on the dev@ list if you're unsure of how to
> >>> implement the policy.
> >>>
> >>
> >> I think we already comply with the policy: we refer to either "Flex" or
> >> "Apache Flex" on our website and we link to http://flex.apache.org/ on
> >> our main pages. You can certainly find "Adobe Flex" in some of our old
> blog
> >> posts and documentations. I have added a notice about "Apache", "Apache
> >> Flex" and "Flex" trademarks at the bottom of our site terms &
> conditions (
> >>
> http://www.granitedataservices.com/contact-us/site-terms-and-conditions-of-use/
> ).
> >> We also have the full Apache 2 License in our distrib
> >> (licenses/third-party/).
> >>
> >> BTW, according to this page:
> http://www.apache.org/foundation/marks/list/,
> >> Flex isn't listed as a trademark of Apache but just as a project...
> >>
> >> Anyway, I would be happy if somebody from the Apache Flex PMC can have a
> >> look at our website and make sure we are not infringing any Apache
> policy.
> >>
> >>
> >> >
> >>> >However, I can't verify that all related projects are complying to
> your
> >>> >request and I'm certainly not the right person to ask them to do so...
> >>> Right, that's the job of the PMC. We should ask each technology owner
> >>> that is going to be in the list to conform before we actually put them
> in
> >>> the list (assuming they are still active).
> >>>
> >>
> >> I will put everything I know related to Flex in the draft, you are free
> >> to remove those who don't comply with the policy.
> >>
> >> Thanks,
> >> Franck.
> >>
> >>
> >>>
> >>> -Alex
> >>>
> >>>
> >>
> >
>
--
Andrew Wetmore
http://cottage14.blogspot.com/
http://portfolio.cottage14.com
https://sites.google.com/site/mvplaywrights/home
Re: Third-party tools / solutions on Apache Flex website
Posted by Andrew Wetmore <co...@gmail.com>.
This is very useful. I do have some small text notes:
- "Adobe® Flash® Builder® 4.7 software is a development environment..."
Don't need the word "software"
- Is it "Haxe" or "haXe"? Should be consistent
- for Cairngorm, this direct quote sounds like Apache Flex is certifying
the framework in some special way: "... but dependent on core principles we
believe are crucial to follow when developing enterprise RIAs." Should be
trimmed to "... but dependent on core principles crucial to follow when
developing enterprise RIAs."
- I would recommend cutting the whole first sentence about WebOrb, as it
is really the mission statement for Midnight Coders.
a
On Wed, Mar 26, 2014 at 6:06 AM, Franck Wolff <fr...@gmail.com> wrote:
> Anyone?
>
>
> 2014-03-25 15:03 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>
> > Hi,
> >
> > Here is the page about third-party tools and solutions (I don't know if
> > attached files are accepted on this mailing list, tell me).
> >
> > I didn't try to create any comparison table, the projects listed having
> > very different scope / kind of features. Each project / tool is listed
> with
> > a link and a pitch which comes from their respective websites. Many of
> them
> > are outdated and inactive, many of them are certainly not compliant with
> > the Apache trademark policy.
> >
> > I have modified a page coming from the Apache Flex website and
> integration
> > should be straightforward.
> >
> > Franck.
> >
> >
> >
> > 2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
> >
> >
> >> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
> >>
> >>
> >>>
> >>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
> >>>
> >>> >I can certainly make sure that GraniteDS website is linking back to
> >>> Apache
> >>> >Flex (we already do that) and following the Apache trademark policy
> (if
> >>> I
> >>> >understand what it is about ;)
> >>> Sounds great. Let us know when you think you've conformed to the
> policy
> >>> and the Apache Flex PMC will review and make suggestions if needed.
> And
> >>> feel free to ask questions on the dev@ list if you're unsure of how to
> >>> implement the policy.
> >>>
> >>
> >> I think we already comply with the policy: we refer to either "Flex" or
> >> "Apache Flex" on our website and we link to http://flex.apache.org/ on
> >> our main pages. You can certainly find "Adobe Flex" in some of our old
> blog
> >> posts and documentations. I have added a notice about "Apache", "Apache
> >> Flex" and "Flex" trademarks at the bottom of our site terms &
> conditions (
> >>
> http://www.granitedataservices.com/contact-us/site-terms-and-conditions-of-use/
> ).
> >> We also have the full Apache 2 License in our distrib
> >> (licenses/third-party/).
> >>
> >> BTW, according to this page:
> http://www.apache.org/foundation/marks/list/,
> >> Flex isn't listed as a trademark of Apache but just as a project...
> >>
> >> Anyway, I would be happy if somebody from the Apache Flex PMC can have a
> >> look at our website and make sure we are not infringing any Apache
> policy.
> >>
> >>
> >> >
> >>> >However, I can't verify that all related projects are complying to
> your
> >>> >request and I'm certainly not the right person to ask them to do so...
> >>> Right, that's the job of the PMC. We should ask each technology owner
> >>> that is going to be in the list to conform before we actually put them
> in
> >>> the list (assuming they are still active).
> >>>
> >>
> >> I will put everything I know related to Flex in the draft, you are free
> >> to remove those who don't comply with the policy.
> >>
> >> Thanks,
> >> Franck.
> >>
> >>
> >>>
> >>> -Alex
> >>>
> >>>
> >>
> >
>
--
Andrew Wetmore
http://cottage14.blogspot.com/
http://portfolio.cottage14.com
https://sites.google.com/site/mvplaywrights/home
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Anyone?
2014-03-25 15:03 GMT+01:00 Franck Wolff <fr...@gmail.com>:
> Hi,
>
> Here is the page about third-party tools and solutions (I don't know if
> attached files are accepted on this mailing list, tell me).
>
> I didn't try to create any comparison table, the projects listed having
> very different scope / kind of features. Each project / tool is listed with
> a link and a pitch which comes from their respective websites. Many of them
> are outdated and inactive, many of them are certainly not compliant with
> the Apache trademark policy.
>
> I have modified a page coming from the Apache Flex website and integration
> should be straightforward.
>
> Franck.
>
>
>
> 2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>
>
>> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
>>
>>
>>>
>>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>>>
>>> >I can certainly make sure that GraniteDS website is linking back to
>>> Apache
>>> >Flex (we already do that) and following the Apache trademark policy (if
>>> I
>>> >understand what it is about ;)
>>> Sounds great. Let us know when you think you've conformed to the policy
>>> and the Apache Flex PMC will review and make suggestions if needed. And
>>> feel free to ask questions on the dev@ list if you're unsure of how to
>>> implement the policy.
>>>
>>
>> I think we already comply with the policy: we refer to either "Flex" or
>> "Apache Flex" on our website and we link to http://flex.apache.org/ on
>> our main pages. You can certainly find "Adobe Flex" in some of our old blog
>> posts and documentations. I have added a notice about "Apache", "Apache
>> Flex" and "Flex" trademarks at the bottom of our site terms & conditions (
>> http://www.granitedataservices.com/contact-us/site-terms-and-conditions-of-use/).
>> We also have the full Apache 2 License in our distrib
>> (licenses/third-party/).
>>
>> BTW, according to this page: http://www.apache.org/foundation/marks/list/,
>> Flex isn't listed as a trademark of Apache but just as a project...
>>
>> Anyway, I would be happy if somebody from the Apache Flex PMC can have a
>> look at our website and make sure we are not infringing any Apache policy.
>>
>>
>> >
>>> >However, I can't verify that all related projects are complying to your
>>> >request and I'm certainly not the right person to ask them to do so...
>>> Right, that's the job of the PMC. We should ask each technology owner
>>> that is going to be in the list to conform before we actually put them in
>>> the list (assuming they are still active).
>>>
>>
>> I will put everything I know related to Flex in the draft, you are free
>> to remove those who don't comply with the policy.
>>
>> Thanks,
>> Franck.
>>
>>
>>>
>>> -Alex
>>>
>>>
>>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Anyone?
2014-03-25 15:03 GMT+01:00 Franck Wolff <fr...@gmail.com>:
> Hi,
>
> Here is the page about third-party tools and solutions (I don't know if
> attached files are accepted on this mailing list, tell me).
>
> I didn't try to create any comparison table, the projects listed having
> very different scope / kind of features. Each project / tool is listed with
> a link and a pitch which comes from their respective websites. Many of them
> are outdated and inactive, many of them are certainly not compliant with
> the Apache trademark policy.
>
> I have modified a page coming from the Apache Flex website and integration
> should be straightforward.
>
> Franck.
>
>
>
> 2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>
>
>> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
>>
>>
>>>
>>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>>>
>>> >I can certainly make sure that GraniteDS website is linking back to
>>> Apache
>>> >Flex (we already do that) and following the Apache trademark policy (if
>>> I
>>> >understand what it is about ;)
>>> Sounds great. Let us know when you think you've conformed to the policy
>>> and the Apache Flex PMC will review and make suggestions if needed. And
>>> feel free to ask questions on the dev@ list if you're unsure of how to
>>> implement the policy.
>>>
>>
>> I think we already comply with the policy: we refer to either "Flex" or
>> "Apache Flex" on our website and we link to http://flex.apache.org/ on
>> our main pages. You can certainly find "Adobe Flex" in some of our old blog
>> posts and documentations. I have added a notice about "Apache", "Apache
>> Flex" and "Flex" trademarks at the bottom of our site terms & conditions (
>> http://www.granitedataservices.com/contact-us/site-terms-and-conditions-of-use/).
>> We also have the full Apache 2 License in our distrib
>> (licenses/third-party/).
>>
>> BTW, according to this page: http://www.apache.org/foundation/marks/list/,
>> Flex isn't listed as a trademark of Apache but just as a project...
>>
>> Anyway, I would be happy if somebody from the Apache Flex PMC can have a
>> look at our website and make sure we are not infringing any Apache policy.
>>
>>
>> >
>>> >However, I can't verify that all related projects are complying to your
>>> >request and I'm certainly not the right person to ask them to do so...
>>> Right, that's the job of the PMC. We should ask each technology owner
>>> that is going to be in the list to conform before we actually put them in
>>> the list (assuming they are still active).
>>>
>>
>> I will put everything I know related to Flex in the draft, you are free
>> to remove those who don't comply with the policy.
>>
>> Thanks,
>> Franck.
>>
>>
>>>
>>> -Alex
>>>
>>>
>>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Hi,
Here is the page about third-party tools and solutions (I don't know if
attached files are accepted on this mailing list, tell me).
I didn't try to create any comparison table, the projects listed having
very different scope / kind of features. Each project / tool is listed with
a link and a pitch which comes from their respective websites. Many of them
are outdated and inactive, many of them are certainly not compliant with
the Apache trademark policy.
I have modified a page coming from the Apache Flex website and integration
should be straightforward.
Franck.
2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>
> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
>
>
>>
>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>>
>> >I can certainly make sure that GraniteDS website is linking back to
>> Apache
>> >Flex (we already do that) and following the Apache trademark policy (if I
>> >understand what it is about ;)
>> Sounds great. Let us know when you think you've conformed to the policy
>> and the Apache Flex PMC will review and make suggestions if needed. And
>> feel free to ask questions on the dev@ list if you're unsure of how to
>> implement the policy.
>>
>
> I think we already comply with the policy: we refer to either "Flex" or
> "Apache Flex" on our website and we link to http://flex.apache.org/ on
> our main pages. You can certainly find "Adobe Flex" in some of our old blog
> posts and documentations. I have added a notice about "Apache", "Apache
> Flex" and "Flex" trademarks at the bottom of our site terms & conditions (
> http://www.granitedataservices.com/contact-us/site-terms-and-conditions-of-use/).
> We also have the full Apache 2 License in our distrib
> (licenses/third-party/).
>
> BTW, according to this page: http://www.apache.org/foundation/marks/list/,
> Flex isn't listed as a trademark of Apache but just as a project...
>
> Anyway, I would be happy if somebody from the Apache Flex PMC can have a
> look at our website and make sure we are not infringing any Apache policy.
>
>
> >
>> >However, I can't verify that all related projects are complying to your
>> >request and I'm certainly not the right person to ask them to do so...
>> Right, that's the job of the PMC. We should ask each technology owner
>> that is going to be in the list to conform before we actually put them in
>> the list (assuming they are still active).
>>
>
> I will put everything I know related to Flex in the draft, you are free to
> remove those who don't comply with the policy.
>
> Thanks,
> Franck.
>
>
>>
>> -Alex
>>
>>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Hi,
Here is the page about third-party tools and solutions (I don't know if
attached files are accepted on this mailing list, tell me).
I didn't try to create any comparison table, the projects listed having
very different scope / kind of features. Each project / tool is listed with
a link and a pitch which comes from their respective websites. Many of them
are outdated and inactive, many of them are certainly not compliant with
the Apache trademark policy.
I have modified a page coming from the Apache Flex website and integration
should be straightforward.
Franck.
2014-03-21 14:28 GMT+01:00 Franck Wolff <fr...@gmail.com>:
>
> 2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
>
>
>>
>> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>>
>> >I can certainly make sure that GraniteDS website is linking back to
>> Apache
>> >Flex (we already do that) and following the Apache trademark policy (if I
>> >understand what it is about ;)
>> Sounds great. Let us know when you think you've conformed to the policy
>> and the Apache Flex PMC will review and make suggestions if needed. And
>> feel free to ask questions on the dev@ list if you're unsure of how to
>> implement the policy.
>>
>
> I think we already comply with the policy: we refer to either "Flex" or
> "Apache Flex" on our website and we link to http://flex.apache.org/ on
> our main pages. You can certainly find "Adobe Flex" in some of our old blog
> posts and documentations. I have added a notice about "Apache", "Apache
> Flex" and "Flex" trademarks at the bottom of our site terms & conditions (
> http://www.granitedataservices.com/contact-us/site-terms-and-conditions-of-use/).
> We also have the full Apache 2 License in our distrib
> (licenses/third-party/).
>
> BTW, according to this page: http://www.apache.org/foundation/marks/list/,
> Flex isn't listed as a trademark of Apache but just as a project...
>
> Anyway, I would be happy if somebody from the Apache Flex PMC can have a
> look at our website and make sure we are not infringing any Apache policy.
>
>
> >
>> >However, I can't verify that all related projects are complying to your
>> >request and I'm certainly not the right person to ask them to do so...
>> Right, that's the job of the PMC. We should ask each technology owner
>> that is going to be in the list to conform before we actually put them in
>> the list (assuming they are still active).
>>
>
> I will put everything I know related to Flex in the draft, you are free to
> remove those who don't comply with the policy.
>
> Thanks,
> Franck.
>
>
>>
>> -Alex
>>
>>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
>
>
> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>
> >I can certainly make sure that GraniteDS website is linking back to Apache
> >Flex (we already do that) and following the Apache trademark policy (if I
> >understand what it is about ;)
> Sounds great. Let us know when you think you've conformed to the policy
> and the Apache Flex PMC will review and make suggestions if needed. And
> feel free to ask questions on the dev@ list if you're unsure of how to
> implement the policy.
>
I think we already comply with the policy: we refer to either "Flex" or
"Apache Flex" on our website and we link to http://flex.apache.org/ on our
main pages. You can certainly find "Adobe Flex" in some of our old blog
posts and documentations. I have added a notice about "Apache", "Apache
Flex" and "Flex" trademarks at the bottom of our site terms & conditions (
http://www.granitedataservices.com/contact-us/site-terms-and-conditions-of-use/).
We also have the full Apache 2 License in our distrib
(licenses/third-party/).
BTW, according to this page: http://www.apache.org/foundation/marks/list/,
Flex isn't listed as a trademark of Apache but just as a project...
Anyway, I would be happy if somebody from the Apache Flex PMC can have a
look at our website and make sure we are not infringing any Apache policy.
>
> >However, I can't verify that all related projects are complying to your
> >request and I'm certainly not the right person to ask them to do so...
> Right, that's the job of the PMC. We should ask each technology owner
> that is going to be in the list to conform before we actually put them in
> the list (assuming they are still active).
>
I will put everything I know related to Flex in the draft, you are free to
remove those who don't comply with the policy.
Thanks,
Franck.
>
> -Alex
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
2014-03-20 19:16 GMT+01:00 Alex Harui <ah...@adobe.com>:
>
>
> On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>
> >I can certainly make sure that GraniteDS website is linking back to Apache
> >Flex (we already do that) and following the Apache trademark policy (if I
> >understand what it is about ;)
> Sounds great. Let us know when you think you've conformed to the policy
> and the Apache Flex PMC will review and make suggestions if needed. And
> feel free to ask questions on the dev@ list if you're unsure of how to
> implement the policy.
>
I think we already comply with the policy: we refer to either "Flex" or
"Apache Flex" on our website and we link to http://flex.apache.org/ on our
main pages. You can certainly find "Adobe Flex" in some of our old blog
posts and documentations. I have added a notice about "Apache", "Apache
Flex" and "Flex" trademarks at the bottom of our site terms & conditions (
http://www.granitedataservices.com/contact-us/site-terms-and-conditions-of-use/).
We also have the full Apache 2 License in our distrib
(licenses/third-party/).
BTW, according to this page: http://www.apache.org/foundation/marks/list/,
Flex isn't listed as a trademark of Apache but just as a project...
Anyway, I would be happy if somebody from the Apache Flex PMC can have a
look at our website and make sure we are not infringing any Apache policy.
>
> >However, I can't verify that all related projects are complying to your
> >request and I'm certainly not the right person to ask them to do so...
> Right, that's the job of the PMC. We should ask each technology owner
> that is going to be in the list to conform before we actually put them in
> the list (assuming they are still active).
>
I will put everything I know related to Flex in the draft, you are free to
remove those who don't comply with the policy.
Thanks,
Franck.
>
> -Alex
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>I can certainly make sure that GraniteDS website is linking back to Apache
>Flex (we already do that) and following the Apache trademark policy (if I
>understand what it is about ;)
Sounds great. Let us know when you think you've conformed to the policy
and the Apache Flex PMC will review and make suggestions if needed. And
feel free to ask questions on the dev@ list if you're unsure of how to
implement the policy.
>
>However, I can't verify that all related projects are complying to your
>request and I'm certainly not the right person to ask them to do so...
Right, that's the job of the PMC. We should ask each technology owner
that is going to be in the list to conform before we actually put them in
the list (assuming they are still active).
-Alex
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
On 3/20/14 9:54 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>I can certainly make sure that GraniteDS website is linking back to Apache
>Flex (we already do that) and following the Apache trademark policy (if I
>understand what it is about ;)
Sounds great. Let us know when you think you've conformed to the policy
and the Apache Flex PMC will review and make suggestions if needed. And
feel free to ask questions on the dev@ list if you're unsure of how to
implement the policy.
>
>However, I can't verify that all related projects are complying to your
>request and I'm certainly not the right person to ask them to do so...
Right, that's the job of the PMC. We should ask each technology owner
that is going to be in the list to conform before we actually put them in
the list (assuming they are still active).
-Alex
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
2014-03-20 17:03 GMT+01:00 Alex Harui <ah...@adobe.com>:
>
>
> On 3/20/14 8:37 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>
> >3) Not sure to understand what you mean here... Do you want to make sure
> >that nobody is mentioning "Adobe Flex" anymore?
> No, you can still mention "Adobe Flex", but it is important that your web
> site use the Flex trademark correctly as per
> http://www.apache.org/foundation/marks/ and help to notify that world that
> Flex is now at Apache.
>
> Adobe did not care as much about proper use of the Flex trademark, but the
> Apache does.
>
I can certainly make sure that GraniteDS website is linking back to Apache
Flex (we already do that) and following the Apache trademark policy (if I
understand what it is about ;)
However, I can't verify that all related projects are complying to your
request and I'm certainly not the right person to ask them to do so...
I should have a first draft next week.
Thanks,
Franck.
>
> -Alex
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
2014-03-20 17:03 GMT+01:00 Alex Harui <ah...@adobe.com>:
>
>
> On 3/20/14 8:37 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>
> >3) Not sure to understand what you mean here... Do you want to make sure
> >that nobody is mentioning "Adobe Flex" anymore?
> No, you can still mention "Adobe Flex", but it is important that your web
> site use the Flex trademark correctly as per
> http://www.apache.org/foundation/marks/ and help to notify that world that
> Flex is now at Apache.
>
> Adobe did not care as much about proper use of the Flex trademark, but the
> Apache does.
>
I can certainly make sure that GraniteDS website is linking back to Apache
Flex (we already do that) and following the Apache trademark policy (if I
understand what it is about ;)
However, I can't verify that all related projects are complying to your
request and I'm certainly not the right person to ask them to do so...
I should have a first draft next week.
Thanks,
Franck.
>
> -Alex
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
On 3/20/14 8:37 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>3) Not sure to understand what you mean here... Do you want to make sure
>that nobody is mentioning "Adobe Flex" anymore?
No, you can still mention "Adobe Flex", but it is important that your web
site use the Flex trademark correctly as per
http://www.apache.org/foundation/marks/ and help to notify that world that
Flex is now at Apache.
Adobe did not care as much about proper use of the Flex trademark, but the
Apache does.
-Alex
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
On 3/20/14 8:37 AM, "Franck Wolff" <fr...@gmail.com> wrote:
>3) Not sure to understand what you mean here... Do you want to make sure
>that nobody is mentioning "Adobe Flex" anymore?
No, you can still mention "Adobe Flex", but it is important that your web
site use the Flex trademark correctly as per
http://www.apache.org/foundation/marks/ and help to notify that world that
Flex is now at Apache.
Adobe did not care as much about proper use of the Flex trademark, but the
Apache does.
-Alex
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Thank you all for your positive feedback!
I can certainly put together a first draft and post it here.
About Alex's questions:
1) A-Z is ok (as unfair as at school, but nobody can really complain about
it).
2) Sure as well.
3) Not sure to understand what you mean here... Do you want to make sure
that nobody is mentioning "Adobe Flex" anymore?
Cheers,
Franck.
2014-03-20 15:42 GMT+01:00 Maurice Amsellem <ma...@systar.com>:
> 1) In what order should these links appear?
> A-Z ?
>
> 2) sure.
>
> 3)
> >domain name policy :
> OK . (rule apply to all active sites, not only the ones in the list,
> right?)
>
> >"Apache Flex" is mentioned with the appropriate pointers to the ASF
> Only if the site or product also points back to flex.a.o.
> If the link is from Apache Flex to the site, it does not have to.
> Correct ?
>
> Maurice
>
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com]
> Envoyé : jeudi 20 mars 2014 15:16
> À : dev@flex.apache.org; users@flex.apache.org
> Objet : Re: Third-party tools / solutions on Apache Flex website
>
> I'm in favor of a list as well.
>
> A few complicating factors (never as simple as one would hope).
>
> 1) In what order should these links appear? Should we give preference to
> technology that donates money to Apache? That is open-source? That is
> under active development?
>
> 2) I think we'll have to go through an exercise of working out the wording
> for this page to make sure that we know the list isn't comprehensive and
> doesn't promote a particular technology.
>
> 3) I think we'll have to ask that anything listed that is under active
> development or active marketing will have to have their web site comply
> with the domain name policy and make sure that "Apache Flex" is mentioned
> with the appropriate pointers to the ASF.
>
> -Alex
>
> On 3/20/14 6:41 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >ActiveMQ is a middleware, so it's rather obvious to have a connectivity
> >section.
> >However, having a section in the website about Apache Flex "Ecosystem"
> >(MVC frameworks, Back-ends, IDEs, etc...) seems an excellent idea to me.
> >
> >I don't think you can contribute directly on the web site, because it
> >requires an svn account, but you are more than welcome to contribute to
> >the content.
> >I think a simple way of doing that is to create a JIRA ticket to
> >support your initiative and provide content as attached files (HTML
> >files are
> >fine)
> >The web site is using a CMS Management system inspired from Django, but
> >we can rather easily convert HTML content if you provide it.
> >
> >Make a first draft of your content and submit it, so we can see how it
> >integrates to the site, and then you can polish / complete it.
> >
> >Thank you again for your offer to help...
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Gary Yang [mailto:flashflexpro@gmail.com] Envoyé : jeudi 20 mars
> >2014 14:28 À : dev@flex.apache.org Objet : Re: Third-party tools /
> >solutions on Apache Flex website
> >
> >Franck, I can not agree more! -Gary
> >
> >
> >On Thu, Mar 20, 2014 at 8:33 AM, Franck Wolff <fr...@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> I'm wondering why there is no section about Flex related server
> >> solutions such as BlazeDS, AMFPHP, FluorineFx, Red5, WebOrb and
> >> GraniteDS (I'm of course especially interesting in seeing GraniteDS
> >> somewhere on the Apache Flex website ;)
> >>
> >> I think people landing on the Apache Flex website and looking for the
> >>required tools / solutions usually accompanying a client-side SDK
> >>(IDEs, frameworks and servers) can end up with Google and the feeling
> >>that a lot of solutions are discontinued or inactive. There is
> >>admittedly something about IDEs
> >> (http://flex.apache.org/about-features.html) but I couldn't find
> >>anything like a comprehensive list of frameworks and server-side
> >>solutions.
> >> The mention of the latest release of BlazeDS at the bottom of every
> >>page
> >> "4.6.0 (Nov 2011)" is a bit awkward in this respect and can even
> >>discourage potential adopters of Apache Flex...
> >>
> >> Apache ActiveMQ is, IMHO, doing the right thing with its "Connectivity"
> >> page (http://activemq.apache.org/connectivity.html): a long and
> >> comprehensive list of third-party solutions, open-source (from Apache
> >> or other players) or not (WebLogic for instance), which gives a quick
> >> overview of a large panel of related tools and solutions.
> >>
> >> Do you think you could add a section on third-party tools? Can I
> >> contribute (I'll try to be fair with everybody) if you don't have
> >> time to write this page?
> >>
> >> Thanks,
> >> Franck Wolff
> >> Granite Data Services.
> >>
> >> PS: we have just released GraniteDS 3.0.3.GA (
> >> http://www.granitedataservices.com/2014/03/20/graniteds-3-0-3-ga-is-o
> >> u
> >> t/) and it would be great if you could mention it in your "Latest
> >> Releases" or "Latest News" panel (or anywhere else). I remember
> >> osflash.org had a News section where related projects could register
> >> and announce their latest releases (osflash is from the neolithic
> >> period, I admit).
> >>
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
On 3/20/14 7:42 AM, "Maurice Amsellem" <ma...@systar.com> wrote:
>>"Apache Flex" is mentioned with the appropriate pointers to the ASF
>Only if the site or product also points back to flex.a.o.
>If the link is from Apache Flex to the site, it does not have to.
>Correct ?
IMO, if we link to them, they should thank us by referencing Apache Flex
correctly.
-Alex
Re: Third-party tools / solutions on Apache Flex website
Posted by Franck Wolff <fr...@gmail.com>.
Thank you all for your positive feedback!
I can certainly put together a first draft and post it here.
About Alex's questions:
1) A-Z is ok (as unfair as at school, but nobody can really complain about
it).
2) Sure as well.
3) Not sure to understand what you mean here... Do you want to make sure
that nobody is mentioning "Adobe Flex" anymore?
Cheers,
Franck.
2014-03-20 15:42 GMT+01:00 Maurice Amsellem <ma...@systar.com>:
> 1) In what order should these links appear?
> A-Z ?
>
> 2) sure.
>
> 3)
> >domain name policy :
> OK . (rule apply to all active sites, not only the ones in the list,
> right?)
>
> >"Apache Flex" is mentioned with the appropriate pointers to the ASF
> Only if the site or product also points back to flex.a.o.
> If the link is from Apache Flex to the site, it does not have to.
> Correct ?
>
> Maurice
>
> -----Message d'origine-----
> De : Alex Harui [mailto:aharui@adobe.com]
> Envoyé : jeudi 20 mars 2014 15:16
> À : dev@flex.apache.org; users@flex.apache.org
> Objet : Re: Third-party tools / solutions on Apache Flex website
>
> I'm in favor of a list as well.
>
> A few complicating factors (never as simple as one would hope).
>
> 1) In what order should these links appear? Should we give preference to
> technology that donates money to Apache? That is open-source? That is
> under active development?
>
> 2) I think we'll have to go through an exercise of working out the wording
> for this page to make sure that we know the list isn't comprehensive and
> doesn't promote a particular technology.
>
> 3) I think we'll have to ask that anything listed that is under active
> development or active marketing will have to have their web site comply
> with the domain name policy and make sure that "Apache Flex" is mentioned
> with the appropriate pointers to the ASF.
>
> -Alex
>
> On 3/20/14 6:41 AM, "Maurice Amsellem" <ma...@systar.com>
> wrote:
>
> >ActiveMQ is a middleware, so it's rather obvious to have a connectivity
> >section.
> >However, having a section in the website about Apache Flex "Ecosystem"
> >(MVC frameworks, Back-ends, IDEs, etc...) seems an excellent idea to me.
> >
> >I don't think you can contribute directly on the web site, because it
> >requires an svn account, but you are more than welcome to contribute to
> >the content.
> >I think a simple way of doing that is to create a JIRA ticket to
> >support your initiative and provide content as attached files (HTML
> >files are
> >fine)
> >The web site is using a CMS Management system inspired from Django, but
> >we can rather easily convert HTML content if you provide it.
> >
> >Make a first draft of your content and submit it, so we can see how it
> >integrates to the site, and then you can polish / complete it.
> >
> >Thank you again for your offer to help...
> >
> >Maurice
> >
> >-----Message d'origine-----
> >De : Gary Yang [mailto:flashflexpro@gmail.com] Envoyé : jeudi 20 mars
> >2014 14:28 À : dev@flex.apache.org Objet : Re: Third-party tools /
> >solutions on Apache Flex website
> >
> >Franck, I can not agree more! -Gary
> >
> >
> >On Thu, Mar 20, 2014 at 8:33 AM, Franck Wolff <fr...@gmail.com> wrote:
> >
> >> Hi,
> >>
> >> I'm wondering why there is no section about Flex related server
> >> solutions such as BlazeDS, AMFPHP, FluorineFx, Red5, WebOrb and
> >> GraniteDS (I'm of course especially interesting in seeing GraniteDS
> >> somewhere on the Apache Flex website ;)
> >>
> >> I think people landing on the Apache Flex website and looking for the
> >>required tools / solutions usually accompanying a client-side SDK
> >>(IDEs, frameworks and servers) can end up with Google and the feeling
> >>that a lot of solutions are discontinued or inactive. There is
> >>admittedly something about IDEs
> >> (http://flex.apache.org/about-features.html) but I couldn't find
> >>anything like a comprehensive list of frameworks and server-side
> >>solutions.
> >> The mention of the latest release of BlazeDS at the bottom of every
> >>page
> >> "4.6.0 (Nov 2011)" is a bit awkward in this respect and can even
> >>discourage potential adopters of Apache Flex...
> >>
> >> Apache ActiveMQ is, IMHO, doing the right thing with its "Connectivity"
> >> page (http://activemq.apache.org/connectivity.html): a long and
> >> comprehensive list of third-party solutions, open-source (from Apache
> >> or other players) or not (WebLogic for instance), which gives a quick
> >> overview of a large panel of related tools and solutions.
> >>
> >> Do you think you could add a section on third-party tools? Can I
> >> contribute (I'll try to be fair with everybody) if you don't have
> >> time to write this page?
> >>
> >> Thanks,
> >> Franck Wolff
> >> Granite Data Services.
> >>
> >> PS: we have just released GraniteDS 3.0.3.GA (
> >> http://www.granitedataservices.com/2014/03/20/graniteds-3-0-3-ga-is-o
> >> u
> >> t/) and it would be great if you could mention it in your "Latest
> >> Releases" or "Latest News" panel (or anywhere else). I remember
> >> osflash.org had a News section where related projects could register
> >> and announce their latest releases (osflash is from the neolithic
> >> period, I admit).
> >>
>
>
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
On 3/20/14 7:42 AM, "Maurice Amsellem" <ma...@systar.com> wrote:
>>"Apache Flex" is mentioned with the appropriate pointers to the ASF
>Only if the site or product also points back to flex.a.o.
>If the link is from Apache Flex to the site, it does not have to.
>Correct ?
IMO, if we link to them, they should thank us by referencing Apache Flex
correctly.
-Alex
RE: Third-party tools / solutions on Apache Flex website
Posted by Maurice Amsellem <ma...@systar.com>.
1) In what order should these links appear?
A-Z ?
2) sure.
3)
>domain name policy :
OK . (rule apply to all active sites, not only the ones in the list, right?)
>"Apache Flex" is mentioned with the appropriate pointers to the ASF
Only if the site or product also points back to flex.a.o.
If the link is from Apache Flex to the site, it does not have to.
Correct ?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : jeudi 20 mars 2014 15:16
À : dev@flex.apache.org; users@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
I'm in favor of a list as well.
A few complicating factors (never as simple as one would hope).
1) In what order should these links appear? Should we give preference to technology that donates money to Apache? That is open-source? That is under active development?
2) I think we'll have to go through an exercise of working out the wording for this page to make sure that we know the list isn't comprehensive and doesn't promote a particular technology.
3) I think we'll have to ask that anything listed that is under active development or active marketing will have to have their web site comply with the domain name policy and make sure that "Apache Flex" is mentioned with the appropriate pointers to the ASF.
-Alex
On 3/20/14 6:41 AM, "Maurice Amsellem" <ma...@systar.com> wrote:
>ActiveMQ is a middleware, so it's rather obvious to have a connectivity
>section.
>However, having a section in the website about Apache Flex "Ecosystem"
>(MVC frameworks, Back-ends, IDEs, etc...) seems an excellent idea to me.
>
>I don't think you can contribute directly on the web site, because it
>requires an svn account, but you are more than welcome to contribute to
>the content.
>I think a simple way of doing that is to create a JIRA ticket to
>support your initiative and provide content as attached files (HTML
>files are
>fine)
>The web site is using a CMS Management system inspired from Django, but
>we can rather easily convert HTML content if you provide it.
>
>Make a first draft of your content and submit it, so we can see how it
>integrates to the site, and then you can polish / complete it.
>
>Thank you again for your offer to help...
>
>Maurice
>
>-----Message d'origine-----
>De : Gary Yang [mailto:flashflexpro@gmail.com] Envoyé : jeudi 20 mars
>2014 14:28 À : dev@flex.apache.org Objet : Re: Third-party tools /
>solutions on Apache Flex website
>
>Franck, I can not agree more! -Gary
>
>
>On Thu, Mar 20, 2014 at 8:33 AM, Franck Wolff <fr...@gmail.com> wrote:
>
>> Hi,
>>
>> I'm wondering why there is no section about Flex related server
>> solutions such as BlazeDS, AMFPHP, FluorineFx, Red5, WebOrb and
>> GraniteDS (I'm of course especially interesting in seeing GraniteDS
>> somewhere on the Apache Flex website ;)
>>
>> I think people landing on the Apache Flex website and looking for the
>>required tools / solutions usually accompanying a client-side SDK
>>(IDEs, frameworks and servers) can end up with Google and the feeling
>>that a lot of solutions are discontinued or inactive. There is
>>admittedly something about IDEs
>> (http://flex.apache.org/about-features.html) but I couldn't find
>>anything like a comprehensive list of frameworks and server-side
>>solutions.
>> The mention of the latest release of BlazeDS at the bottom of every
>>page
>> "4.6.0 (Nov 2011)" is a bit awkward in this respect and can even
>>discourage potential adopters of Apache Flex...
>>
>> Apache ActiveMQ is, IMHO, doing the right thing with its "Connectivity"
>> page (http://activemq.apache.org/connectivity.html): a long and
>> comprehensive list of third-party solutions, open-source (from Apache
>> or other players) or not (WebLogic for instance), which gives a quick
>> overview of a large panel of related tools and solutions.
>>
>> Do you think you could add a section on third-party tools? Can I
>> contribute (I'll try to be fair with everybody) if you don't have
>> time to write this page?
>>
>> Thanks,
>> Franck Wolff
>> Granite Data Services.
>>
>> PS: we have just released GraniteDS 3.0.3.GA (
>> http://www.granitedataservices.com/2014/03/20/graniteds-3-0-3-ga-is-o
>> u
>> t/) and it would be great if you could mention it in your "Latest
>> Releases" or "Latest News" panel (or anywhere else). I remember
>> osflash.org had a News section where related projects could register
>> and announce their latest releases (osflash is from the neolithic
>> period, I admit).
>>
RE: Third-party tools / solutions on Apache Flex website
Posted by Maurice Amsellem <ma...@systar.com>.
1) In what order should these links appear?
A-Z ?
2) sure.
3)
>domain name policy :
OK . (rule apply to all active sites, not only the ones in the list, right?)
>"Apache Flex" is mentioned with the appropriate pointers to the ASF
Only if the site or product also points back to flex.a.o.
If the link is from Apache Flex to the site, it does not have to.
Correct ?
Maurice
-----Message d'origine-----
De : Alex Harui [mailto:aharui@adobe.com]
Envoyé : jeudi 20 mars 2014 15:16
À : dev@flex.apache.org; users@flex.apache.org
Objet : Re: Third-party tools / solutions on Apache Flex website
I'm in favor of a list as well.
A few complicating factors (never as simple as one would hope).
1) In what order should these links appear? Should we give preference to technology that donates money to Apache? That is open-source? That is under active development?
2) I think we'll have to go through an exercise of working out the wording for this page to make sure that we know the list isn't comprehensive and doesn't promote a particular technology.
3) I think we'll have to ask that anything listed that is under active development or active marketing will have to have their web site comply with the domain name policy and make sure that "Apache Flex" is mentioned with the appropriate pointers to the ASF.
-Alex
On 3/20/14 6:41 AM, "Maurice Amsellem" <ma...@systar.com> wrote:
>ActiveMQ is a middleware, so it's rather obvious to have a connectivity
>section.
>However, having a section in the website about Apache Flex "Ecosystem"
>(MVC frameworks, Back-ends, IDEs, etc...) seems an excellent idea to me.
>
>I don't think you can contribute directly on the web site, because it
>requires an svn account, but you are more than welcome to contribute to
>the content.
>I think a simple way of doing that is to create a JIRA ticket to
>support your initiative and provide content as attached files (HTML
>files are
>fine)
>The web site is using a CMS Management system inspired from Django, but
>we can rather easily convert HTML content if you provide it.
>
>Make a first draft of your content and submit it, so we can see how it
>integrates to the site, and then you can polish / complete it.
>
>Thank you again for your offer to help...
>
>Maurice
>
>-----Message d'origine-----
>De : Gary Yang [mailto:flashflexpro@gmail.com] Envoyé : jeudi 20 mars
>2014 14:28 À : dev@flex.apache.org Objet : Re: Third-party tools /
>solutions on Apache Flex website
>
>Franck, I can not agree more! -Gary
>
>
>On Thu, Mar 20, 2014 at 8:33 AM, Franck Wolff <fr...@gmail.com> wrote:
>
>> Hi,
>>
>> I'm wondering why there is no section about Flex related server
>> solutions such as BlazeDS, AMFPHP, FluorineFx, Red5, WebOrb and
>> GraniteDS (I'm of course especially interesting in seeing GraniteDS
>> somewhere on the Apache Flex website ;)
>>
>> I think people landing on the Apache Flex website and looking for the
>>required tools / solutions usually accompanying a client-side SDK
>>(IDEs, frameworks and servers) can end up with Google and the feeling
>>that a lot of solutions are discontinued or inactive. There is
>>admittedly something about IDEs
>> (http://flex.apache.org/about-features.html) but I couldn't find
>>anything like a comprehensive list of frameworks and server-side
>>solutions.
>> The mention of the latest release of BlazeDS at the bottom of every
>>page
>> "4.6.0 (Nov 2011)" is a bit awkward in this respect and can even
>>discourage potential adopters of Apache Flex...
>>
>> Apache ActiveMQ is, IMHO, doing the right thing with its "Connectivity"
>> page (http://activemq.apache.org/connectivity.html): a long and
>> comprehensive list of third-party solutions, open-source (from Apache
>> or other players) or not (WebLogic for instance), which gives a quick
>> overview of a large panel of related tools and solutions.
>>
>> Do you think you could add a section on third-party tools? Can I
>> contribute (I'll try to be fair with everybody) if you don't have
>> time to write this page?
>>
>> Thanks,
>> Franck Wolff
>> Granite Data Services.
>>
>> PS: we have just released GraniteDS 3.0.3.GA (
>> http://www.granitedataservices.com/2014/03/20/graniteds-3-0-3-ga-is-o
>> u
>> t/) and it would be great if you could mention it in your "Latest
>> Releases" or "Latest News" panel (or anywhere else). I remember
>> osflash.org had a News section where related projects could register
>> and announce their latest releases (osflash is from the neolithic
>> period, I admit).
>>
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
I'm in favor of a list as well.
A few complicating factors (never as simple as one would hope).
1) In what order should these links appear? Should we give preference to
technology that donates money to Apache? That is open-source? That is
under active development?
2) I think we'll have to go through an exercise of working out the wording
for this page to make sure that we know the list isn't comprehensive and
doesn't promote a particular technology.
3) I think we'll have to ask that anything listed that is under active
development or active marketing will have to have their web site comply
with the domain name policy and make sure that "Apache Flex" is mentioned
with the appropriate pointers to the ASF.
-Alex
On 3/20/14 6:41 AM, "Maurice Amsellem" <ma...@systar.com> wrote:
>ActiveMQ is a middleware, so it's rather obvious to have a connectivity
>section.
>However, having a section in the website about Apache Flex "Ecosystem"
>(MVC frameworks, Back-ends, IDEs, etc...) seems an excellent idea to me.
>
>I don't think you can contribute directly on the web site, because it
>requires an svn account, but you are more than welcome to contribute to
>the content.
>I think a simple way of doing that is to create a JIRA ticket to support
>your initiative and provide content as attached files (HTML files are
>fine)
>The web site is using a CMS Management system inspired from Django, but
>we can rather easily convert HTML content if you provide it.
>
>Make a first draft of your content and submit it, so we can see how it
>integrates to the site, and then you can polish / complete it.
>
>Thank you again for your offer to help...
>
>Maurice
>
>-----Message d'origine-----
>De : Gary Yang [mailto:flashflexpro@gmail.com]
>Envoyé : jeudi 20 mars 2014 14:28
>À : dev@flex.apache.org
>Objet : Re: Third-party tools / solutions on Apache Flex website
>
>Franck, I can not agree more! -Gary
>
>
>On Thu, Mar 20, 2014 at 8:33 AM, Franck Wolff <fr...@gmail.com> wrote:
>
>> Hi,
>>
>> I'm wondering why there is no section about Flex related server
>> solutions such as BlazeDS, AMFPHP, FluorineFx, Red5, WebOrb and
>> GraniteDS (I'm of course especially interesting in seeing GraniteDS
>> somewhere on the Apache Flex website ;)
>>
>> I think people landing on the Apache Flex website and looking for the
>> required tools / solutions usually accompanying a client-side SDK
>> (IDEs, frameworks and servers) can end up with Google and the feeling
>> that a lot of solutions are discontinued or inactive. There is
>> admittedly something about IDEs
>> (http://flex.apache.org/about-features.html) but I couldn't find
>> anything like a comprehensive list of frameworks and server-side
>>solutions.
>> The mention of the latest release of BlazeDS at the bottom of every
>> page
>> "4.6.0 (Nov 2011)" is a bit awkward in this respect and can even
>> discourage potential adopters of Apache Flex...
>>
>> Apache ActiveMQ is, IMHO, doing the right thing with its "Connectivity"
>> page (http://activemq.apache.org/connectivity.html): a long and
>> comprehensive list of third-party solutions, open-source (from Apache
>> or other players) or not (WebLogic for instance), which gives a quick
>> overview of a large panel of related tools and solutions.
>>
>> Do you think you could add a section on third-party tools? Can I
>> contribute (I'll try to be fair with everybody) if you don't have time
>> to write this page?
>>
>> Thanks,
>> Franck Wolff
>> Granite Data Services.
>>
>> PS: we have just released GraniteDS 3.0.3.GA (
>> http://www.granitedataservices.com/2014/03/20/graniteds-3-0-3-ga-is-ou
>> t/) and it would be great if you could mention it in your "Latest
>> Releases" or "Latest News" panel (or anywhere else). I remember
>> osflash.org had a News section where related projects could register
>> and announce their latest releases (osflash is from the neolithic
>> period, I admit).
>>
Re: Third-party tools / solutions on Apache Flex website
Posted by Alex Harui <ah...@adobe.com>.
I'm in favor of a list as well.
A few complicating factors (never as simple as one would hope).
1) In what order should these links appear? Should we give preference to
technology that donates money to Apache? That is open-source? That is
under active development?
2) I think we'll have to go through an exercise of working out the wording
for this page to make sure that we know the list isn't comprehensive and
doesn't promote a particular technology.
3) I think we'll have to ask that anything listed that is under active
development or active marketing will have to have their web site comply
with the domain name policy and make sure that "Apache Flex" is mentioned
with the appropriate pointers to the ASF.
-Alex
On 3/20/14 6:41 AM, "Maurice Amsellem" <ma...@systar.com> wrote:
>ActiveMQ is a middleware, so it's rather obvious to have a connectivity
>section.
>However, having a section in the website about Apache Flex "Ecosystem"
>(MVC frameworks, Back-ends, IDEs, etc...) seems an excellent idea to me.
>
>I don't think you can contribute directly on the web site, because it
>requires an svn account, but you are more than welcome to contribute to
>the content.
>I think a simple way of doing that is to create a JIRA ticket to support
>your initiative and provide content as attached files (HTML files are
>fine)
>The web site is using a CMS Management system inspired from Django, but
>we can rather easily convert HTML content if you provide it.
>
>Make a first draft of your content and submit it, so we can see how it
>integrates to the site, and then you can polish / complete it.
>
>Thank you again for your offer to help...
>
>Maurice
>
>-----Message d'origine-----
>De : Gary Yang [mailto:flashflexpro@gmail.com]
>Envoyé : jeudi 20 mars 2014 14:28
>À : dev@flex.apache.org
>Objet : Re: Third-party tools / solutions on Apache Flex website
>
>Franck, I can not agree more! -Gary
>
>
>On Thu, Mar 20, 2014 at 8:33 AM, Franck Wolff <fr...@gmail.com> wrote:
>
>> Hi,
>>
>> I'm wondering why there is no section about Flex related server
>> solutions such as BlazeDS, AMFPHP, FluorineFx, Red5, WebOrb and
>> GraniteDS (I'm of course especially interesting in seeing GraniteDS
>> somewhere on the Apache Flex website ;)
>>
>> I think people landing on the Apache Flex website and looking for the
>> required tools / solutions usually accompanying a client-side SDK
>> (IDEs, frameworks and servers) can end up with Google and the feeling
>> that a lot of solutions are discontinued or inactive. There is
>> admittedly something about IDEs
>> (http://flex.apache.org/about-features.html) but I couldn't find
>> anything like a comprehensive list of frameworks and server-side
>>solutions.
>> The mention of the latest release of BlazeDS at the bottom of every
>> page
>> "4.6.0 (Nov 2011)" is a bit awkward in this respect and can even
>> discourage potential adopters of Apache Flex...
>>
>> Apache ActiveMQ is, IMHO, doing the right thing with its "Connectivity"
>> page (http://activemq.apache.org/connectivity.html): a long and
>> comprehensive list of third-party solutions, open-source (from Apache
>> or other players) or not (WebLogic for instance), which gives a quick
>> overview of a large panel of related tools and solutions.
>>
>> Do you think you could add a section on third-party tools? Can I
>> contribute (I'll try to be fair with everybody) if you don't have time
>> to write this page?
>>
>> Thanks,
>> Franck Wolff
>> Granite Data Services.
>>
>> PS: we have just released GraniteDS 3.0.3.GA (
>> http://www.granitedataservices.com/2014/03/20/graniteds-3-0-3-ga-is-ou
>> t/) and it would be great if you could mention it in your "Latest
>> Releases" or "Latest News" panel (or anywhere else). I remember
>> osflash.org had a News section where related projects could register
>> and announce their latest releases (osflash is from the neolithic
>> period, I admit).
>>