Re: [DISCUSS] Building the brand for Royale

[Dave Fisher]

Hi,

One thing we could do with an external Wordpress is have tooling which captures 
posts and checks these into git.

We can probably do it with a WP addin. I've used a variation of this approach 
to provide content to an iOS app.

Regards,
Dave

Sent from my iPhone

> On Sep 20, 2017, at 1:51 PM, Dave Fisher  wrote:
> 
> Hi -
> 
> Wordpress on apache infrastructure would require following every Wordpress 
> release which can be more frequently than monthly. The PMC would need to 
> provide the manpower to do this. We would also need to be careful about 
> plugins which can also have security issues.
> 
> I say if we can eat our Royale then that would be best. If we go with Git it 
> can be there and then we can refer to it from the official ask site and/or 
> merge the two under standard ASF CMS.
> 
> Regards,
> Dave
> 
>> On Sep 20, 2017, at 1:36 PM, OmPrakash Muppirala  
>> wrote:
>> 
>> I would stay away from WordPress just because of all the security issues
>> and maintenance required.
>> 
>> Github pages should be a better place.
>> 
>> Thanks,
>> Om
>> 
>>> On Sep 20, 2017 10:26 AM, "Alex Harui"  wrote:
>>> 
>>> Hmm.
>>> 
>>> I think if we grab a domain and donate it to the ASF, that it can't be
>>> hosted on non-ASF hardware.  That would need to be verified.
>>> Maybe it would be better for the Royale PMC to approve Royale.xx as a
>>> third-party domain under Carlos's control.  I think that's allowed.  The
>>> policy [1] says that "in general" it is NOT allowed, but "in general"
>>> implies it isn't a hard and fast rule.
>>> 
>>> IMO, things under the PMC's control have certain obligations.  It has to
>>> be sustainable by "anyone".  How many folks know how to edit WordPress
>>> themes?  I don't.  I always choose one of their default themes.  It might
>>> have to be hosted or host-able by Apache Infra, and I don't know if they
>>> are ok with WordPress.
>>> 
>>> Personally, I want to be able to stick FlexJS apps in our web presence.
>>> Honestly, I'd actually like to see our entire web presence be built in
>>> FlexJS.  It would truly be "eating our own dog food".  Yes, I know that
>>> mostly static pages aren't a great match for FlexJS/Royale, but in the
>>> end, shouldn't all of our web presence be dynamic?
>>> 
>>> My 2 cents,
>>> -Alex
>>> 
>>> [1] http://www.apache.org/foundation/marks/domains.html
>>> 
>>> On 9/20/17, 10:02 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>>> 
>>> wrote:
>>> 
 Hi Alex,
 
 that's my bet. To make a good website I proposed to make it in Wordpress
 since is what I have some expertise in that field (If I'm the person in
 charge to make it happen). All the team can as well have an account in the
 WP dash board to be able to post and share content in a easy way.
 
 WP will gave as the landing and some pages that would be useful for
 convenience. But I think, as well, to link directly to the resources in
 the
 apache infrastructure in the main menu of the site just as we do now
 (code,
 GitHub, wiki, links to our mailing lists, releases, binaries, and so on)
 
 For domain registration I'd prefer .io since is very popular today, but
 .as
 seems ok for me as well.
 I think Erik proposed to register the domain for us, so I think is ok for
 me that he makes the registration. Maybe we could do it as soon as the
 board approve the new TLP and name.
 
 I can host the site in CO servers with the rest of our websites, to
 support
 as well this change and initiative. Again I'll be waiting for board
 approval to start working. I'm assuming here that you guys trust me to
 make
 this website and branding work, of course.
 
 So maybe we could make a thread to select from Royale.io and Royale.as,
 and
 of course if price for .io is very high we could go with .as if it's more
 low.
 
 
 
 
 2017-09-20 18:44 GMT+02:00 Alex Harui :
 
> Hi Carlos,
> 
> We can go grab some royale. domains.  Apache will have some rules
> about what can go on them.  At the worst it will have to be a straight
> redirect to royale.apache.org, but I think we might be able to have at
> least a landing page.  I think the goal is that Apache wants strong
> association with a project's web presence.  Even on a royale.foo landing
> page, the first mention of Royale probably has to be "Apache Royale".
> 
> But also, I am hopeful we will be using GitBox and thus GitHub will be
> our
> hub of activity.  And I think we should use GitHub pages and build a
> solid
> web presence there, again within Apache's rules.
> 
> Royale.io is for sale.  We could ask what the price is.
> Royale.as appears to be unregistered.
> 
> My 2 cents,
> -Alex
> 
> On 9/20/17, 8:31 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira"
> 
> wrote:
> 
>> Hi,
>> 
>> a

Re: [DISCUSS] Building the brand for Royale

[Mark Thomas]

On 20/09/17 19:08, Alex Harui wrote:
> AIUI, we are going to build at least three sites:
> 
> 1) Royale.apache.org is a requirement.  And I think we have to use ASF CMS
> and whatever markup language it requires unless we generate html and js
> elsewhere and copy it in, which would be the case for any FlexJS/Royale
> apps.

No need to use the CMS.

Any system the project wants that results in a bunch of static files in
the right place in svn or git is fine.

Mark

> 
> 2) https://github.com/apache/royale.  Folks are going to land here quite
> often.  My understanding is that GH Pages can affect what folks land on.
> It doesn't have to be the standard page with the README.MD and a folder of
> files.  But I could be wrong about that.  Many GH projects mention a
> website on the standard landing page.  I don't know if we can make that
> something other than royale.apache.org.  We'll find out if we get to use
> GitBox.  If we can't I don't think we get to use GH Pages or control the
> landing page.
> 
> 3) Facebook/Royale.
> 
> The development of these 3 sites must be done the Apache Way and I suspect
> that there will be plenty of discussion on it.  I don't want to put stones
> in the road in front of Carlos.  I think he should go and build what he
> wants to build, host it on his hardware and show it to us.  Then we can
> ask for the minimum tweaks required to get approval as royale.xx.  If we
> can't agree on how to do that, Carlos can always publish it as
> royale.codeoscopic.com.  Domains of that pattern are supposedly easier to
> approve.
> 
> Also, we don't need to decide on royale.xx vs royale.yy if we can afford
> to get both.
> 
> Does that sound reasonable?
> 
> -Alex
> 
> On 9/20/17, 10:52 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>  wrote:
> 
>> Hi Alex,
>>
>> I was not thinking in promote Codeoscopic, but if I can put a link in some
>> place, it would be ok.
>> In the end Codeoscopic is a product company and its customers are
>> insurance
>> companies, so there's no much interest for me in that regard or at least I
>> can see a logic relation since we don't sell "flex services" anymore.
>>
>> 2017-09-20 19:49 GMT+02:00 Alex Harui :
>>
>>> True, that's a lot of rules.  Part of that is because we owe our hosts
>>> (the ASF) some "props".
>>>
>>> But that may be why it is easier for us to approve Carlos to do what we
>>> wants outside the project.  It will free him most of these rules.  AIUI,
>>> the only rules would then be:
>>> 1) make sure Apache is mentioned often enough
>>> 2) make sure there are enough links back to royale.apache.org
>>> 3) make sure he doesn't promote his company more than the project. (I
>>> think he is allowed to say the site is hosted by his company and some
>>> promotional info).
>>>
>>> Thoughts?
>>> -Alex
>>>
>>> On 9/20/17, 10:36 AM, "Erik de Bruin"  wrote:
>>>
> I think if we grab a domain and donate it to the ASF, that it can't
>>> be
> hosted on non-ASF hardware.  That would need to be verified.
> Maybe it would be better for the Royale PMC to approve Royale.xx as a
> third-party domain under Carlos's control.  I think that's allowed.
>>> The
> policy [1] says that "in general" it is NOT allowed, but "in general"
> implies it isn't a hard and fast rule.
>
> IMO, things under the PMC's control have certain obligations.  It
>>> has to
> be sustainable by "anyone".  How many folks know how to edit
>>> WordPress
> themes?  I don't.  I always choose one of their default themes.  It
> might
> have to be hosted or host-able by Apache Infra, and I don't know if
>>> they
> are ok with WordPress.
>

 That is an awful lot of rules that seem to work against the creativity
>>> of
 the project...

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I.
 https://na01.safelinks.protection.outlook.com/?url=
>>>
>>> https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl&data
>>> =02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b34438794aed2c1
>>> 78decee1%7C0%7C0%7C636415267698995147&sdata=NQ%2BjrPGhT7zQtWVbo0nStXLzQit
>>> 19Ny3Y1JOczHt3hs%3D&reserved=0&data=
 02%7C01%7C%7Ceb4bfa47a0da41fe511b08d5004e3980%
>>> 7Cfa7b1b5a7b34438794aed2c178
 decee1%7C0%7C0%7C636415258339861760&sdata=K%
>>> 2FKg9eeTxMwS%2BsxE7xGAXU6KlhtQ
 sQNLKnv3gG81OKs%3D&reserved=0
>>>
>>>
>>
>>
>> -- 
>>
>> > scopic.com&data=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636415267698995147&sdata=LBwi00UXVvi%2F7U
>> gwYDmrS2QKANVigbic9dJpsaQ31Xw%3D&reserved=0>
>>
>> Carlos Rovira
>>
>> Director General
>>
>> M: +34 607 22 60 05
>>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>> copic.com&data=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b3
>

Re: [DISCUSS] Building the brand for Royale

[Alex Harui]

AIUI, one of the other "rules" for royale.apache.org is that it cannot run
web servers, so JSFiddle type of things may not be possible without
calling out to a server outside apache.org and thus facing cross-domain
issues.  I've seen some recent mention that Apache project can now get
their own VM, but that offer has been rescinded from time to time so I'm
concerned about betting on always having a VM.  So that's another reason
for a non-Apache site to host RoyaleFiddle.

Of course, I could be wrong...
-Alex

On 9/20/17, 11:09 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>I use to update my WP installations regularly. I did it just minutes ago
>;)
>I get notifications when some update is ready. As others in the team will
>have admin privileges in the installation, we can organice us easily to
>see
>how is in charge of doing updates. Others in the team could only have
>editor profiles to avoid a bloated admin interface but be able to publish
>in the system.
>
>As I said we can in the future to change to a Royale App since we can get
>data from WP REST APIs, but based in my experience I think you'll end
>thinking that's not the right way as you manage the system for some time.
>
>For me the real goal to get is to make our landing very intuitive. If we
>get people that doesn't know anything about Flex or Royale, and can make
>them understand and try it in minutes, we can transform that visit in a
>new
>Royale user, and that should be our real target.
>
>If you see competitors sites, they post code to show people what can they
>do. It's easy to post code in the same way, but we could make a difference
>if we can create a Royale App that could run the code posted and make
>people do updates in our home to see how easy is to get ready with Royale.
>
>If we get something like that I'm sure we'll make people get on board.
>
>We should plan as well a great launch of our new brand and website as we
>get ready talking with as most tech sites as we can to make people turn
>their heads and look at us.
>
>
>
>
>
>2017-09-20 19:51 GMT+02:00 Dave Fisher :
>
>> Hi -
>>
>> Wordpress on apache infrastructure would require following every
>>Wordpress
>> release which can be more frequently than monthly. The PMC would need to
>> provide the manpower to do this. We would also need to be careful about
>> plugins which can also have security issues.
>>
>> I say if we can eat our Royale then that would be best. If we go with
>>Git
>> it can be there and then we can refer to it from the official ask site
>> and/or merge the two under standard ASF CMS.
>>
>> Regards,
>> Dave
>>
>> > On Sep 20, 2017, at 1:36 PM, OmPrakash Muppirala
>>
>> wrote:
>> >
>> > I would stay away from WordPress just because of all the security
>>issues
>> > and maintenance required.
>> >
>> > Github pages should be a better place.
>> >
>> > Thanks,
>> > Om
>> >
>> > On Sep 20, 2017 10:26 AM, "Alex Harui" 
>>wrote:
>> >
>> >> Hmm.
>> >>
>> >> I think if we grab a domain and donate it to the ASF, that it can't
>>be
>> >> hosted on non-ASF hardware.  That would need to be verified.
>> >> Maybe it would be better for the Royale PMC to approve Royale.xx as a
>> >> third-party domain under Carlos's control.  I think that's allowed.
>>The
>> >> policy [1] says that "in general" it is NOT allowed, but "in general"
>> >> implies it isn't a hard and fast rule.
>> >>
>> >> IMO, things under the PMC's control have certain obligations.  It
>>has to
>> >> be sustainable by "anyone".  How many folks know how to edit
>>WordPress
>> >> themes?  I don't.  I always choose one of their default themes.  It
>> might
>> >> have to be hosted or host-able by Apache Infra, and I don't know if
>>they
>> >> are ok with WordPress.
>> >>
>> >> Personally, I want to be able to stick FlexJS apps in our web
>>presence.
>> >> Honestly, I'd actually like to see our entire web presence be built
>>in
>> >> FlexJS.  It would truly be "eating our own dog food".  Yes, I know
>>that
>> >> mostly static pages aren't a great match for FlexJS/Royale, but in
>>the
>> >> end, shouldn't all of our web presence be dynamic?
>> >>
>> >> My 2 cents,
>> >> -Alex
>> >>
>> >> [1] 
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apach
>>e.org%2Ffoundation%2Fmarks%2Fdomains.html&data=02%7C01%7C%7C4fca064ec1484
>>2be067308d50052c771%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63641527
>>7899139815&sdata=6fZ5yrBTsjk1gl6M9hB2VpTSjqv%2B0g78DCdCfSJh67w%3D&reserve
>>d=0
>> >>
>> >> On 9/20/17, 10:02 AM, "carlos.rov...@gmail.com on behalf of Carlos
>> Rovira"
>> >> 
>> >> wrote:
>> >>
>> >>> Hi Alex,
>> >>>
>> >>> that's my bet. To make a good website I proposed to make it in
>> Wordpress
>> >>> since is what I have some expertise in that field (If I'm the
>>person in
>> >>> charge to make it happen). All the team can as well have an account
>>in
>> the
>> >>> WP dash board to be able to post and share content in a easy way.
>> >>>
>> >>> WP will gave as the landing and some p

Re: [DISCUSS] Building the brand for Royale

[Carlos Rovira]

I think that's right Alex,

I think I can start creating as we get boards approval for "Royale"

Thanks

2017-09-20 20:08 GMT+02:00 Alex Harui :

> AIUI, we are going to build at least three sites:
>
> 1) Royale.apache.org is a requirement.  And I think we have to use ASF CMS
> and whatever markup language it requires unless we generate html and js
> elsewhere and copy it in, which would be the case for any FlexJS/Royale
> apps.
>
> 2) https://github.com/apache/royale.  Folks are going to land here quite
> often.  My understanding is that GH Pages can affect what folks land on.
> It doesn't have to be the standard page with the README.MD and a folder of
> files.  But I could be wrong about that.  Many GH projects mention a
> website on the standard landing page.  I don't know if we can make that
> something other than royale.apache.org.  We'll find out if we get to use
> GitBox.  If we can't I don't think we get to use GH Pages or control the
> landing page.
>
> 3) Facebook/Royale.
>
> The development of these 3 sites must be done the Apache Way and I suspect
> that there will be plenty of discussion on it.  I don't want to put stones
> in the road in front of Carlos.  I think he should go and build what he
> wants to build, host it on his hardware and show it to us.  Then we can
> ask for the minimum tweaks required to get approval as royale.xx.  If we
> can't agree on how to do that, Carlos can always publish it as
> royale.codeoscopic.com.  Domains of that pattern are supposedly easier to
> approve.
>
> Also, we don't need to decide on royale.xx vs royale.yy if we can afford
> to get both.
>
> Does that sound reasonable?
>
> -Alex
>
> On 9/20/17, 10:52 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> 
> wrote:
>
> >Hi Alex,
> >
> >I was not thinking in promote Codeoscopic, but if I can put a link in some
> >place, it would be ok.
> >In the end Codeoscopic is a product company and its customers are
> >insurance
> >companies, so there's no much interest for me in that regard or at least I
> >can see a logic relation since we don't sell "flex services" anymore.
> >
> >2017-09-20 19:49 GMT+02:00 Alex Harui :
> >
> >> True, that's a lot of rules.  Part of that is because we owe our hosts
> >> (the ASF) some "props".
> >>
> >> But that may be why it is easier for us to approve Carlos to do what we
> >> wants outside the project.  It will free him most of these rules.  AIUI,
> >> the only rules would then be:
> >> 1) make sure Apache is mentioned often enough
> >> 2) make sure there are enough links back to royale.apache.org
> >> 3) make sure he doesn't promote his company more than the project. (I
> >> think he is allowed to say the site is hosted by his company and some
> >> promotional info).
> >>
> >> Thoughts?
> >> -Alex
> >>
> >> On 9/20/17, 10:36 AM, "Erik de Bruin"  wrote:
> >>
> >> >> I think if we grab a domain and donate it to the ASF, that it can't
> >>be
> >> >> hosted on non-ASF hardware.  That would need to be verified.
> >> >> Maybe it would be better for the Royale PMC to approve Royale.xx as a
> >> >> third-party domain under Carlos's control.  I think that's allowed.
> >>The
> >> >> policy [1] says that "in general" it is NOT allowed, but "in general"
> >> >> implies it isn't a hard and fast rule.
> >> >>
> >> >> IMO, things under the PMC's control have certain obligations.  It
> >>has to
> >> >> be sustainable by "anyone".  How many folks know how to edit
> >>WordPress
> >> >> themes?  I don't.  I always choose one of their default themes.  It
> >> >>might
> >> >> have to be hosted or host-able by Apache Infra, and I don't know if
> >>they
> >> >> are ok with WordPress.
> >> >>
> >> >
> >> >That is an awful lot of rules that seem to work against the creativity
> >>of
> >> >the project...
> >> >
> >> >EdB
> >> >
> >> >
> >> >
> >> >--
> >> >Ix Multimedia Software
> >> >
> >> >Jan Luykenstraat 27
> >> >3521 VB Utrecht
> >> >
> >> >T. 06-51952295
> >> >I.
> >> >https://na01.safelinks.protection.outlook.com/?url=
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> www.ixsoftware.nl&data
> >>=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%
> 7Cfa7b1b5a7b34438794aed2c1
> >>78decee1%7C0%7C0%7C636415267698995147&sdata=NQ%
> 2BjrPGhT7zQtWVbo0nStXLzQit
> >>19Ny3Y1JOczHt3hs%3D&reserved=0&data=
> >> >02%7C01%7C%7Ceb4bfa47a0da41fe511b08d5004e3980%
> >> 7Cfa7b1b5a7b34438794aed2c178
> >> >decee1%7C0%7C0%7C636415258339861760&sdata=K%
> >> 2FKg9eeTxMwS%2BsxE7xGAXU6KlhtQ
> >> >sQNLKnv3gG81OKs%3D&reserved=0
> >>
> >>
> >
> >
> >--
> >
> > http%3A%2F%2Fwww.codeo
> >scopic.com&data=02%7C01%7C%7Cd586e21dd7764cafe6f508d50050
> 6787%7Cfa7b1b5a7b
> >34438794aed2c178decee1%7C0%7C0%7C636415267698995147&
> sdata=LBwi00UXVvi%2F7U
> >gwYDmrS2QKANVigbic9dJpsaQ31Xw%3D&reserved=0>
> >
> >Carlos Rovira
> >
> >Director General
> >
> >M: +34 607 22 60 05
> >
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeos
> >copic.com&da

Re: [DISCUSS] Building the brand for Royale

[Carlos Rovira]

I use to update my WP installations regularly. I did it just minutes ago ;)
I get notifications when some update is ready. As others in the team will
have admin privileges in the installation, we can organice us easily to see
how is in charge of doing updates. Others in the team could only have
editor profiles to avoid a bloated admin interface but be able to publish
in the system.

As I said we can in the future to change to a Royale App since we can get
data from WP REST APIs, but based in my experience I think you'll end
thinking that's not the right way as you manage the system for some time.

For me the real goal to get is to make our landing very intuitive. If we
get people that doesn't know anything about Flex or Royale, and can make
them understand and try it in minutes, we can transform that visit in a new
Royale user, and that should be our real target.

If you see competitors sites, they post code to show people what can they
do. It's easy to post code in the same way, but we could make a difference
if we can create a Royale App that could run the code posted and make
people do updates in our home to see how easy is to get ready with Royale.

If we get something like that I'm sure we'll make people get on board.

We should plan as well a great launch of our new brand and website as we
get ready talking with as most tech sites as we can to make people turn
their heads and look at us.





2017-09-20 19:51 GMT+02:00 Dave Fisher :

> Hi -
>
> Wordpress on apache infrastructure would require following every Wordpress
> release which can be more frequently than monthly. The PMC would need to
> provide the manpower to do this. We would also need to be careful about
> plugins which can also have security issues.
>
> I say if we can eat our Royale then that would be best. If we go with Git
> it can be there and then we can refer to it from the official ask site
> and/or merge the two under standard ASF CMS.
>
> Regards,
> Dave
>
> > On Sep 20, 2017, at 1:36 PM, OmPrakash Muppirala 
> wrote:
> >
> > I would stay away from WordPress just because of all the security issues
> > and maintenance required.
> >
> > Github pages should be a better place.
> >
> > Thanks,
> > Om
> >
> > On Sep 20, 2017 10:26 AM, "Alex Harui"  wrote:
> >
> >> Hmm.
> >>
> >> I think if we grab a domain and donate it to the ASF, that it can't be
> >> hosted on non-ASF hardware.  That would need to be verified.
> >> Maybe it would be better for the Royale PMC to approve Royale.xx as a
> >> third-party domain under Carlos's control.  I think that's allowed.  The
> >> policy [1] says that "in general" it is NOT allowed, but "in general"
> >> implies it isn't a hard and fast rule.
> >>
> >> IMO, things under the PMC's control have certain obligations.  It has to
> >> be sustainable by "anyone".  How many folks know how to edit WordPress
> >> themes?  I don't.  I always choose one of their default themes.  It
> might
> >> have to be hosted or host-able by Apache Infra, and I don't know if they
> >> are ok with WordPress.
> >>
> >> Personally, I want to be able to stick FlexJS apps in our web presence.
> >> Honestly, I'd actually like to see our entire web presence be built in
> >> FlexJS.  It would truly be "eating our own dog food".  Yes, I know that
> >> mostly static pages aren't a great match for FlexJS/Royale, but in the
> >> end, shouldn't all of our web presence be dynamic?
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> [1] http://www.apache.org/foundation/marks/domains.html
> >>
> >> On 9/20/17, 10:02 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira"
> >> 
> >> wrote:
> >>
> >>> Hi Alex,
> >>>
> >>> that's my bet. To make a good website I proposed to make it in
> Wordpress
> >>> since is what I have some expertise in that field (If I'm the person in
> >>> charge to make it happen). All the team can as well have an account in
> the
> >>> WP dash board to be able to post and share content in a easy way.
> >>>
> >>> WP will gave as the landing and some pages that would be useful for
> >>> convenience. But I think, as well, to link directly to the resources in
> >>> the
> >>> apache infrastructure in the main menu of the site just as we do now
> >>> (code,
> >>> GitHub, wiki, links to our mailing lists, releases, binaries, and so
> on)
> >>>
> >>> For domain registration I'd prefer .io since is very popular today, but
> >>> .as
> >>> seems ok for me as well.
> >>> I think Erik proposed to register the domain for us, so I think is ok
> for
> >>> me that he makes the registration. Maybe we could do it as soon as the
> >>> board approve the new TLP and name.
> >>>
> >>> I can host the site in CO servers with the rest of our websites, to
> >>> support
> >>> as well this change and initiative. Again I'll be waiting for board
> >>> approval to start working. I'm assuming here that you guys trust me to
> >>> make
> >>> this website and branding work, of course.
> >>>
> >>> So maybe we could make a thread to select from Royale.io and Roy

Re: [DISCUSS] Building the brand for Royale

[Alex Harui]

AIUI, we are going to build at least three sites:

1) Royale.apache.org is a requirement.  And I think we have to use ASF CMS
and whatever markup language it requires unless we generate html and js
elsewhere and copy it in, which would be the case for any FlexJS/Royale
apps.

2) https://github.com/apache/royale.  Folks are going to land here quite
often.  My understanding is that GH Pages can affect what folks land on.
It doesn't have to be the standard page with the README.MD and a folder of
files.  But I could be wrong about that.  Many GH projects mention a
website on the standard landing page.  I don't know if we can make that
something other than royale.apache.org.  We'll find out if we get to use
GitBox.  If we can't I don't think we get to use GH Pages or control the
landing page.

3) Facebook/Royale.

The development of these 3 sites must be done the Apache Way and I suspect
that there will be plenty of discussion on it.  I don't want to put stones
in the road in front of Carlos.  I think he should go and build what he
wants to build, host it on his hardware and show it to us.  Then we can
ask for the minimum tweaks required to get approval as royale.xx.  If we
can't agree on how to do that, Carlos can always publish it as
royale.codeoscopic.com.  Domains of that pattern are supposedly easier to
approve.

Also, we don't need to decide on royale.xx vs royale.yy if we can afford
to get both.

Does that sound reasonable?

-Alex

On 9/20/17, 10:52 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>I was not thinking in promote Codeoscopic, but if I can put a link in some
>place, it would be ok.
>In the end Codeoscopic is a product company and its customers are
>insurance
>companies, so there's no much interest for me in that regard or at least I
>can see a logic relation since we don't sell "flex services" anymore.
>
>2017-09-20 19:49 GMT+02:00 Alex Harui :
>
>> True, that's a lot of rules.  Part of that is because we owe our hosts
>> (the ASF) some "props".
>>
>> But that may be why it is easier for us to approve Carlos to do what we
>> wants outside the project.  It will free him most of these rules.  AIUI,
>> the only rules would then be:
>> 1) make sure Apache is mentioned often enough
>> 2) make sure there are enough links back to royale.apache.org
>> 3) make sure he doesn't promote his company more than the project. (I
>> think he is allowed to say the site is hosted by his company and some
>> promotional info).
>>
>> Thoughts?
>> -Alex
>>
>> On 9/20/17, 10:36 AM, "Erik de Bruin"  wrote:
>>
>> >> I think if we grab a domain and donate it to the ASF, that it can't
>>be
>> >> hosted on non-ASF hardware.  That would need to be verified.
>> >> Maybe it would be better for the Royale PMC to approve Royale.xx as a
>> >> third-party domain under Carlos's control.  I think that's allowed.
>>The
>> >> policy [1] says that "in general" it is NOT allowed, but "in general"
>> >> implies it isn't a hard and fast rule.
>> >>
>> >> IMO, things under the PMC's control have certain obligations.  It
>>has to
>> >> be sustainable by "anyone".  How many folks know how to edit
>>WordPress
>> >> themes?  I don't.  I always choose one of their default themes.  It
>> >>might
>> >> have to be hosted or host-able by Apache Infra, and I don't know if
>>they
>> >> are ok with WordPress.
>> >>
>> >
>> >That is an awful lot of rules that seem to work against the creativity
>>of
>> >the project...
>> >
>> >EdB
>> >
>> >
>> >
>> >--
>> >Ix Multimedia Software
>> >
>> >Jan Luykenstraat 27
>> >3521 VB Utrecht
>> >
>> >T. 06-51952295
>> >I.
>> >https://na01.safelinks.protection.outlook.com/?url=
>> 
>>https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl&data
>>=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b34438794aed2c1
>>78decee1%7C0%7C0%7C636415267698995147&sdata=NQ%2BjrPGhT7zQtWVbo0nStXLzQit
>>19Ny3Y1JOczHt3hs%3D&reserved=0&data=
>> >02%7C01%7C%7Ceb4bfa47a0da41fe511b08d5004e3980%
>> 7Cfa7b1b5a7b34438794aed2c178
>> >decee1%7C0%7C0%7C636415258339861760&sdata=K%
>> 2FKg9eeTxMwS%2BsxE7xGAXU6KlhtQ
>> >sQNLKnv3gG81OKs%3D&reserved=0
>>
>>
>
>
>-- 
>
>scopic.com&data=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636415267698995147&sdata=LBwi00UXVvi%2F7U
>gwYDmrS2QKANVigbic9dJpsaQ31Xw%3D&reserved=0>
>
>Carlos Rovira
>
>Director General
>
>M: +34 607 22 60 05
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>copic.com&data=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636415267698995147&sdata=LBwi00UXVvi%2F7Ug
>wYDmrS2QKANVigbic9dJpsaQ31Xw%3D&reserved=0
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.avant2
>.es&data=02%7C01%7C%7Cd586e21dd7764cafe6f508d500506787%7Cfa7b1b5a7b3443879
>4aed2c178decee1%7C0%7C0%7C636415267698995147&sdata=MXtIvX%2BRZI1Rhc9hAdo7e
>yPNH%2

Re: [DISCUSS] Building the brand for Royale

[Carlos Rovira]

Hi Alex,

I was not thinking in promote Codeoscopic, but if I can put a link in some
place, it would be ok.
In the end Codeoscopic is a product company and its customers are insurance
companies, so there's no much interest for me in that regard or at least I
can see a logic relation since we don't sell "flex services" anymore.

2017-09-20 19:49 GMT+02:00 Alex Harui :

> True, that's a lot of rules.  Part of that is because we owe our hosts
> (the ASF) some "props".
>
> But that may be why it is easier for us to approve Carlos to do what we
> wants outside the project.  It will free him most of these rules.  AIUI,
> the only rules would then be:
> 1) make sure Apache is mentioned often enough
> 2) make sure there are enough links back to royale.apache.org
> 3) make sure he doesn't promote his company more than the project. (I
> think he is allowed to say the site is hosted by his company and some
> promotional info).
>
> Thoughts?
> -Alex
>
> On 9/20/17, 10:36 AM, "Erik de Bruin"  wrote:
>
> >> I think if we grab a domain and donate it to the ASF, that it can't be
> >> hosted on non-ASF hardware.  That would need to be verified.
> >> Maybe it would be better for the Royale PMC to approve Royale.xx as a
> >> third-party domain under Carlos's control.  I think that's allowed.  The
> >> policy [1] says that "in general" it is NOT allowed, but "in general"
> >> implies it isn't a hard and fast rule.
> >>
> >> IMO, things under the PMC's control have certain obligations.  It has to
> >> be sustainable by "anyone".  How many folks know how to edit WordPress
> >> themes?  I don't.  I always choose one of their default themes.  It
> >>might
> >> have to be hosted or host-able by Apache Infra, and I don't know if they
> >> are ok with WordPress.
> >>
> >
> >That is an awful lot of rules that seem to work against the creativity of
> >the project...
> >
> >EdB
> >
> >
> >
> >--
> >Ix Multimedia Software
> >
> >Jan Luykenstraat 27
> >3521 VB Utrecht
> >
> >T. 06-51952295
> >I.
> >https://na01.safelinks.protection.outlook.com/?url=
> www.ixsoftware.nl&data=
> >02%7C01%7C%7Ceb4bfa47a0da41fe511b08d5004e3980%
> 7Cfa7b1b5a7b34438794aed2c178
> >decee1%7C0%7C0%7C636415258339861760&sdata=K%
> 2FKg9eeTxMwS%2BsxE7xGAXU6KlhtQ
> >sQNLKnv3gG81OKs%3D&reserved=0
>
>


-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Conocenos en 1 minuto! 


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: [DISCUSS] Building the brand for Royale

[Dave Fisher]

Hi -

Wordpress on apache infrastructure would require following every Wordpress 
release which can be more frequently than monthly. The PMC would need to 
provide the manpower to do this. We would also need to be careful about plugins 
which can also have security issues.

I say if we can eat our Royale then that would be best. If we go with Git it 
can be there and then we can refer to it from the official ask site and/or 
merge the two under standard ASF CMS.

Regards,
Dave

> On Sep 20, 2017, at 1:36 PM, OmPrakash Muppirala  wrote:
> 
> I would stay away from WordPress just because of all the security issues
> and maintenance required.
> 
> Github pages should be a better place.
> 
> Thanks,
> Om
> 
> On Sep 20, 2017 10:26 AM, "Alex Harui"  wrote:
> 
>> Hmm.
>> 
>> I think if we grab a domain and donate it to the ASF, that it can't be
>> hosted on non-ASF hardware.  That would need to be verified.
>> Maybe it would be better for the Royale PMC to approve Royale.xx as a
>> third-party domain under Carlos's control.  I think that's allowed.  The
>> policy [1] says that "in general" it is NOT allowed, but "in general"
>> implies it isn't a hard and fast rule.
>> 
>> IMO, things under the PMC's control have certain obligations.  It has to
>> be sustainable by "anyone".  How many folks know how to edit WordPress
>> themes?  I don't.  I always choose one of their default themes.  It might
>> have to be hosted or host-able by Apache Infra, and I don't know if they
>> are ok with WordPress.
>> 
>> Personally, I want to be able to stick FlexJS apps in our web presence.
>> Honestly, I'd actually like to see our entire web presence be built in
>> FlexJS.  It would truly be "eating our own dog food".  Yes, I know that
>> mostly static pages aren't a great match for FlexJS/Royale, but in the
>> end, shouldn't all of our web presence be dynamic?
>> 
>> My 2 cents,
>> -Alex
>> 
>> [1] http://www.apache.org/foundation/marks/domains.html
>> 
>> On 9/20/17, 10:02 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
>> 
>> wrote:
>> 
>>> Hi Alex,
>>> 
>>> that's my bet. To make a good website I proposed to make it in Wordpress
>>> since is what I have some expertise in that field (If I'm the person in
>>> charge to make it happen). All the team can as well have an account in the
>>> WP dash board to be able to post and share content in a easy way.
>>> 
>>> WP will gave as the landing and some pages that would be useful for
>>> convenience. But I think, as well, to link directly to the resources in
>>> the
>>> apache infrastructure in the main menu of the site just as we do now
>>> (code,
>>> GitHub, wiki, links to our mailing lists, releases, binaries, and so on)
>>> 
>>> For domain registration I'd prefer .io since is very popular today, but
>>> .as
>>> seems ok for me as well.
>>> I think Erik proposed to register the domain for us, so I think is ok for
>>> me that he makes the registration. Maybe we could do it as soon as the
>>> board approve the new TLP and name.
>>> 
>>> I can host the site in CO servers with the rest of our websites, to
>>> support
>>> as well this change and initiative. Again I'll be waiting for board
>>> approval to start working. I'm assuming here that you guys trust me to
>>> make
>>> this website and branding work, of course.
>>> 
>>> So maybe we could make a thread to select from Royale.io and Royale.as,
>>> and
>>> of course if price for .io is very high we could go with .as if it's more
>>> low.
>>> 
>>> 
>>> 
>>> 
>>> 2017-09-20 18:44 GMT+02:00 Alex Harui :
>>> 
 Hi Carlos,
 
 We can go grab some royale. domains.  Apache will have some rules
 about what can go on them.  At the worst it will have to be a straight
 redirect to royale.apache.org, but I think we might be able to have at
 least a landing page.  I think the goal is that Apache wants strong
 association with a project's web presence.  Even on a royale.foo landing
 page, the first mention of Royale probably has to be "Apache Royale".
 
 But also, I am hopeful we will be using GitBox and thus GitHub will be
 our
 hub of activity.  And I think we should use GitHub pages and build a
 solid
 web presence there, again within Apache's rules.
 
 Royale.io is for sale.  We could ask what the price is.
 Royale.as appears to be unregistered.
 
 My 2 cents,
 -Alex
 
 On 9/20/17, 8:31 AM, "carlos.rov...@gmail.com on behalf of Carlos
 Rovira"
 
 wrote:
 
> Hi,
> 
> as Alex and Dave said, we should wait for board approval.
> 
> @Harbs, I was using "xxx" to refer to "whatever domain extension out
 there
> that would fit for us" ;)
> 
> @Dave, I understand that we should use the apache domain for the
 service
> apache provide (i.e: store code, mailing list, releases...), but as
 many
> other projects out there, I suppose we should as well have an external
> tools or domains that serve

Re: [DISCUSS] Building the brand for Royale

[piotrz]

Alex,

I would like to see getting the website done in FlexJS for a long time. If
Carlos will design the things, let's see what can we actually do. It just
would be awesome not waiting half year or so to launch our website. 

+1 for building it in FlexJS, but before that we should have some start - no
matter in what technology. Nice and shiny website. :)

Let's give Carlos free what kind of design it will be and we will see how
much work it need to be putted in order to have it in FlexJS.

Piotr



-
Apache Flex PMC
piotrzarzyck...@gmail.com
--
Sent from: http://apache-flex-development.247.n4.nabble.com/

Re: [DISCUSS] Building the brand for Royale

[Carlos Rovira]

Hi,

as Erik stated, apache put stones on our road, and we must look more
careful were you step.

@Om, my problem with gihub pages is that I can't get the same product that
I could do in WP. Take a look at one of my websites (i.e
https://www.avant2.es). Maybe I could get a final static page, but in the
end, we'll lost all the benefits of the WP publishing system and resource
management. Github pages are very simple.

@Alex, nowadays is normal to use each tool for what it was build. If we
want to expose real Apps, we can make a showcase section that people will
want to look at, Other path is to make a Royale App that consume the new WP
REST API, but that should happen as Royale gets more expression options,
since right now it can't compete with a great WP theme that will has a
great design. For me the right step in our actual situation is to create a
showcase section in the site and in the future recheck to see if we still
want Wordpress or we can go with some custom website build in Royale




2017-09-20 19:36 GMT+02:00 Erik de Bruin :

> > I think if we grab a domain and donate it to the ASF, that it can't be
> > hosted on non-ASF hardware.  That would need to be verified.
> > Maybe it would be better for the Royale PMC to approve Royale.xx as a
> > third-party domain under Carlos's control.  I think that's allowed.  The
> > policy [1] says that "in general" it is NOT allowed, but "in general"
> > implies it isn't a hard and fast rule.
> >
> > IMO, things under the PMC's control have certain obligations.  It has to
> > be sustainable by "anyone".  How many folks know how to edit WordPress
> > themes?  I don't.  I always choose one of their default themes.  It might
> > have to be hosted or host-able by Apache Infra, and I don't know if they
> > are ok with WordPress.
> >
>
> That is an awful lot of rules that seem to work against the creativity of
> the project...
>
> EdB
>
>
>
> --
> Ix Multimedia Software
>
> Jan Luykenstraat 27
> 3521 VB Utrecht
>
> T. 06-51952295
> I. www.ixsoftware.nl
>



-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Conocenos en 1 minuto! 


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: [DISCUSS] Building the brand for Royale

[Alex Harui]

True, that's a lot of rules.  Part of that is because we owe our hosts
(the ASF) some "props".

But that may be why it is easier for us to approve Carlos to do what we
wants outside the project.  It will free him most of these rules.  AIUI,
the only rules would then be:
1) make sure Apache is mentioned often enough
2) make sure there are enough links back to royale.apache.org
3) make sure he doesn't promote his company more than the project. (I
think he is allowed to say the site is hosted by his company and some
promotional info).

Thoughts?
-Alex

On 9/20/17, 10:36 AM, "Erik de Bruin"  wrote:

>> I think if we grab a domain and donate it to the ASF, that it can't be
>> hosted on non-ASF hardware.  That would need to be verified.
>> Maybe it would be better for the Royale PMC to approve Royale.xx as a
>> third-party domain under Carlos's control.  I think that's allowed.  The
>> policy [1] says that "in general" it is NOT allowed, but "in general"
>> implies it isn't a hard and fast rule.
>>
>> IMO, things under the PMC's control have certain obligations.  It has to
>> be sustainable by "anyone".  How many folks know how to edit WordPress
>> themes?  I don't.  I always choose one of their default themes.  It
>>might
>> have to be hosted or host-able by Apache Infra, and I don't know if they
>> are ok with WordPress.
>>
>
>That is an awful lot of rules that seem to work against the creativity of
>the project...
>
>EdB
>
>
>
>-- 
>Ix Multimedia Software
>
>Jan Luykenstraat 27
>3521 VB Utrecht
>
>T. 06-51952295
>I. 
>https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl&data=
>02%7C01%7C%7Ceb4bfa47a0da41fe511b08d5004e3980%7Cfa7b1b5a7b34438794aed2c178
>decee1%7C0%7C0%7C636415258339861760&sdata=K%2FKg9eeTxMwS%2BsxE7xGAXU6KlhtQ
>sQNLKnv3gG81OKs%3D&reserved=0

Re: [DISCUSS] Building the brand for Royale

[Erik de Bruin]

> I think if we grab a domain and donate it to the ASF, that it can't be
> hosted on non-ASF hardware.  That would need to be verified.
> Maybe it would be better for the Royale PMC to approve Royale.xx as a
> third-party domain under Carlos's control.  I think that's allowed.  The
> policy [1] says that "in general" it is NOT allowed, but "in general"
> implies it isn't a hard and fast rule.
>
> IMO, things under the PMC's control have certain obligations.  It has to
> be sustainable by "anyone".  How many folks know how to edit WordPress
> themes?  I don't.  I always choose one of their default themes.  It might
> have to be hosted or host-able by Apache Infra, and I don't know if they
> are ok with WordPress.
>

That is an awful lot of rules that seem to work against the creativity of
the project...

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [DISCUSS] Building the brand for Royale

[OmPrakash Muppirala]

I would stay away from WordPress just because of all the security issues
and maintenance required.

Github pages should be a better place.

Thanks,
Om

On Sep 20, 2017 10:26 AM, "Alex Harui"  wrote:

> Hmm.
>
> I think if we grab a domain and donate it to the ASF, that it can't be
> hosted on non-ASF hardware.  That would need to be verified.
> Maybe it would be better for the Royale PMC to approve Royale.xx as a
> third-party domain under Carlos's control.  I think that's allowed.  The
> policy [1] says that "in general" it is NOT allowed, but "in general"
> implies it isn't a hard and fast rule.
>
> IMO, things under the PMC's control have certain obligations.  It has to
> be sustainable by "anyone".  How many folks know how to edit WordPress
> themes?  I don't.  I always choose one of their default themes.  It might
> have to be hosted or host-able by Apache Infra, and I don't know if they
> are ok with WordPress.
>
> Personally, I want to be able to stick FlexJS apps in our web presence.
> Honestly, I'd actually like to see our entire web presence be built in
> FlexJS.  It would truly be "eating our own dog food".  Yes, I know that
> mostly static pages aren't a great match for FlexJS/Royale, but in the
> end, shouldn't all of our web presence be dynamic?
>
> My 2 cents,
> -Alex
>
> [1] http://www.apache.org/foundation/marks/domains.html
>
> On 9/20/17, 10:02 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> 
> wrote:
>
> >Hi Alex,
> >
> >that's my bet. To make a good website I proposed to make it in Wordpress
> >since is what I have some expertise in that field (If I'm the person in
> >charge to make it happen). All the team can as well have an account in the
> >WP dash board to be able to post and share content in a easy way.
> >
> >WP will gave as the landing and some pages that would be useful for
> >convenience. But I think, as well, to link directly to the resources in
> >the
> >apache infrastructure in the main menu of the site just as we do now
> >(code,
> >GitHub, wiki, links to our mailing lists, releases, binaries, and so on)
> >
> >For domain registration I'd prefer .io since is very popular today, but
> >.as
> >seems ok for me as well.
> >I think Erik proposed to register the domain for us, so I think is ok for
> >me that he makes the registration. Maybe we could do it as soon as the
> >board approve the new TLP and name.
> >
> >I can host the site in CO servers with the rest of our websites, to
> >support
> >as well this change and initiative. Again I'll be waiting for board
> >approval to start working. I'm assuming here that you guys trust me to
> >make
> >this website and branding work, of course.
> >
> >So maybe we could make a thread to select from Royale.io and Royale.as,
> >and
> >of course if price for .io is very high we could go with .as if it's more
> >low.
> >
> >
> >
> >
> >2017-09-20 18:44 GMT+02:00 Alex Harui :
> >
> >> Hi Carlos,
> >>
> >> We can go grab some royale. domains.  Apache will have some rules
> >> about what can go on them.  At the worst it will have to be a straight
> >> redirect to royale.apache.org, but I think we might be able to have at
> >> least a landing page.  I think the goal is that Apache wants strong
> >> association with a project's web presence.  Even on a royale.foo landing
> >> page, the first mention of Royale probably has to be "Apache Royale".
> >>
> >> But also, I am hopeful we will be using GitBox and thus GitHub will be
> >>our
> >> hub of activity.  And I think we should use GitHub pages and build a
> >>solid
> >> web presence there, again within Apache's rules.
> >>
> >> Royale.io is for sale.  We could ask what the price is.
> >> Royale.as appears to be unregistered.
> >>
> >> My 2 cents,
> >> -Alex
> >>
> >> On 9/20/17, 8:31 AM, "carlos.rov...@gmail.com on behalf of Carlos
> >>Rovira"
> >> 
> >> wrote:
> >>
> >> >Hi,
> >> >
> >> >as Alex and Dave said, we should wait for board approval.
> >> >
> >> >@Harbs, I was using "xxx" to refer to "whatever domain extension out
> >>there
> >> >that would fit for us" ;)
> >> >
> >> >@Dave, I understand that we should use the apache domain for the
> >>service
> >> >apache provide (i.e: store code, mailing list, releases...), but as
> >>many
> >> >other projects out there, I suppose we should as well have an external
> >> >tools or domains that serve our purpose. In the same way we have  some
> >> >external servers or tools actually.
> >> >For example, we could have a cool name domain that points to a website
> >>and
> >> >there refer to the apache resources. If that option should go against
> >> >apache rules, that would be strange for me, and would certainly be
> >> >hopeless
> >> >to work in and organization with such limitations.
> >> >
> >> >Thanks
> >> >
> >> >
> >> >2017-09-20 16:44 GMT+02:00 Tomislav Pokrajcic :
> >> >
> >> >> Guys, congrats for selecting the new project name.
> >> >> Still not sure how Royale resonates with me, but like it much more
> >>than
> >> >> the 1st runner

Re: [DISCUSS] Building the brand for Royale

[Alex Harui]

Hmm.  

I think if we grab a domain and donate it to the ASF, that it can't be
hosted on non-ASF hardware.  That would need to be verified.
Maybe it would be better for the Royale PMC to approve Royale.xx as a
third-party domain under Carlos's control.  I think that's allowed.  The
policy [1] says that "in general" it is NOT allowed, but "in general"
implies it isn't a hard and fast rule.

IMO, things under the PMC's control have certain obligations.  It has to
be sustainable by "anyone".  How many folks know how to edit WordPress
themes?  I don't.  I always choose one of their default themes.  It might
have to be hosted or host-able by Apache Infra, and I don't know if they
are ok with WordPress.

Personally, I want to be able to stick FlexJS apps in our web presence.
Honestly, I'd actually like to see our entire web presence be built in
FlexJS.  It would truly be "eating our own dog food".  Yes, I know that
mostly static pages aren't a great match for FlexJS/Royale, but in the
end, shouldn't all of our web presence be dynamic?

My 2 cents,
-Alex

[1] http://www.apache.org/foundation/marks/domains.html

On 9/20/17, 10:02 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi Alex,
>
>that's my bet. To make a good website I proposed to make it in Wordpress
>since is what I have some expertise in that field (If I'm the person in
>charge to make it happen). All the team can as well have an account in the
>WP dash board to be able to post and share content in a easy way.
>
>WP will gave as the landing and some pages that would be useful for
>convenience. But I think, as well, to link directly to the resources in
>the
>apache infrastructure in the main menu of the site just as we do now
>(code,
>GitHub, wiki, links to our mailing lists, releases, binaries, and so on)
>
>For domain registration I'd prefer .io since is very popular today, but
>.as
>seems ok for me as well.
>I think Erik proposed to register the domain for us, so I think is ok for
>me that he makes the registration. Maybe we could do it as soon as the
>board approve the new TLP and name.
>
>I can host the site in CO servers with the rest of our websites, to
>support
>as well this change and initiative. Again I'll be waiting for board
>approval to start working. I'm assuming here that you guys trust me to
>make
>this website and branding work, of course.
>
>So maybe we could make a thread to select from Royale.io and Royale.as,
>and
>of course if price for .io is very high we could go with .as if it's more
>low.
>
>
>
>
>2017-09-20 18:44 GMT+02:00 Alex Harui :
>
>> Hi Carlos,
>>
>> We can go grab some royale. domains.  Apache will have some rules
>> about what can go on them.  At the worst it will have to be a straight
>> redirect to royale.apache.org, but I think we might be able to have at
>> least a landing page.  I think the goal is that Apache wants strong
>> association with a project's web presence.  Even on a royale.foo landing
>> page, the first mention of Royale probably has to be "Apache Royale".
>>
>> But also, I am hopeful we will be using GitBox and thus GitHub will be
>>our
>> hub of activity.  And I think we should use GitHub pages and build a
>>solid
>> web presence there, again within Apache's rules.
>>
>> Royale.io is for sale.  We could ask what the price is.
>> Royale.as appears to be unregistered.
>>
>> My 2 cents,
>> -Alex
>>
>> On 9/20/17, 8:31 AM, "carlos.rov...@gmail.com on behalf of Carlos
>>Rovira"
>> 
>> wrote:
>>
>> >Hi,
>> >
>> >as Alex and Dave said, we should wait for board approval.
>> >
>> >@Harbs, I was using "xxx" to refer to "whatever domain extension out
>>there
>> >that would fit for us" ;)
>> >
>> >@Dave, I understand that we should use the apache domain for the
>>service
>> >apache provide (i.e: store code, mailing list, releases...), but as
>>many
>> >other projects out there, I suppose we should as well have an external
>> >tools or domains that serve our purpose. In the same way we have  some
>> >external servers or tools actually.
>> >For example, we could have a cool name domain that points to a website
>>and
>> >there refer to the apache resources. If that option should go against
>> >apache rules, that would be strange for me, and would certainly be
>> >hopeless
>> >to work in and organization with such limitations.
>> >
>> >Thanks
>> >
>> >
>> >2017-09-20 16:44 GMT+02:00 Tomislav Pokrajcic :
>> >
>> >> Guys, congrats for selecting the new project name.
>> >> Still not sure how Royale resonates with me, but like it much more
>>than
>> >> the 1st runner up.
>> >> Non English speakers would pretty often confuse beads with beds and
>>job
>> >> ads might sound strange.
>> >> Just imagine:
>> >> "Looking for an amazing Beads expert to join our team."
>> >> :)
>> >>
>> >> Cheers,
>> >>
>> >> Tom
>> >>
>> >>
>> >> On 20.9.2017. 15:45, Dave Fisher wrote:
>> >>
>> >>> As an Apache project the domain would be:
>> >>>
>> >>> Royale.apache.org
>> >>>
>> >>> I can write a long discussion about pol

Re: [DISCUSS] Building the brand for Royale

[Carlos Rovira]

Hi Piotr,

as you said, I'll go for WP, but we can point to some GitHub pages if we
need. That would be more clear as we start the website development

2017-09-20 18:56 GMT+02:00 Piotr Zarzycki :

> I think Carlos's idea with using wordpress can be better one. He can build
> based on that system our website much faster. I don't think we will have so
> much possibility visually using github pages.
>
> Although in githubpages I would see Olaf's documentation [1].
>
> [1] https://github.com/ok-at-github/flexjs-docs/wiki
>
> Thanks, Piotr
>
> 2017-09-20 18:44 GMT+02:00 Alex Harui :
>
> > Hi Carlos,
> >
> > We can go grab some royale. domains.  Apache will have some rules
> > about what can go on them.  At the worst it will have to be a straight
> > redirect to royale.apache.org, but I think we might be able to have at
> > least a landing page.  I think the goal is that Apache wants strong
> > association with a project's web presence.  Even on a royale.foo landing
> > page, the first mention of Royale probably has to be "Apache Royale".
> >
> > But also, I am hopeful we will be using GitBox and thus GitHub will be
> our
> > hub of activity.  And I think we should use GitHub pages and build a
> solid
> > web presence there, again within Apache's rules.
> >
> > Royale.io is for sale.  We could ask what the price is.
> > Royale.as appears to be unregistered.
> >
> > My 2 cents,
> > -Alex
> >
> > On 9/20/17, 8:31 AM, "carlos.rov...@gmail.com on behalf of Carlos
> Rovira"
> > 
> > wrote:
> >
> > >Hi,
> > >
> > >as Alex and Dave said, we should wait for board approval.
> > >
> > >@Harbs, I was using "xxx" to refer to "whatever domain extension out
> there
> > >that would fit for us" ;)
> > >
> > >@Dave, I understand that we should use the apache domain for the service
> > >apache provide (i.e: store code, mailing list, releases...), but as many
> > >other projects out there, I suppose we should as well have an external
> > >tools or domains that serve our purpose. In the same way we have  some
> > >external servers or tools actually.
> > >For example, we could have a cool name domain that points to a website
> and
> > >there refer to the apache resources. If that option should go against
> > >apache rules, that would be strange for me, and would certainly be
> > >hopeless
> > >to work in and organization with such limitations.
> > >
> > >Thanks
> > >
> > >
> > >2017-09-20 16:44 GMT+02:00 Tomislav Pokrajcic :
> > >
> > >> Guys, congrats for selecting the new project name.
> > >> Still not sure how Royale resonates with me, but like it much more
> than
> > >> the 1st runner up.
> > >> Non English speakers would pretty often confuse beads with beds and
> job
> > >> ads might sound strange.
> > >> Just imagine:
> > >> "Looking for an amazing Beads expert to join our team."
> > >> :)
> > >>
> > >> Cheers,
> > >>
> > >> Tom
> > >>
> > >>
> > >> On 20.9.2017. 15:45, Dave Fisher wrote:
> > >>
> > >>> As an Apache project the domain would be:
> > >>>
> > >>> Royale.apache.org
> > >>>
> > >>> I can write a long discussion about policy later but there are
> reasons,
> > >>> requirements, approvals around use of other domains.
> > >>>
> > >>> I know everyone is enthusiastic but let's get approved by the board
> > >>>first.
> > >>>
> > >>> Regards,
> > >>> Dave
> > >>>
> > >>> Sent from my iPhone
> > >>>
> > >>> On Sep 20, 2017, at 6:33 AM, Erik de Bruin 
> wrote:
> > >>>
> > >>> * Domain: We must find a good and simple domain for Royale. I think
> if
> > >>>we
> > > can find something short like "royale.XXX" would be great over
> > > "apacheroyale.XXX".
> > >
> > > .com, .org, .net, .io etc. all seem to be either in use or squatted
> >  upon.
> >  Am I forgetting memorable TLP extensions? I assume we don't want
> > anything
> >  like 'royale.foundation' or any fancy extensions like that, right?
> > 
> >  Are we considering extended names, like 'royaleframework' as well?
> > 
> >  I can register anything we decide and sponsor until a foundation
> takes
> >  over
> >  and then transfer the domain.
> > 
> >  Thanks,
> > 
> >  EdB
> > 
> > 
> > 
> >  --
> >  Ix Multimedia Software
> > 
> >  Jan Luykenstraat 27
> >  3521 VB Utrecht
> > 
> >  T. 06-51952295
> >  I.
> > https://na01.safelinks.protection.outlook.com/?url=
> > www.ixsoftware.nl&da
> > ta=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
> > ad9e%7Cfa7b1b5a7b34438794ae
> > d2c178decee1%7C0%7C0%7C636415182976392829&sdata=
> > LDQFlmzgCBkY3NyhB%2BZ1W
> > bJnC6FcmPRRXhB7Ltggre8%3D&reserved=0
> > 
> > >>>
> > >>>
> > >>
> > >
> > >
> > >--
> > >
> > > > http%3A%2F%2Fwww.codeo
> > >scopic.com&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
> > ad9e%7Cfa7b1b5a7b
> > >34438794aed2c178decee1%7C0%7C0%7C636415182976392829&
> > sdata=snzdFt3cDT4GcWGa
> > >NJF3dFIfdKedU5jF%2FBM1XqrkQHY%3D&reserved=0>
> > 

Re: [DISCUSS] Building the brand for Royale

[Carlos Rovira]

Hi Alex,

that's my bet. To make a good website I proposed to make it in Wordpress
since is what I have some expertise in that field (If I'm the person in
charge to make it happen). All the team can as well have an account in the
WP dash board to be able to post and share content in a easy way.

WP will gave as the landing and some pages that would be useful for
convenience. But I think, as well, to link directly to the resources in the
apache infrastructure in the main menu of the site just as we do now (code,
GitHub, wiki, links to our mailing lists, releases, binaries, and so on)

For domain registration I'd prefer .io since is very popular today, but .as
seems ok for me as well.
I think Erik proposed to register the domain for us, so I think is ok for
me that he makes the registration. Maybe we could do it as soon as the
board approve the new TLP and name.

I can host the site in CO servers with the rest of our websites, to support
as well this change and initiative. Again I'll be waiting for board
approval to start working. I'm assuming here that you guys trust me to make
this website and branding work, of course.

So maybe we could make a thread to select from Royale.io and Royale.as, and
of course if price for .io is very high we could go with .as if it's more
low.




2017-09-20 18:44 GMT+02:00 Alex Harui :

> Hi Carlos,
>
> We can go grab some royale. domains.  Apache will have some rules
> about what can go on them.  At the worst it will have to be a straight
> redirect to royale.apache.org, but I think we might be able to have at
> least a landing page.  I think the goal is that Apache wants strong
> association with a project's web presence.  Even on a royale.foo landing
> page, the first mention of Royale probably has to be "Apache Royale".
>
> But also, I am hopeful we will be using GitBox and thus GitHub will be our
> hub of activity.  And I think we should use GitHub pages and build a solid
> web presence there, again within Apache's rules.
>
> Royale.io is for sale.  We could ask what the price is.
> Royale.as appears to be unregistered.
>
> My 2 cents,
> -Alex
>
> On 9/20/17, 8:31 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> 
> wrote:
>
> >Hi,
> >
> >as Alex and Dave said, we should wait for board approval.
> >
> >@Harbs, I was using "xxx" to refer to "whatever domain extension out there
> >that would fit for us" ;)
> >
> >@Dave, I understand that we should use the apache domain for the service
> >apache provide (i.e: store code, mailing list, releases...), but as many
> >other projects out there, I suppose we should as well have an external
> >tools or domains that serve our purpose. In the same way we have  some
> >external servers or tools actually.
> >For example, we could have a cool name domain that points to a website and
> >there refer to the apache resources. If that option should go against
> >apache rules, that would be strange for me, and would certainly be
> >hopeless
> >to work in and organization with such limitations.
> >
> >Thanks
> >
> >
> >2017-09-20 16:44 GMT+02:00 Tomislav Pokrajcic :
> >
> >> Guys, congrats for selecting the new project name.
> >> Still not sure how Royale resonates with me, but like it much more than
> >> the 1st runner up.
> >> Non English speakers would pretty often confuse beads with beds and job
> >> ads might sound strange.
> >> Just imagine:
> >> "Looking for an amazing Beads expert to join our team."
> >> :)
> >>
> >> Cheers,
> >>
> >> Tom
> >>
> >>
> >> On 20.9.2017. 15:45, Dave Fisher wrote:
> >>
> >>> As an Apache project the domain would be:
> >>>
> >>> Royale.apache.org
> >>>
> >>> I can write a long discussion about policy later but there are reasons,
> >>> requirements, approvals around use of other domains.
> >>>
> >>> I know everyone is enthusiastic but let's get approved by the board
> >>>first.
> >>>
> >>> Regards,
> >>> Dave
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On Sep 20, 2017, at 6:33 AM, Erik de Bruin  wrote:
> >>>
> >>> * Domain: We must find a good and simple domain for Royale. I think if
> >>>we
> > can find something short like "royale.XXX" would be great over
> > "apacheroyale.XXX".
> >
> > .com, .org, .net, .io etc. all seem to be either in use or squatted
>  upon.
>  Am I forgetting memorable TLP extensions? I assume we don't want
> anything
>  like 'royale.foundation' or any fancy extensions like that, right?
> 
>  Are we considering extended names, like 'royaleframework' as well?
> 
>  I can register anything we decide and sponsor until a foundation takes
>  over
>  and then transfer the domain.
> 
>  Thanks,
> 
>  EdB
> 
> 
> 
>  --
>  Ix Multimedia Software
> 
>  Jan Luykenstraat 27
>  3521 VB Utrecht
> 
>  T. 06-51952295
>  I.
> https://na01.safelinks.protection.outlook.com/?url=
> www.ixsoftware.nl&da
> ta=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
> ad9e%7Cfa7b1b5a7b3443879

Re: [DISCUSS] Building the brand for Royale

[Piotr Zarzycki]

I think Carlos's idea with using wordpress can be better one. He can build
based on that system our website much faster. I don't think we will have so
much possibility visually using github pages.

Although in githubpages I would see Olaf's documentation [1].

[1] https://github.com/ok-at-github/flexjs-docs/wiki

Thanks, Piotr

2017-09-20 18:44 GMT+02:00 Alex Harui :

> Hi Carlos,
>
> We can go grab some royale. domains.  Apache will have some rules
> about what can go on them.  At the worst it will have to be a straight
> redirect to royale.apache.org, but I think we might be able to have at
> least a landing page.  I think the goal is that Apache wants strong
> association with a project's web presence.  Even on a royale.foo landing
> page, the first mention of Royale probably has to be "Apache Royale".
>
> But also, I am hopeful we will be using GitBox and thus GitHub will be our
> hub of activity.  And I think we should use GitHub pages and build a solid
> web presence there, again within Apache's rules.
>
> Royale.io is for sale.  We could ask what the price is.
> Royale.as appears to be unregistered.
>
> My 2 cents,
> -Alex
>
> On 9/20/17, 8:31 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
> 
> wrote:
>
> >Hi,
> >
> >as Alex and Dave said, we should wait for board approval.
> >
> >@Harbs, I was using "xxx" to refer to "whatever domain extension out there
> >that would fit for us" ;)
> >
> >@Dave, I understand that we should use the apache domain for the service
> >apache provide (i.e: store code, mailing list, releases...), but as many
> >other projects out there, I suppose we should as well have an external
> >tools or domains that serve our purpose. In the same way we have  some
> >external servers or tools actually.
> >For example, we could have a cool name domain that points to a website and
> >there refer to the apache resources. If that option should go against
> >apache rules, that would be strange for me, and would certainly be
> >hopeless
> >to work in and organization with such limitations.
> >
> >Thanks
> >
> >
> >2017-09-20 16:44 GMT+02:00 Tomislav Pokrajcic :
> >
> >> Guys, congrats for selecting the new project name.
> >> Still not sure how Royale resonates with me, but like it much more than
> >> the 1st runner up.
> >> Non English speakers would pretty often confuse beads with beds and job
> >> ads might sound strange.
> >> Just imagine:
> >> "Looking for an amazing Beads expert to join our team."
> >> :)
> >>
> >> Cheers,
> >>
> >> Tom
> >>
> >>
> >> On 20.9.2017. 15:45, Dave Fisher wrote:
> >>
> >>> As an Apache project the domain would be:
> >>>
> >>> Royale.apache.org
> >>>
> >>> I can write a long discussion about policy later but there are reasons,
> >>> requirements, approvals around use of other domains.
> >>>
> >>> I know everyone is enthusiastic but let's get approved by the board
> >>>first.
> >>>
> >>> Regards,
> >>> Dave
> >>>
> >>> Sent from my iPhone
> >>>
> >>> On Sep 20, 2017, at 6:33 AM, Erik de Bruin  wrote:
> >>>
> >>> * Domain: We must find a good and simple domain for Royale. I think if
> >>>we
> > can find something short like "royale.XXX" would be great over
> > "apacheroyale.XXX".
> >
> > .com, .org, .net, .io etc. all seem to be either in use or squatted
>  upon.
>  Am I forgetting memorable TLP extensions? I assume we don't want
> anything
>  like 'royale.foundation' or any fancy extensions like that, right?
> 
>  Are we considering extended names, like 'royaleframework' as well?
> 
>  I can register anything we decide and sponsor until a foundation takes
>  over
>  and then transfer the domain.
> 
>  Thanks,
> 
>  EdB
> 
> 
> 
>  --
>  Ix Multimedia Software
> 
>  Jan Luykenstraat 27
>  3521 VB Utrecht
> 
>  T. 06-51952295
>  I.
> https://na01.safelinks.protection.outlook.com/?url=
> www.ixsoftware.nl&da
> ta=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
> ad9e%7Cfa7b1b5a7b34438794ae
> d2c178decee1%7C0%7C0%7C636415182976392829&sdata=
> LDQFlmzgCBkY3NyhB%2BZ1W
> bJnC6FcmPRRXhB7Ltggre8%3D&reserved=0
> 
> >>>
> >>>
> >>
> >
> >
> >--
> >
> > http%3A%2F%2Fwww.codeo
> >scopic.com&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
> ad9e%7Cfa7b1b5a7b
> >34438794aed2c178decee1%7C0%7C0%7C636415182976392829&
> sdata=snzdFt3cDT4GcWGa
> >NJF3dFIfdKedU5jF%2FBM1XqrkQHY%3D&reserved=0>
> >
> >Carlos Rovira
> >
> >Director General
> >
> >M: +34 607 22 60 05
> >
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeos
> >copic.com&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
> ad9e%7Cfa7b1b5a7b3
> >4438794aed2c178decee1%7C0%7C0%7C636415182976392829&
> sdata=snzdFt3cDT4GcWGaN
> >JF3dFIfdKedU5jF%2FBM1XqrkQHY%3D&reserved=0
> >
> >https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.avant2
> >.es&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003c
> 

Re: [DISCUSS] Building the brand for Royale

[Alex Harui]

Hi Carlos,

We can go grab some royale. domains.  Apache will have some rules
about what can go on them.  At the worst it will have to be a straight
redirect to royale.apache.org, but I think we might be able to have at
least a landing page.  I think the goal is that Apache wants strong
association with a project's web presence.  Even on a royale.foo landing
page, the first mention of Royale probably has to be "Apache Royale".

But also, I am hopeful we will be using GitBox and thus GitHub will be our
hub of activity.  And I think we should use GitHub pages and build a solid
web presence there, again within Apache's rules.

Royale.io is for sale.  We could ask what the price is.
Royale.as appears to be unregistered.

My 2 cents,
-Alex

On 9/20/17, 8:31 AM, "carlos.rov...@gmail.com on behalf of Carlos Rovira"
 wrote:

>Hi,
>
>as Alex and Dave said, we should wait for board approval.
>
>@Harbs, I was using "xxx" to refer to "whatever domain extension out there
>that would fit for us" ;)
>
>@Dave, I understand that we should use the apache domain for the service
>apache provide (i.e: store code, mailing list, releases...), but as many
>other projects out there, I suppose we should as well have an external
>tools or domains that serve our purpose. In the same way we have  some
>external servers or tools actually.
>For example, we could have a cool name domain that points to a website and
>there refer to the apache resources. If that option should go against
>apache rules, that would be strange for me, and would certainly be
>hopeless
>to work in and organization with such limitations.
>
>Thanks
>
>
>2017-09-20 16:44 GMT+02:00 Tomislav Pokrajcic :
>
>> Guys, congrats for selecting the new project name.
>> Still not sure how Royale resonates with me, but like it much more than
>> the 1st runner up.
>> Non English speakers would pretty often confuse beads with beds and job
>> ads might sound strange.
>> Just imagine:
>> "Looking for an amazing Beads expert to join our team."
>> :)
>>
>> Cheers,
>>
>> Tom
>>
>>
>> On 20.9.2017. 15:45, Dave Fisher wrote:
>>
>>> As an Apache project the domain would be:
>>>
>>> Royale.apache.org
>>>
>>> I can write a long discussion about policy later but there are reasons,
>>> requirements, approvals around use of other domains.
>>>
>>> I know everyone is enthusiastic but let's get approved by the board
>>>first.
>>>
>>> Regards,
>>> Dave
>>>
>>> Sent from my iPhone
>>>
>>> On Sep 20, 2017, at 6:33 AM, Erik de Bruin  wrote:
>>>
>>> * Domain: We must find a good and simple domain for Royale. I think if
>>>we
> can find something short like "royale.XXX" would be great over
> "apacheroyale.XXX".
>
> .com, .org, .net, .io etc. all seem to be either in use or squatted
 upon.
 Am I forgetting memorable TLP extensions? I assume we don't want
anything
 like 'royale.foundation' or any fancy extensions like that, right?

 Are we considering extended names, like 'royaleframework' as well?

 I can register anything we decide and sponsor until a foundation takes
 over
 and then transfer the domain.

 Thanks,

 EdB



 --
 Ix Multimedia Software

 Jan Luykenstraat 27
 3521 VB Utrecht

 T. 06-51952295
 I. 
https://na01.safelinks.protection.outlook.com/?url=www.ixsoftware.nl&da
ta=02%7C01%7C%7Cab05fef4543644f67e2c08d5003cad9e%7Cfa7b1b5a7b34438794ae
d2c178decee1%7C0%7C0%7C636415182976392829&sdata=LDQFlmzgCBkY3NyhB%2BZ1W
bJnC6FcmPRRXhB7Ltggre8%3D&reserved=0

>>>
>>>
>>
>
>
>-- 
>
>scopic.com&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003cad9e%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636415182976392829&sdata=snzdFt3cDT4GcWGa
>NJF3dFIfdKedU5jF%2FBM1XqrkQHY%3D&reserved=0>
>
>Carlos Rovira
>
>Director General
>
>M: +34 607 22 60 05
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>copic.com&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003cad9e%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636415182976392829&sdata=snzdFt3cDT4GcWGaN
>JF3dFIfdKedU5jF%2FBM1XqrkQHY%3D&reserved=0
>
>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.avant2
>.es&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003cad9e%7Cfa7b1b5a7b3443879
>4aed2c178decee1%7C0%7C0%7C636415182976392829&sdata=8SXVcRe3E%2FLVCSIODbbnL
>wsN3AIsG4djE9F0VhpX8H0%3D&reserved=0
>
>
>Conocenos en 1 minuto!
>%2FP2IEAYDG5HU&data=02%7C01%7C%7Cab05fef4543644f67e2c08d5003cad9e%7Cfa7b1b
>5a7b34438794aed2c178decee1%7C0%7C0%7C636415182976392829&sdata=%2FWlOcenx8I
>qTu2PYyD%2FBiChaLHKstZC0eLlmb5gpmng%3D&reserved=0>
>
>
>Este mensaje se dirige exclusivamente a su destinatario y puede contener
>información privilegiada o confidencial. Si ha recibido este mensaje por
>error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
>

Re: [DISCUSS] Building the brand for Royale

[Carlos Rovira]

Hi,

as Alex and Dave said, we should wait for board approval.

@Harbs, I was using "xxx" to refer to "whatever domain extension out there
that would fit for us" ;)

@Dave, I understand that we should use the apache domain for the service
apache provide (i.e: store code, mailing list, releases...), but as many
other projects out there, I suppose we should as well have an external
tools or domains that serve our purpose. In the same way we have  some
external servers or tools actually.
For example, we could have a cool name domain that points to a website and
there refer to the apache resources. If that option should go against
apache rules, that would be strange for me, and would certainly be hopeless
to work in and organization with such limitations.

Thanks


2017-09-20 16:44 GMT+02:00 Tomislav Pokrajcic :

> Guys, congrats for selecting the new project name.
> Still not sure how Royale resonates with me, but like it much more than
> the 1st runner up.
> Non English speakers would pretty often confuse beads with beds and job
> ads might sound strange.
> Just imagine:
> "Looking for an amazing Beads expert to join our team."
> :)
>
> Cheers,
>
> Tom
>
>
> On 20.9.2017. 15:45, Dave Fisher wrote:
>
>> As an Apache project the domain would be:
>>
>> Royale.apache.org
>>
>> I can write a long discussion about policy later but there are reasons,
>> requirements, approvals around use of other domains.
>>
>> I know everyone is enthusiastic but let's get approved by the board first.
>>
>> Regards,
>> Dave
>>
>> Sent from my iPhone
>>
>> On Sep 20, 2017, at 6:33 AM, Erik de Bruin  wrote:
>>
>> * Domain: We must find a good and simple domain for Royale. I think if we
 can find something short like "royale.XXX" would be great over
 "apacheroyale.XXX".

 .com, .org, .net, .io etc. all seem to be either in use or squatted
>>> upon.
>>> Am I forgetting memorable TLP extensions? I assume we don't want anything
>>> like 'royale.foundation' or any fancy extensions like that, right?
>>>
>>> Are we considering extended names, like 'royaleframework' as well?
>>>
>>> I can register anything we decide and sponsor until a foundation takes
>>> over
>>> and then transfer the domain.
>>>
>>> Thanks,
>>>
>>> EdB
>>>
>>>
>>>
>>> --
>>> Ix Multimedia Software
>>>
>>> Jan Luykenstraat 27
>>> 3521 VB Utrecht
>>>
>>> T. 06-51952295
>>> I. www.ixsoftware.nl
>>>
>>
>>
>


-- 



Carlos Rovira

Director General

M: +34 607 22 60 05

http://www.codeoscopic.com

http://www.avant2.es


Conocenos en 1 minuto! 


Este mensaje se dirige exclusivamente a su destinatario y puede contener
información privilegiada o confidencial. Si ha recibido este mensaje por
error, le rogamos que nos lo comunique inmediatamente por esta misma vía y
proceda a su destrucción.

De la vigente Ley Orgánica de Protección de Datos (15/1999), le comunicamos
que sus datos forman parte de un fichero cuyo responsable es CODEOSCOPIC
S.A. La finalidad de dicho tratamiento es facilitar la prestación del
servicio o información solicitados, teniendo usted derecho de acceso,
rectificación, cancelación y oposición de sus datos dirigiéndose a nuestras
oficinas c/ Paseo de la Habana 9-11, 28036, Madrid con la documentación
necesaria.

Re: [DISCUSS] Building the brand for Royale

[Tomislav Pokrajcic]

Guys, congrats for selecting the new project name.
Still not sure how Royale resonates with me, but like it much more than 
the 1st runner up.
Non English speakers would pretty often confuse beads with beds and job 
ads might sound strange.

Just imagine:
"Looking for an amazing Beads expert to join our team."
:)

Cheers,

Tom

On 20.9.2017. 15:45, Dave Fisher wrote:

As an Apache project the domain would be:

Royale.apache.org

I can write a long discussion about policy later but there are reasons, 
requirements, approvals around use of other domains.

I know everyone is enthusiastic but let's get approved by the board first.

Regards,
Dave

Sent from my iPhone

On Sep 20, 2017, at 6:33 AM, Erik de Bruin  wrote:


* Domain: We must find a good and simple domain for Royale. I think if we
can find something short like "royale.XXX" would be great over
"apacheroyale.XXX".


.com, .org, .net, .io etc. all seem to be either in use or squatted upon.
Am I forgetting memorable TLP extensions? I assume we don't want anything
like 'royale.foundation' or any fancy extensions like that, right?

Are we considering extended names, like 'royaleframework' as well?

I can register anything we decide and sponsor until a foundation takes over
and then transfer the domain.

Thanks,

EdB



--
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

Re: [DISCUSS] Building the brand for Royale

[Dave Fisher]

As an Apache project the domain would be:

Royale.apache.org

I can write a long discussion about policy later but there are reasons, 
requirements, approvals around use of other domains.

I know everyone is enthusiastic but let's get approved by the board first.

Regards,
Dave

Sent from my iPhone

On Sep 20, 2017, at 6:33 AM, Erik de Bruin  wrote:

>> 
>> * Domain: We must find a good and simple domain for Royale. I think if we
>> can find something short like "royale.XXX" would be great over
>> "apacheroyale.XXX".
>> 
> 
> .com, .org, .net, .io etc. all seem to be either in use or squatted upon.
> Am I forgetting memorable TLP extensions? I assume we don't want anything
> like 'royale.foundation' or any fancy extensions like that, right?
> 
> Are we considering extended names, like 'royaleframework' as well?
> 
> I can register anything we decide and sponsor until a foundation takes over
> and then transfer the domain.
> 
> Thanks,
> 
> EdB
> 
> 
> 
> -- 
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl

Re: [DISCUSS] Building the brand for Royale

[Harbs]

Definitely not royale.xxx. We’re trying to steer clear of adult sites. :-D

I think an apache.org  site is totally fine.

FWIW, royalesdk.io royalesdk.com , etc. are all 
available.

Harbs

> On Sep 20, 2017, at 1:33 PM, Erik de Bruin  wrote:
> 
>> 
>> * Domain: We must find a good and simple domain for Royale. I think if we
>> can find something short like "royale.XXX" would be great over
>> "apacheroyale.XXX".
>> 
> 
> .com, .org, .net, .io etc. all seem to be either in use or squatted upon.
> Am I forgetting memorable TLP extensions? I assume we don't want anything
> like 'royale.foundation' or any fancy extensions like that, right?
> 
> Are we considering extended names, like 'royaleframework' as well?
> 
> I can register anything we decide and sponsor until a foundation takes over
> and then transfer the domain.
> 
> Thanks,
> 
> EdB
> 
> 
> 
> -- 
> Ix Multimedia Software
> 
> Jan Luykenstraat 27
> 3521 VB Utrecht
> 
> T. 06-51952295
> I. www.ixsoftware.nl

Re: [DISCUSS] Building the brand for Royale

[Erik de Bruin]

>
> * Domain: We must find a good and simple domain for Royale. I think if we
> can find something short like "royale.XXX" would be great over
> "apacheroyale.XXX".
>

.com, .org, .net, .io etc. all seem to be either in use or squatted upon.
Am I forgetting memorable TLP extensions? I assume we don't want anything
like 'royale.foundation' or any fancy extensions like that, right?

Are we considering extended names, like 'royaleframework' as well?

I can register anything we decide and sponsor until a foundation takes over
and then transfer the domain.

Thanks,

EdB



-- 
Ix Multimedia Software

Jan Luykenstraat 27
3521 VB Utrecht

T. 06-51952295
I. www.ixsoftware.nl

[DISCUSS] Building the brand for Royale

[Carlos Rovira]

Hi all,

now that we decided to change our name to Royale. we must to make some
serious work in the next weeks. We talked about:

* Logo: We need to design logo to make Royale attractive at first sight
* Website: A new name, and logo requires a good, clean and beautiful
website that make us be elegible for people searching for a front end
technology
* Domain: We must find a good and simple domain for Royale. I think if we
can find something short like "royale.XXX" would be great over
"apacheroyale.XXX".
(Something I don't know is how will register the domain once selected (and
available), this is something apache will be buying? must be done by us?)
* Social networks: we need to register new accounts for Royale in twitter,
Facebook, and the rest we want.
* ... more? (we'll be looking for the things we need as we progress)

As I stated, I can propose myself to work in website and logo if you all
want me there.
Let me know in order to take this into account in my agenda and make me a
plan.

Thanks



-- 
Carlos Rovira
http://about.me/carlosrovira