You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@royale.apache.org by Carlos Rovira <ca...@apache.org> on 2017/10/24 16:30:15 UTC
Apache Royale static web site
Hi,
just let you know that I tried to create an static version of the preview
site with success. I use this plugin :
https://wordpress.org/plugins/simply-static/
and we can generate all static content with relative or absolute urls. The
final preview site in static is 134mb
Another thing I was searching was to use a WP to Jekyll exporter but this
is not what I wanted since it seems Jekyll is all about markdown and we
want a full html site with all the eye candy JS+CSS resources. In the end,
and thinking more about it, is not what we want since although the site
would be exported ok, we don't want to upload it to the GitHub pages like
we discusses in the other thread due to expose part of the code of a
commercial wp theme.
So, the workflow we can use is: Use the WP backend to enter new content and
modify existing want with ease (this is important is we want people
contributing here). Next, with all changes done, generate a static version
and replace the entire site with a fresh generated static site at
royale.apache.org. and as well route the more friendly domain to this if
board is ok with that.
We can check with apache board or trademarks what they propose about to
create a Wordpress.com account managed by Apache and migrate from my server
to that account, and all this stuff from there, since if I remember some
people said that would be more ok with Apache.I'd end removing my temp
subdomain after this.
What do you think? Can I move this with the people we were talking some
weeks ago?
Let me know in order to start making the next steps
Thanks
--
Carlos Rovira
http://about.me/carlosrovira
Re: Apache Royale static web site
Posted by Dave Fisher <da...@comcast.net>.
Hi -
I already did write an email to trademarks. It is cc’d on private@royale
Regards,
Dave
> On Oct 24, 2017, at 10:19 AM, Carlos Rovira <ca...@codeoscopic.com> wrote:
>
> Thanks Dave,
>
> I'll write an email to trademarks to start with the process. I think is
> better to migrate to WP.com before continue working on content so we can
> detect whatever issue we could get.
>
> Thanks!
>
> Carlos
>
>
>
> 2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>:
>
>> Hi Carlos,
>>
>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>
>> wrote:
>>>
>>> Hi,
>>>
>>> just let you know that I tried to create an static version of the preview
>>> site with success. I use this plugin :
>>> https://wordpress.org/plugins/simply-static/
>>>
>>> and we can generate all static content with relative or absolute urls.
>> The
>>> final preview site in static is 134mb
>>>
>>> Another thing I was searching was to use a WP to Jekyll exporter but this
>>> is not what I wanted since it seems Jekyll is all about markdown and we
>>> want a full html site with all the eye candy JS+CSS resources. In the
>> end,
>>> and thinking more about it, is not what we want since although the site
>>> would be exported ok, we don't want to upload it to the GitHub pages like
>>> we discusses in the other thread due to expose part of the code of a
>>> commercial wp theme.
>>>
>>> So, the workflow we can use is: Use the WP backend to enter new content
>> and
>>> modify existing want with ease (this is important is we want people
>>> contributing here). Next, with all changes done, generate a static
>> version
>>> and replace the entire site with a fresh generated static site at
>>> royale.apache.org. and as well route the more friendly domain to this if
>>> board is ok with that.
>>
>> Yes! External domain royalysdk.org is redirected to royale.apache.org as
>> discussed.
>>
>>>
>>> We can check with apache board or trademarks what they propose about to
>>> create a Wordpress.com account managed by Apache and migrate from my
>> server
>>> to that account, and all this stuff from there, since if I remember some
>>> people said that would be more ok with Apache.I'd end removing my temp
>>> subdomain after this.
>>
>> The advantage of using the Wordpress.com location is twofold:
>>
>> (1) Wordpress keeps security up to date.
>> (2) If something happens to you or your company then we have better access.
>>
>> I suspect though that with the status export method this will not be as
>> great a concern.
>>
>>>
>>> What do you think? Can I move this with the people we were talking some
>>> weeks ago?
>>
>> Either you or I can email Trademarks with the plan.
>>
>> We can then discuss the redirection with Infrastructure and get the site
>> checked in.
>>
>> Regards,
>> Dave
>>
>>>
>>> Let me know in order to start making the next steps
>>>
>>> Thanks
>>>
>>>
>>> --
>>> Carlos Rovira
>>> http://about.me/carlosrovira
>>
>>
>
>
> --
>
> <http://www.codeoscopic.com>
>
> Carlos Rovira
>
> Director General
>
> M: +34 607 22 60 05
>
> http://www.codeoscopic.com
>
>
> Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
>
>
> 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: Apache Royale static web site
Posted by Harbs <ha...@gmail.com>.
Yes. Definitely, our first priority is getting a working site. :-)
> On Oct 24, 2017, at 9:24 PM, Carlos Rovira <ca...@codeoscopic.com> wrote:
>
> That would be an option for the future, but from my point of view, I'll
> prefer to spend that time making some App example to put on showcase, or
> make the "Try it now" App, or working in a Apache Royale Theme, or in any
> feature we need, forms, validation, AMF,...and so on...this could happen
> some years in the future since there's already too much to do.
Re: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Harbs
2017-10-24 20:10 GMT+02:00 Harbs <ha...@gmail.com>:
> Here’s how I see things:
>
> 1. For the immediate, we want a good web presence. If putting the
> WordPress site on wordpress.com <http://wordpress.com/> with a CNAME
> entry pointing to royale.apache.com <http://royale.apache.com/> is the
> fastest way to get there, we should start with that.
>
If we do that, don't need to generate static content, wp.com can serve it
directly.
Static content make the site more fast, but we really don't need with your
solution, so for me is ok.
> 2. We should look into getting a static version of the site, so the site
> can be edited on Github and pushed to royale.apache.com <
> http://royale.apache.com/>. That is more ideal than having private access
> to a WordPress installation.
>
following your point 1, royale.apache.org will be pointing to WP.com so no
need to upload the site.
In the other hand, I continue saying that we really don't need to upload
the site to a repo since is not our business. Our business is to spend our
time working on make Apache Royale source code better and better, so this
is only a tool to expose what we do.
> 3. We should contact greatives and see if they would give us permission to
> reuse the css and js for a static site. (possibly with attribution)
>
That's a good idea, I can contact them and ask for this.
> 4. We should ask trademarks@ and/or legal@ whether the terms (assuming we
> get them) are ok from an Apache perspective.
>
Rigth, I can ask first to trademarks, before asking greatives
> 5. Assuming #4 and #5 work out, we will probably want various pieces of
> our site constructed using this styling i.e. main site, docs, blog (as a
> WordPress installation), examples.
>
That would be an option for the future, but from my point of view, I'll
prefer to spend that time making some App example to put on showcase, or
make the "Try it now" App, or working in a Apache Royale Theme, or in any
feature we need, forms, validation, AMF,...and so on...this could happen
some years in the future since there's already too much to do.
Thanks
Carlos
>
> Harbs
>
> > On Oct 24, 2017, at 8:56 PM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > Hi Dave,
> >
> > I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we
> have the rights to replicate use of that look-and-feel elsewhere? I don't
> understand who owns the creative content.
> >
> > Thoughts?
> > -Alex
> >
> > From: Dave Fisher <da...@comcast.net>>
> > Reply-To: <de...@royale.apache.org>>
> > Date: Tuesday, October 24, 2017 at 10:50 AM
> > To: <de...@royale.apache.org>>
> > Subject: Re: Apache Royale static web site
> >
> > Hi Alex,
> >
> > On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID<
> mailto:aharui@adobe.com.INVALID>> wrote:
> >
> > There is something I don't think I understand. AIUI, at some point, we
> > will want the Apache Royale site to include actual Royale applications,
> > right? And I would think we would want the styling of those applications
> > to be consistent with the rest of the site. So I'm not clear how we will
> > be able to implement the styling/theme of these Royale applications if we
> > don't have rights to the styling. I don't understand how WP themes and
> > commercial licensing works if we want to replicate that user experience
> > outside of WP.
> >
> > We need to examine the static export of the CSS and HTML.
> >
> >
> > If we can use those visuals outside of WP, then why must we continue to
> > use WP to generate the site? I would hope the theme would be implemented
> > as CSS and some templates we could use without WP.
> >
> > We should be able to adapt. Site building in the CMS can get complex if
> needed. For OpenOffice.org<http://OpenOffice.org> we use the legacy html
> pulling out the title and content body and place it within a markdown
> template.
> >
> >
> > Also, if someone wants to patch the site, they can't just offer a patch
> of
> > the HTML right? They would need to figure out where in WP it comes from?
> > Is there a patch process for WP content?
> >
> > Possibly.
> >
> >
> > Sorry if there is some basic thing I am missing.
> >
> > It will get complex first as we figure out how to embed and then it will
> get simplified as we find the best way.
> >
> > Regards,
> > Dave
> >
> >
> >
> > Thanks,
> > -Alex
> >
> > On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
> carlos.rovira@gmail.com> on behalf of Carlos
> > Rovira" <ca...@gmail.com> on
> behalf of
> > carlos.rovira@codeoscopic.com<ma...@codeoscopic.com>>
> wrote:
> >
> > Thanks Dave,
> >
> > I'll write an email to trademarks to start with the process. I think is
> > better to migrate to WP.com<http://WP.com> before continue working on
> content so we can
> > detect whatever issue we could get.
> >
> > Thanks!
> >
> > Carlos
> >
> >
> >
> > 2017-10-24 18:56 GMT+02:00 Dave Fisher <dave2wave@comcast.net<mailto:
> dave2wave@comcast.net>>:
> >
> > Hi Carlos,
> >
> > On Oct 24, 2017, at 9:30 AM, Carlos Rovira <carlosrovira@apache.org<
> mailto:carlosrovira@apache.org>>
> > wrote:
> >
> > Hi,
> >
> > just let you know that I tried to create an static version of the
> > preview
> > site with success. I use this plugin :
> >
> > https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwordpres
> > s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%
> 7Cb448363ee5984b3b3e0f
> > 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636444624020033
> > 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
> >
> > and we can generate all static content with relative or absolute urls.
> > The
> > final preview site in static is 134mb
> >
> > Another thing I was searching was to use a WP to Jekyll exporter but
> > this
> > is not what I wanted since it seems Jekyll is all about markdown and
> > we
> > want a full html site with all the eye candy JS+CSS resources. In the
> > end,
> > and thinking more about it, is not what we want since although the
> > site
> > would be exported ok, we don't want to upload it to the GitHub pages
> > like
> > we discusses in the other thread due to expose part of the code of a
> > commercial wp theme.
> >
> > So, the workflow we can use is: Use the WP backend to enter new
> > content
> > and
> > modify existing want with ease (this is important is we want people
> > contributing here). Next, with all changes done, generate a static
> > version
> > and replace the entire site with a fresh generated static site at
> > royale.apache.org<http://royale.apache.org/>. and as well route the
> more friendly domain to this
> > if
> > board is ok with that.
> >
> > Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected
> to royale.apache.org<http://royale.apache.org/> as
> > discussed.
> >
> >
> > We can check with apache board or trademarks what they propose about
> > to
> > create a Wordpress.com<http://wordpress.com/> account managed by Apache
> and migrate from my
> > server
> > to that account, and all this stuff from there, since if I remember
> > some
> > people said that would be more ok with Apache.I'd end removing my temp
> > subdomain after this.
> >
> > The advantage of using the Wordpress.com<http://wordpress.com/>
> location is twofold:
> >
> > (1) Wordpress keeps security up to date.
> > (2) If something happens to you or your company then we have better
> > access.
> >
> > I suspect though that with the status export method this will not be as
> > great a concern.
> >
> >
> > What do you think? Can I move this with the people we were talking
> > some
> > weeks ago?
> >
> > Either you or I can email Trademarks with the plan.
> >
> > We can then discuss the redirection with Infrastructure and get the site
> > checked in.
> >
> > Regards,
> > Dave
> >
> >
> > Let me know in order to start making the next steps
> >
> > Thanks
> >
> >
> > --
> > Carlos Rovira
> >
> > https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%
> > 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> 73f8%7Cfa7b1
> > b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> sdata=1q5B1u1lLR
> > HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
> >
> >
> >
> >
> > --
> >
> > <https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo
> > scopic.com<http://scopic.com/>&data=02%7C01%7C%
> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> > 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> sdata=Y%2Fkytu4lJUWu5H
> > zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%
> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> > 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
> 2Fkytu4lJUWu5Hz
> > inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
> >
> >
> > Conocenos Avant2 en 1 minuto!
> > <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant2.e
> > s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> 73f8%7Cfa7b1b5a
> > 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> sdata=SJmmZQTVSb0tmX
> > r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> > 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.
> >
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Dave Fisher <da...@comcast.net>.
Hi -
> On Oct 24, 2017, at 11:10 AM, Harbs <ha...@gmail.com> wrote:
>
> Here’s how I see things:
>
> 1. For the immediate, we want a good web presence. If putting the WordPress site on wordpress.com <http://wordpress.com/> with a CNAME entry pointing to royale.apache.com <http://royale.apache.com/> is the fastest way to get there, we should start with that.
Here is nslookup for feathercast:
nslookup feathercast.apache.org
Server: 192.168.1.1
Address: 192.168.1.1#53
Non-authoritative answer:
feathercast.apache.org canonical name = feathercastapache.wordpress.com.
feathercastapache.wordpress.com canonical name = lb.wordpress.com.
Name: lb.wordpress.com
Address: 192.0.78.12
Name: lb.wordpress.com
Address: 192.0.78.13
.
This suggests that royaleapache would be the subdomain from WP.com <http://wp.com/>.
We may want this domain to be blog.royale.apache.org
> 2. We should look into getting a static version of the site, so the site can be edited on Github and pushed to royale.apache.com <http://royale.apache.com/>. That is more ideal than having private access to a WordPress installation.
> 3. We should contact greatives and see if they would give us permission to reuse the css and js for a static site. (possibly with attribution)
> 4. We should ask trademarks@ and/or legal@ whether the terms (assuming we get them) are ok from an Apache perspective.
I think we should ask infrastructure and then possibly legal-discuss about any theme terms.
> 5. Assuming #4 and #5 work out, we will probably want various pieces of our site constructed using this styling i.e. main site, docs, blog (as a WordPress installation), examples.
Regards,
Dave
>
> Harbs
>
>> On Oct 24, 2017, at 8:56 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>>
>> Hi Dave,
>>
>> I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we have the rights to replicate use of that look-and-feel elsewhere? I don't understand who owns the creative content.
>>
>> Thoughts?
>> -Alex
>>
>> From: Dave Fisher <da...@comcast.net>>
>> Reply-To: <de...@royale.apache.org>>
>> Date: Tuesday, October 24, 2017 at 10:50 AM
>> To: <de...@royale.apache.org>>
>> Subject: Re: Apache Royale static web site
>>
>> Hi Alex,
>>
>> On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID>> wrote:
>>
>> There is something I don't think I understand. AIUI, at some point, we
>> will want the Apache Royale site to include actual Royale applications,
>> right? And I would think we would want the styling of those applications
>> to be consistent with the rest of the site. So I'm not clear how we will
>> be able to implement the styling/theme of these Royale applications if we
>> don't have rights to the styling. I don't understand how WP themes and
>> commercial licensing works if we want to replicate that user experience
>> outside of WP.
>>
>> We need to examine the static export of the CSS and HTML.
>>
>>
>> If we can use those visuals outside of WP, then why must we continue to
>> use WP to generate the site? I would hope the theme would be implemented
>> as CSS and some templates we could use without WP.
>>
>> We should be able to adapt. Site building in the CMS can get complex if needed. For OpenOffice.org<http://OpenOffice.org> we use the legacy html pulling out the title and content body and place it within a markdown template.
>>
>>
>> Also, if someone wants to patch the site, they can't just offer a patch of
>> the HTML right? They would need to figure out where in WP it comes from?
>> Is there a patch process for WP content?
>>
>> Possibly.
>>
>>
>> Sorry if there is some basic thing I am missing.
>>
>> It will get complex first as we figure out how to embed and then it will get simplified as we find the best way.
>>
>> Regards,
>> Dave
>>
>>
>>
>> Thanks,
>> -Alex
>>
>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<ma...@gmail.com> on behalf of Carlos
>> Rovira" <ca...@gmail.com> on behalf of
>> carlos.rovira@codeoscopic.com<ma...@codeoscopic.com>> wrote:
>>
>> Thanks Dave,
>>
>> I'll write an email to trademarks to start with the process. I think is
>> better to migrate to WP.com<http://WP.com> before continue working on content so we can
>> detect whatever issue we could get.
>>
>> Thanks!
>>
>> Carlos
>>
>>
>>
>> 2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>>:
>>
>> Hi Carlos,
>>
>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>>
>> wrote:
>>
>> Hi,
>>
>> just let you know that I tried to create an static version of the
>> preview
>> site with success. I use this plugin :
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
>> s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>>
>> and we can generate all static content with relative or absolute urls.
>> The
>> final preview site in static is 134mb
>>
>> Another thing I was searching was to use a WP to Jekyll exporter but
>> this
>> is not what I wanted since it seems Jekyll is all about markdown and
>> we
>> want a full html site with all the eye candy JS+CSS resources. In the
>> end,
>> and thinking more about it, is not what we want since although the
>> site
>> would be exported ok, we don't want to upload it to the GitHub pages
>> like
>> we discusses in the other thread due to expose part of the code of a
>> commercial wp theme.
>>
>> So, the workflow we can use is: Use the WP backend to enter new
>> content
>> and
>> modify existing want with ease (this is important is we want people
>> contributing here). Next, with all changes done, generate a static
>> version
>> and replace the entire site with a fresh generated static site at
>> royale.apache.org<http://royale.apache.org/>. and as well route the more friendly domain to this
>> if
>> board is ok with that.
>>
>> Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected to royale.apache.org<http://royale.apache.org/> as
>> discussed.
>>
>>
>> We can check with apache board or trademarks what they propose about
>> to
>> create a Wordpress.com<http://wordpress.com/> account managed by Apache and migrate from my
>> server
>> to that account, and all this stuff from there, since if I remember
>> some
>> people said that would be more ok with Apache.I'd end removing my temp
>> subdomain after this.
>>
>> The advantage of using the Wordpress.com<http://wordpress.com/> location is twofold:
>>
>> (1) Wordpress keeps security up to date.
>> (2) If something happens to you or your company then we have better
>> access.
>>
>> I suspect though that with the status export method this will not be as
>> great a concern.
>>
>>
>> What do you think? Can I move this with the people we were talking
>> some
>> weeks ago?
>>
>> Either you or I can email Trademarks with the plan.
>>
>> We can then discuss the redirection with Infrastructure and get the site
>> checked in.
>>
>> Regards,
>> Dave
>>
>>
>> Let me know in order to start making the next steps
>>
>> Thanks
>>
>>
>> --
>> Carlos Rovira
>>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>>
>>
>>
>>
>> --
>>
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>> scopic.com<http://scopic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>>
>>
>> Conocenos Avant2 en 1 minuto!
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>> 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: Apache Royale static web site
Posted by Harbs <ha...@gmail.com>.
Here’s how I see things:
1. For the immediate, we want a good web presence. If putting the WordPress site on wordpress.com <http://wordpress.com/> with a CNAME entry pointing to royale.apache.com <http://royale.apache.com/> is the fastest way to get there, we should start with that.
2. We should look into getting a static version of the site, so the site can be edited on Github and pushed to royale.apache.com <http://royale.apache.com/>. That is more ideal than having private access to a WordPress installation.
3. We should contact greatives and see if they would give us permission to reuse the css and js for a static site. (possibly with attribution)
4. We should ask trademarks@ and/or legal@ whether the terms (assuming we get them) are ok from an Apache perspective.
5. Assuming #4 and #5 work out, we will probably want various pieces of our site constructed using this styling i.e. main site, docs, blog (as a WordPress installation), examples.
Harbs
> On Oct 24, 2017, at 8:56 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Hi Dave,
>
> I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we have the rights to replicate use of that look-and-feel elsewhere? I don't understand who owns the creative content.
>
> Thoughts?
> -Alex
>
> From: Dave Fisher <da...@comcast.net>>
> Reply-To: <de...@royale.apache.org>>
> Date: Tuesday, October 24, 2017 at 10:50 AM
> To: <de...@royale.apache.org>>
> Subject: Re: Apache Royale static web site
>
> Hi Alex,
>
> On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID>> wrote:
>
> There is something I don't think I understand. AIUI, at some point, we
> will want the Apache Royale site to include actual Royale applications,
> right? And I would think we would want the styling of those applications
> to be consistent with the rest of the site. So I'm not clear how we will
> be able to implement the styling/theme of these Royale applications if we
> don't have rights to the styling. I don't understand how WP themes and
> commercial licensing works if we want to replicate that user experience
> outside of WP.
>
> We need to examine the static export of the CSS and HTML.
>
>
> If we can use those visuals outside of WP, then why must we continue to
> use WP to generate the site? I would hope the theme would be implemented
> as CSS and some templates we could use without WP.
>
> We should be able to adapt. Site building in the CMS can get complex if needed. For OpenOffice.org<http://OpenOffice.org> we use the legacy html pulling out the title and content body and place it within a markdown template.
>
>
> Also, if someone wants to patch the site, they can't just offer a patch of
> the HTML right? They would need to figure out where in WP it comes from?
> Is there a patch process for WP content?
>
> Possibly.
>
>
> Sorry if there is some basic thing I am missing.
>
> It will get complex first as we figure out how to embed and then it will get simplified as we find the best way.
>
> Regards,
> Dave
>
>
>
> Thanks,
> -Alex
>
> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<ma...@gmail.com> on behalf of Carlos
> Rovira" <ca...@gmail.com> on behalf of
> carlos.rovira@codeoscopic.com<ma...@codeoscopic.com>> wrote:
>
> Thanks Dave,
>
> I'll write an email to trademarks to start with the process. I think is
> better to migrate to WP.com<http://WP.com> before continue working on content so we can
> detect whatever issue we could get.
>
> Thanks!
>
> Carlos
>
>
>
> 2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>>:
>
> Hi Carlos,
>
> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>>
> wrote:
>
> Hi,
>
> just let you know that I tried to create an static version of the
> preview
> site with success. I use this plugin :
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
> s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>
> and we can generate all static content with relative or absolute urls.
> The
> final preview site in static is 134mb
>
> Another thing I was searching was to use a WP to Jekyll exporter but
> this
> is not what I wanted since it seems Jekyll is all about markdown and
> we
> want a full html site with all the eye candy JS+CSS resources. In the
> end,
> and thinking more about it, is not what we want since although the
> site
> would be exported ok, we don't want to upload it to the GitHub pages
> like
> we discusses in the other thread due to expose part of the code of a
> commercial wp theme.
>
> So, the workflow we can use is: Use the WP backend to enter new
> content
> and
> modify existing want with ease (this is important is we want people
> contributing here). Next, with all changes done, generate a static
> version
> and replace the entire site with a fresh generated static site at
> royale.apache.org<http://royale.apache.org/>. and as well route the more friendly domain to this
> if
> board is ok with that.
>
> Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected to royale.apache.org<http://royale.apache.org/> as
> discussed.
>
>
> We can check with apache board or trademarks what they propose about
> to
> create a Wordpress.com<http://wordpress.com/> account managed by Apache and migrate from my
> server
> to that account, and all this stuff from there, since if I remember
> some
> people said that would be more ok with Apache.I'd end removing my temp
> subdomain after this.
>
> The advantage of using the Wordpress.com<http://wordpress.com/> location is twofold:
>
> (1) Wordpress keeps security up to date.
> (2) If something happens to you or your company then we have better
> access.
>
> I suspect though that with the status export method this will not be as
> great a concern.
>
>
> What do you think? Can I move this with the people we were talking
> some
> weeks ago?
>
> Either you or I can email Trademarks with the plan.
>
> We can then discuss the redirection with Infrastructure and get the site
> checked in.
>
> Regards,
> Dave
>
>
> Let me know in order to start making the next steps
>
> Thanks
>
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>
>
>
>
> --
>
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
> scopic.com<http://scopic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>
>
> Conocenos Avant2 en 1 minuto!
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> 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: Apache Royale static web site
Posted by Harbs <ha...@gmail.com>.
I belive this is there web presence:
https://greatives.eu/ <https://greatives.eu/>
> On Oct 24, 2017, at 9:06 PM, Dave Fisher <da...@comcast.net> wrote:
>
> Hi Alex,
>
> We will need to ask Carlos to list out all of the themes he uses and then we will need to track things down and ask questions.
>
> Here is the site for what looks like the main theme: https://greatives.ticksy.com/ <https://greatives.ticksy.com/>
>
> It is the Move Do theme.
>
> Regards,
> Dave
>
>> On Oct 24, 2017, at 10:56 AM, Alex Harui <aharui@adobe.com.INVALID <ma...@adobe.com.INVALID>> wrote:
>>
>> Hi Dave,
>>
>> I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we have the rights to replicate use of that look-and-feel elsewhere? I don't understand who owns the creative content.
>>
>> Thoughts?
>> -Alex
>>
>> From: Dave Fisher <dave2wave@comcast.net <ma...@comcast.net><mailto:dave2wave@comcast.net <ma...@comcast.net>>>
>> Reply-To: <dev@royale.apache.org <ma...@royale.apache.org><mailto:dev@royale.apache.org <ma...@royale.apache.org>>>
>> Date: Tuesday, October 24, 2017 at 10:50 AM
>> To: <dev@royale.apache.org <ma...@royale.apache.org><mailto:dev@royale.apache.org <ma...@royale.apache.org>>>
>> Subject: Re: Apache Royale static web site
>>
>> Hi Alex,
>>
>> On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID <ma...@adobe.com.INVALID><mailto:aharui@adobe.com.INVALID <ma...@adobe.com.INVALID>>> wrote:
>>
>> There is something I don't think I understand. AIUI, at some point, we
>> will want the Apache Royale site to include actual Royale applications,
>> right? And I would think we would want the styling of those applications
>> to be consistent with the rest of the site. So I'm not clear how we will
>> be able to implement the styling/theme of these Royale applications if we
>> don't have rights to the styling. I don't understand how WP themes and
>> commercial licensing works if we want to replicate that user experience
>> outside of WP.
>>
>> We need to examine the static export of the CSS and HTML.
>>
>>
>> If we can use those visuals outside of WP, then why must we continue to
>> use WP to generate the site? I would hope the theme would be implemented
>> as CSS and some templates we could use without WP.
>>
>> We should be able to adapt. Site building in the CMS can get complex if needed. For OpenOffice.org <http://openoffice.org/><http://OpenOffice.org <http://openoffice.org/>> we use the legacy html pulling out the title and content body and place it within a markdown template.
>>
>>
>> Also, if someone wants to patch the site, they can't just offer a patch of
>> the HTML right? They would need to figure out where in WP it comes from?
>> Is there a patch process for WP content?
>>
>> Possibly.
>>
>>
>> Sorry if there is some basic thing I am missing.
>>
>> It will get complex first as we figure out how to embed and then it will get simplified as we find the best way.
>>
>> Regards,
>> Dave
>>
>>
>>
>> Thanks,
>> -Alex
>>
>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com <ma...@gmail.com><mailto:carlos.rovira@gmail.com <ma...@gmail.com>> on behalf of Carlos
>> Rovira" <carlos.rovira@gmail.com <ma...@gmail.com><mailto:carlos.rovira@gmail.com <ma...@gmail.com>> on behalf of
>> carlos.rovira@codeoscopic.com <ma...@codeoscopic.com><mailto:carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>>> wrote:
>>
>> Thanks Dave,
>>
>> I'll write an email to trademarks to start with the process. I think is
>> better to migrate to WP.com <http://wp.com/><http://WP.com <http://wp.com/>> before continue working on content so we can
>> detect whatever issue we could get.
>>
>> Thanks!
>>
>> Carlos
>>
>>
>>
>> 2017-10-24 18:56 GMT+02:00 Dave Fisher <dave2wave@comcast.net <ma...@comcast.net><mailto:dave2wave@comcast.net <ma...@comcast.net>>>:
>>
>> Hi Carlos,
>>
>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <carlosrovira@apache.org <ma...@apache.org><mailto:carlosrovira@apache.org <ma...@apache.org>>>
>> wrote:
>>
>> Hi,
>>
>> just let you know that I tried to create an static version of the
>> preview
>> site with success. I use this plugin :
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres>
>> s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>>
>> and we can generate all static content with relative or absolute urls.
>> The
>> final preview site in static is 134mb
>>
>> Another thing I was searching was to use a WP to Jekyll exporter but
>> this
>> is not what I wanted since it seems Jekyll is all about markdown and
>> we
>> want a full html site with all the eye candy JS+CSS resources. In the
>> end,
>> and thinking more about it, is not what we want since although the
>> site
>> would be exported ok, we don't want to upload it to the GitHub pages
>> like
>> we discusses in the other thread due to expose part of the code of a
>> commercial wp theme.
>>
>> So, the workflow we can use is: Use the WP backend to enter new
>> content
>> and
>> modify existing want with ease (this is important is we want people
>> contributing here). Next, with all changes done, generate a static
>> version
>> and replace the entire site with a fresh generated static site at
>> royale.apache.org<http://royale.apache.org/>. and as well route the more friendly domain to this
>> if
>> board is ok with that.
>>
>> Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected to royale.apache.org<http://royale.apache.org/> as
>> discussed.
>>
>>
>> We can check with apache board or trademarks what they propose about
>> to
>> create a Wordpress.com<http://wordpress.com/> account managed by Apache and migrate from my
>> server
>> to that account, and all this stuff from there, since if I remember
>> some
>> people said that would be more ok with Apache.I'd end removing my temp
>> subdomain after this.
>>
>> The advantage of using the Wordpress.com<http://wordpress.com/> location is twofold:
>>
>> (1) Wordpress keeps security up to date.
>> (2) If something happens to you or your company then we have better
>> access.
>>
>> I suspect though that with the status export method this will not be as
>> great a concern.
>>
>>
>> What do you think? Can I move this with the people we were talking
>> some
>> weeks ago?
>>
>> Either you or I can email Trademarks with the plan.
>>
>> We can then discuss the redirection with Infrastructure and get the site
>> checked in.
>>
>> Regards,
>> Dave
>>
>>
>> Let me know in order to start making the next steps
>>
>> Thanks
>>
>>
>> --
>> Carlos Rovira
>>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>>
>>
>>
>>
>> --
>>
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>> scopic.com<http://scopic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>>
>>
>> Conocenos Avant2 en 1 minuto!
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>> 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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
2017-10-26 22:07 GMT+02:00 Harbs <ha...@gmail.com>:
> Good idea.
>
I already did some hours ago the accounts, hope you get an email to enter,
if not let me know ;)
>
> > On Oct 26, 2017, at 9:27 PM, Carlos Rovira <
> carlos.rovira@codeoscopic.com> wrote:
> >
> > in order to help you, Alex and Harbs (others could join as well) to
> > understand all the picture, I could create an account for you in
> > royale.codeoscopic.com <http://royale.codeoscopic.com/>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Harbs <ha...@gmail.com>.
Good idea.
> On Oct 26, 2017, at 9:27 PM, Carlos Rovira <ca...@codeoscopic.com> wrote:
>
> in order to help you, Alex and Harbs (others could join as well) to
> understand all the picture, I could create an account for you in
> royale.codeoscopic.com <http://royale.codeoscopic.com/>
Re: Apache Royale static web site
Posted by Carlos Rovira <ca...@apache.org>.
Hi Alex
2017-10-26 23:38 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
>
> 1) keep pushing to allow hosting on WP for royale.a.o.
>
ok
> 2) Do one static export and copy to the Git repo currently behind roe.a.o
>
I think we can't do this as I commented before. We can't upload code from
movedo theme in ASF repos. And the static version generated will have code
from movedo clearly recognized.
But, again, we as Apache Royale, are not interested in upload any website
code to a repo, since is not our mission. We are interested in upload code
to Apache Royale SDK.
> 3) try to recreate the look and feel in standard CSS/HTML/JS.
>
yes. But we can't expect to do this soon although someone wants to make
this effort
--
Carlos Rovira
http://about.me/carlosrovira
Re: Apache Royale static web site
Posted by Dave Fisher <da...@comcast.net>.
Hi
> On Oct 26, 2017, at 2:38 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> OK, it sounds like there is general agreement from the technical
> perspective and that we don't have enough people and that we want to get
> something up on royale.a.o sooner rather than later. What I'm trying to
> figure out is what is the best way to get a site up on royale.a.o. I also
> realized that we haven't done a review from the Apache perspective [1].
> We might need places for a link to the license and a donate button and
> some other things.
>
> But once we have that, I think our choices are:
>
> 1) keep pushing to allow hosting on WP for royale.a.o.
The push its two fold.
(a) Using the theme CSS/JS that is licensed for the project site.
(b) Using WP.com to host the files.
> 2) Do one static export and copy to the Git repo currently behind roe.a.o
I think we do this and then the focus is (1a)
> 3) try to recreate the look and feel in standard CSS/HTML/JS.
Yes - I have some thoughts based on OpenOffice.org migration.
https://openoffice.apache.org/website-local.html
https://svn.apache.org/repos/asf/openoffice/ooo-site/trunk
https://cms.apache.org/ooo-site/
It gets complicated, but basically we take the old legacy HTML and extract content which goes into a new CMS template.
Django, Python, Perl thing.
Once we have a pattern I can help automate.
>
> We could do #2 for now and try to get to #3 before we do a lot more
> website work.
Yes.
>
> Thoughts?
> -Alex
>
> [1] http://www.apache.org/foundation/marks/pmcs
>
> On 10/26/17, 2:18 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>
>> Hi Alex,
>>
>> 2017-10-26 22:06 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
>>
>>> Hi Carlos,
>>>
>>> I have a WP-based blog, so I understand how easy it is to write some
>>> text
>>> and have it look nice. But I'm still confused about who owns what.
>>> Does
>>> Envato/Greatives own the look and feel of royale.codeoscopic.com or do
>>> you?
>>
>>
>> codeoscopic owns a license of movedo theme.
>> anyone that buys the license (59$) will own it, so I think it's not a huge
>> quantity of money
>>
>>
>>
>>> I understand that Royale is tuned more towards web applications but
>>> to my mind, I see more and more web sites being about interactivity
>>> rather
>>> than just displaying text and images. Even blog commenting and upvoting
>>> looks like an app to me.
>>>
>>
>> The two worlds interesect, that's evidently, but are different beast. I
>> tried to make in the past
>> some website with Flex, and although I did it and we get some cool
>> effects,
>> in the end it wasn't the
>> right tool for the job. I did as well an Application in wordpress with
>> some
>> plugins due to time restrictions
>> and while I did it, again it was not the right tool for the job and many
>> things was very limited.
>>
>>
>>>
>>> I would like to some day use Royale to create the page you've prototyped
>>> at royale.codeoscopic.com and maybe enhance it by having a Royale news
>>> feed or some other backend connectivity for some of the content. But
>>> can
>>> we replicate the look and feel of what you have prototyped and put that
>>> under ALv2? I think we have to find a way to make that possible. The
>>> theme or CSS that we use to replicate your prototype may not be our
>>> default theme/CSS, but it should still be a valid theme or CSS file and
>>> components.
>>>
>>
>> without doubt, but for me this is not the right time to do it. As Harbs
>> already agree, we need
>> to put a website online ASAP.
>>
>> We can always come back and with time, can make that work. But IMHO, we
>> need to choose
>> an strategy and see what things are needed first and organize efforts. For
>> me UI theme is more need than replicate something that we already have.
>>
>>
>>>
>>> That's why I'm concerned that working from Movedo is going to leak into
>>> other things we want to do. But if we start from scratch and try to
>>> replicate the visuals you've chosen, I would hope we can get something
>>> that looks similar quickly and then invite more folks to help tune it.
>>> And as Harbs says, I'm not asking you to do that work, someone else can.
>>> What you've done already is significant and very helpful and I think you
>>> made the right choice of using your WP skills to create it quickly.
>>
>>
>> Right, but for me that work could fit into Royale examples, but would not
>> be of much use in the framework
>>
>>
>>> If we were to reproduce your prototype in Royale, I would want to create
>>> re-usable components such as:
>>> MenuBar
>>> SearchShareUserProfileMoreMenuBar
>>> TopBar (that holds all of the icon, title, MenuBar and
>>> SearchShareProfileButtonBar)
>>> IconTitleTextPanel
>>> And more...
>>>
>>>
>> I think you are right if we want to recreate the website and make Royale
>> components...again for me this is and example.
>>
>> But, if I start to create a styling that could fit more use cases and be
>> the default Express Component Set face? Don't you think that work would be
>> more valuable? I think so, and is what I want to contribute next.
>> That would be more "application" style and less "web" style. based on that
>> work we can make more theme projects like Apache Flex already has and have
>> an Application property "theme" to switch between themes. I think that is
>> what I think people migrating from Apache Flex SDK expects.
>>
>>
>>
>>> Then someone else can come along and assemble their own site from these
>>> pieces.
>>>
>>
>> completely right, but expect many few people doing that since, or at least
>> very residual, since there are other tools far better to do the job. If we
>> want to go that route I think we will need to focus in many task that will
>> ease that kind of target and make Apache Royale good in that area. For
>> example, routing. For Royale to make good websites, routing is essential,
>> and no body will use it without be able to configure deep linking in a
>> reliable and useful way.
>>
>>
>>>
>>> Back in the Adobe days, some folks actually took the FlexStore example,
>>> modified it slightly and deployed it in production for their own
>>> products.
>>> We didn't care that they pretty much used the same look-and-feel. I
>>> think
>>> we want to make the same sort of thing possible for Royale.
>>>
>>
>> Alex, I think this is possible. In fact, all you expose is completely
>> right, but I want you to think in how many hands have we now. Many of this
>> things can be done if we get more people on board, but for this to happen
>> we need to unblock what we have, and go to other things we need. If I need
>> two things (website and themes), I prefer to have 1-1 than 2-0. And in
>> some
>> months from now, we always can come back and make the website in our
>> technology, and maybe even change it for something fresh again.
>>
>> That's my 2ctns.
>>
>> Carlos
>>
>>
>>>
>>> Thoughts?
>>> -Alex
>>>
>>> On 10/26/17, 11:27 AM, "carlos.rovira@gmail.com on behalf of Carlos
>>> Rovira" <carlos.rovira@gmail.com on behalf of
>>> carlos.rovira@codeoscopic.com> wrote:
>>>
>>>> Hi,
>>>>
>>>> in order to help you, Alex and Harbs (others could join as well) to
>>>> understand all the picture, I could create an account for you in
>>>> royale.codeoscopic.com
>>>>
>>>> In this way you could see point 1 of Alex's list (how integrate some
>>> new
>>>> content in website). and most important, you will see the visual tool
>>> to
>>>> edit and mount a new content in pages or posts.
>>>>
>>>> This last thing is one of the main reasons I want to use WP in the day
>>> by
>>>> day. If you want to create some content, doing manually is a nightmare.
>>>>
>>>> I'll send you admin users to your accounts and you're free to enter and
>>>> watch, (but please don't modify anything to avoid break the actual
>>> site)
>>>>
>>>> In order to create some default theme (point 2), again here I think we
>>>> talking about different things. I think we don't want to base our
>>> default
>>>> theme for UI controls in apache royale in what I did in the theme. That
>>>> would be a mistake in since movedo principles are based on website look
>>>> and
>>>> usability. Fonts and spacing is huge to express content in a modern
>>>> website. To make a comparative, if you take MDL and movedo side by
>>> side,
>>>> the first is for applications while the second is to present text and
>>>> images in a website.
>>>>
>>>> My plan, as I mention before, is to start creating a UI component
>>> styles
>>>> that could be programed in a theme. I have in mind to make two of
>>> them: a
>>>> wireframe theme and a full default theme. The first one could have the
>>>> same
>>>> sizes and fonts but with only outlines and black and white (like the
>>> flex
>>>> wireframe to avoid style and application when you're prototyping.
>>>>
>>>> Regarding time to replicate movedo theme with our own styling, I'm
>>> sure is
>>>> not a two day task, but more, there's so much there, and only to get
>>>> something that only will be a shadow of the original.
>>>>
>>>> As Harbs mention there's people making styling, but as they are not
>>>> commenting in this list we don't know anything about if they are doing
>>>> something this days, or maybe they couldn't use that time to work on
>>> this.
>>>>
>>>> For last (point 3), I did wordpress themes some years ago, and is a
>>> huge
>>>> task to do, in time and effort. And with time you can get something of
>>>> quality, but again, why we want to spend our time in something we
>>> already
>>>> have? I don't find anything here, since we are not here to create WP
>>>> themes, I prefer to use that time to create an Apache Royale UI theme
>>> and
>>>> even help to program it, because that is what we really need to make
>>> more
>>>> people join us.
>>>>
>>>>
>>>>
>>>>
>>>> 2017-10-26 19:37 GMT+02:00 Harbs <ha...@gmail.com>:
>>>>
>>>>> Another point to consider:
>>>>>
>>>>> We’ve had some folks offer to help with skinning Royale components.
>>> It
>>>>> should be pretty straightforward to give them (and anyone else who
>>>>> wants to
>>>>> help) committer rights to the website repo. If we have more people
>>>>> working
>>>>> on it, the task of recreating the appearance achieved through the
>>> Movedo
>>>>> CSS should be al lot easier.
>>>>>
>>>>> I don’t feel comfortable asking Carlos to do more work than he’s
>>>>> offered,
>>>>> but with help from others, it might be a lot easier.
>>>>>
>>>>> Harbs
>>>>>
>>>>>> On Oct 26, 2017, at 7:41 PM, Alex Harui <ah...@adobe.com.INVALID>
>>>>> wrote:
>>>>>>
>>>>>> Hi Carlos,
>>>>>>
>>>>>> I don't know if the "Apache Way" is a problem here. So far I
>>> think we
>>>>>> have heard opinions and concerns but AFAICT no hard policy has been
>>>>> quoted
>>>>>> that prevents having royale.a.o point to WP.com.
>>>>>>
>>>>>> But I am still unclear if hosting our site on WP is really the best
>>>>>> strategy. I have the following concerns:
>>>>>>
>>>>>> 1) How would be include a Royale application in our site?
>>>>>> 2) How would we style the Royale application to look consistent
>>> with
>>>>> the
>>>>>> rest of the site?
>>>>>> 3) Could we ever create a theme based on this styling?
>>>>>>
>>>>>> I didn't, and still don't, understand how WP themes and their
>>>>> licensing
>>>>>> work, otherwise I think I would have asked more questions up
>>> front. I
>>>>>> thought you would own copyright on the results, just like using
>>> Adobe
>>>>>> Dreamweaver and Adobe Illustrator to build out a site doesn't put
>>> the
>>>>>> content under Adobe licensing.
>>>>>>
>>>>>> That doesn't appear to be the case here, but I think we do need to
>>>>>> consider the 3 concerns I've listed.
>>>>>>
>>>>>> Both you and Harbs claim that replicating your prototype's look and
>>>>> feel
>>>>>> will be a lot of work, but how much work are really talking about,
>>>>> and do
>>>>>> we have to exactly replicate it (and should we)? If you think
>>> about
>>>>> how
>>>>>> Royale components are created, they work with some default CSS. I
>>>>> think
>>>>>> if we implement themes, we'll end up with components with
>>> particular
>>>>>> "sub-DOMs" and CSS that dictates the visuals on those sub-DOMs.
>>>>> AIUI, we
>>>>>> are expecting artwork from some designers about other default looks
>>>>> for
>>>>>> Royale components. Won't we be facing a similar challenge of
>>> trying
>>>>> to
>>>>>> figure out the CSS that best matches what we see on a screen?
>>>>>>
>>>>>> So, I think it is great that WP and MoveDo helped you create this
>>>>>> fantastic looking prototype. But, IMO, one direction we can go
>>> from
>>>>> here
>>>>>> is to try to replicate the visuals you created in CSS in a way that
>>>>> can
>>>>> be
>>>>>> re-used via the Apache Way. I think we'd learn about themes as we
>>>>> try to
>>>>>> do that. Could we get most of the way there in a couple of days?
>>>>> Then
>>>>>> others can offer fine-tuning via patches.
>>>>>>
>>>>>> And yes, WP is tuned towards templated content in a consistent way,
>>>>> but
>>>>> it
>>>>>> would be interesting to build Royale components that do something
>>>>> similar.
>>>>>>
>>>>>> Thoughts?
>>>>>> -Alex
>>>>>>
>>>>>> On 10/26/17, 1:12 AM, "carlos.rovira@gmail.com on behalf of Carlos
>>>>> Rovira"
>>>>>> <carlos.rovira@gmail.com on behalf of
>>> carlos.rovira@codeoscopic.com>
>>>>> wrote:
>>>>>>
>>>>>>> Harbs is right,
>>>>>>>
>>>>>>> to get something that looks cool and consistent is difficult and
>>> for
>>>>> this
>>>>>>> reason I use wordpress+theme (in this case movedo). Is the same
>>>>> thing as
>>>>>>> why people use flex or royale. Is the way to start from a point
>>> where
>>>>> you
>>>>>>> are more efficient and maintenance can be assumed.
>>>>>>>
>>>>>>> Alex, you see lots of difference since I customized via movedo
>>>>> interface
>>>>>>> but as well did some tweaks in custom css (for example the footer
>>>>> column
>>>>>>> menus)
>>>>>>>
>>>>>>> So could we rework the site without wp and movedo. Sure, as I
>>> stated
>>>>> all
>>>>>>> sites can be write in different ways, but the long term reason to
>>>>> adopt
>>>>> a
>>>>>>> CMS like WP is to have a backend to introduce content of quality
>>> in
>>>>> the
>>>>>>> most easy way while preserving quality on presentation (styles,
>>>>> fonts,
>>>>>>> effects...)
>>>>>>>
>>>>>>> I think we are in a situation where "the Apache way" fails
>>> completely
>>>>>>> since
>>>>>>> we should be able to make this quick and easy and concentrate in
>>> our
>>>>>>> Royale
>>>>>>> code, that is why we are here, and why I tried to go this path: to
>>>>> get
>>>>>>> something that looks good and professional but to spend very few
>>> time
>>>>> for
>>>>>>> our part.
>>>>>>>
>>>>>>> I'm very pragmatic, and like to go to the point. All Apache rules
>>>>> should
>>>>>>> be
>>>>>>> focused in protect the code we release, and we should have less
>>>>> trouble
>>>>>>> with tools like WP, Jira, Nexus, and the rest. In fact Apache is
>>>>> using
>>>>>>> those tools all along the way, why is so hard to do this?
>>>>>>>
>>>>>>> We only need:
>>>>>>>
>>>>>>> * Some host for a Wordpress instance: this could be the current
>>>>>>> Codeoscopic
>>>>>>> subdomain or whatever people like. I'd be more happy if the wp
>>>>> instance
>>>>> is
>>>>>>> in some server that could be controlled and maintained by ASF. I
>>>>> don't
>>>>>>> know
>>>>>>> if this could be WP.com or some ASF's virtual machine that could
>>> host
>>>>>>> that.
>>>>>>>
>>>>>>> * The Movedo theme: I write to Dimitri, from greatives. He is very
>>>>>>> supportive and very like the idea, but is not in their hands. He
>>>>> point
>>>>> me
>>>>>>> to talk with envato, and I write to them, but still doesn't have a
>>>>>>> response. My thinking here is that we really don't need nothing of
>>>>> this.
>>>>>>> Envato could donate a license but is only 59$, so is something
>>>>> affordable
>>>>>>> by a simple donation.
>>>>>>>
>>>>>>> * Finaly to generate an static site from WP. This is as well not
>>>>> needed,
>>>>>>> but we can do it. People use to generate wp static version in
>>> order
>>>>> to
>>>>>>> protect their sites from hacking. That's the only relevant point
>>> to
>>>>> do
>>>>>>> this. So for me is something we can do if the rest of community
>>> wants
>>>>> it.
>>>>>>> Is very easy to do.
>>>>>>>
>>>>>>>
>>>>>>> Additionaly: As we are not uploading any website code to any ASF
>>>>> repo,
>>>>>>> since as I said, it would be like to upload the JIRA source code
>>> to
>>>>> our
>>>>>>> repos, and that doesn't give us anything (we're here to release
>>> only
>>>>>>> apache
>>>>>>> royale code). we can :
>>>>>>>
>>>>>>> 1.- Use the royale.codeoscopic.com wp instance as the tool for us
>>> to
>>>>>>> modify
>>>>>>> the site (people in our community will have user/pass in this wp
>>>>> instance
>>>>>>> to create post and pages)
>>>>>>> (in this way is similar to the server Alex had on his own to make
>>>>> some
>>>>>>> apache flex task, correct me if I'm wrong)
>>>>>>> Again, it can be royale.codeoscopic.com or other hosting ASF
>>> wants.
>>>>>>>
>>>>>>> 2.- Each time something changes: generate static site and deploy
>>> to
>>>>>>> royale.apache.org
>>>>>>> (in this case the set of static generated html/js/css could not be
>>>>>>> uploaded
>>>>>>> to any ASF repo since we don't want to release the website code,
>>> that
>>>>> must
>>>>>>> be served in the same way ASF serves JIRA, or whatever other
>>>>> commercial
>>>>>>> tool
>>>>>>>
>>>>>>> Hosting a generated site with a movedo commercial theme needs of a
>>>>> 59$
>>>>>>> license that could be donated by envato or donated for other
>>>>>>> person/company
>>>>>>> (for example Codeoscopic)
>>>>>>>
>>>>>>> For me this is quick and easy and I think we're not making
>>> something
>>>>> wrong
>>>>>>> in legal terms
>>>>>>>
>>>>>>> Carlos
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> 2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
>>>>>>>
>>>>>>>> It’s using greatives’ CSS and JS files for styling, layout and
>>>>> effects.
>>>>>>>>
>>>>>>>> Generally, these themes have a lot of flexibility to change the
>>>>> look of
>>>>>>>> a
>>>>>>>> site without messing with CSS and JS.
>>>>>>>>
>>>>>>>> Can we re-write the CSS and JS to do the same kind of thing?
>>>>> Probably.
>>>>>>>> But
>>>>>>>> it would be a considerable amount of work.
>>>>>>>>
>>>>>>>> What’s included in the license? I’m really not sure.
>>>>>>>>
>>>>>>>> It gives rights to us the theme in WordPress. Does that allow
>>>>>>>> repurposing
>>>>>>>> the CSS and JS files for use elsewhere? I don’t know.
>>>>>>>>
>>>>>>>> Harbs
>>>>>>>>
>>>>>>>>> On Oct 26, 2017, at 9:56 AM, Alex Harui
>>> <ah...@adobe.com.INVALID>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I'm still confused about something.
>>>>>>>>>
>>>>>>>>> Can someone explain how creativity and licensing are
>>>>> interconnected?
>>>>>>>> I'm not familiar with WP themes, but I think they are templates
>>> with
>>>>>>>> placeholders for particular aspects of a web page/blog. I've
>>> been
>>>>> told
>>>>>>>> that this Royale site prototype is based on the Movedo theme.
>>> When
>>>>> I
>>>>>>>> searched for it on the internet I ended up here:
>>>>>>>> https://na01.safelinks.protection.outlook.com/?url=
>>>>> http%3A%2F%2Fgreatives
>>>>>>>> .eu%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b1b5a7b344
>>>>>>>> 38794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>>>>> VI0EOLywsaxbKgmhAe
>>>>>>>> F08cdZNQjcgtIjyFvJ2R33hlo%3D&reserved=0
>>>>>>>> themeforest/themeswitcher/?product=movedo#movedo
>>>>>>>>>
>>>>>>>>> It doesn't look at all like the prototype at
>>>>>>>>
>>>>>>>> https://na01.safelinks.protection.outlook.com/?url=
>>>>> http%3A%2F%2Froyale.co
>>>>>>>> deoscopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b1b
>>>>>>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>>>>> sdata=3GHfDzdFp6B
>>>>>>>> 4RQMLuP00jKAHmwQ1QMubUd4dgz3FdTA%3D&reserved=0. Maybe the menu
>>> bar
>>>>>>>> along the top?
>>>>>>>>>
>>>>>>>>> So what did we license from greatives? Can Carlos or someone
>>> else
>>>>>>>> try
>>>>>>>> to reproduce the prototype without looking at the current CSS and
>>>>> maybe
>>>>>>>> use
>>>>>>>> AL licensed fonts or something like that?
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> -Alex
>>>>>>>>>
>>>>>>>>> From: Dave Fisher
>>>>>>>> <da...@comcast.net>>
>>>>>>>>> Reply-To: <de...@royale.apache.org>>
>>>>>>>>> Date: Tuesday, October 24, 2017 at 11:06 AM
>>>>>>>>> To: <de...@royale.apache.org>>
>>>>>>>>> Subject: Re: Apache Royale static web site
>>>>>>>>>
>>>>>>>>> Hi Alex,
>>>>>>>>>
>>>>>>>>> We will need to ask Carlos to list out all of the themes he uses
>>>>> and
>>>>>>>> then we will need to track things down and ask questions.
>>>>>>>>>
>>>>>>>>> Here is the site for what looks like the main theme:
>>>>>>>>
>>>>>>>> https://na01.safelinks.protection.outlook.com/?url=
>>>>> https%3A%2F%2Fgreative
>>>>>>>> s.ticksy.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b
>>>>>>>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>>>>> sdata=KBxlYi2QO
>>>>>>>> PDqNGhTsU6GJMhdUggdHVZjiYetcIcE8vE%3D&reserved=0
>>>>>>>>>
>>>>>>>>> It is the Move Do theme.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Dave
>>>>>>>>>
>>>>>>>>> On Oct 24, 2017, at 10:56 AM, Alex Harui
>>> <aharui@adobe.com.INVALID
>>> <
>>>>>>>> mailto:aharui@adobe.com.INVALID>> wrote:
>>>>>>>>>
>>>>>>>>> Hi Dave,
>>>>>>>>>
>>>>>>>>> I'm still wondering, even if we can see and reuse the
>>> CSS/JS/HTML,
>>>>> do
>>>>>>>> we
>>>>>>>> have the rights to replicate use of that look-and-feel
>>> elsewhere? I
>>>>>>>> don't
>>>>>>>> understand who owns the creative content.
>>>>>>>>>
>>>>>>>>> Thoughts?
>>>>>>>>> -Alex
>>>>>>>>>
>>>>>>>>> From: Dave Fisher
>>>>> <dave2wave@comcast.net<mailto:dave2wave@comcast.net
>>>>>>>>> <ma...@comcast.net>>
>>>>>>>>> Reply-To: <dev@royale.apache.org<mailto:dev@royale.apache.org
>>>>>> <mailto:
>>>>>>>> dev@royale.apache.org>>
>>>>>>>>> Date: Tuesday, October 24, 2017 at 10:50 AM
>>>>>>>>> To: <de...@royale.apache.org><mailto:
>>>>>>>> dev@royale.apache.org>>
>>>>>>>>> Subject: Re: Apache Royale static web site
>>>>>>>>>
>>>>>>>>> Hi Alex,
>>>>>>>>>
>>>>>>>>> On Oct 24, 2017, at 10:43 AM, Alex Harui
>>> <aharui@adobe.com.INVALID
>>> <
>>>>>>>>
>>> mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> There is something I don't think I understand. AIUI, at some
>>>>> point,
>>>>>>>> we
>>>>>>>>> will want the Apache Royale site to include actual Royale
>>>>>>>> applications,
>>>>>>>>> right? And I would think we would want the styling of those
>>>>>>>> applications
>>>>>>>>> to be consistent with the rest of the site. So I'm not clear
>>> how
>>>>> we
>>>>>>>> will
>>>>>>>>> be able to implement the styling/theme of these Royale
>>> applications
>>>>>>>> if we
>>>>>>>>> don't have rights to the styling. I don't understand how WP
>>> themes
>>>>>>>> and
>>>>>>>>> commercial licensing works if we want to replicate that user
>>>>>>>> experience
>>>>>>>>> outside of WP.
>>>>>>>>>
>>>>>>>>> We need to examine the static export of the CSS and HTML.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> If we can use those visuals outside of WP, then why must we
>>>>> continue
>>>>>>>> to
>>>>>>>>> use WP to generate the site? I would hope the theme would be
>>>>>>>> implemented
>>>>>>>>> as CSS and some templates we could use without WP.
>>>>>>>>>
>>>>>>>>> We should be able to adapt. Site building in the CMS can get
>>>>> complex
>>>>>>>> if
>>>>>>>> needed. For
>>>>>>>>
>>>
>>>>> OpenOffice.org<https://na01.safelinks.protection.outlook.com/?url=https
>>>>> %3A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a27
>>>>> 554170019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636
>>>>> 446495300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&
>>>>> reserved=0.
>>> com/?url=https%3
>>>>> A%2F%2Fna01.safelinks.protection.outlook&data=02%
>>> 7C01%7C%7Cf48589d8bd1f49
>>>>> 2c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C636446392
>>>>> 882621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
>>> S9p2zHjJMq%2FnM%3D&reserved
>>>>> =0.
>>>>> com/?url=http%3A
>>>>>>>>
>>> %2F%2FOpenOffice.org&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7
>>>>>>>>
>>>>> Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>>>>> m3Mv
>>>>>>>> XfpJIZbB4u1Zhr0AB%2B%2BVI5uPKwu7N33MkPuovjs%3D&reserved=0><
>>>>>
>>>>> https://na01.safelinks.protection.outlook.com/?url=
>>> https%3A%2F%2Fna01.s&d
>>>>> ata=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
>>> 4cfc%7Cfa7b1b5a7b34438794aed
>>>>> 2c178decee1%7C0%7C0%7C636446392882621163&sdata=
>>> hxky0LHm5GqF8zMjFHm3bXfugJ
>>>>> xCS6qWPoG%2FbWItNgQ%3D&reserved=0
>>>>>>>> afelinks.protection.outlook.com/?url=http%3A%2F%
>>>>> 2FOpenOffice.org&data=02%
>>>>>>>> 7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>>>>> 7Cfa7b1b5a7b34438794aed2c178de
>>>>>>>> cee1%7C0%7C0%7C636446023931803217&sdata=m3MvXfpJIZbB4u1Zhr0AB%2B%
>>>>> 2BVI5uPK
>>>>>>>> wu7N33MkPuovjs%3D&reserved=0>
>>>>>>>> we use the legacy html pulling out the title and content body and
>>>>> place
>>>>>>>> it
>>>>>>>> within a markdown template.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Also, if someone wants to patch the site, they can't just offer
>>> a
>>>>>>>> patch
>>>>>>>> of
>>>>>>>>> the HTML right? They would need to figure out where in WP it
>>> comes
>>>>>>>> from?
>>>>>>>>> Is there a patch process for WP content?
>>>>>>>>>
>>>>>>>>> Possibly.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Sorry if there is some basic thing I am missing.
>>>>>>>>>
>>>>>>>>> It will get complex first as we figure out how to embed and
>>> then it
>>>>>>>> will
>>>>>>>> get simplified as we find the best way.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Dave
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Thanks,
>>>>>>>>> -Alex
>>>>>>>>>
>>>>>>>>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
>>>>>>>> carlos.rovira@gmail.com><ma...@gmail.com> on
>>> behalf
>>>>> of
>>>>>>>> Carlos
>>>>>>>>> Rovira"
>>>>>>>> <ca...@gmail.com><mailto:
>>>>>>>> carlos.rovira@gmail.com> on behalf of
>>>>>>>>>
>>> carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
>>>>>>>>> <ma...@codeoscopic.com>> wrote:
>>>>>>>>>
>>>>>>>>> Thanks Dave,
>>>>>>>>>
>>>>>>>>> I'll write an email to trademarks to start with the process. I
>>>>> think
>>>>>>>> is
>>>>>>>>> better to migrate to
>>>>>>>> WP.com<https://na01.safelinks.protection.outlook.com/?url=
>>>>> http%3A%2F%2FWP
>>>>>>>> .com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b1b5a7b34438
>>>>>>>> 794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>>>>> pPTlG8DjwzO%2FN%2B0r
>>>>>>>> euRRSegBNuKdtuonR2fro55wfgs%3D&reserved=0><https://na01.
>>>>> safelinks.protect
>>>>>>>> ion.outlook.com/?url=http%3A%2F%2FWP.com&data=02%7C01%7C%
>>>>> 7Cdb97bd994ab24e
>>>>>>>> e2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178de
>>>>> cee1%7C0%7C0%7C636446023
>>>>>>>> 931803217&sdata=pPTlG8DjwzO%2FN%2B0reuRRSegBNuKdtuonR2fro55wfg
>>>>> s%3D&reserv
>>>>>>>> ed=0> before
>>>>>>>> continue working on content so we can
>>>>>>>>> detect whatever issue we could get.
>>>>>>>>>
>>>>>>>>> Thanks!
>>>>>>>>>
>>>>>>>>> Carlos
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> 2017-10-24 18:56 GMT+02:00 Dave Fisher
>>>>> <dave2wave@comcast.net<mailto:
>>>>>>>> dave2wave@comcast.net><ma...@comcast.net>>:
>>>>>>>>>
>>>>>>>>> Hi Carlos,
>>>>>>>>>
>>>>>>>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira
>>>>> <carlosrovira@apache.org<
>>>>>>>> mailto:carlosrovira@apache.org><ma...@apache.org>>
>>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Hi,
>>>>>>>>>
>>>>>>>>> just let you know that I tried to create an static version of
>>> the
>>>>>>>>> preview
>>>>>>>>> site with success. I use this plugin :
>>>>>>>>>
>>>>>>>>> https://na01.safelinks.protection.outlook.com/?url=
>>>>>>>> https%3A%2F%2Fwordpres
>>>>>>>>>
>>>>>>>> s.org<https://na01.safelinks.protection.outlook.com/?url=
>>>>> http%3A%2F%2Fs.o
>>>>>>>> rg%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b1b5a7b3443
>>>>>>>> 8794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>>>>> 6zrqW3l9%2BJqeOxjih
>>>>>>>> uPWtMuguPsUDWnbqhyRxVXiTfI%3D&reserved=0>%2Fplugins%
>>>>> 2Fsimply-static%2F&da
>>>>>>>> ta=02%7C01%7C%
>>>>>>>> 7Cb448363ee5984b3b3e0f
>>>>>>>>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
>>>>>>>> cee1%7C0%7C0%7C636444624020033
>>>>>>>>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpn
>>> rieARat1lz2bk%3D&reserved=0
>>>>>>>>>
>>>>>>>>> and we can generate all static content with relative or absolute
>>>>> urls.
>>>>>>>>> The
>>>>>>>>> final preview site in static is 134mb
>>>>>>>>>
>>>>>>>>> Another thing I was searching was to use a WP to Jekyll exporter
>>>>> but
>>>>>>>>> this
>>>>>>>>> is not what I wanted since it seems Jekyll is all about markdown
>>>>> and
>>>>>>>>> we
>>>>>>>>> want a full html site with all the eye candy JS+CSS resources.
>>> In
>>>>> the
>>>>>>>>> end,
>>>>>>>>> and thinking more about it, is not what we want since although
>>> the
>>>>>>>>> site
>>>>>>>>> would be exported ok, we don't want to upload it to the GitHub
>>>>> pages
>>>>>>>>> like
>>>>>>>>> we discusses in the other thread due to expose part of the code
>>> of
>>>>> a
>>>>>>>>> commercial wp theme.
>>>>>>>>>
>>>>>>>>> So, the workflow we can use is: Use the WP backend to enter new
>>>>>>>>> content
>>>>>>>>> and
>>>>>>>>> modify existing want with ease (this is important is we want
>>> people
>>>>>>>>> contributing here). Next, with all changes done, generate a
>>> static
>>>>>>>>> version
>>>>>>>>> and replace the entire site with a fresh generated static site
>>> at
>>>>>>>>>
>>>>>>>>
>>>
>>>>> royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=ht
>>>>> tps%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%7C637c696a2755417
>>>>> 0019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644649
>>>>> 5300309403&sdata=NX4DYwHDg7mc0fCcOJQiUInXeTlOR5BBjNgsv09I3tw%3D&reserve
>>>>> d=0.
>>> outlook.com/?url=http
>>>>> s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%
>>> 7Cf48589d8bd1f492c5fa
>>>>> a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C63644639288262
>>>>> 1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
>>>>> outlook.com/?url=http
>>>>>>>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
>>>>> 7Cdb97bd994ab24ee2f91c08d51
>>>>>>>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>>>> 7C636446023931803217&s
>>>>>>>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&
>>> reserved=0>.
>>>>> and
>>>>>>>> as well route the
>>>>>>>> more friendly domain to this
>>>>>>>>> if
>>>>>>>>> board is ok with that.
>>>>>>>>>
>>>>>>>>> Yes! External domain
>>>>>>>>
>>>
>>>>> royalysdk.org<https://na01.safelinks.protection.outlook.com/?url=https%
>>>>> 3A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a275
>>>>> 54170019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364
>>>>> 46495300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&r
>>>>> eserved=0.
>>> com/?url=https%3A
>>>>> %2F%2Fna01.safelinks.protection.outlook&data=02%
>>> 7C01%7C%7Cf48589d8bd1f492
>>>>> c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C6364463928
>>>>> 82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
>>> S9p2zHjJMq%2FnM%3D&reserved=
>>>>> 0.
>>>>> com/?url=http%3A%
>>>>>>>> 2F%2Froyalysdk.org%2F&data=02%7C01%7C%
>>> 7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%
>>>>>>>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>>>> 7C636446023931803217&sdata=Dmo
>>>>>>>> CAUlAVHkkOp0uFdDH0%2FoUUU9qwdl00M8fWRe888Q%3D&reserved=0> is
>>>>> redirected
>>>>>>>> to
>>>>>>>>
>>>
>>>>> royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=ht
>>>>> tps%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%7C637c696a2755417
>>>>> 0019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644649
>>>>> 5300309403&sdata=NX4DYwHDg7mc0fCcOJQiUInXeTlOR5BBjNgsv09I3tw%3D&reserve
>>>>> d=0.
>>> outlook.com/?url=http
>>>>> s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%
>>> 7Cf48589d8bd1f492c5fa
>>>>> a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C63644639288262
>>>>> 1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
>>>>> outlook.com/?url=http
>>>>>>>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
>>>>> 7Cdb97bd994ab24ee2f91c08d51
>>>>>>>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>>>> 7C636446023931803217&s
>>>>>>>>
>>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>
>>>>> as
>>>>>>>>> discussed.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> We can check with apache board or trademarks what they propose
>>>>> about
>>>>>>>>> to
>>>>>>>>> create a
>>>>>>>>
>>>
>>>>> Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=https%
>>>>> 3A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a275
>>>>> 54170019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364
>>>>> 46495300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&r
>>>>> eserved=0.
>>> com/?url=https%3A
>>>>> %2F%2Fna01.safelinks.protection.outlook&data=02%
>>> 7C01%7C%7Cf48589d8bd1f492
>>>>> c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C6364463928
>>>>> 82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
>>> S9p2zHjJMq%2FnM%3D&reserved=
>>>>> 0.
>>>>> com/?url=http%3A%
>>>>>>>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%
>>> 7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%
>>>>>>>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>>>> 7C636446023931803217&sdata=%2B
>>>>>>>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
>>>>> account
>>>>>>>> managed by Apache
>>>>>>>> and migrate from my
>>>>>>>>> server
>>>>>>>>> to that account, and all this stuff from there, since if I
>>> remember
>>>>>>>>> some
>>>>>>>>> people said that would be more ok with Apache.I'd end removing
>>> my
>>>>> temp
>>>>>>>>> subdomain after this.
>>>>>>>>>
>>>>>>>>> The advantage of using the
>>>>>>>>
>>>
>>>>> Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=https%
>>>>> 3A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a275
>>>>> 54170019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364
>>>>> 46495300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&r
>>>>> eserved=0.
>>> com/?url=https%3A
>>>>> %2F%2Fna01.safelinks.protection.outlook&data=02%
>>> 7C01%7C%7Cf48589d8bd1f492
>>>>> c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C6364463928
>>>>> 82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
>>> S9p2zHjJMq%2FnM%3D&reserved=
>>>>> 0.
>>>>> com/?url=http%3A%
>>>>>>>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%
>>> 7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%
>>>>>>>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>>>>> 7C636446023931803217&sdata=%2B
>>>>>>>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
>>>>>>>> location is twofold:
>>>>>>>>>
>>>>>>>>> (1) Wordpress keeps security up to date.
>>>>>>>>> (2) If something happens to you or your company then we have
>>> better
>>>>>>>>> access.
>>>>>>>>>
>>>>>>>>> I suspect though that with the status export method this will
>>> not
>>>>> be
>>>>>>>> as
>>>>>>>>> great a concern.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> What do you think? Can I move this with the people we were
>>> talking
>>>>>>>>> some
>>>>>>>>> weeks ago?
>>>>>>>>>
>>>>>>>>> Either you or I can email Trademarks with the plan.
>>>>>>>>>
>>>>>>>>> We can then discuss the redirection with Infrastructure and get
>>> the
>>>>>>>> site
>>>>>>>>> checked in.
>>>>>>>>>
>>>>>>>>> Regards,
>>>>>>>>> Dave
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Let me know in order to start making the next steps
>>>>>>>>>
>>>>>>>>> Thanks
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> Carlos Rovira
>>>>>>>>>
>>>>>>>>> https://na01.safelinks.protection.outlook.com/?url=
>>>>>>>> http%3A%2F%2Fabout.me%
>>>>>>>>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>>>>>>>> 73f8%7Cfa7b1
>>>>>>>>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>>>>>>>> sdata=1q5B1u1lLR
>>>>>>>>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>>
>>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>>>>>>> http%3A%2F%2Fwww.codeo
>>>>>>>>>
>>>>>>>>
>>>
>>>>> scopic.com<https://na01.safelinks.protection.outlook.com/?url=https%3A%
>>>>> 2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a275541
>>>>> 70019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364464
>>>>> 95300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&rese
>>>>> rved=0.
>>> com/?url=https%3A%2F
>>>>> %2Fna01.safelinks.protection.outlook&data=02%
>>> 7C01%7C%7Cf48589d8bd1f492c5f
>>>>> aa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C6364463928826
>>>
>>>>> 21163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0
>>>>> .
>>>>> com/?url=http%3A%2F%
>>>>>>>> 2Fscopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b
>>>>>>>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>>>>> sdata=oG9idkXzU
>>>>>>>>
>>> tg91G5vhl5P0Dn2u8gXX55UvN172PAlPXs%3D&reserved=0>&data=02%7C01%7C%
>>>>>>>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>>>>>>>>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>>>>>>>> sdata=Y%2Fkytu4lJUWu5H
>>>>>>>>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<https://na01.safelinks.protection.outlook.com/?url=https%3A%2
>>>>> F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a2755417
>>>>> 0019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644649
>>>>> 5300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&reser
>>>>> ved=0.
>>> com/?url=https%3A%2F%
>>>>> 2Fna01.safelinks.protection.outlook&data=02%7C01%7C%
>>> 7Cf48589d8bd1f492c5fa
>>>>> a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C63644639288262
>>>
>>>>> 1163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0.
>>>>> com/?url=http%3A%2F%2
>>>>>>>> Fcopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b1b
>>>>>>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>>>>> sdata=ZPPDqp5SNhK
>>>>>>>> C2rzYxfzkSV7f8lDtLmaRyyaMAlvtRcw%3D&reserved=0>&data=02%7C01%7C%
>>>>>>>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>>>>>>>>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
>>>>>>>> 2Fkytu4lJUWu5Hz
>>>>>>>>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Conocenos Avant2 en 1 minuto!
>>>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>>>>>>> https%3A%2F%2Favant2.e
>>>>>>>>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>>>>>>>> 73f8%7Cfa7b1b5a
>>>>>>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>>>>>>>> sdata=SJmmZQTVSb0tmX
>>>>>>>>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>>>>>>>>> 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.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>>
>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>>>> http%3A%2F%2Fwww.codeo
>>>>>>> scopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b1b5a7b
>>>>>>> 34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>>>>> sdata=ZPowinnGs4jxxXQ4
>>>>>>> hULLfJLfWsGXx9zNLKnS9W7JoNY%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%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b1b5a7b3
>>>>>>> 4438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>>>>> ZPowinnGs4jxxXQ4h
>>>>>>> ULLfJLfWsGXx9zNLKnS9W7JoNY%3D&reserved=0
>>>>>>>
>>>>>>>
>>>>>>> Conocenos Avant2 en 1 minuto!
>>>>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>>>> https%3A%2F%2Favant2.e
>>>>>>> s%2F%23video&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>>>>> 6496%7Cfa7b1b5a
>>>>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>>>>> sdata=ZiX3l%2FtQwsOG
>>>>>>> QN%2BibIJ5pxYpI5UboaH26BzM%2F9AtaLg%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
>>>>>>> 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.
>>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>> http%3A%2F%2Fwww.codeo
>>>> scopic.com&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
>>> 4cfc%7Cfa7b1b5a7b
>>>> 34438794aed2c178decee1%7C0%7C0%7C636446392882621163&
>>> sdata=lKI9XjSOeXi%2Brk
>>>> UN0qJG%2F57in9KVLsXMs2yU56LYHmk%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%7Cf48589d8bd1f492c5faa08d51c9f
>>> 4cfc%7Cfa7b1b5a7b3
>>>> 4438794aed2c178decee1%7C0%7C0%7C636446392882621163&
>>> sdata=lKI9XjSOeXi%2BrkU
>>>> N0qJG%2F57in9KVLsXMs2yU56LYHmk%3D&reserved=0
>>>>
>>>>
>>>> Conocenos Avant2 en 1 minuto!
>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>> https%3A%2F%2Favant2.e
>>>> s%2F%23video&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
>>> 4cfc%7Cfa7b1b5a
>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636446392882621163&
>>> sdata=H2q8lqkz3DT6UD
>>>> tSbrEjUPjektN2ii9zreOhSmlCdB0%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
>>>> 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.
>>>
>>>
>>
>>
>> --
>>
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>> scopic.com&data=02%7C01%7C%7C637c696a27554170019708d51cb724b5%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636446495300309403&sdata=55cIzTLKfzqGo%2F
>> HGX%2FXfL15xYVHFio9w%2B53ZFLeOMKs%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%7C637c696a27554170019708d51cb724b5%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636446495300309403&sdata=55cIzTLKfzqGo%2FH
>> GX%2FXfL15xYVHFio9w%2B53ZFLeOMKs%3D&reserved=0
>>
>>
>> Conocenos Avant2 en 1 minuto!
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>> s%2F%23video&data=02%7C01%7C%7C637c696a27554170019708d51cb724b5%7Cfa7b1b5a
>> 7b34438794aed2c178decee1%7C0%7C0%7C636446495300309403&sdata=12fJSD64x7wVLx
>> p%2BoS9nTVHp1snqwQNif9LVIJmm1GU%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
>> 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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
OK, it sounds like there is general agreement from the technical
perspective and that we don't have enough people and that we want to get
something up on royale.a.o sooner rather than later. What I'm trying to
figure out is what is the best way to get a site up on royale.a.o. I also
realized that we haven't done a review from the Apache perspective [1].
We might need places for a link to the license and a donate button and
some other things.
But once we have that, I think our choices are:
1) keep pushing to allow hosting on WP for royale.a.o.
2) Do one static export and copy to the Git repo currently behind roe.a.o
3) try to recreate the look and feel in standard CSS/HTML/JS.
We could do #2 for now and try to get to #3 before we do a lot more
website work.
Thoughts?
-Alex
[1] http://www.apache.org/foundation/marks/pmcs
On 10/26/17, 2:18 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Hi Alex,
>
>2017-10-26 22:06 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
>
>> Hi Carlos,
>>
>> I have a WP-based blog, so I understand how easy it is to write some
>>text
>> and have it look nice. But I'm still confused about who owns what.
>>Does
>> Envato/Greatives own the look and feel of royale.codeoscopic.com or do
>> you?
>
>
>codeoscopic owns a license of movedo theme.
>anyone that buys the license (59$) will own it, so I think it's not a huge
>quantity of money
>
>
>
>> I understand that Royale is tuned more towards web applications but
>> to my mind, I see more and more web sites being about interactivity
>>rather
>> than just displaying text and images. Even blog commenting and upvoting
>> looks like an app to me.
>>
>
>The two worlds interesect, that's evidently, but are different beast. I
>tried to make in the past
>some website with Flex, and although I did it and we get some cool
>effects,
>in the end it wasn't the
>right tool for the job. I did as well an Application in wordpress with
>some
>plugins due to time restrictions
>and while I did it, again it was not the right tool for the job and many
>things was very limited.
>
>
>>
>> I would like to some day use Royale to create the page you've prototyped
>> at royale.codeoscopic.com and maybe enhance it by having a Royale news
>> feed or some other backend connectivity for some of the content. But
>>can
>> we replicate the look and feel of what you have prototyped and put that
>> under ALv2? I think we have to find a way to make that possible. The
>> theme or CSS that we use to replicate your prototype may not be our
>> default theme/CSS, but it should still be a valid theme or CSS file and
>> components.
>>
>
>without doubt, but for me this is not the right time to do it. As Harbs
>already agree, we need
>to put a website online ASAP.
>
>We can always come back and with time, can make that work. But IMHO, we
>need to choose
>an strategy and see what things are needed first and organize efforts. For
>me UI theme is more need than replicate something that we already have.
>
>
>>
>> That's why I'm concerned that working from Movedo is going to leak into
>> other things we want to do. But if we start from scratch and try to
>> replicate the visuals you've chosen, I would hope we can get something
>> that looks similar quickly and then invite more folks to help tune it.
>> And as Harbs says, I'm not asking you to do that work, someone else can.
>> What you've done already is significant and very helpful and I think you
>> made the right choice of using your WP skills to create it quickly.
>
>
>Right, but for me that work could fit into Royale examples, but would not
>be of much use in the framework
>
>
>> If we were to reproduce your prototype in Royale, I would want to create
>> re-usable components such as:
>> MenuBar
>> SearchShareUserProfileMoreMenuBar
>> TopBar (that holds all of the icon, title, MenuBar and
>> SearchShareProfileButtonBar)
>> IconTitleTextPanel
>> And more...
>>
>>
>I think you are right if we want to recreate the website and make Royale
>components...again for me this is and example.
>
>But, if I start to create a styling that could fit more use cases and be
>the default Express Component Set face? Don't you think that work would be
>more valuable? I think so, and is what I want to contribute next.
>That would be more "application" style and less "web" style. based on that
>work we can make more theme projects like Apache Flex already has and have
>an Application property "theme" to switch between themes. I think that is
>what I think people migrating from Apache Flex SDK expects.
>
>
>
>> Then someone else can come along and assemble their own site from these
>> pieces.
>>
>
>completely right, but expect many few people doing that since, or at least
>very residual, since there are other tools far better to do the job. If we
>want to go that route I think we will need to focus in many task that will
>ease that kind of target and make Apache Royale good in that area. For
>example, routing. For Royale to make good websites, routing is essential,
>and no body will use it without be able to configure deep linking in a
>reliable and useful way.
>
>
>>
>> Back in the Adobe days, some folks actually took the FlexStore example,
>> modified it slightly and deployed it in production for their own
>>products.
>> We didn't care that they pretty much used the same look-and-feel. I
>>think
>> we want to make the same sort of thing possible for Royale.
>>
>
>Alex, I think this is possible. In fact, all you expose is completely
>right, but I want you to think in how many hands have we now. Many of this
>things can be done if we get more people on board, but for this to happen
>we need to unblock what we have, and go to other things we need. If I need
>two things (website and themes), I prefer to have 1-1 than 2-0. And in
>some
>months from now, we always can come back and make the website in our
>technology, and maybe even change it for something fresh again.
>
>That's my 2ctns.
>
>Carlos
>
>
>>
>> Thoughts?
>> -Alex
>>
>> On 10/26/17, 11:27 AM, "carlos.rovira@gmail.com on behalf of Carlos
>> Rovira" <carlos.rovira@gmail.com on behalf of
>> carlos.rovira@codeoscopic.com> wrote:
>>
>> >Hi,
>> >
>> >in order to help you, Alex and Harbs (others could join as well) to
>> >understand all the picture, I could create an account for you in
>> >royale.codeoscopic.com
>> >
>> >In this way you could see point 1 of Alex's list (how integrate some
>>new
>> >content in website). and most important, you will see the visual tool
>>to
>> >edit and mount a new content in pages or posts.
>> >
>> >This last thing is one of the main reasons I want to use WP in the day
>>by
>> >day. If you want to create some content, doing manually is a nightmare.
>> >
>> >I'll send you admin users to your accounts and you're free to enter and
>> >watch, (but please don't modify anything to avoid break the actual
>>site)
>> >
>> >In order to create some default theme (point 2), again here I think we
>> >talking about different things. I think we don't want to base our
>>default
>> >theme for UI controls in apache royale in what I did in the theme. That
>> >would be a mistake in since movedo principles are based on website look
>> >and
>> >usability. Fonts and spacing is huge to express content in a modern
>> >website. To make a comparative, if you take MDL and movedo side by
>>side,
>> >the first is for applications while the second is to present text and
>> >images in a website.
>> >
>> >My plan, as I mention before, is to start creating a UI component
>>styles
>> >that could be programed in a theme. I have in mind to make two of
>>them: a
>> >wireframe theme and a full default theme. The first one could have the
>> >same
>> >sizes and fonts but with only outlines and black and white (like the
>>flex
>> >wireframe to avoid style and application when you're prototyping.
>> >
>> >Regarding time to replicate movedo theme with our own styling, I'm
>>sure is
>> >not a two day task, but more, there's so much there, and only to get
>> >something that only will be a shadow of the original.
>> >
>> >As Harbs mention there's people making styling, but as they are not
>> >commenting in this list we don't know anything about if they are doing
>> >something this days, or maybe they couldn't use that time to work on
>>this.
>> >
>> >For last (point 3), I did wordpress themes some years ago, and is a
>>huge
>> >task to do, in time and effort. And with time you can get something of
>> >quality, but again, why we want to spend our time in something we
>>already
>> >have? I don't find anything here, since we are not here to create WP
>> >themes, I prefer to use that time to create an Apache Royale UI theme
>>and
>> >even help to program it, because that is what we really need to make
>>more
>> >people join us.
>> >
>> >
>> >
>> >
>> >2017-10-26 19:37 GMT+02:00 Harbs <ha...@gmail.com>:
>> >
>> >> Another point to consider:
>> >>
>> >> We’ve had some folks offer to help with skinning Royale components.
>>It
>> >> should be pretty straightforward to give them (and anyone else who
>> >>wants to
>> >> help) committer rights to the website repo. If we have more people
>> >>working
>> >> on it, the task of recreating the appearance achieved through the
>>Movedo
>> >> CSS should be al lot easier.
>> >>
>> >> I don’t feel comfortable asking Carlos to do more work than he’s
>> >>offered,
>> >> but with help from others, it might be a lot easier.
>> >>
>> >> Harbs
>> >>
>> >> > On Oct 26, 2017, at 7:41 PM, Alex Harui <ah...@adobe.com.INVALID>
>> >> wrote:
>> >> >
>> >> > Hi Carlos,
>> >> >
>> >> > I don't know if the "Apache Way" is a problem here. So far I
>>think we
>> >> > have heard opinions and concerns but AFAICT no hard policy has been
>> >> quoted
>> >> > that prevents having royale.a.o point to WP.com.
>> >> >
>> >> > But I am still unclear if hosting our site on WP is really the best
>> >> > strategy. I have the following concerns:
>> >> >
>> >> > 1) How would be include a Royale application in our site?
>> >> > 2) How would we style the Royale application to look consistent
>>with
>> >>the
>> >> > rest of the site?
>> >> > 3) Could we ever create a theme based on this styling?
>> >> >
>> >> > I didn't, and still don't, understand how WP themes and their
>> >>licensing
>> >> > work, otherwise I think I would have asked more questions up
>>front. I
>> >> > thought you would own copyright on the results, just like using
>>Adobe
>> >> > Dreamweaver and Adobe Illustrator to build out a site doesn't put
>>the
>> >> > content under Adobe licensing.
>> >> >
>> >> > That doesn't appear to be the case here, but I think we do need to
>> >> > consider the 3 concerns I've listed.
>> >> >
>> >> > Both you and Harbs claim that replicating your prototype's look and
>> >>feel
>> >> > will be a lot of work, but how much work are really talking about,
>> >>and do
>> >> > we have to exactly replicate it (and should we)? If you think
>>about
>> >>how
>> >> > Royale components are created, they work with some default CSS. I
>> >>think
>> >> > if we implement themes, we'll end up with components with
>>particular
>> >> > "sub-DOMs" and CSS that dictates the visuals on those sub-DOMs.
>> >>AIUI, we
>> >> > are expecting artwork from some designers about other default looks
>> >>for
>> >> > Royale components. Won't we be facing a similar challenge of
>>trying
>> >>to
>> >> > figure out the CSS that best matches what we see on a screen?
>> >> >
>> >> > So, I think it is great that WP and MoveDo helped you create this
>> >> > fantastic looking prototype. But, IMO, one direction we can go
>>from
>> >>here
>> >> > is to try to replicate the visuals you created in CSS in a way that
>> >>can
>> >> be
>> >> > re-used via the Apache Way. I think we'd learn about themes as we
>> >>try to
>> >> > do that. Could we get most of the way there in a couple of days?
>> >>Then
>> >> > others can offer fine-tuning via patches.
>> >> >
>> >> > And yes, WP is tuned towards templated content in a consistent way,
>> >>but
>> >> it
>> >> > would be interesting to build Royale components that do something
>> >> similar.
>> >> >
>> >> > Thoughts?
>> >> > -Alex
>> >> >
>> >> > On 10/26/17, 1:12 AM, "carlos.rovira@gmail.com on behalf of Carlos
>> >> Rovira"
>> >> > <carlos.rovira@gmail.com on behalf of
>>carlos.rovira@codeoscopic.com>
>> >> wrote:
>> >> >
>> >> >> Harbs is right,
>> >> >>
>> >> >> to get something that looks cool and consistent is difficult and
>>for
>> >> this
>> >> >> reason I use wordpress+theme (in this case movedo). Is the same
>> >>thing as
>> >> >> why people use flex or royale. Is the way to start from a point
>>where
>> >> you
>> >> >> are more efficient and maintenance can be assumed.
>> >> >>
>> >> >> Alex, you see lots of difference since I customized via movedo
>> >>interface
>> >> >> but as well did some tweaks in custom css (for example the footer
>> >>column
>> >> >> menus)
>> >> >>
>> >> >> So could we rework the site without wp and movedo. Sure, as I
>>stated
>> >>all
>> >> >> sites can be write in different ways, but the long term reason to
>> >>adopt
>> >> a
>> >> >> CMS like WP is to have a backend to introduce content of quality
>>in
>> >>the
>> >> >> most easy way while preserving quality on presentation (styles,
>> >>fonts,
>> >> >> effects...)
>> >> >>
>> >> >> I think we are in a situation where "the Apache way" fails
>>completely
>> >> >> since
>> >> >> we should be able to make this quick and easy and concentrate in
>>our
>> >> >> Royale
>> >> >> code, that is why we are here, and why I tried to go this path: to
>> >>get
>> >> >> something that looks good and professional but to spend very few
>>time
>> >> for
>> >> >> our part.
>> >> >>
>> >> >> I'm very pragmatic, and like to go to the point. All Apache rules
>> >>should
>> >> >> be
>> >> >> focused in protect the code we release, and we should have less
>> >>trouble
>> >> >> with tools like WP, Jira, Nexus, and the rest. In fact Apache is
>> >>using
>> >> >> those tools all along the way, why is so hard to do this?
>> >> >>
>> >> >> We only need:
>> >> >>
>> >> >> * Some host for a Wordpress instance: this could be the current
>> >> >> Codeoscopic
>> >> >> subdomain or whatever people like. I'd be more happy if the wp
>> >>instance
>> >> is
>> >> >> in some server that could be controlled and maintained by ASF. I
>> >>don't
>> >> >> know
>> >> >> if this could be WP.com or some ASF's virtual machine that could
>>host
>> >> >> that.
>> >> >>
>> >> >> * The Movedo theme: I write to Dimitri, from greatives. He is very
>> >> >> supportive and very like the idea, but is not in their hands. He
>> >>point
>> >> me
>> >> >> to talk with envato, and I write to them, but still doesn't have a
>> >> >> response. My thinking here is that we really don't need nothing of
>> >>this.
>> >> >> Envato could donate a license but is only 59$, so is something
>> >> affordable
>> >> >> by a simple donation.
>> >> >>
>> >> >> * Finaly to generate an static site from WP. This is as well not
>> >>needed,
>> >> >> but we can do it. People use to generate wp static version in
>>order
>> >>to
>> >> >> protect their sites from hacking. That's the only relevant point
>>to
>> >>do
>> >> >> this. So for me is something we can do if the rest of community
>>wants
>> >> it.
>> >> >> Is very easy to do.
>> >> >>
>> >> >>
>> >> >> Additionaly: As we are not uploading any website code to any ASF
>> >>repo,
>> >> >> since as I said, it would be like to upload the JIRA source code
>>to
>> >>our
>> >> >> repos, and that doesn't give us anything (we're here to release
>>only
>> >> >> apache
>> >> >> royale code). we can :
>> >> >>
>> >> >> 1.- Use the royale.codeoscopic.com wp instance as the tool for us
>>to
>> >> >> modify
>> >> >> the site (people in our community will have user/pass in this wp
>> >> instance
>> >> >> to create post and pages)
>> >> >> (in this way is similar to the server Alex had on his own to make
>> >>some
>> >> >> apache flex task, correct me if I'm wrong)
>> >> >> Again, it can be royale.codeoscopic.com or other hosting ASF
>>wants.
>> >> >>
>> >> >> 2.- Each time something changes: generate static site and deploy
>>to
>> >> >> royale.apache.org
>> >> >> (in this case the set of static generated html/js/css could not be
>> >> >> uploaded
>> >> >> to any ASF repo since we don't want to release the website code,
>>that
>> >> must
>> >> >> be served in the same way ASF serves JIRA, or whatever other
>> >>commercial
>> >> >> tool
>> >> >>
>> >> >> Hosting a generated site with a movedo commercial theme needs of a
>> >>59$
>> >> >> license that could be donated by envato or donated for other
>> >> >> person/company
>> >> >> (for example Codeoscopic)
>> >> >>
>> >> >> For me this is quick and easy and I think we're not making
>>something
>> >> wrong
>> >> >> in legal terms
>> >> >>
>> >> >> Carlos
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >>
>> >> >> 2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
>> >> >>
>> >> >>> It’s using greatives’ CSS and JS files for styling, layout and
>> >>effects.
>> >> >>>
>> >> >>> Generally, these themes have a lot of flexibility to change the
>> >>look of
>> >> >>> a
>> >> >>> site without messing with CSS and JS.
>> >> >>>
>> >> >>> Can we re-write the CSS and JS to do the same kind of thing?
>> >>Probably.
>> >> >>> But
>> >> >>> it would be a considerable amount of work.
>> >> >>>
>> >> >>> What’s included in the license? I’m really not sure.
>> >> >>>
>> >> >>> It gives rights to us the theme in WordPress. Does that allow
>> >> >>> repurposing
>> >> >>> the CSS and JS files for use elsewhere? I don’t know.
>> >> >>>
>> >> >>> Harbs
>> >> >>>
>> >> >>>> On Oct 26, 2017, at 9:56 AM, Alex Harui
>><ah...@adobe.com.INVALID>
>> >> >>> wrote:
>> >> >>>>
>> >> >>>> I'm still confused about something.
>> >> >>>>
>> >> >>>> Can someone explain how creativity and licensing are
>> >>interconnected?
>> >> >>> I'm not familiar with WP themes, but I think they are templates
>>with
>> >> >>> placeholders for particular aspects of a web page/blog. I've
>>been
>> >>told
>> >> >>> that this Royale site prototype is based on the Movedo theme.
>>When
>> >>I
>> >> >>> searched for it on the internet I ended up here:
>> >> >>> https://na01.safelinks.protection.outlook.com/?url=
>> >> http%3A%2F%2Fgreatives
>> >> >>> .eu%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b1b5a7b344
>> >> >>> 38794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> >> VI0EOLywsaxbKgmhAe
>> >> >>> F08cdZNQjcgtIjyFvJ2R33hlo%3D&reserved=0
>> >> >>> themeforest/themeswitcher/?product=movedo#movedo
>> >> >>>>
>> >> >>>> It doesn't look at all like the prototype at
>> >> >>>
>> >> >>> https://na01.safelinks.protection.outlook.com/?url=
>> >> http%3A%2F%2Froyale.co
>> >> >>> deoscopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b1b
>> >> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> >> sdata=3GHfDzdFp6B
>> >> >>> 4RQMLuP00jKAHmwQ1QMubUd4dgz3FdTA%3D&reserved=0. Maybe the menu
>>bar
>> >> >>> along the top?
>> >> >>>>
>> >> >>>> So what did we license from greatives? Can Carlos or someone
>>else
>> >> >>> try
>> >> >>> to reproduce the prototype without looking at the current CSS and
>> >>maybe
>> >> >>> use
>> >> >>> AL licensed fonts or something like that?
>> >> >>>>
>> >> >>>> Thanks,
>> >> >>>> -Alex
>> >> >>>>
>> >> >>>> From: Dave Fisher
>> >> >>> <da...@comcast.net>>
>> >> >>>> Reply-To: <de...@royale.apache.org>>
>> >> >>>> Date: Tuesday, October 24, 2017 at 11:06 AM
>> >> >>>> To: <de...@royale.apache.org>>
>> >> >>>> Subject: Re: Apache Royale static web site
>> >> >>>>
>> >> >>>> Hi Alex,
>> >> >>>>
>> >> >>>> We will need to ask Carlos to list out all of the themes he uses
>> >>and
>> >> >>> then we will need to track things down and ask questions.
>> >> >>>>
>> >> >>>> Here is the site for what looks like the main theme:
>> >> >>>
>> >> >>> https://na01.safelinks.protection.outlook.com/?url=
>> >> https%3A%2F%2Fgreative
>> >> >>> s.ticksy.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b
>> >> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> >> sdata=KBxlYi2QO
>> >> >>> PDqNGhTsU6GJMhdUggdHVZjiYetcIcE8vE%3D&reserved=0
>> >> >>>>
>> >> >>>> It is the Move Do theme.
>> >> >>>>
>> >> >>>> Regards,
>> >> >>>> Dave
>> >> >>>>
>> >> >>>> On Oct 24, 2017, at 10:56 AM, Alex Harui
>><aharui@adobe.com.INVALID
>> <
>> >> >>> mailto:aharui@adobe.com.INVALID>> wrote:
>> >> >>>>
>> >> >>>> Hi Dave,
>> >> >>>>
>> >> >>>> I'm still wondering, even if we can see and reuse the
>>CSS/JS/HTML,
>> >>do
>> >> >>> we
>> >> >>> have the rights to replicate use of that look-and-feel
>>elsewhere? I
>> >> >>> don't
>> >> >>> understand who owns the creative content.
>> >> >>>>
>> >> >>>> Thoughts?
>> >> >>>> -Alex
>> >> >>>>
>> >> >>>> From: Dave Fisher
>> >><dave2wave@comcast.net<mailto:dave2wave@comcast.net
>> >> >>>> <ma...@comcast.net>>
>> >> >>>> Reply-To: <dev@royale.apache.org<mailto:dev@royale.apache.org
>> >> ><mailto:
>> >> >>> dev@royale.apache.org>>
>> >> >>>> Date: Tuesday, October 24, 2017 at 10:50 AM
>> >> >>>> To: <de...@royale.apache.org><mailto:
>> >> >>> dev@royale.apache.org>>
>> >> >>>> Subject: Re: Apache Royale static web site
>> >> >>>>
>> >> >>>> Hi Alex,
>> >> >>>>
>> >> >>>> On Oct 24, 2017, at 10:43 AM, Alex Harui
>><aharui@adobe.com.INVALID
>> <
>> >> >>>
>>mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>>
>> >> >>> wrote:
>> >> >>>>
>> >> >>>> There is something I don't think I understand. AIUI, at some
>> >>point,
>> >> >>> we
>> >> >>>> will want the Apache Royale site to include actual Royale
>> >> >>> applications,
>> >> >>>> right? And I would think we would want the styling of those
>> >> >>> applications
>> >> >>>> to be consistent with the rest of the site. So I'm not clear
>>how
>> >>we
>> >> >>> will
>> >> >>>> be able to implement the styling/theme of these Royale
>>applications
>> >> >>> if we
>> >> >>>> don't have rights to the styling. I don't understand how WP
>>themes
>> >> >>> and
>> >> >>>> commercial licensing works if we want to replicate that user
>> >> >>> experience
>> >> >>>> outside of WP.
>> >> >>>>
>> >> >>>> We need to examine the static export of the CSS and HTML.
>> >> >>>>
>> >> >>>>
>> >> >>>> If we can use those visuals outside of WP, then why must we
>> >>continue
>> >> >>> to
>> >> >>>> use WP to generate the site? I would hope the theme would be
>> >> >>> implemented
>> >> >>>> as CSS and some templates we could use without WP.
>> >> >>>>
>> >> >>>> We should be able to adapt. Site building in the CMS can get
>> >>complex
>> >> >>> if
>> >> >>> needed. For
>> >> >>>
>>
>>>>OpenOffice.org<https://na01.safelinks.protection.outlook.com/?url=https
>>>>%3A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a27
>>>>554170019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636
>>>>446495300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&
>>>>reserved=0.
>> com/?url=https%3
>> >>A%2F%2Fna01.safelinks.protection.outlook&data=02%
>> 7C01%7C%7Cf48589d8bd1f49
>> >>2c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636446392
>> >>882621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
>> S9p2zHjJMq%2FnM%3D&reserved
>> >>=0.
>> >> com/?url=http%3A
>> >> >>>
>>%2F%2FOpenOffice.org&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7
>> >> >>>
>> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> >> m3Mv
>> >> >>> XfpJIZbB4u1Zhr0AB%2B%2BVI5uPKwu7N33MkPuovjs%3D&reserved=0><
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fna01.s&d
>> >>ata=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
>> 4cfc%7Cfa7b1b5a7b34438794aed
>> >>2c178decee1%7C0%7C0%7C636446392882621163&sdata=
>> hxky0LHm5GqF8zMjFHm3bXfugJ
>> >>xCS6qWPoG%2FbWItNgQ%3D&reserved=0
>> >> >>> afelinks.protection.outlook.com/?url=http%3A%2F%
>> >> 2FOpenOffice.org&data=02%
>> >> >>> 7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>> >> 7Cfa7b1b5a7b34438794aed2c178de
>> >> >>> cee1%7C0%7C0%7C636446023931803217&sdata=m3MvXfpJIZbB4u1Zhr0AB%2B%
>> >> 2BVI5uPK
>> >> >>> wu7N33MkPuovjs%3D&reserved=0>
>> >> >>> we use the legacy html pulling out the title and content body and
>> >>place
>> >> >>> it
>> >> >>> within a markdown template.
>> >> >>>>
>> >> >>>>
>> >> >>>> Also, if someone wants to patch the site, they can't just offer
>>a
>> >> >>> patch
>> >> >>> of
>> >> >>>> the HTML right? They would need to figure out where in WP it
>>comes
>> >> >>> from?
>> >> >>>> Is there a patch process for WP content?
>> >> >>>>
>> >> >>>> Possibly.
>> >> >>>>
>> >> >>>>
>> >> >>>> Sorry if there is some basic thing I am missing.
>> >> >>>>
>> >> >>>> It will get complex first as we figure out how to embed and
>>then it
>> >> >>> will
>> >> >>> get simplified as we find the best way.
>> >> >>>>
>> >> >>>> Regards,
>> >> >>>> Dave
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> Thanks,
>> >> >>>> -Alex
>> >> >>>>
>> >> >>>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
>> >> >>> carlos.rovira@gmail.com><ma...@gmail.com> on
>>behalf
>> >>of
>> >> >>> Carlos
>> >> >>>> Rovira"
>> >> >>> <ca...@gmail.com><mailto:
>> >> >>> carlos.rovira@gmail.com> on behalf of
>> >> >>>>
>>carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
>> >> >>>> <ma...@codeoscopic.com>> wrote:
>> >> >>>>
>> >> >>>> Thanks Dave,
>> >> >>>>
>> >> >>>> I'll write an email to trademarks to start with the process. I
>> >>think
>> >> >>> is
>> >> >>>> better to migrate to
>> >> >>> WP.com<https://na01.safelinks.protection.outlook.com/?url=
>> >> http%3A%2F%2FWP
>> >> >>> .com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b1b5a7b34438
>> >> >>> 794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> >> pPTlG8DjwzO%2FN%2B0r
>> >> >>> euRRSegBNuKdtuonR2fro55wfgs%3D&reserved=0><https://na01.
>> >> safelinks.protect
>> >> >>> ion.outlook.com/?url=http%3A%2F%2FWP.com&data=02%7C01%7C%
>> >> 7Cdb97bd994ab24e
>> >> >>> e2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178de
>> >> cee1%7C0%7C0%7C636446023
>> >> >>> 931803217&sdata=pPTlG8DjwzO%2FN%2B0reuRRSegBNuKdtuonR2fro55wfg
>> >> s%3D&reserv
>> >> >>> ed=0> before
>> >> >>> continue working on content so we can
>> >> >>>> detect whatever issue we could get.
>> >> >>>>
>> >> >>>> Thanks!
>> >> >>>>
>> >> >>>> Carlos
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> 2017-10-24 18:56 GMT+02:00 Dave Fisher
>> >><dave2wave@comcast.net<mailto:
>> >> >>> dave2wave@comcast.net><ma...@comcast.net>>:
>> >> >>>>
>> >> >>>> Hi Carlos,
>> >> >>>>
>> >> >>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira
>> >><carlosrovira@apache.org<
>> >> >>> mailto:carlosrovira@apache.org><ma...@apache.org>>
>> >> >>>> wrote:
>> >> >>>>
>> >> >>>> Hi,
>> >> >>>>
>> >> >>>> just let you know that I tried to create an static version of
>>the
>> >> >>>> preview
>> >> >>>> site with success. I use this plugin :
>> >> >>>>
>> >> >>>> https://na01.safelinks.protection.outlook.com/?url=
>> >> >>> https%3A%2F%2Fwordpres
>> >> >>>>
>> >> >>> s.org<https://na01.safelinks.protection.outlook.com/?url=
>> >> http%3A%2F%2Fs.o
>> >> >>> rg%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b1b5a7b3443
>> >> >>> 8794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> >> 6zrqW3l9%2BJqeOxjih
>> >> >>> uPWtMuguPsUDWnbqhyRxVXiTfI%3D&reserved=0>%2Fplugins%
>> >> 2Fsimply-static%2F&da
>> >> >>> ta=02%7C01%7C%
>> >> >>> 7Cb448363ee5984b3b3e0f
>> >> >>>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
>> >> >>> cee1%7C0%7C0%7C636444624020033
>> >> >>>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpn
>> rieARat1lz2bk%3D&reserved=0
>> >> >>>>
>> >> >>>> and we can generate all static content with relative or absolute
>> >>urls.
>> >> >>>> The
>> >> >>>> final preview site in static is 134mb
>> >> >>>>
>> >> >>>> Another thing I was searching was to use a WP to Jekyll exporter
>> >>but
>> >> >>>> this
>> >> >>>> is not what I wanted since it seems Jekyll is all about markdown
>> >>and
>> >> >>>> we
>> >> >>>> want a full html site with all the eye candy JS+CSS resources.
>>In
>> >>the
>> >> >>>> end,
>> >> >>>> and thinking more about it, is not what we want since although
>>the
>> >> >>>> site
>> >> >>>> would be exported ok, we don't want to upload it to the GitHub
>> >>pages
>> >> >>>> like
>> >> >>>> we discusses in the other thread due to expose part of the code
>>of
>> >>a
>> >> >>>> commercial wp theme.
>> >> >>>>
>> >> >>>> So, the workflow we can use is: Use the WP backend to enter new
>> >> >>>> content
>> >> >>>> and
>> >> >>>> modify existing want with ease (this is important is we want
>>people
>> >> >>>> contributing here). Next, with all changes done, generate a
>>static
>> >> >>>> version
>> >> >>>> and replace the entire site with a fresh generated static site
>>at
>> >> >>>>
>> >> >>>
>>
>>>>royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=ht
>>>>tps%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%7C637c696a2755417
>>>>0019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644649
>>>>5300309403&sdata=NX4DYwHDg7mc0fCcOJQiUInXeTlOR5BBjNgsv09I3tw%3D&reserve
>>>>d=0.
>> outlook.com/?url=http
>> >>s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%
>> 7Cf48589d8bd1f492c5fa
>> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C63644639288262
>> >>1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
>> >> outlook.com/?url=http
>> >> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
>> >> 7Cdb97bd994ab24ee2f91c08d51
>> >> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> 7C636446023931803217&s
>> >> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&
>> reserved=0>.
>> >> and
>> >> >>> as well route the
>> >> >>> more friendly domain to this
>> >> >>>> if
>> >> >>>> board is ok with that.
>> >> >>>>
>> >> >>>> Yes! External domain
>> >> >>>
>>
>>>>royalysdk.org<https://na01.safelinks.protection.outlook.com/?url=https%
>>>>3A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a275
>>>>54170019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364
>>>>46495300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&r
>>>>eserved=0.
>> com/?url=https%3A
>> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
>> 7C01%7C%7Cf48589d8bd1f492
>> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6364463928
>> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
>> S9p2zHjJMq%2FnM%3D&reserved=
>> >>0.
>> >> com/?url=http%3A%
>> >> >>> 2F%2Froyalysdk.org%2F&data=02%7C01%7C%
>> 7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%
>> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> 7C636446023931803217&sdata=Dmo
>> >> >>> CAUlAVHkkOp0uFdDH0%2FoUUU9qwdl00M8fWRe888Q%3D&reserved=0> is
>> >> redirected
>> >> >>> to
>> >> >>>
>>
>>>>royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=ht
>>>>tps%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%7C637c696a2755417
>>>>0019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644649
>>>>5300309403&sdata=NX4DYwHDg7mc0fCcOJQiUInXeTlOR5BBjNgsv09I3tw%3D&reserve
>>>>d=0.
>> outlook.com/?url=http
>> >>s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%
>> 7Cf48589d8bd1f492c5fa
>> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C63644639288262
>> >>1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
>> >> outlook.com/?url=http
>> >> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
>> >> 7Cdb97bd994ab24ee2f91c08d51
>> >> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> 7C636446023931803217&s
>> >> >>>
>>data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>
>> >>as
>> >> >>>> discussed.
>> >> >>>>
>> >> >>>>
>> >> >>>> We can check with apache board or trademarks what they propose
>> >>about
>> >> >>>> to
>> >> >>>> create a
>> >> >>>
>>
>>>>Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=https%
>>>>3A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a275
>>>>54170019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364
>>>>46495300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&r
>>>>eserved=0.
>> com/?url=https%3A
>> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
>> 7C01%7C%7Cf48589d8bd1f492
>> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6364463928
>> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
>> S9p2zHjJMq%2FnM%3D&reserved=
>> >>0.
>> >> com/?url=http%3A%
>> >> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%
>> 7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%
>> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> 7C636446023931803217&sdata=%2B
>> >> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
>> >>account
>> >> >>> managed by Apache
>> >> >>> and migrate from my
>> >> >>>> server
>> >> >>>> to that account, and all this stuff from there, since if I
>>remember
>> >> >>>> some
>> >> >>>> people said that would be more ok with Apache.I'd end removing
>>my
>> >>temp
>> >> >>>> subdomain after this.
>> >> >>>>
>> >> >>>> The advantage of using the
>> >> >>>
>>
>>>>Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=https%
>>>>3A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a275
>>>>54170019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364
>>>>46495300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&r
>>>>eserved=0.
>> com/?url=https%3A
>> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
>> 7C01%7C%7Cf48589d8bd1f492
>> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6364463928
>> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
>> S9p2zHjJMq%2FnM%3D&reserved=
>> >>0.
>> >> com/?url=http%3A%
>> >> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%
>> 7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%
>> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> >> 7C636446023931803217&sdata=%2B
>> >> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
>> >> >>> location is twofold:
>> >> >>>>
>> >> >>>> (1) Wordpress keeps security up to date.
>> >> >>>> (2) If something happens to you or your company then we have
>>better
>> >> >>>> access.
>> >> >>>>
>> >> >>>> I suspect though that with the status export method this will
>>not
>> >>be
>> >> >>> as
>> >> >>>> great a concern.
>> >> >>>>
>> >> >>>>
>> >> >>>> What do you think? Can I move this with the people we were
>>talking
>> >> >>>> some
>> >> >>>> weeks ago?
>> >> >>>>
>> >> >>>> Either you or I can email Trademarks with the plan.
>> >> >>>>
>> >> >>>> We can then discuss the redirection with Infrastructure and get
>>the
>> >> >>> site
>> >> >>>> checked in.
>> >> >>>>
>> >> >>>> Regards,
>> >> >>>> Dave
>> >> >>>>
>> >> >>>>
>> >> >>>> Let me know in order to start making the next steps
>> >> >>>>
>> >> >>>> Thanks
>> >> >>>>
>> >> >>>>
>> >> >>>> --
>> >> >>>> Carlos Rovira
>> >> >>>>
>> >> >>>> https://na01.safelinks.protection.outlook.com/?url=
>> >> >>> http%3A%2F%2Fabout.me%
>> >> >>>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>> >> >>> 73f8%7Cfa7b1
>> >> >>>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> >> >>> sdata=1q5B1u1lLR
>> >> >>>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>>
>> >> >>>> --
>> >> >>>>
>> >> >>>> <https://na01.safelinks.protection.outlook.com/?url=
>> >> >>> http%3A%2F%2Fwww.codeo
>> >> >>>>
>> >> >>>
>>
>>>>scopic.com<https://na01.safelinks.protection.outlook.com/?url=https%3A%
>>>>2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a275541
>>>>70019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364464
>>>>95300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&rese
>>>>rved=0.
>> com/?url=https%3A%2F
>> >>%2Fna01.safelinks.protection.outlook&data=02%
>> 7C01%7C%7Cf48589d8bd1f492c5f
>> >>aa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C6364463928826
>>
>>>>21163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0
>>>>.
>> >> com/?url=http%3A%2F%
>> >> >>> 2Fscopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b
>> >> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> >> sdata=oG9idkXzU
>> >> >>>
>>tg91G5vhl5P0Dn2u8gXX55UvN172PAlPXs%3D&reserved=0>&data=02%7C01%7C%
>> >> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>> >> >>>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> >> >>> sdata=Y%2Fkytu4lJUWu5H
>> >> >>>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<https://na01.safelinks.protection.outlook.com/?url=https%3A%2
>>>>F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7C637c696a2755417
>>>>0019708d51cb724b5%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644649
>>>>5300309403&sdata=NiS%2FyKcl2hUU4CGmX8DNJvm17bSdDpEnTPfIv6JF1KU%3D&reser
>>>>ved=0.
>> com/?url=https%3A%2F%
>> >>2Fna01.safelinks.protection.outlook&data=02%7C01%7C%
>> 7Cf48589d8bd1f492c5fa
>> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C63644639288262
>>
>>>>1163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0.
>> >> com/?url=http%3A%2F%2
>> >> >>> Fcopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b1b
>> >> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> >> sdata=ZPPDqp5SNhK
>> >> >>> C2rzYxfzkSV7f8lDtLmaRyyaMAlvtRcw%3D&reserved=0>&data=02%7C01%7C%
>> >> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>> >> >>>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
>> >> >>> 2Fkytu4lJUWu5Hz
>> >> >>>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>> >> >>>>
>> >> >>>>
>> >> >>>> Conocenos Avant2 en 1 minuto!
>> >> >>>> <https://na01.safelinks.protection.outlook.com/?url=
>> >> >>> https%3A%2F%2Favant2.e
>> >> >>>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>> >> >>> 73f8%7Cfa7b1b5a
>> >> >>>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> >> >>> sdata=SJmmZQTVSb0tmX
>> >> >>>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>> >> >>>> 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.
>> >> >>>>
>> >> >>>>
>> >> >>>
>> >> >>>
>> >> >>
>> >> >>
>> >> >> --
>> >> >>
>> >> >> <https://na01.safelinks.protection.outlook.com/?url=
>> >> http%3A%2F%2Fwww.codeo
>> >> >> scopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b1b5a7b
>> >> >> 34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> >> sdata=ZPowinnGs4jxxXQ4
>> >> >> hULLfJLfWsGXx9zNLKnS9W7JoNY%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%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b1b5a7b3
>> >> >> 4438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> >> ZPowinnGs4jxxXQ4h
>> >> >> ULLfJLfWsGXx9zNLKnS9W7JoNY%3D&reserved=0
>> >> >>
>> >> >>
>> >> >> Conocenos Avant2 en 1 minuto!
>> >> >> <https://na01.safelinks.protection.outlook.com/?url=
>> >> https%3A%2F%2Favant2.e
>> >> >> s%2F%23video&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> >> 6496%7Cfa7b1b5a
>> >> >> 7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> >> sdata=ZiX3l%2FtQwsOG
>> >> >> QN%2BibIJ5pxYpI5UboaH26BzM%2F9AtaLg%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
>> >> >> 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.
>> >> >
>> >>
>> >>
>> >
>> >
>> >--
>> >
>> ><https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.codeo
>> >scopic.com&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
>> 4cfc%7Cfa7b1b5a7b
>> >34438794aed2c178decee1%7C0%7C0%7C636446392882621163&
>> sdata=lKI9XjSOeXi%2Brk
>> >UN0qJG%2F57in9KVLsXMs2yU56LYHmk%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%7Cf48589d8bd1f492c5faa08d51c9f
>> 4cfc%7Cfa7b1b5a7b3
>> >4438794aed2c178decee1%7C0%7C0%7C636446392882621163&
>> sdata=lKI9XjSOeXi%2BrkU
>> >N0qJG%2F57in9KVLsXMs2yU56LYHmk%3D&reserved=0
>> >
>> >
>> >Conocenos Avant2 en 1 minuto!
>> ><https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Favant2.e
>> >s%2F%23video&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
>> 4cfc%7Cfa7b1b5a
>> >7b34438794aed2c178decee1%7C0%7C0%7C636446392882621163&
>> sdata=H2q8lqkz3DT6UD
>> >tSbrEjUPjektN2ii9zreOhSmlCdB0%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
>> >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.
>>
>>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7C637c696a27554170019708d51cb724b5%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636446495300309403&sdata=55cIzTLKfzqGo%2F
>HGX%2FXfL15xYVHFio9w%2B53ZFLeOMKs%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%7C637c696a27554170019708d51cb724b5%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636446495300309403&sdata=55cIzTLKfzqGo%2FH
>GX%2FXfL15xYVHFio9w%2B53ZFLeOMKs%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7C637c696a27554170019708d51cb724b5%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636446495300309403&sdata=12fJSD64x7wVLx
>p%2BoS9nTVHp1snqwQNif9LVIJmm1GU%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
>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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Alex, I'll ask in the private thread about this and see what Greg and
others has to said and then come back
let me try this and we could talk about it
2017-11-03 2:55 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> Hi Carlos,
>
> I'm not quite sure what you meant here. I think without a deadline there
> is no chance they will approve. Is the deadline what you meant by "other
> option"?
>
> -Alex
>
> On 11/2/17, 4:36 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> wrote:
>
> >Hi,
> >
> >since nobody is responding to the latest plan of put static html site on
> >our repo, I think this could be what we want and could get it live even
> >without a concrete deadline so we can go with other solution with more or
> >less time. Let me try to ask in the current thread with trademarks if it's
> >ok to do this although we didn't get any response on legal, if they put
> >some problems we could see that other option. do you agree?
> >
> >Thanks
> >
> >2017-11-02 22:49 GMT+01:00 Harbs <ha...@gmail.com>:
> >
> >> I would ask for 90 days to give us a bit more time, but I think this is
> >>a
> >> good idea.
> >>
> >> > On Nov 2, 2017, at 11:44 PM, Alex Harui <ah...@adobe.com.INVALID>
> >> wrote:
> >> >
> >> > FWIW, maybe the least effort choice right now is to ask ASF Trademarks
> >> and
> >> > Infra for a 60 day exception to redirect royale.a.o to
> >> > royale.codeoscopic.com
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Froyale.c
> >>odeoscopic.com%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa
> >>7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636452626010525995&
> sdata=gB4SXym
> >>lfdv2HPJX%2Fa5KwkLKXYH%2F98Iyh6CgbqVwHUI%3D&reserved=0>. That'll keep
> >> us for burning more energy trying to
> >> > make this work some other way so we can get other stuff done,
> >>including
> >> > creating a similar site the traditional way based on the things we
> >>liked
> >> > from royale.codeoscopic.
> >> >
> >> > Thoughts?
> >> > -Alex
> >> >
> >> > On 10/30/17, 3:45 AM, "carlos.rovira@gmail.com <mailto:
> >> carlos.rovira@gmail.com> on behalf of Carlos Rovira"
> >> > <carlos.rovira@gmail.com <ma...@gmail.com> on behalf
> of
> >> carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>>
> >> wrote:
> >> >
> >> >> Hi Alex,
> >> >>
> >> >> notice that the actual preview site is only that. We told about to
> >>get
> >> the
> >> >> site to some compromise point when we could evaluate it.
> >> >> As I get to that point, folks agree about the direction of the site.
> >>We
> >> >> are
> >> >> know seeing how to put this working for us. It seems that current
> >>talk
> >> >> with
> >> >> Greg and others is going on the good track. So If we end pushing the
> >> >> preview site to royale.apache.org, I'll be working ASAP to finish
> the
> >> rest
> >> >> of the site in order to get it final.
> >> >>
> >> >> Let's see what happen.
> >> >>
> >> >> Thanks
> >> >>
> >> >> Carlos
> >> >>
> >> >>
> >> >>
> >> >> 2017-10-30 4:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >> >>
> >> >>> I think there were objections to that as well. Also note that the
> >> >>> current
> >> >>> state of
> >> >>> https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Froyale.co
> >><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fna01.sa
> >>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34
> >>438794aed2c178decee1%7C0%7C0%7C636452626010525995&
> sdata=MyV%2BUtPretK0tCC
> >>WBESOLTjLF0Bck%2Fljj%2FSwOURKJYE%3D&reserved=0.
> >> protection.outlook.com/?url=http%3A%2F%2Froyale.co>
> >> >>> deoscopic.com
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fdeoscopi
> >>c.com%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b3
> >>4438794aed2c178decee1%7C0%7C0%7C636452626010525995&
> sdata=DV1IQrOAv1xBeBzT
> >>3iBX3PH%2FK3spZ%2BkEQw19FyvQtL4%3D&reserved=0>&data=02%7C01%7C%
> >> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b
> >> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
> >> sdata=0899xFFPDf8
> >> >>> NmBRpAp%2FlHVCzspV5ed7fKnf6WwJPIlM%3D&reserved=0 may need some
> other
> >> >>> adjustments to
> >> >>> be approved by Apache's VP Branding as a valid home page for an
> >>Apache
> >> >>> project. This page [1] mentions a "Donate" button and some other
> >> >>> things.
> >> >>>
> >> >>> Carlos has done a great job and spent plenty of his precious time on
> >> >>> this
> >> >>> already, but the choice of commercial themes is turning out to be a
> >> >>> problem. One option I think we have is to see what changes Carlos
> >> would
> >> >>> have to make to his site for it to be ruled as a "fan site" and
> >>build a
> >> >>> simpler and conforming site on royale.a.o with CSS that "looks
> >>similar"
> >> >>> but with conforming content.
> >> >>>
> >> >>> My 2 cents,
> >> >>> -Alex
> >> >>>
> >> >>> [1]
> >> >>> https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fwww.apach
> >><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fna01.sa
> >>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34
> >>438794aed2c178decee1%7C0%7C0%7C636452626010525995&
> sdata=MyV%2BUtPretK0tCC
> >>WBESOLTjLF0Bck%2Fljj%2FSwOURKJYE%3D&reserved=0.
> >> protection.outlook.com/?url=http%3A%2F%2Fwww.apach>
> >> >>> e.org
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fe.org%2F
> >>&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34438794a
> >>ed2c178decee1%7C0%7C0%7C636452626010525995&sdata=
> nFhbJlMEWmlXL8rTZjr%2FYJ
> >>uogiFi%2F4%2FrzeWMnxkNpY8%3D&reserved=0>%2Ffoundation%
> 2Fmarks%2Fpmcs&data
> >>=02%7C01%
> >> 7C%7Cbd5f09b6f99c4af619510
> >> >>> 8d51f8370fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C6364495717568822
> >> >>> 95&sdata=wkvJSvbx7mZ4ZlVaI5pp36eed0MEE6BdROZVTJu7nfs%3D&reserved=0
> >> >>>
> >> >>> On 10/29/17, 10:51 AM, "omuppi1@gmail.com <mailto:omuppi1@gmail.com
> >
> >> on behalf of OmPrakash
> >> >>> Muppirala" <omuppi1@gmail.com <ma...@gmail.com> on behalf
> >>of
> >> bigosmallm@gmail.com <ma...@gmail.com>> wrote:
> >> >>>
> >> >>>> I agree. We might want to avoid that.
> >> >>>>
> >> >>>> Looks like the option of pointing to a wp.com
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwp.com%2
> >>F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34438794
> >>aed2c178decee1%7C0%7C0%7C636452626010525995&sdata=
> w8UeUrnwJ3W7RloMjW9zwk9
> >>ISuIS0nVaAYzRWiU0nDQ%3D&reserved=0> site
> >> has been done
> >> >>> already.
> >> >>>>
> >> >>>> Can we push for this?
> >> >>>>
> >> >>>> Thanks,
> >> >>>> Om
> >> >>>>
> >> >>>> On Oct 29, 2017 10:37 AM, "Carlos Rovira"
> >> >>> <carlos.rovira@codeoscopic.com
> >><ma...@codeoscopic.com>>
> >> >>>> wrote:
> >> >>>>
> >> >>>>> Hi Om,
> >> >>>>>
> >> >>>>> I think that's the better option, but my question is how to do
> >>this.
> >> >>>>>
> >> >>>>> How we can put the static generated site live under
> >> royale.apache.org
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Froyale.a
> >>pache.org%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5
> >>a7b34438794aed2c178decee1%7C0%7C0%7C636452626010525995&
> sdata=kktPhISM8UZE
> >>lkXdY570mwFULNOaprlUs%2BObd1v%2BdQ4%3D&reserved=0>
> >> >>>>> without having that code on some repo? (the latest is very
> >>important)
> >> >>>>> can we do this? do you know how to do it?
> >> >>>>>
> >> >>>>> note: remember that we don't want to upload the actual website
> >>code
> >> >>> to
> >> >>>>> some
> >> >>>>> public repo due to commercial code licenses (movedo theme license)
> >> >>>>>
> >> >>>>> Thanks
> >> >>>>>
> >> >>>>> Carlos
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> 2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala
> >><bigosmallm@gmail.com
> >> <ma...@gmail.com>>:
> >> >>>>>
> >> >>>>>> I suggest we just release what Carlos as a static website for
> >>now.
> >> >>>>>> As time goes by, volunteers can build up a separate website using
> >> >>> just
> >> >>>>>> Royale. At some point we can simply swap out the wp.com <
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwp.com%2F
> >>&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34438794a
> >>ed2c178decee1%7C0%7C0%7C636452626010536004&sdata=
> brKHppK76sogysVk09rLScMO
> >>sJ08ezFkT9bD5BYnlUM%3D&reserved=0> site with
> >> >>> the
> >> >>>>> new
> >> >>>>>> Royale based website.
> >> >>>>>>
> >> >>>>>> There is absolutely no requirement that the new site has to look
> >> >>> like
> >> >>>>> the
> >> >>>>>> wp.com
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwp.com%2
> >>F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34438794
> >>aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=
> brKHppK76sogysVk09rLScM
> >>OsJ08ezFkT9bD5BYnlUM%3D&reserved=0>. So, worrying about legal
> >>implications of
> >> maintaining the
> >> >>> same
> >> >>>>>> look
> >> >>>>>> and feel is premature.
> >> >>>>>>
> >> >>>>>> Let's not make perfect the enemy of the good.
> >> >>>>>>
> >> >>>>>> Thanks,
> >> >>>>>> Om
> >> >>>>>>
> >> >>>>>> On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira
> >> >>>>> <carlosrovira@apache.org <ma...@apache.org>>
> >> >>>>>> wrote:
> >> >>>>>>
> >> >>>>>>> Thanks Yishay for your words
> >> >>>>>>>
> >> >>>>>>> 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yishayjobs@hotmail.com
> >> <ma...@hotmail.com>>:
> >> >>>>>>>
> >> >>>>>>>> Carlos, I agree that our resources are limited and this this
> >> >>> might
> >> >>>>> not
> >> >>>>>> be
> >> >>>>>>>> the best way to spend them at this point. However, there are
> >> >>> some
> >> >>>>>> points
> >> >>>>>>>> that have not been mentioned in this discussion that make me
> >> >>>>> think we
> >> >>>>>>>> should try to move our site to Royale.
> >> >>>>>>>>
> >> >>>>>>>> One is that we claim to be different to other frameworks in
> >> >>> that
> >> >>>>>> overhead
> >> >>>>>>>> can be much smaller. A site that performs at the level of a
> >> >>>>> classic
> >> >>>>>>> static
> >> >>>>>>>> site would be a significant proof of concept. If it doesn’t
> >> >>>>> perform
> >> >>>>>> well
> >> >>>>>>>> enough we’ll have some information on where we can improve in
> >> >>> that
> >> >>>>>>> regard.
> >> >>>>>>>>
> >> >>>>>>>> Related, we need to finally start eating our dog food. The more
> >> >>>>> visible
> >> >>>>>>>> our dog food, the more feedback we’ll get.
> >> >>>>>>>>
> >> >>>>>>>> Also, if new people really want to contribute to out site, I’d
> >> >>>>> much
> >> >>>>>>> rather
> >> >>>>>>>> have them learn Royale than WP.
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>> That's ok. I only said that we are run out of resources and I
> >> >>> don't
> >> >>>>> see
> >> >>>>>>> many people available to make this effort.
> >> >>>>>>> In my case, my plan was to focus on design to bring something
> >> >>> good
> >> >>>>> to
> >> >>>>>>> production, but didn't expect such problems with something we
> >> >>> should
> >> >>>>> put
> >> >>>>>>> online, complete with real content and focus on other things.
> >> >>>>>>> In my case, I would prefer to donate my tiny time in other
> >>things
> >> >>>>> more
> >> >>>>>>> needed. In concrete I prefer to donate in "theme" feature,
> >> >>> styling
> >> >>>>>> express,
> >> >>>>>>> and so on...
> >> >>>>>>> But if someone wants to work on replicate the site with Royale
> >> >>> our
> >> >>>>> other
> >> >>>>>>> html plain code, that's right.
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>>>
> >> >>>>>>>> In other words, whether or not Royale ends up being a good tool
> >> >>>>> for
> >> >>>>>>>> classic web sites I see some reasons to try and achieve that
> >> >>> for
> >> >>>>> our
> >> >>>>>> own
> >> >>>>>>>> site.
> >> >>>>>>>>
> >> >>>>>>>> Finally, suppose I wanted to replicate your site in Royale just
> >> >>>>> for
> >> >>>>> the
> >> >>>>>>>> heck of it. Would that be ok from a legal stand-point? I
> >> >>> couldn’t
> >> >>>>>>>> understand that from the thread so far.
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>> If we recreate the site with our own set of CSS, JS, that's
> >> >>> right.
> >> >>>>> Nobody
> >> >>>>>>> could say us nothing since no commercial code is involved there.
> >> >>>>>>> As well, If we put the actual static generated site online,
> >> >>> without
> >> >>>>>> having
> >> >>>>>>> to upload the code to any repo, that's alright as well, since is
> >> >>> the
> >> >>>>>> normal
> >> >>>>>>> use, and the rest of people using that theme is doing the same.
> >> >>>>>>>
> >> >>>>>>> Thanks for your considerations.
> >> >>>>>>>
> >> >>>>>>> Carlos
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>>>
> >> >>>>>>>> Thanks, and great work so far.
> >> >>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>>
> >> >>>>>>>
> >> >>>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> --
> >> >>>>>
> >> >>>>>
> >> >>>>> <https://na01.safelinks.protection.outlook.com/?url= <
> >> https://na01.safelinks.protection.outlook.com/?url=>
> >> >>> http%3A%2F%2Fwww.code
> >> >>>>> oscopic.com
> >><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Foscopic
> .
> >>com%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b344
> >>38794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=
> bxjDK400uDWLdm2HAj
> >>snwqGJ9e97ckSjAIt6nwnEDms%3D&reserved=0>&data=02%7C01%7C%
> >> 7C76c801888c3d4049ca8c08d51ef5
> >> >>> b4c5%7Cfa7b1b5a
> >> >>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> >> >>> sdata=9LfHDTE%2BCri
> >> >>>>> 6177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0>
> >> >>>>>
> >> >>>>> Carlos Rovira
> >> >>>>>
> >> >>>>> Director General
> >> >>>>>
> >> >>>>> M: +34 607 22 60 05
> >> >>>>>
> >> >>>>>
> >> >>>>> https://na01.safelinks.protection.outlook.com/?url= <
> >> https://na01.safelinks.protection.outlook.com/?url=>
> >> >>> http%3A%2F%2Fwww.codeo
> >> >>>>> scopic.com
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fscopic.c
> >>om%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b3443
> >>8794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=
> mF2YITpsdZnE2Wq0lmQ
> >>al4L5y%2F%2BrB61VP%2BypY8waI74%3D&reserved=0>&data=02%7C01%7C%
> >> 7C76c801888c3d4049ca8c08d51ef5
> >> >>> b4c5%7Cfa7b1b5a7
> >> >>>>> b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> >> >>> sdata=9LfHDTE%2BCri6
> >> >>>>> 177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0
> >> >>>>>
> >> >>>>>
> >> >>>>> Conocenos Avant2 en 1 minuto!
> >> >>>
> >> >>>>> <https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Favant <https://na01.safelinks.
> protection.outlook.com/?url=
> >> https%3A%2F%2Favant>
> >> >>>>> 2
> >> >>> .
> >> >>>>> es%2F%23video&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
> >> >>> b4c5%7Cfa7b1b
> >> >>>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> >> >>> sdata=AHQo5j38pqI
> >> >>>>> 0UEabS7J1AW0jQEwOvWcvqFsVdpKTakM%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
> >> >>>>> 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.
> >> >>>>>
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> <https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fwww.codeo
> >><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fna01.sa
> >>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34
> >>438794aed2c178decee1%7C0%7C0%7C636452626010536004&
> sdata=o5%2FbQqEXnW5F7H%
> >>2Fced2ohKlQxWc%2FvUula9QjeDJtjcU%3D&reserved=0.
> >> protection.outlook.com/?url=http%3A%2F%2Fwww.codeo>
> >> >> scopic.com
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fscopic.c
> >>om%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b3443
> >>8794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=
> mF2YITpsdZnE2Wq0lmQ
> >>al4L5y%2F%2BrB61VP%2BypY8waI74%3D&reserved=0>&data=02%7C01%7C%
> >> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b
> >> >> 34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
> >> sdata=x6RD%2Fu56EFXXK5
> >> >> aWDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%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
> >><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fna01.sa
> >>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34
> >>438794aed2c178decee1%7C0%7C0%7C636452626010536004&
> sdata=o5%2FbQqEXnW5F7H%
> >>2Fced2ohKlQxWc%2FvUula9QjeDJtjcU%3D&reserved=0.
> >> protection.outlook.com/?url=http%3A%2F%2Fwww.codeos>
> >> >> copic.com
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fcopic.co
> >>m%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34438
> >>794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=%
> 2B7Iy9%2BQDCQYtzctF
> >>O9uDT4243I%2BnzLnNH1PQ1gAegHc%3D&reserved=0>&data=02%7C01%7C%
> >> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b3
> >> >> 4438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=
> >> x6RD%2Fu56EFXXK5a
> >> >> WDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%3D&reserved=0
> >> >>
> >> >>
> >> >> Conocenos Avant2 en 1 minuto!
> >> >> <https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Favant2.e
> >><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fna01.sa
> >>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b34
> >>438794aed2c178decee1%7C0%7C0%7C636452626010536004&
> sdata=o5%2FbQqEXnW5F7H%
> >>2Fced2ohKlQxWc%2FvUula9QjeDJtjcU%3D&reserved=0.
> >> protection.outlook.com/?url=https%3A%2F%2Favant2.e>
> >> >> s%2F%23video&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f83
> >> 70fa%7Cfa7b1b5a
> >> >> 7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
> >> sdata=7F7ul9r6XR%2Bj
> >> >> K%2FpAqHmvUtNPoNaMSaZlixNNaOLbbC0%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
> >> >> 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.
> >>
> >>
> >
> >
> >--
> >
> ><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo
> >scopic.com&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b
> >34438794aed2c178decee1%7C0%7C0%7C636452626010536004&
> sdata=XOtz%2FqKfQ8RaMa
> >V%2F6lbsxXMKcaC6c1r%2FuuAEbUmrruQ%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%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a7b3
> >4438794aed2c178decee1%7C0%7C0%7C636452626010536004&
> sdata=XOtz%2FqKfQ8RaMaV
> >%2F6lbsxXMKcaC6c1r%2FuuAEbUmrruQ%3D&reserved=0
> >
> >
> >Conocenos Avant2 en 1 minuto!
> ><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant2.e
> >s%2F%23video&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a
> 909c%7Cfa7b1b5a
> >7b34438794aed2c178decee1%7C0%7C0%7C636452626010536004&
> sdata=ii7BU%2Bmws3xh
> >XUkWoUY2kEI2ndr5h59Ww3ogbDFtgPU%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
> >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.
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi Carlos,
I'm not quite sure what you meant here. I think without a deadline there
is no chance they will approve. Is the deadline what you meant by "other
option"?
-Alex
On 11/2/17, 4:36 PM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Hi,
>
>since nobody is responding to the latest plan of put static html site on
>our repo, I think this could be what we want and could get it live even
>without a concrete deadline so we can go with other solution with more or
>less time. Let me try to ask in the current thread with trademarks if it's
>ok to do this although we didn't get any response on legal, if they put
>some problems we could see that other option. do you agree?
>
>Thanks
>
>2017-11-02 22:49 GMT+01:00 Harbs <ha...@gmail.com>:
>
>> I would ask for 90 days to give us a bit more time, but I think this is
>>a
>> good idea.
>>
>> > On Nov 2, 2017, at 11:44 PM, Alex Harui <ah...@adobe.com.INVALID>
>> wrote:
>> >
>> > FWIW, maybe the least effort choice right now is to ask ASF Trademarks
>> and
>> > Infra for a 60 day exception to redirect royale.a.o to
>> > royale.codeoscopic.com
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.c
>>odeoscopic.com%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa
>>7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636452626010525995&sdata=gB4SXym
>>lfdv2HPJX%2Fa5KwkLKXYH%2F98Iyh6CgbqVwHUI%3D&reserved=0>. That'll keep
>> us for burning more energy trying to
>> > make this work some other way so we can get other stuff done,
>>including
>> > creating a similar site the traditional way based on the things we
>>liked
>> > from royale.codeoscopic.
>> >
>> > Thoughts?
>> > -Alex
>> >
>> > On 10/30/17, 3:45 AM, "carlos.rovira@gmail.com <mailto:
>> carlos.rovira@gmail.com> on behalf of Carlos Rovira"
>> > <carlos.rovira@gmail.com <ma...@gmail.com> on behalf of
>> carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>>
>> wrote:
>> >
>> >> Hi Alex,
>> >>
>> >> notice that the actual preview site is only that. We told about to
>>get
>> the
>> >> site to some compromise point when we could evaluate it.
>> >> As I get to that point, folks agree about the direction of the site.
>>We
>> >> are
>> >> know seeing how to put this working for us. It seems that current
>>talk
>> >> with
>> >> Greg and others is going on the good track. So If we end pushing the
>> >> preview site to royale.apache.org, I'll be working ASAP to finish the
>> rest
>> >> of the site in order to get it final.
>> >>
>> >> Let's see what happen.
>> >>
>> >> Thanks
>> >>
>> >> Carlos
>> >>
>> >>
>> >>
>> >> 2017-10-30 4:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>> >>
>> >>> I think there were objections to that as well. Also note that the
>> >>> current
>> >>> state of
>> >>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Froyale.co
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.sa
>>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34
>>438794aed2c178decee1%7C0%7C0%7C636452626010525995&sdata=MyV%2BUtPretK0tCC
>>WBESOLTjLF0Bck%2Fljj%2FSwOURKJYE%3D&reserved=0.
>> protection.outlook.com/?url=http%3A%2F%2Froyale.co>
>> >>> deoscopic.com
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fdeoscopi
>>c.com%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b3
>>4438794aed2c178decee1%7C0%7C0%7C636452626010525995&sdata=DV1IQrOAv1xBeBzT
>>3iBX3PH%2FK3spZ%2BkEQw19FyvQtL4%3D&reserved=0>&data=02%7C01%7C%
>> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b
>> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
>> sdata=0899xFFPDf8
>> >>> NmBRpAp%2FlHVCzspV5ed7fKnf6WwJPIlM%3D&reserved=0 may need some other
>> >>> adjustments to
>> >>> be approved by Apache's VP Branding as a valid home page for an
>>Apache
>> >>> project. This page [1] mentions a "Donate" button and some other
>> >>> things.
>> >>>
>> >>> Carlos has done a great job and spent plenty of his precious time on
>> >>> this
>> >>> already, but the choice of commercial themes is turning out to be a
>> >>> problem. One option I think we have is to see what changes Carlos
>> would
>> >>> have to make to his site for it to be ruled as a "fan site" and
>>build a
>> >>> simpler and conforming site on royale.a.o with CSS that "looks
>>similar"
>> >>> but with conforming content.
>> >>>
>> >>> My 2 cents,
>> >>> -Alex
>> >>>
>> >>> [1]
>> >>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.apach
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.sa
>>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34
>>438794aed2c178decee1%7C0%7C0%7C636452626010525995&sdata=MyV%2BUtPretK0tCC
>>WBESOLTjLF0Bck%2Fljj%2FSwOURKJYE%3D&reserved=0.
>> protection.outlook.com/?url=http%3A%2F%2Fwww.apach>
>> >>> e.org
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fe.org%2F
>>&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34438794a
>>ed2c178decee1%7C0%7C0%7C636452626010525995&sdata=nFhbJlMEWmlXL8rTZjr%2FYJ
>>uogiFi%2F4%2FrzeWMnxkNpY8%3D&reserved=0>%2Ffoundation%2Fmarks%2Fpmcs&data
>>=02%7C01%
>> 7C%7Cbd5f09b6f99c4af619510
>> >>> 8d51f8370fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C6364495717568822
>> >>> 95&sdata=wkvJSvbx7mZ4ZlVaI5pp36eed0MEE6BdROZVTJu7nfs%3D&reserved=0
>> >>>
>> >>> On 10/29/17, 10:51 AM, "omuppi1@gmail.com <ma...@gmail.com>
>> on behalf of OmPrakash
>> >>> Muppirala" <omuppi1@gmail.com <ma...@gmail.com> on behalf
>>of
>> bigosmallm@gmail.com <ma...@gmail.com>> wrote:
>> >>>
>> >>>> I agree. We might want to avoid that.
>> >>>>
>> >>>> Looks like the option of pointing to a wp.com
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwp.com%2
>>F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34438794
>>aed2c178decee1%7C0%7C0%7C636452626010525995&sdata=w8UeUrnwJ3W7RloMjW9zwk9
>>ISuIS0nVaAYzRWiU0nDQ%3D&reserved=0> site
>> has been done
>> >>> already.
>> >>>>
>> >>>> Can we push for this?
>> >>>>
>> >>>> Thanks,
>> >>>> Om
>> >>>>
>> >>>> On Oct 29, 2017 10:37 AM, "Carlos Rovira"
>> >>> <carlos.rovira@codeoscopic.com
>><ma...@codeoscopic.com>>
>> >>>> wrote:
>> >>>>
>> >>>>> Hi Om,
>> >>>>>
>> >>>>> I think that's the better option, but my question is how to do
>>this.
>> >>>>>
>> >>>>> How we can put the static generated site live under
>> royale.apache.org
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.a
>>pache.org%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5
>>a7b34438794aed2c178decee1%7C0%7C0%7C636452626010525995&sdata=kktPhISM8UZE
>>lkXdY570mwFULNOaprlUs%2BObd1v%2BdQ4%3D&reserved=0>
>> >>>>> without having that code on some repo? (the latest is very
>>important)
>> >>>>> can we do this? do you know how to do it?
>> >>>>>
>> >>>>> note: remember that we don't want to upload the actual website
>>code
>> >>> to
>> >>>>> some
>> >>>>> public repo due to commercial code licenses (movedo theme license)
>> >>>>>
>> >>>>> Thanks
>> >>>>>
>> >>>>> Carlos
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> 2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala
>><bigosmallm@gmail.com
>> <ma...@gmail.com>>:
>> >>>>>
>> >>>>>> I suggest we just release what Carlos as a static website for
>>now.
>> >>>>>> As time goes by, volunteers can build up a separate website using
>> >>> just
>> >>>>>> Royale. At some point we can simply swap out the wp.com <
>>
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwp.com%2F
>>&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34438794a
>>ed2c178decee1%7C0%7C0%7C636452626010536004&sdata=brKHppK76sogysVk09rLScMO
>>sJ08ezFkT9bD5BYnlUM%3D&reserved=0> site with
>> >>> the
>> >>>>> new
>> >>>>>> Royale based website.
>> >>>>>>
>> >>>>>> There is absolutely no requirement that the new site has to look
>> >>> like
>> >>>>> the
>> >>>>>> wp.com
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwp.com%2
>>F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34438794
>>aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=brKHppK76sogysVk09rLScM
>>OsJ08ezFkT9bD5BYnlUM%3D&reserved=0>. So, worrying about legal
>>implications of
>> maintaining the
>> >>> same
>> >>>>>> look
>> >>>>>> and feel is premature.
>> >>>>>>
>> >>>>>> Let's not make perfect the enemy of the good.
>> >>>>>>
>> >>>>>> Thanks,
>> >>>>>> Om
>> >>>>>>
>> >>>>>> On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira
>> >>>>> <carlosrovira@apache.org <ma...@apache.org>>
>> >>>>>> wrote:
>> >>>>>>
>> >>>>>>> Thanks Yishay for your words
>> >>>>>>>
>> >>>>>>> 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yishayjobs@hotmail.com
>> <ma...@hotmail.com>>:
>> >>>>>>>
>> >>>>>>>> Carlos, I agree that our resources are limited and this this
>> >>> might
>> >>>>> not
>> >>>>>> be
>> >>>>>>>> the best way to spend them at this point. However, there are
>> >>> some
>> >>>>>> points
>> >>>>>>>> that have not been mentioned in this discussion that make me
>> >>>>> think we
>> >>>>>>>> should try to move our site to Royale.
>> >>>>>>>>
>> >>>>>>>> One is that we claim to be different to other frameworks in
>> >>> that
>> >>>>>> overhead
>> >>>>>>>> can be much smaller. A site that performs at the level of a
>> >>>>> classic
>> >>>>>>> static
>> >>>>>>>> site would be a significant proof of concept. If it doesn’t
>> >>>>> perform
>> >>>>>> well
>> >>>>>>>> enough we’ll have some information on where we can improve in
>> >>> that
>> >>>>>>> regard.
>> >>>>>>>>
>> >>>>>>>> Related, we need to finally start eating our dog food. The more
>> >>>>> visible
>> >>>>>>>> our dog food, the more feedback we’ll get.
>> >>>>>>>>
>> >>>>>>>> Also, if new people really want to contribute to out site, I’d
>> >>>>> much
>> >>>>>>> rather
>> >>>>>>>> have them learn Royale than WP.
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>> That's ok. I only said that we are run out of resources and I
>> >>> don't
>> >>>>> see
>> >>>>>>> many people available to make this effort.
>> >>>>>>> In my case, my plan was to focus on design to bring something
>> >>> good
>> >>>>> to
>> >>>>>>> production, but didn't expect such problems with something we
>> >>> should
>> >>>>> put
>> >>>>>>> online, complete with real content and focus on other things.
>> >>>>>>> In my case, I would prefer to donate my tiny time in other
>>things
>> >>>>> more
>> >>>>>>> needed. In concrete I prefer to donate in "theme" feature,
>> >>> styling
>> >>>>>> express,
>> >>>>>>> and so on...
>> >>>>>>> But if someone wants to work on replicate the site with Royale
>> >>> our
>> >>>>> other
>> >>>>>>> html plain code, that's right.
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>>
>> >>>>>>>> In other words, whether or not Royale ends up being a good tool
>> >>>>> for
>> >>>>>>>> classic web sites I see some reasons to try and achieve that
>> >>> for
>> >>>>> our
>> >>>>>> own
>> >>>>>>>> site.
>> >>>>>>>>
>> >>>>>>>> Finally, suppose I wanted to replicate your site in Royale just
>> >>>>> for
>> >>>>> the
>> >>>>>>>> heck of it. Would that be ok from a legal stand-point? I
>> >>> couldn’t
>> >>>>>>>> understand that from the thread so far.
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>> If we recreate the site with our own set of CSS, JS, that's
>> >>> right.
>> >>>>> Nobody
>> >>>>>>> could say us nothing since no commercial code is involved there.
>> >>>>>>> As well, If we put the actual static generated site online,
>> >>> without
>> >>>>>> having
>> >>>>>>> to upload the code to any repo, that's alright as well, since is
>> >>> the
>> >>>>>> normal
>> >>>>>>> use, and the rest of people using that theme is doing the same.
>> >>>>>>>
>> >>>>>>> Thanks for your considerations.
>> >>>>>>>
>> >>>>>>> Carlos
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>>>
>> >>>>>>>> Thanks, and great work so far.
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> --
>> >>>>>
>> >>>>>
>> >>>>> <https://na01.safelinks.protection.outlook.com/?url= <
>> https://na01.safelinks.protection.outlook.com/?url=>
>> >>> http%3A%2F%2Fwww.code
>> >>>>> oscopic.com
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Foscopic.
>>com%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b344
>>38794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=bxjDK400uDWLdm2HAj
>>snwqGJ9e97ckSjAIt6nwnEDms%3D&reserved=0>&data=02%7C01%7C%
>> 7C76c801888c3d4049ca8c08d51ef5
>> >>> b4c5%7Cfa7b1b5a
>> >>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>> >>> sdata=9LfHDTE%2BCri
>> >>>>> 6177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0>
>> >>>>>
>> >>>>> Carlos Rovira
>> >>>>>
>> >>>>> Director General
>> >>>>>
>> >>>>> M: +34 607 22 60 05
>> >>>>>
>> >>>>>
>> >>>>> https://na01.safelinks.protection.outlook.com/?url= <
>> https://na01.safelinks.protection.outlook.com/?url=>
>> >>> http%3A%2F%2Fwww.codeo
>> >>>>> scopic.com
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fscopic.c
>>om%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b3443
>>8794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=mF2YITpsdZnE2Wq0lmQ
>>al4L5y%2F%2BrB61VP%2BypY8waI74%3D&reserved=0>&data=02%7C01%7C%
>> 7C76c801888c3d4049ca8c08d51ef5
>> >>> b4c5%7Cfa7b1b5a7
>> >>>>> b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>> >>> sdata=9LfHDTE%2BCri6
>> >>>>> 177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0
>> >>>>>
>> >>>>>
>> >>>>> Conocenos Avant2 en 1 minuto!
>> >>>
>> >>>>> <https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Favant <https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Favant>
>> >>>>> 2
>> >>> .
>> >>>>> es%2F%23video&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
>> >>> b4c5%7Cfa7b1b
>> >>>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>> >>> sdata=AHQo5j38pqI
>> >>>>> 0UEabS7J1AW0jQEwOvWcvqFsVdpKTakM%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
>> >>>>> 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.
>> >>>>>
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >>
>> >> <https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.codeo
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.sa
>>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34
>>438794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=o5%2FbQqEXnW5F7H%
>>2Fced2ohKlQxWc%2FvUula9QjeDJtjcU%3D&reserved=0.
>> protection.outlook.com/?url=http%3A%2F%2Fwww.codeo>
>> >> scopic.com
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fscopic.c
>>om%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b3443
>>8794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=mF2YITpsdZnE2Wq0lmQ
>>al4L5y%2F%2BrB61VP%2BypY8waI74%3D&reserved=0>&data=02%7C01%7C%
>> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b
>> >> 34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
>> sdata=x6RD%2Fu56EFXXK5
>> >> aWDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%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
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.sa
>>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34
>>438794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=o5%2FbQqEXnW5F7H%
>>2Fced2ohKlQxWc%2FvUula9QjeDJtjcU%3D&reserved=0.
>> protection.outlook.com/?url=http%3A%2F%2Fwww.codeos>
>> >> copic.com
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fcopic.co
>>m%2F&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34438
>>794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=%2B7Iy9%2BQDCQYtzctF
>>O9uDT4243I%2BnzLnNH1PQ1gAegHc%3D&reserved=0>&data=02%7C01%7C%
>> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b3
>> >> 4438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=
>> x6RD%2Fu56EFXXK5a
>> >> WDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%3D&reserved=0
>> >>
>> >>
>> >> Conocenos Avant2 en 1 minuto!
>> >> <https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Favant2.e
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.sa
>>felinks&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b34
>>438794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=o5%2FbQqEXnW5F7H%
>>2Fced2ohKlQxWc%2FvUula9QjeDJtjcU%3D&reserved=0.
>> protection.outlook.com/?url=https%3A%2F%2Favant2.e>
>> >> s%2F%23video&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f83
>> 70fa%7Cfa7b1b5a
>> >> 7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
>> sdata=7F7ul9r6XR%2Bj
>> >> K%2FpAqHmvUtNPoNaMSaZlixNNaOLbbC0%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
>> >> 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.
>>
>>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=XOtz%2FqKfQ8RaMa
>V%2F6lbsxXMKcaC6c1r%2FuuAEbUmrruQ%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%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=XOtz%2FqKfQ8RaMaV
>%2F6lbsxXMKcaC6c1r%2FuuAEbUmrruQ%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7Cbab2e5f3273d44537f9f08d5224a909c%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636452626010536004&sdata=ii7BU%2Bmws3xh
>XUkWoUY2kEI2ndr5h59Ww3ogbDFtgPU%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
>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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi,
since nobody is responding to the latest plan of put static html site on
our repo, I think this could be what we want and could get it live even
without a concrete deadline so we can go with other solution with more or
less time. Let me try to ask in the current thread with trademarks if it's
ok to do this although we didn't get any response on legal, if they put
some problems we could see that other option. do you agree?
Thanks
2017-11-02 22:49 GMT+01:00 Harbs <ha...@gmail.com>:
> I would ask for 90 days to give us a bit more time, but I think this is a
> good idea.
>
> > On Nov 2, 2017, at 11:44 PM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > FWIW, maybe the least effort choice right now is to ask ASF Trademarks
> and
> > Infra for a 60 day exception to redirect royale.a.o to
> > royale.codeoscopic.com <http://royale.codeoscopic.com/>. That'll keep
> us for burning more energy trying to
> > make this work some other way so we can get other stuff done, including
> > creating a similar site the traditional way based on the things we liked
> > from royale.codeoscopic.
> >
> > Thoughts?
> > -Alex
> >
> > On 10/30/17, 3:45 AM, "carlos.rovira@gmail.com <mailto:
> carlos.rovira@gmail.com> on behalf of Carlos Rovira"
> > <carlos.rovira@gmail.com <ma...@gmail.com> on behalf of
> carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>>
> wrote:
> >
> >> Hi Alex,
> >>
> >> notice that the actual preview site is only that. We told about to get
> the
> >> site to some compromise point when we could evaluate it.
> >> As I get to that point, folks agree about the direction of the site. We
> >> are
> >> know seeing how to put this working for us. It seems that current talk
> >> with
> >> Greg and others is going on the good track. So If we end pushing the
> >> preview site to royale.apache.org, I'll be working ASAP to finish the
> rest
> >> of the site in order to get it final.
> >>
> >> Let's see what happen.
> >>
> >> Thanks
> >>
> >> Carlos
> >>
> >>
> >>
> >> 2017-10-30 4:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> >>
> >>> I think there were objections to that as well. Also note that the
> >>> current
> >>> state of
> >>> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Froyale.co <https://na01.safelinks.
> protection.outlook.com/?url=http%3A%2F%2Froyale.co>
> >>> deoscopic.com <http://deoscopic.com/>&data=02%7C01%7C%
> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b
> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
> sdata=0899xFFPDf8
> >>> NmBRpAp%2FlHVCzspV5ed7fKnf6WwJPIlM%3D&reserved=0 may need some other
> >>> adjustments to
> >>> be approved by Apache's VP Branding as a valid home page for an Apache
> >>> project. This page [1] mentions a "Donate" button and some other
> >>> things.
> >>>
> >>> Carlos has done a great job and spent plenty of his precious time on
> >>> this
> >>> already, but the choice of commercial themes is turning out to be a
> >>> problem. One option I think we have is to see what changes Carlos
> would
> >>> have to make to his site for it to be ruled as a "fan site" and build a
> >>> simpler and conforming site on royale.a.o with CSS that "looks similar"
> >>> but with conforming content.
> >>>
> >>> My 2 cents,
> >>> -Alex
> >>>
> >>> [1]
> >>> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.apach <https://na01.safelinks.
> protection.outlook.com/?url=http%3A%2F%2Fwww.apach>
> >>> e.org <http://e.org/>%2Ffoundation%2Fmarks%2Fpmcs&data=02%7C01%
> 7C%7Cbd5f09b6f99c4af619510
> >>> 8d51f8370fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C6364495717568822
> >>> 95&sdata=wkvJSvbx7mZ4ZlVaI5pp36eed0MEE6BdROZVTJu7nfs%3D&reserved=0
> >>>
> >>> On 10/29/17, 10:51 AM, "omuppi1@gmail.com <ma...@gmail.com>
> on behalf of OmPrakash
> >>> Muppirala" <omuppi1@gmail.com <ma...@gmail.com> on behalf of
> bigosmallm@gmail.com <ma...@gmail.com>> wrote:
> >>>
> >>>> I agree. We might want to avoid that.
> >>>>
> >>>> Looks like the option of pointing to a wp.com <http://wp.com/> site
> has been done
> >>> already.
> >>>>
> >>>> Can we push for this?
> >>>>
> >>>> Thanks,
> >>>> Om
> >>>>
> >>>> On Oct 29, 2017 10:37 AM, "Carlos Rovira"
> >>> <carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>>
> >>>> wrote:
> >>>>
> >>>>> Hi Om,
> >>>>>
> >>>>> I think that's the better option, but my question is how to do this.
> >>>>>
> >>>>> How we can put the static generated site live under
> royale.apache.org <http://royale.apache.org/>
> >>>>> without having that code on some repo? (the latest is very important)
> >>>>> can we do this? do you know how to do it?
> >>>>>
> >>>>> note: remember that we don't want to upload the actual website code
> >>> to
> >>>>> some
> >>>>> public repo due to commercial code licenses (movedo theme license)
> >>>>>
> >>>>> Thanks
> >>>>>
> >>>>> Carlos
> >>>>>
> >>>>>
> >>>>>
> >>>>> 2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala <bigosmallm@gmail.com
> <ma...@gmail.com>>:
> >>>>>
> >>>>>> I suggest we just release what Carlos as a static website for now.
> >>>>>> As time goes by, volunteers can build up a separate website using
> >>> just
> >>>>>> Royale. At some point we can simply swap out the wp.com <
> http://wp.com/> site with
> >>> the
> >>>>> new
> >>>>>> Royale based website.
> >>>>>>
> >>>>>> There is absolutely no requirement that the new site has to look
> >>> like
> >>>>> the
> >>>>>> wp.com <http://wp.com/>. So, worrying about legal implications of
> maintaining the
> >>> same
> >>>>>> look
> >>>>>> and feel is premature.
> >>>>>>
> >>>>>> Let's not make perfect the enemy of the good.
> >>>>>>
> >>>>>> Thanks,
> >>>>>> Om
> >>>>>>
> >>>>>> On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira
> >>>>> <carlosrovira@apache.org <ma...@apache.org>>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Thanks Yishay for your words
> >>>>>>>
> >>>>>>> 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yishayjobs@hotmail.com
> <ma...@hotmail.com>>:
> >>>>>>>
> >>>>>>>> Carlos, I agree that our resources are limited and this this
> >>> might
> >>>>> not
> >>>>>> be
> >>>>>>>> the best way to spend them at this point. However, there are
> >>> some
> >>>>>> points
> >>>>>>>> that have not been mentioned in this discussion that make me
> >>>>> think we
> >>>>>>>> should try to move our site to Royale.
> >>>>>>>>
> >>>>>>>> One is that we claim to be different to other frameworks in
> >>> that
> >>>>>> overhead
> >>>>>>>> can be much smaller. A site that performs at the level of a
> >>>>> classic
> >>>>>>> static
> >>>>>>>> site would be a significant proof of concept. If it doesn’t
> >>>>> perform
> >>>>>> well
> >>>>>>>> enough we’ll have some information on where we can improve in
> >>> that
> >>>>>>> regard.
> >>>>>>>>
> >>>>>>>> Related, we need to finally start eating our dog food. The more
> >>>>> visible
> >>>>>>>> our dog food, the more feedback we’ll get.
> >>>>>>>>
> >>>>>>>> Also, if new people really want to contribute to out site, I’d
> >>>>> much
> >>>>>>> rather
> >>>>>>>> have them learn Royale than WP.
> >>>>>>>>
> >>>>>>>
> >>>>>>> That's ok. I only said that we are run out of resources and I
> >>> don't
> >>>>> see
> >>>>>>> many people available to make this effort.
> >>>>>>> In my case, my plan was to focus on design to bring something
> >>> good
> >>>>> to
> >>>>>>> production, but didn't expect such problems with something we
> >>> should
> >>>>> put
> >>>>>>> online, complete with real content and focus on other things.
> >>>>>>> In my case, I would prefer to donate my tiny time in other things
> >>>>> more
> >>>>>>> needed. In concrete I prefer to donate in "theme" feature,
> >>> styling
> >>>>>> express,
> >>>>>>> and so on...
> >>>>>>> But if someone wants to work on replicate the site with Royale
> >>> our
> >>>>> other
> >>>>>>> html plain code, that's right.
> >>>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>> In other words, whether or not Royale ends up being a good tool
> >>>>> for
> >>>>>>>> classic web sites I see some reasons to try and achieve that
> >>> for
> >>>>> our
> >>>>>> own
> >>>>>>>> site.
> >>>>>>>>
> >>>>>>>> Finally, suppose I wanted to replicate your site in Royale just
> >>>>> for
> >>>>> the
> >>>>>>>> heck of it. Would that be ok from a legal stand-point? I
> >>> couldn’t
> >>>>>>>> understand that from the thread so far.
> >>>>>>>>
> >>>>>>>
> >>>>>>> If we recreate the site with our own set of CSS, JS, that's
> >>> right.
> >>>>> Nobody
> >>>>>>> could say us nothing since no commercial code is involved there.
> >>>>>>> As well, If we put the actual static generated site online,
> >>> without
> >>>>>> having
> >>>>>>> to upload the code to any repo, that's alright as well, since is
> >>> the
> >>>>>> normal
> >>>>>>> use, and the rest of people using that theme is doing the same.
> >>>>>>>
> >>>>>>> Thanks for your considerations.
> >>>>>>>
> >>>>>>> Carlos
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>>
> >>>>>>>> Thanks, and great work so far.
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>>
> >>>>>
> >>>>> <https://na01.safelinks.protection.outlook.com/?url= <
> https://na01.safelinks.protection.outlook.com/?url=>
> >>> http%3A%2F%2Fwww.code
> >>>>> oscopic.com <http://oscopic.com/>&data=02%7C01%7C%
> 7C76c801888c3d4049ca8c08d51ef5
> >>> b4c5%7Cfa7b1b5a
> >>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> >>> sdata=9LfHDTE%2BCri
> >>>>> 6177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0>
> >>>>>
> >>>>> Carlos Rovira
> >>>>>
> >>>>> Director General
> >>>>>
> >>>>> M: +34 607 22 60 05
> >>>>>
> >>>>>
> >>>>> https://na01.safelinks.protection.outlook.com/?url= <
> https://na01.safelinks.protection.outlook.com/?url=>
> >>> http%3A%2F%2Fwww.codeo
> >>>>> scopic.com <http://scopic.com/>&data=02%7C01%7C%
> 7C76c801888c3d4049ca8c08d51ef5
> >>> b4c5%7Cfa7b1b5a7
> >>>>> b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> >>> sdata=9LfHDTE%2BCri6
> >>>>> 177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0
> >>>>>
> >>>>>
> >>>>> Conocenos Avant2 en 1 minuto!
> >>>
> >>>>> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant>
> >>>>> 2
> >>> .
> >>>>> es%2F%23video&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
> >>> b4c5%7Cfa7b1b
> >>>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> >>> sdata=AHQo5j38pqI
> >>>>> 0UEabS7J1AW0jQEwOvWcvqFsVdpKTakM%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
> >>>>> 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.
> >>>>>
> >>>
> >>>
> >>
> >>
> >> --
> >>
> >> <https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo <https://na01.safelinks.
> protection.outlook.com/?url=http%3A%2F%2Fwww.codeo>
> >> scopic.com <http://scopic.com/>&data=02%7C01%7C%
> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b
> >> 34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
> sdata=x6RD%2Fu56EFXXK5
> >> aWDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%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 <https://na01.safelinks.
> protection.outlook.com/?url=http%3A%2F%2Fwww.codeos>
> >> copic.com <http://copic.com/>&data=02%7C01%7C%
> 7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b3
> >> 4438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=
> x6RD%2Fu56EFXXK5a
> >> WDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%3D&reserved=0
> >>
> >>
> >> Conocenos Avant2 en 1 minuto!
> >> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant2.e <https://na01.safelinks.
> protection.outlook.com/?url=https%3A%2F%2Favant2.e>
> >> s%2F%23video&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f83
> 70fa%7Cfa7b1b5a
> >> 7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&
> sdata=7F7ul9r6XR%2Bj
> >> K%2FpAqHmvUtNPoNaMSaZlixNNaOLbbC0%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
> >> 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.
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Harbs <ha...@gmail.com>.
I would ask for 90 days to give us a bit more time, but I think this is a good idea.
> On Nov 2, 2017, at 11:44 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> FWIW, maybe the least effort choice right now is to ask ASF Trademarks and
> Infra for a 60 day exception to redirect royale.a.o to
> royale.codeoscopic.com <http://royale.codeoscopic.com/>. That'll keep us for burning more energy trying to
> make this work some other way so we can get other stuff done, including
> creating a similar site the traditional way based on the things we liked
> from royale.codeoscopic.
>
> Thoughts?
> -Alex
>
> On 10/30/17, 3:45 AM, "carlos.rovira@gmail.com <ma...@gmail.com> on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com <ma...@gmail.com> on behalf of carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>> wrote:
>
>> Hi Alex,
>>
>> notice that the actual preview site is only that. We told about to get the
>> site to some compromise point when we could evaluate it.
>> As I get to that point, folks agree about the direction of the site. We
>> are
>> know seeing how to put this working for us. It seems that current talk
>> with
>> Greg and others is going on the good track. So If we end pushing the
>> preview site to royale.apache.org, I'll be working ASAP to finish the rest
>> of the site in order to get it final.
>>
>> Let's see what happen.
>>
>> Thanks
>>
>> Carlos
>>
>>
>>
>> 2017-10-30 4:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>>
>>> I think there were objections to that as well. Also note that the
>>> current
>>> state of
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.co <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.co>
>>> deoscopic.com <http://deoscopic.com/>&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b
>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=0899xFFPDf8
>>> NmBRpAp%2FlHVCzspV5ed7fKnf6WwJPIlM%3D&reserved=0 may need some other
>>> adjustments to
>>> be approved by Apache's VP Branding as a valid home page for an Apache
>>> project. This page [1] mentions a "Donate" button and some other
>>> things.
>>>
>>> Carlos has done a great job and spent plenty of his precious time on
>>> this
>>> already, but the choice of commercial themes is turning out to be a
>>> problem. One option I think we have is to see what changes Carlos would
>>> have to make to his site for it to be ruled as a "fan site" and build a
>>> simpler and conforming site on royale.a.o with CSS that "looks similar"
>>> but with conforming content.
>>>
>>> My 2 cents,
>>> -Alex
>>>
>>> [1]
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apach <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apach>
>>> e.org <http://e.org/>%2Ffoundation%2Fmarks%2Fpmcs&data=02%7C01%7C%7Cbd5f09b6f99c4af619510
>>> 8d51f8370fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364495717568822
>>> 95&sdata=wkvJSvbx7mZ4ZlVaI5pp36eed0MEE6BdROZVTJu7nfs%3D&reserved=0
>>>
>>> On 10/29/17, 10:51 AM, "omuppi1@gmail.com <ma...@gmail.com> on behalf of OmPrakash
>>> Muppirala" <omuppi1@gmail.com <ma...@gmail.com> on behalf of bigosmallm@gmail.com <ma...@gmail.com>> wrote:
>>>
>>>> I agree. We might want to avoid that.
>>>>
>>>> Looks like the option of pointing to a wp.com <http://wp.com/> site has been done
>>> already.
>>>>
>>>> Can we push for this?
>>>>
>>>> Thanks,
>>>> Om
>>>>
>>>> On Oct 29, 2017 10:37 AM, "Carlos Rovira"
>>> <carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>>
>>>> wrote:
>>>>
>>>>> Hi Om,
>>>>>
>>>>> I think that's the better option, but my question is how to do this.
>>>>>
>>>>> How we can put the static generated site live under royale.apache.org <http://royale.apache.org/>
>>>>> without having that code on some repo? (the latest is very important)
>>>>> can we do this? do you know how to do it?
>>>>>
>>>>> note: remember that we don't want to upload the actual website code
>>> to
>>>>> some
>>>>> public repo due to commercial code licenses (movedo theme license)
>>>>>
>>>>> Thanks
>>>>>
>>>>> Carlos
>>>>>
>>>>>
>>>>>
>>>>> 2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala <bigosmallm@gmail.com <ma...@gmail.com>>:
>>>>>
>>>>>> I suggest we just release what Carlos as a static website for now.
>>>>>> As time goes by, volunteers can build up a separate website using
>>> just
>>>>>> Royale. At some point we can simply swap out the wp.com <http://wp.com/> site with
>>> the
>>>>> new
>>>>>> Royale based website.
>>>>>>
>>>>>> There is absolutely no requirement that the new site has to look
>>> like
>>>>> the
>>>>>> wp.com <http://wp.com/>. So, worrying about legal implications of maintaining the
>>> same
>>>>>> look
>>>>>> and feel is premature.
>>>>>>
>>>>>> Let's not make perfect the enemy of the good.
>>>>>>
>>>>>> Thanks,
>>>>>> Om
>>>>>>
>>>>>> On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira
>>>>> <carlosrovira@apache.org <ma...@apache.org>>
>>>>>> wrote:
>>>>>>
>>>>>>> Thanks Yishay for your words
>>>>>>>
>>>>>>> 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yishayjobs@hotmail.com <ma...@hotmail.com>>:
>>>>>>>
>>>>>>>> Carlos, I agree that our resources are limited and this this
>>> might
>>>>> not
>>>>>> be
>>>>>>>> the best way to spend them at this point. However, there are
>>> some
>>>>>> points
>>>>>>>> that have not been mentioned in this discussion that make me
>>>>> think we
>>>>>>>> should try to move our site to Royale.
>>>>>>>>
>>>>>>>> One is that we claim to be different to other frameworks in
>>> that
>>>>>> overhead
>>>>>>>> can be much smaller. A site that performs at the level of a
>>>>> classic
>>>>>>> static
>>>>>>>> site would be a significant proof of concept. If it doesn’t
>>>>> perform
>>>>>> well
>>>>>>>> enough we’ll have some information on where we can improve in
>>> that
>>>>>>> regard.
>>>>>>>>
>>>>>>>> Related, we need to finally start eating our dog food. The more
>>>>> visible
>>>>>>>> our dog food, the more feedback we’ll get.
>>>>>>>>
>>>>>>>> Also, if new people really want to contribute to out site, I’d
>>>>> much
>>>>>>> rather
>>>>>>>> have them learn Royale than WP.
>>>>>>>>
>>>>>>>
>>>>>>> That's ok. I only said that we are run out of resources and I
>>> don't
>>>>> see
>>>>>>> many people available to make this effort.
>>>>>>> In my case, my plan was to focus on design to bring something
>>> good
>>>>> to
>>>>>>> production, but didn't expect such problems with something we
>>> should
>>>>> put
>>>>>>> online, complete with real content and focus on other things.
>>>>>>> In my case, I would prefer to donate my tiny time in other things
>>>>> more
>>>>>>> needed. In concrete I prefer to donate in "theme" feature,
>>> styling
>>>>>> express,
>>>>>>> and so on...
>>>>>>> But if someone wants to work on replicate the site with Royale
>>> our
>>>>> other
>>>>>>> html plain code, that's right.
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> In other words, whether or not Royale ends up being a good tool
>>>>> for
>>>>>>>> classic web sites I see some reasons to try and achieve that
>>> for
>>>>> our
>>>>>> own
>>>>>>>> site.
>>>>>>>>
>>>>>>>> Finally, suppose I wanted to replicate your site in Royale just
>>>>> for
>>>>> the
>>>>>>>> heck of it. Would that be ok from a legal stand-point? I
>>> couldn’t
>>>>>>>> understand that from the thread so far.
>>>>>>>>
>>>>>>>
>>>>>>> If we recreate the site with our own set of CSS, JS, that's
>>> right.
>>>>> Nobody
>>>>>>> could say us nothing since no commercial code is involved there.
>>>>>>> As well, If we put the actual static generated site online,
>>> without
>>>>>> having
>>>>>>> to upload the code to any repo, that's alright as well, since is
>>> the
>>>>>> normal
>>>>>>> use, and the rest of people using that theme is doing the same.
>>>>>>>
>>>>>>> Thanks for your considerations.
>>>>>>>
>>>>>>> Carlos
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>> Thanks, and great work so far.
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>>
>>>>>
>>>>> <https://na01.safelinks.protection.outlook.com/?url= <https://na01.safelinks.protection.outlook.com/?url=>
>>> http%3A%2F%2Fwww.code
>>>>> oscopic.com <http://oscopic.com/>&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
>>> b4c5%7Cfa7b1b5a
>>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>>> sdata=9LfHDTE%2BCri
>>>>> 6177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0>
>>>>>
>>>>> Carlos Rovira
>>>>>
>>>>> Director General
>>>>>
>>>>> M: +34 607 22 60 05
>>>>>
>>>>>
>>>>> https://na01.safelinks.protection.outlook.com/?url= <https://na01.safelinks.protection.outlook.com/?url=>
>>> http%3A%2F%2Fwww.codeo
>>>>> scopic.com <http://scopic.com/>&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
>>> b4c5%7Cfa7b1b5a7
>>>>> b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>>> sdata=9LfHDTE%2BCri6
>>>>> 177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0
>>>>>
>>>>>
>>>>> Conocenos Avant2 en 1 minuto!
>>>
>>>>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant>
>>>>> 2
>>> .
>>>>> es%2F%23video&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
>>> b4c5%7Cfa7b1b
>>>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>>> sdata=AHQo5j38pqI
>>>>> 0UEabS7J1AW0jQEwOvWcvqFsVdpKTakM%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
>>>>> 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.
>>>>>
>>>
>>>
>>
>>
>> --
>>
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo>
>> scopic.com <http://scopic.com/>&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=x6RD%2Fu56EFXXK5
>> aWDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%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 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos>
>> copic.com <http://copic.com/>&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=x6RD%2Fu56EFXXK5a
>> WDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%3D&reserved=0
>>
>>
>> Conocenos Avant2 en 1 minuto!
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e>
>> s%2F%23video&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a
>> 7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=7F7ul9r6XR%2Bj
>> K%2FpAqHmvUtNPoNaMSaZlixNNaOLbbC0%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
>> 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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
FWIW, maybe the least effort choice right now is to ask ASF Trademarks and
Infra for a 60 day exception to redirect royale.a.o to
royale.codeoscopic.com. That'll keep us for burning more energy trying to
make this work some other way so we can get other stuff done, including
creating a similar site the traditional way based on the things we liked
from royale.codeoscopic.
Thoughts?
-Alex
On 10/30/17, 3:45 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Hi Alex,
>
>notice that the actual preview site is only that. We told about to get the
>site to some compromise point when we could evaluate it.
>As I get to that point, folks agree about the direction of the site. We
>are
>know seeing how to put this working for us. It seems that current talk
>with
>Greg and others is going on the good track. So If we end pushing the
>preview site to royale.apache.org, I'll be working ASAP to finish the rest
>of the site in order to get it final.
>
>Let's see what happen.
>
>Thanks
>
>Carlos
>
>
>
>2017-10-30 4:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
>
>> I think there were objections to that as well. Also note that the
>>current
>> state of
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.co
>>deoscopic.com&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b
>>5a7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=0899xFFPDf8
>>NmBRpAp%2FlHVCzspV5ed7fKnf6WwJPIlM%3D&reserved=0 may need some other
>>adjustments to
>> be approved by Apache's VP Branding as a valid home page for an Apache
>> project. This page [1] mentions a "Donate" button and some other
>>things.
>>
>> Carlos has done a great job and spent plenty of his precious time on
>>this
>> already, but the choice of commercial themes is turning out to be a
>> problem. One option I think we have is to see what changes Carlos would
>> have to make to his site for it to be ruled as a "fan site" and build a
>> simpler and conforming site on royale.a.o with CSS that "looks similar"
>> but with conforming content.
>>
>> My 2 cents,
>> -Alex
>>
>> [1]
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.apach
>>e.org%2Ffoundation%2Fmarks%2Fpmcs&data=02%7C01%7C%7Cbd5f09b6f99c4af619510
>>8d51f8370fa%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364495717568822
>>95&sdata=wkvJSvbx7mZ4ZlVaI5pp36eed0MEE6BdROZVTJu7nfs%3D&reserved=0
>>
>> On 10/29/17, 10:51 AM, "omuppi1@gmail.com on behalf of OmPrakash
>> Muppirala" <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>>
>> >I agree. We might want to avoid that.
>> >
>> >Looks like the option of pointing to a wp.com site has been done
>>already.
>> >
>> >Can we push for this?
>> >
>> >Thanks,
>> >Om
>> >
>> >On Oct 29, 2017 10:37 AM, "Carlos Rovira"
>><ca...@codeoscopic.com>
>> >wrote:
>> >
>> >> Hi Om,
>> >>
>> >> I think that's the better option, but my question is how to do this.
>> >>
>> >> How we can put the static generated site live under royale.apache.org
>> >> without having that code on some repo? (the latest is very important)
>> >> can we do this? do you know how to do it?
>> >>
>> >> note: remember that we don't want to upload the actual website code
>>to
>> >>some
>> >> public repo due to commercial code licenses (movedo theme license)
>> >>
>> >> Thanks
>> >>
>> >> Carlos
>> >>
>> >>
>> >>
>> >> 2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
>> >>
>> >> > I suggest we just release what Carlos as a static website for now.
>> >> > As time goes by, volunteers can build up a separate website using
>>just
>> >> > Royale. At some point we can simply swap out the wp.com site with
>> the
>> >> new
>> >> > Royale based website.
>> >> >
>> >> > There is absolutely no requirement that the new site has to look
>>like
>> >>the
>> >> > wp.com. So, worrying about legal implications of maintaining the
>> same
>> >> > look
>> >> > and feel is premature.
>> >> >
>> >> > Let's not make perfect the enemy of the good.
>> >> >
>> >> > Thanks,
>> >> > Om
>> >> >
>> >> > On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira
>> >><ca...@apache.org>
>> >> > wrote:
>> >> >
>> >> > > Thanks Yishay for your words
>> >> > >
>> >> > > 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yi...@hotmail.com>:
>> >> > >
>> >> > > > Carlos, I agree that our resources are limited and this this
>>might
>> >> not
>> >> > be
>> >> > > > the best way to spend them at this point. However, there are
>>some
>> >> > points
>> >> > > > that have not been mentioned in this discussion that make me
>> >>think we
>> >> > > > should try to move our site to Royale.
>> >> > > >
>> >> > > > One is that we claim to be different to other frameworks in
>>that
>> >> > overhead
>> >> > > > can be much smaller. A site that performs at the level of a
>> >>classic
>> >> > > static
>> >> > > > site would be a significant proof of concept. If it doesn’t
>> >>perform
>> >> > well
>> >> > > > enough we’ll have some information on where we can improve in
>>that
>> >> > > regard.
>> >> > > >
>> >> > > > Related, we need to finally start eating our dog food. The more
>> >> visible
>> >> > > > our dog food, the more feedback we’ll get.
>> >> > > >
>> >> > > > Also, if new people really want to contribute to out site, I’d
>> >>much
>> >> > > rather
>> >> > > > have them learn Royale than WP.
>> >> > > >
>> >> > >
>> >> > > That's ok. I only said that we are run out of resources and I
>>don't
>> >> see
>> >> > > many people available to make this effort.
>> >> > > In my case, my plan was to focus on design to bring something
>>good
>> >>to
>> >> > > production, but didn't expect such problems with something we
>>should
>> >> put
>> >> > > online, complete with real content and focus on other things.
>> >> > > In my case, I would prefer to donate my tiny time in other things
>> >>more
>> >> > > needed. In concrete I prefer to donate in "theme" feature,
>>styling
>> >> > express,
>> >> > > and so on...
>> >> > > But if someone wants to work on replicate the site with Royale
>>our
>> >> other
>> >> > > html plain code, that's right.
>> >> > >
>> >> > >
>> >> > > >
>> >> > > > In other words, whether or not Royale ends up being a good tool
>> >>for
>> >> > > > classic web sites I see some reasons to try and achieve that
>>for
>> >>our
>> >> > own
>> >> > > > site.
>> >> > > >
>> >> > > > Finally, suppose I wanted to replicate your site in Royale just
>> >>for
>> >> the
>> >> > > > heck of it. Would that be ok from a legal stand-point? I
>>couldn’t
>> >> > > > understand that from the thread so far.
>> >> > > >
>> >> > >
>> >> > > If we recreate the site with our own set of CSS, JS, that's
>>right.
>> >> Nobody
>> >> > > could say us nothing since no commercial code is involved there.
>> >> > > As well, If we put the actual static generated site online,
>>without
>> >> > having
>> >> > > to upload the code to any repo, that's alright as well, since is
>>the
>> >> > normal
>> >> > > use, and the rest of people using that theme is doing the same.
>> >> > >
>> >> > > Thanks for your considerations.
>> >> > >
>> >> > > Carlos
>> >> > >
>> >> > >
>> >> > >
>> >> > > >
>> >> > > > Thanks, and great work so far.
>> >> > > >
>> >> > > >
>> >> > > >
>> >> > >
>> >> >
>> >>
>> >>
>> >>
>> >> --
>> >>
>> >>
>> >><https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.code
>> >>oscopic.com&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
>> b4c5%7Cfa7b1b5a
>> >>7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>> sdata=9LfHDTE%2BCri
>> >>6177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0>
>> >>
>> >> Carlos Rovira
>> >>
>> >> Director General
>> >>
>> >> M: +34 607 22 60 05
>> >>
>> >>
>> >>https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.codeo
>> >>scopic.com&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
>> b4c5%7Cfa7b1b5a7
>> >>b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>> sdata=9LfHDTE%2BCri6
>> >>177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0
>> >>
>> >>
>> >> Conocenos Avant2 en 1 minuto!
>>
>>>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant
>>>>2
>> .
>> >>es%2F%23video&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
>> b4c5%7Cfa7b1b
>> >>5a7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
>> sdata=AHQo5j38pqI
>> >>0UEabS7J1AW0jQEwOvWcvqFsVdpKTakM%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
>> >> 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.
>> >>
>>
>>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=x6RD%2Fu56EFXXK5
>aWDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%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%7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=x6RD%2Fu56EFXXK5a
>WDZFGSpBV%2B%2FMduJT8tFYH%2Fi37IwI%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7Cbd5f09b6f99c4af6195108d51f8370fa%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636449571756882295&sdata=7F7ul9r6XR%2Bj
>K%2FpAqHmvUtNPoNaMSaZlixNNaOLbbC0%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
>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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Alex,
notice that the actual preview site is only that. We told about to get the
site to some compromise point when we could evaluate it.
As I get to that point, folks agree about the direction of the site. We are
know seeing how to put this working for us. It seems that current talk with
Greg and others is going on the good track. So If we end pushing the
preview site to royale.apache.org, I'll be working ASAP to finish the rest
of the site in order to get it final.
Let's see what happen.
Thanks
Carlos
2017-10-30 4:13 GMT+01:00 Alex Harui <ah...@adobe.com.invalid>:
> I think there were objections to that as well. Also note that the current
> state of http://royale.codeoscopic.com may need some other adjustments to
> be approved by Apache's VP Branding as a valid home page for an Apache
> project. This page [1] mentions a "Donate" button and some other things.
>
> Carlos has done a great job and spent plenty of his precious time on this
> already, but the choice of commercial themes is turning out to be a
> problem. One option I think we have is to see what changes Carlos would
> have to make to his site for it to be ruled as a "fan site" and build a
> simpler and conforming site on royale.a.o with CSS that "looks similar"
> but with conforming content.
>
> My 2 cents,
> -Alex
>
> [1] http://www.apache.org/foundation/marks/pmcs
>
> On 10/29/17, 10:51 AM, "omuppi1@gmail.com on behalf of OmPrakash
> Muppirala" <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>
> >I agree. We might want to avoid that.
> >
> >Looks like the option of pointing to a wp.com site has been done already.
> >
> >Can we push for this?
> >
> >Thanks,
> >Om
> >
> >On Oct 29, 2017 10:37 AM, "Carlos Rovira" <ca...@codeoscopic.com>
> >wrote:
> >
> >> Hi Om,
> >>
> >> I think that's the better option, but my question is how to do this.
> >>
> >> How we can put the static generated site live under royale.apache.org
> >> without having that code on some repo? (the latest is very important)
> >> can we do this? do you know how to do it?
> >>
> >> note: remember that we don't want to upload the actual website code to
> >>some
> >> public repo due to commercial code licenses (movedo theme license)
> >>
> >> Thanks
> >>
> >> Carlos
> >>
> >>
> >>
> >> 2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
> >>
> >> > I suggest we just release what Carlos as a static website for now.
> >> > As time goes by, volunteers can build up a separate website using just
> >> > Royale. At some point we can simply swap out the wp.com site with
> the
> >> new
> >> > Royale based website.
> >> >
> >> > There is absolutely no requirement that the new site has to look like
> >>the
> >> > wp.com. So, worrying about legal implications of maintaining the
> same
> >> > look
> >> > and feel is premature.
> >> >
> >> > Let's not make perfect the enemy of the good.
> >> >
> >> > Thanks,
> >> > Om
> >> >
> >> > On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira
> >><ca...@apache.org>
> >> > wrote:
> >> >
> >> > > Thanks Yishay for your words
> >> > >
> >> > > 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yi...@hotmail.com>:
> >> > >
> >> > > > Carlos, I agree that our resources are limited and this this might
> >> not
> >> > be
> >> > > > the best way to spend them at this point. However, there are some
> >> > points
> >> > > > that have not been mentioned in this discussion that make me
> >>think we
> >> > > > should try to move our site to Royale.
> >> > > >
> >> > > > One is that we claim to be different to other frameworks in that
> >> > overhead
> >> > > > can be much smaller. A site that performs at the level of a
> >>classic
> >> > > static
> >> > > > site would be a significant proof of concept. If it doesn’t
> >>perform
> >> > well
> >> > > > enough we’ll have some information on where we can improve in that
> >> > > regard.
> >> > > >
> >> > > > Related, we need to finally start eating our dog food. The more
> >> visible
> >> > > > our dog food, the more feedback we’ll get.
> >> > > >
> >> > > > Also, if new people really want to contribute to out site, I’d
> >>much
> >> > > rather
> >> > > > have them learn Royale than WP.
> >> > > >
> >> > >
> >> > > That's ok. I only said that we are run out of resources and I don't
> >> see
> >> > > many people available to make this effort.
> >> > > In my case, my plan was to focus on design to bring something good
> >>to
> >> > > production, but didn't expect such problems with something we should
> >> put
> >> > > online, complete with real content and focus on other things.
> >> > > In my case, I would prefer to donate my tiny time in other things
> >>more
> >> > > needed. In concrete I prefer to donate in "theme" feature, styling
> >> > express,
> >> > > and so on...
> >> > > But if someone wants to work on replicate the site with Royale our
> >> other
> >> > > html plain code, that's right.
> >> > >
> >> > >
> >> > > >
> >> > > > In other words, whether or not Royale ends up being a good tool
> >>for
> >> > > > classic web sites I see some reasons to try and achieve that for
> >>our
> >> > own
> >> > > > site.
> >> > > >
> >> > > > Finally, suppose I wanted to replicate your site in Royale just
> >>for
> >> the
> >> > > > heck of it. Would that be ok from a legal stand-point? I couldn’t
> >> > > > understand that from the thread so far.
> >> > > >
> >> > >
> >> > > If we recreate the site with our own set of CSS, JS, that's right.
> >> Nobody
> >> > > could say us nothing since no commercial code is involved there.
> >> > > As well, If we put the actual static generated site online, without
> >> > having
> >> > > to upload the code to any repo, that's alright as well, since is the
> >> > normal
> >> > > use, and the rest of people using that theme is doing the same.
> >> > >
> >> > > Thanks for your considerations.
> >> > >
> >> > > Carlos
> >> > >
> >> > >
> >> > >
> >> > > >
> >> > > > Thanks, and great work so far.
> >> > > >
> >> > > >
> >> > > >
> >> > >
> >> >
> >>
> >>
> >>
> >> --
> >>
> >>
> >><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.code
> >>oscopic.com&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
> b4c5%7Cfa7b1b5a
> >>7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> sdata=9LfHDTE%2BCri
> >>6177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0>
> >>
> >> Carlos Rovira
> >>
> >> Director General
> >>
> >> M: +34 607 22 60 05
> >>
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo
> >>scopic.com&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
> b4c5%7Cfa7b1b5a7
> >>b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> sdata=9LfHDTE%2BCri6
> >>177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0
> >>
> >>
> >> Conocenos Avant2 en 1 minuto!
> >><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2
> .
> >>es%2F%23video&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5
> b4c5%7Cfa7b1b
> >>5a7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&
> sdata=AHQo5j38pqI
> >>0UEabS7J1AW0jQEwOvWcvqFsVdpKTakM%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
> >> 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.
> >>
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I think there were objections to that as well. Also note that the current
state of http://royale.codeoscopic.com may need some other adjustments to
be approved by Apache's VP Branding as a valid home page for an Apache
project. This page [1] mentions a "Donate" button and some other things.
Carlos has done a great job and spent plenty of his precious time on this
already, but the choice of commercial themes is turning out to be a
problem. One option I think we have is to see what changes Carlos would
have to make to his site for it to be ruled as a "fan site" and build a
simpler and conforming site on royale.a.o with CSS that "looks similar"
but with conforming content.
My 2 cents,
-Alex
[1] http://www.apache.org/foundation/marks/pmcs
On 10/29/17, 10:51 AM, "omuppi1@gmail.com on behalf of OmPrakash
Muppirala" <omuppi1@gmail.com on behalf of bigosmallm@gmail.com> wrote:
>I agree. We might want to avoid that.
>
>Looks like the option of pointing to a wp.com site has been done already.
>
>Can we push for this?
>
>Thanks,
>Om
>
>On Oct 29, 2017 10:37 AM, "Carlos Rovira" <ca...@codeoscopic.com>
>wrote:
>
>> Hi Om,
>>
>> I think that's the better option, but my question is how to do this.
>>
>> How we can put the static generated site live under royale.apache.org
>> without having that code on some repo? (the latest is very important)
>> can we do this? do you know how to do it?
>>
>> note: remember that we don't want to upload the actual website code to
>>some
>> public repo due to commercial code licenses (movedo theme license)
>>
>> Thanks
>>
>> Carlos
>>
>>
>>
>> 2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
>>
>> > I suggest we just release what Carlos as a static website for now.
>> > As time goes by, volunteers can build up a separate website using just
>> > Royale. At some point we can simply swap out the wp.com site with the
>> new
>> > Royale based website.
>> >
>> > There is absolutely no requirement that the new site has to look like
>>the
>> > wp.com. So, worrying about legal implications of maintaining the same
>> > look
>> > and feel is premature.
>> >
>> > Let's not make perfect the enemy of the good.
>> >
>> > Thanks,
>> > Om
>> >
>> > On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira
>><ca...@apache.org>
>> > wrote:
>> >
>> > > Thanks Yishay for your words
>> > >
>> > > 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yi...@hotmail.com>:
>> > >
>> > > > Carlos, I agree that our resources are limited and this this might
>> not
>> > be
>> > > > the best way to spend them at this point. However, there are some
>> > points
>> > > > that have not been mentioned in this discussion that make me
>>think we
>> > > > should try to move our site to Royale.
>> > > >
>> > > > One is that we claim to be different to other frameworks in that
>> > overhead
>> > > > can be much smaller. A site that performs at the level of a
>>classic
>> > > static
>> > > > site would be a significant proof of concept. If it doesn’t
>>perform
>> > well
>> > > > enough we’ll have some information on where we can improve in that
>> > > regard.
>> > > >
>> > > > Related, we need to finally start eating our dog food. The more
>> visible
>> > > > our dog food, the more feedback we’ll get.
>> > > >
>> > > > Also, if new people really want to contribute to out site, I’d
>>much
>> > > rather
>> > > > have them learn Royale than WP.
>> > > >
>> > >
>> > > That's ok. I only said that we are run out of resources and I don't
>> see
>> > > many people available to make this effort.
>> > > In my case, my plan was to focus on design to bring something good
>>to
>> > > production, but didn't expect such problems with something we should
>> put
>> > > online, complete with real content and focus on other things.
>> > > In my case, I would prefer to donate my tiny time in other things
>>more
>> > > needed. In concrete I prefer to donate in "theme" feature, styling
>> > express,
>> > > and so on...
>> > > But if someone wants to work on replicate the site with Royale our
>> other
>> > > html plain code, that's right.
>> > >
>> > >
>> > > >
>> > > > In other words, whether or not Royale ends up being a good tool
>>for
>> > > > classic web sites I see some reasons to try and achieve that for
>>our
>> > own
>> > > > site.
>> > > >
>> > > > Finally, suppose I wanted to replicate your site in Royale just
>>for
>> the
>> > > > heck of it. Would that be ok from a legal stand-point? I couldn’t
>> > > > understand that from the thread so far.
>> > > >
>> > >
>> > > If we recreate the site with our own set of CSS, JS, that's right.
>> Nobody
>> > > could say us nothing since no commercial code is involved there.
>> > > As well, If we put the actual static generated site online, without
>> > having
>> > > to upload the code to any repo, that's alright as well, since is the
>> > normal
>> > > use, and the rest of people using that theme is doing the same.
>> > >
>> > > Thanks for your considerations.
>> > >
>> > > Carlos
>> > >
>> > >
>> > >
>> > > >
>> > > > Thanks, and great work so far.
>> > > >
>> > > >
>> > > >
>> > >
>> >
>>
>>
>>
>> --
>>
>>
>><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.code
>>oscopic.com&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5b4c5%7Cfa7b1b5a
>>7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&sdata=9LfHDTE%2BCri
>>6177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0>
>>
>> Carlos Rovira
>>
>> Director General
>>
>> M: +34 607 22 60 05
>>
>>
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>>scopic.com&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5b4c5%7Cfa7b1b5a7
>>b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&sdata=9LfHDTE%2BCri6
>>177x5CCX1J0QTkIry1aQDsYS%2FBxHNz4%3D&reserved=0
>>
>>
>> Conocenos Avant2 en 1 minuto!
>><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.
>>es%2F%23video&data=02%7C01%7C%7C76c801888c3d4049ca8c08d51ef5b4c5%7Cfa7b1b
>>5a7b34438794aed2c178decee1%7C0%7C0%7C636448963003434412&sdata=AHQo5j38pqI
>>0UEabS7J1AW0jQEwOvWcvqFsVdpKTakM%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
>> 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: Apache Royale static web site
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I agree. We might want to avoid that.
Looks like the option of pointing to a wp.com site has been done already.
Can we push for this?
Thanks,
Om
On Oct 29, 2017 10:37 AM, "Carlos Rovira" <ca...@codeoscopic.com>
wrote:
> Hi Om,
>
> I think that's the better option, but my question is how to do this.
>
> How we can put the static generated site live under royale.apache.org
> without having that code on some repo? (the latest is very important)
> can we do this? do you know how to do it?
>
> note: remember that we don't want to upload the actual website code to some
> public repo due to commercial code licenses (movedo theme license)
>
> Thanks
>
> Carlos
>
>
>
> 2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
>
> > I suggest we just release what Carlos as a static website for now.
> > As time goes by, volunteers can build up a separate website using just
> > Royale. At some point we can simply swap out the wp.com site with the
> new
> > Royale based website.
> >
> > There is absolutely no requirement that the new site has to look like the
> > wp.com. So, worrying about legal implications of maintaining the same
> > look
> > and feel is premature.
> >
> > Let's not make perfect the enemy of the good.
> >
> > Thanks,
> > Om
> >
> > On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira <ca...@apache.org>
> > wrote:
> >
> > > Thanks Yishay for your words
> > >
> > > 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yi...@hotmail.com>:
> > >
> > > > Carlos, I agree that our resources are limited and this this might
> not
> > be
> > > > the best way to spend them at this point. However, there are some
> > points
> > > > that have not been mentioned in this discussion that make me think we
> > > > should try to move our site to Royale.
> > > >
> > > > One is that we claim to be different to other frameworks in that
> > overhead
> > > > can be much smaller. A site that performs at the level of a classic
> > > static
> > > > site would be a significant proof of concept. If it doesn’t perform
> > well
> > > > enough we’ll have some information on where we can improve in that
> > > regard.
> > > >
> > > > Related, we need to finally start eating our dog food. The more
> visible
> > > > our dog food, the more feedback we’ll get.
> > > >
> > > > Also, if new people really want to contribute to out site, I’d much
> > > rather
> > > > have them learn Royale than WP.
> > > >
> > >
> > > That's ok. I only said that we are run out of resources and I don't
> see
> > > many people available to make this effort.
> > > In my case, my plan was to focus on design to bring something good to
> > > production, but didn't expect such problems with something we should
> put
> > > online, complete with real content and focus on other things.
> > > In my case, I would prefer to donate my tiny time in other things more
> > > needed. In concrete I prefer to donate in "theme" feature, styling
> > express,
> > > and so on...
> > > But if someone wants to work on replicate the site with Royale our
> other
> > > html plain code, that's right.
> > >
> > >
> > > >
> > > > In other words, whether or not Royale ends up being a good tool for
> > > > classic web sites I see some reasons to try and achieve that for our
> > own
> > > > site.
> > > >
> > > > Finally, suppose I wanted to replicate your site in Royale just for
> the
> > > > heck of it. Would that be ok from a legal stand-point? I couldn’t
> > > > understand that from the thread so far.
> > > >
> > >
> > > If we recreate the site with our own set of CSS, JS, that's right.
> Nobody
> > > could say us nothing since no commercial code is involved there.
> > > As well, If we put the actual static generated site online, without
> > having
> > > to upload the code to any repo, that's alright as well, since is the
> > normal
> > > use, and the rest of people using that theme is doing the same.
> > >
> > > Thanks for your considerations.
> > >
> > > Carlos
> > >
> > >
> > >
> > > >
> > > > Thanks, and great work so far.
> > > >
> > > >
> > > >
> > >
> >
>
>
>
> --
>
> <http://www.codeoscopic.com>
>
> Carlos Rovira
>
> Director General
>
> M: +34 607 22 60 05
>
> http://www.codeoscopic.com
>
>
> Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
>
>
> 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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Om,
I think that's the better option, but my question is how to do this.
How we can put the static generated site live under royale.apache.org
without having that code on some repo? (the latest is very important)
can we do this? do you know how to do it?
note: remember that we don't want to upload the actual website code to some
public repo due to commercial code licenses (movedo theme license)
Thanks
Carlos
2017-10-29 2:10 GMT+01:00 OmPrakash Muppirala <bi...@gmail.com>:
> I suggest we just release what Carlos as a static website for now.
> As time goes by, volunteers can build up a separate website using just
> Royale. At some point we can simply swap out the wp.com site with the new
> Royale based website.
>
> There is absolutely no requirement that the new site has to look like the
> wp.com. So, worrying about legal implications of maintaining the same
> look
> and feel is premature.
>
> Let's not make perfect the enemy of the good.
>
> Thanks,
> Om
>
> On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira <ca...@apache.org>
> wrote:
>
> > Thanks Yishay for your words
> >
> > 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yi...@hotmail.com>:
> >
> > > Carlos, I agree that our resources are limited and this this might not
> be
> > > the best way to spend them at this point. However, there are some
> points
> > > that have not been mentioned in this discussion that make me think we
> > > should try to move our site to Royale.
> > >
> > > One is that we claim to be different to other frameworks in that
> overhead
> > > can be much smaller. A site that performs at the level of a classic
> > static
> > > site would be a significant proof of concept. If it doesn’t perform
> well
> > > enough we’ll have some information on where we can improve in that
> > regard.
> > >
> > > Related, we need to finally start eating our dog food. The more visible
> > > our dog food, the more feedback we’ll get.
> > >
> > > Also, if new people really want to contribute to out site, I’d much
> > rather
> > > have them learn Royale than WP.
> > >
> >
> > That's ok. I only said that we are run out of resources and I don't see
> > many people available to make this effort.
> > In my case, my plan was to focus on design to bring something good to
> > production, but didn't expect such problems with something we should put
> > online, complete with real content and focus on other things.
> > In my case, I would prefer to donate my tiny time in other things more
> > needed. In concrete I prefer to donate in "theme" feature, styling
> express,
> > and so on...
> > But if someone wants to work on replicate the site with Royale our other
> > html plain code, that's right.
> >
> >
> > >
> > > In other words, whether or not Royale ends up being a good tool for
> > > classic web sites I see some reasons to try and achieve that for our
> own
> > > site.
> > >
> > > Finally, suppose I wanted to replicate your site in Royale just for the
> > > heck of it. Would that be ok from a legal stand-point? I couldn’t
> > > understand that from the thread so far.
> > >
> >
> > If we recreate the site with our own set of CSS, JS, that's right. Nobody
> > could say us nothing since no commercial code is involved there.
> > As well, If we put the actual static generated site online, without
> having
> > to upload the code to any repo, that's alright as well, since is the
> normal
> > use, and the rest of people using that theme is doing the same.
> >
> > Thanks for your considerations.
> >
> > Carlos
> >
> >
> >
> > >
> > > Thanks, and great work so far.
> > >
> > >
> > >
> >
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by OmPrakash Muppirala <bi...@gmail.com>.
I suggest we just release what Carlos as a static website for now.
As time goes by, volunteers can build up a separate website using just
Royale. At some point we can simply swap out the wp.com site with the new
Royale based website.
There is absolutely no requirement that the new site has to look like the
wp.com. So, worrying about legal implications of maintaining the same look
and feel is premature.
Let's not make perfect the enemy of the good.
Thanks,
Om
On Sat, Oct 28, 2017 at 1:12 PM, Carlos Rovira <ca...@apache.org>
wrote:
> Thanks Yishay for your words
>
> 2017-10-28 19:09 GMT+02:00 Yishay Weiss <yi...@hotmail.com>:
>
> > Carlos, I agree that our resources are limited and this this might not be
> > the best way to spend them at this point. However, there are some points
> > that have not been mentioned in this discussion that make me think we
> > should try to move our site to Royale.
> >
> > One is that we claim to be different to other frameworks in that overhead
> > can be much smaller. A site that performs at the level of a classic
> static
> > site would be a significant proof of concept. If it doesn’t perform well
> > enough we’ll have some information on where we can improve in that
> regard.
> >
> > Related, we need to finally start eating our dog food. The more visible
> > our dog food, the more feedback we’ll get.
> >
> > Also, if new people really want to contribute to out site, I’d much
> rather
> > have them learn Royale than WP.
> >
>
> That's ok. I only said that we are run out of resources and I don't see
> many people available to make this effort.
> In my case, my plan was to focus on design to bring something good to
> production, but didn't expect such problems with something we should put
> online, complete with real content and focus on other things.
> In my case, I would prefer to donate my tiny time in other things more
> needed. In concrete I prefer to donate in "theme" feature, styling express,
> and so on...
> But if someone wants to work on replicate the site with Royale our other
> html plain code, that's right.
>
>
> >
> > In other words, whether or not Royale ends up being a good tool for
> > classic web sites I see some reasons to try and achieve that for our own
> > site.
> >
> > Finally, suppose I wanted to replicate your site in Royale just for the
> > heck of it. Would that be ok from a legal stand-point? I couldn’t
> > understand that from the thread so far.
> >
>
> If we recreate the site with our own set of CSS, JS, that's right. Nobody
> could say us nothing since no commercial code is involved there.
> As well, If we put the actual static generated site online, without having
> to upload the code to any repo, that's alright as well, since is the normal
> use, and the rest of people using that theme is doing the same.
>
> Thanks for your considerations.
>
> Carlos
>
>
>
> >
> > Thanks, and great work so far.
> >
> >
> >
>
Re: Apache Royale static web site
Posted by Carlos Rovira <ca...@apache.org>.
Thanks Yishay for your words
2017-10-28 19:09 GMT+02:00 Yishay Weiss <yi...@hotmail.com>:
> Carlos, I agree that our resources are limited and this this might not be
> the best way to spend them at this point. However, there are some points
> that have not been mentioned in this discussion that make me think we
> should try to move our site to Royale.
>
> One is that we claim to be different to other frameworks in that overhead
> can be much smaller. A site that performs at the level of a classic static
> site would be a significant proof of concept. If it doesn’t perform well
> enough we’ll have some information on where we can improve in that regard.
>
> Related, we need to finally start eating our dog food. The more visible
> our dog food, the more feedback we’ll get.
>
> Also, if new people really want to contribute to out site, I’d much rather
> have them learn Royale than WP.
>
That's ok. I only said that we are run out of resources and I don't see
many people available to make this effort.
In my case, my plan was to focus on design to bring something good to
production, but didn't expect such problems with something we should put
online, complete with real content and focus on other things.
In my case, I would prefer to donate my tiny time in other things more
needed. In concrete I prefer to donate in "theme" feature, styling express,
and so on...
But if someone wants to work on replicate the site with Royale our other
html plain code, that's right.
>
> In other words, whether or not Royale ends up being a good tool for
> classic web sites I see some reasons to try and achieve that for our own
> site.
>
> Finally, suppose I wanted to replicate your site in Royale just for the
> heck of it. Would that be ok from a legal stand-point? I couldn’t
> understand that from the thread so far.
>
If we recreate the site with our own set of CSS, JS, that's right. Nobody
could say us nothing since no commercial code is involved there.
As well, If we put the actual static generated site online, without having
to upload the code to any repo, that's alright as well, since is the normal
use, and the rest of people using that theme is doing the same.
Thanks for your considerations.
Carlos
>
> Thanks, and great work so far.
>
>
>
RE: Apache Royale static web site
Posted by Yishay Weiss <yi...@hotmail.com>.
Carlos, I agree that our resources are limited and this this might not be the best way to spend them at this point. However, there are some points that have not been mentioned in this discussion that make me think we should try to move our site to Royale.
One is that we claim to be different to other frameworks in that overhead can be much smaller. A site that performs at the level of a classic static site would be a significant proof of concept. If it doesn’t perform well enough we’ll have some information on where we can improve in that regard.
Related, we need to finally start eating our dog food. The more visible our dog food, the more feedback we’ll get.
Also, if new people really want to contribute to out site, I’d much rather have them learn Royale than WP.
In other words, whether or not Royale ends up being a good tool for classic web sites I see some reasons to try and achieve that for our own site.
Finally, suppose I wanted to replicate your site in Royale just for the heck of it. Would that be ok from a legal stand-point? I couldn’t understand that from the thread so far.
Thanks, and great work so far.
From: Carlos Rovira<ma...@codeoscopic.com>
Sent: Friday, October 27, 2017 12:18 AM
To: dev@royale.apache.org<ma...@royale.apache.org>
Subject: Re: Apache Royale static web site
Hi Alex,
2017-10-26 22:06 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
> Hi Carlos,
>
> I have a WP-based blog, so I understand how easy it is to write some text
> and have it look nice. But I'm still confused about who owns what. Does
> Envato/Greatives own the look and feel of royale.codeoscopic.com or do
> you?
codeoscopic owns a license of movedo theme.
anyone that buys the license (59$) will own it, so I think it's not a huge
quantity of money
> I understand that Royale is tuned more towards web applications but
> to my mind, I see more and more web sites being about interactivity rather
> than just displaying text and images. Even blog commenting and upvoting
> looks like an app to me.
>
The two worlds interesect, that's evidently, but are different beast. I
tried to make in the past
some website with Flex, and although I did it and we get some cool effects,
in the end it wasn't the
right tool for the job. I did as well an Application in wordpress with some
plugins due to time restrictions
and while I did it, again it was not the right tool for the job and many
things was very limited.
>
> I would like to some day use Royale to create the page you've prototyped
> at royale.codeoscopic.com and maybe enhance it by having a Royale news
> feed or some other backend connectivity for some of the content. But can
> we replicate the look and feel of what you have prototyped and put that
> under ALv2? I think we have to find a way to make that possible. The
> theme or CSS that we use to replicate your prototype may not be our
> default theme/CSS, but it should still be a valid theme or CSS file and
> components.
>
without doubt, but for me this is not the right time to do it. As Harbs
already agree, we need
to put a website online ASAP.
We can always come back and with time, can make that work. But IMHO, we
need to choose
an strategy and see what things are needed first and organize efforts. For
me UI theme is more need than replicate something that we already have.
>
> That's why I'm concerned that working from Movedo is going to leak into
> other things we want to do. But if we start from scratch and try to
> replicate the visuals you've chosen, I would hope we can get something
> that looks similar quickly and then invite more folks to help tune it.
> And as Harbs says, I'm not asking you to do that work, someone else can.
> What you've done already is significant and very helpful and I think you
> made the right choice of using your WP skills to create it quickly.
Right, but for me that work could fit into Royale examples, but would not
be of much use in the framework
> If we were to reproduce your prototype in Royale, I would want to create
> re-usable components such as:
> MenuBar
> SearchShareUserProfileMoreMenuBar
> TopBar (that holds all of the icon, title, MenuBar and
> SearchShareProfileButtonBar)
> IconTitleTextPanel
> And more...
>
>
I think you are right if we want to recreate the website and make Royale
components...again for me this is and example.
But, if I start to create a styling that could fit more use cases and be
the default Express Component Set face? Don't you think that work would be
more valuable? I think so, and is what I want to contribute next.
That would be more "application" style and less "web" style. based on that
work we can make more theme projects like Apache Flex already has and have
an Application property "theme" to switch between themes. I think that is
what I think people migrating from Apache Flex SDK expects.
> Then someone else can come along and assemble their own site from these
> pieces.
>
completely right, but expect many few people doing that since, or at least
very residual, since there are other tools far better to do the job. If we
want to go that route I think we will need to focus in many task that will
ease that kind of target and make Apache Royale good in that area. For
example, routing. For Royale to make good websites, routing is essential,
and no body will use it without be able to configure deep linking in a
reliable and useful way.
>
> Back in the Adobe days, some folks actually took the FlexStore example,
> modified it slightly and deployed it in production for their own products.
> We didn't care that they pretty much used the same look-and-feel. I think
> we want to make the same sort of thing possible for Royale.
>
Alex, I think this is possible. In fact, all you expose is completely
right, but I want you to think in how many hands have we now. Many of this
things can be done if we get more people on board, but for this to happen
we need to unblock what we have, and go to other things we need. If I need
two things (website and themes), I prefer to have 1-1 than 2-0. And in some
months from now, we always can come back and make the website in our
technology, and maybe even change it for something fresh again.
That's my 2ctns.
Carlos
>
> Thoughts?
> -Alex
>
> On 10/26/17, 11:27 AM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira" <carlos.rovira@gmail.com on behalf of
> carlos.rovira@codeoscopic.com> wrote:
>
> >Hi,
> >
> >in order to help you, Alex and Harbs (others could join as well) to
> >understand all the picture, I could create an account for you in
> >royale.codeoscopic.com
> >
> >In this way you could see point 1 of Alex's list (how integrate some new
> >content in website). and most important, you will see the visual tool to
> >edit and mount a new content in pages or posts.
> >
> >This last thing is one of the main reasons I want to use WP in the day by
> >day. If you want to create some content, doing manually is a nightmare.
> >
> >I'll send you admin users to your accounts and you're free to enter and
> >watch, (but please don't modify anything to avoid break the actual site)
> >
> >In order to create some default theme (point 2), again here I think we
> >talking about different things. I think we don't want to base our default
> >theme for UI controls in apache royale in what I did in the theme. That
> >would be a mistake in since movedo principles are based on website look
> >and
> >usability. Fonts and spacing is huge to express content in a modern
> >website. To make a comparative, if you take MDL and movedo side by side,
> >the first is for applications while the second is to present text and
> >images in a website.
> >
> >My plan, as I mention before, is to start creating a UI component styles
> >that could be programed in a theme. I have in mind to make two of them: a
> >wireframe theme and a full default theme. The first one could have the
> >same
> >sizes and fonts but with only outlines and black and white (like the flex
> >wireframe to avoid style and application when you're prototyping.
> >
> >Regarding time to replicate movedo theme with our own styling, I'm sure is
> >not a two day task, but more, there's so much there, and only to get
> >something that only will be a shadow of the original.
> >
> >As Harbs mention there's people making styling, but as they are not
> >commenting in this list we don't know anything about if they are doing
> >something this days, or maybe they couldn't use that time to work on this.
> >
> >For last (point 3), I did wordpress themes some years ago, and is a huge
> >task to do, in time and effort. And with time you can get something of
> >quality, but again, why we want to spend our time in something we already
> >have? I don't find anything here, since we are not here to create WP
> >themes, I prefer to use that time to create an Apache Royale UI theme and
> >even help to program it, because that is what we really need to make more
> >people join us.
> >
> >
> >
> >
> >2017-10-26 19:37 GMT+02:00 Harbs <ha...@gmail.com>:
> >
> >> Another point to consider:
> >>
> >> We’ve had some folks offer to help with skinning Royale components. It
> >> should be pretty straightforward to give them (and anyone else who
> >>wants to
> >> help) committer rights to the website repo. If we have more people
> >>working
> >> on it, the task of recreating the appearance achieved through the Movedo
> >> CSS should be al lot easier.
> >>
> >> I don’t feel comfortable asking Carlos to do more work than he’s
> >>offered,
> >> but with help from others, it might be a lot easier.
> >>
> >> Harbs
> >>
> >> > On Oct 26, 2017, at 7:41 PM, Alex Harui <ah...@adobe.com.INVALID>
> >> wrote:
> >> >
> >> > Hi Carlos,
> >> >
> >> > I don't know if the "Apache Way" is a problem here. So far I think we
> >> > have heard opinions and concerns but AFAICT no hard policy has been
> >> quoted
> >> > that prevents having royale.a.o point to WP.com.
> >> >
> >> > But I am still unclear if hosting our site on WP is really the best
> >> > strategy. I have the following concerns:
> >> >
> >> > 1) How would be include a Royale application in our site?
> >> > 2) How would we style the Royale application to look consistent with
> >>the
> >> > rest of the site?
> >> > 3) Could we ever create a theme based on this styling?
> >> >
> >> > I didn't, and still don't, understand how WP themes and their
> >>licensing
> >> > work, otherwise I think I would have asked more questions up front. I
> >> > thought you would own copyright on the results, just like using Adobe
> >> > Dreamweaver and Adobe Illustrator to build out a site doesn't put the
> >> > content under Adobe licensing.
> >> >
> >> > That doesn't appear to be the case here, but I think we do need to
> >> > consider the 3 concerns I've listed.
> >> >
> >> > Both you and Harbs claim that replicating your prototype's look and
> >>feel
> >> > will be a lot of work, but how much work are really talking about,
> >>and do
> >> > we have to exactly replicate it (and should we)? If you think about
> >>how
> >> > Royale components are created, they work with some default CSS. I
> >>think
> >> > if we implement themes, we'll end up with components with particular
> >> > "sub-DOMs" and CSS that dictates the visuals on those sub-DOMs.
> >>AIUI, we
> >> > are expecting artwork from some designers about other default looks
> >>for
> >> > Royale components. Won't we be facing a similar challenge of trying
> >>to
> >> > figure out the CSS that best matches what we see on a screen?
> >> >
> >> > So, I think it is great that WP and MoveDo helped you create this
> >> > fantastic looking prototype. But, IMO, one direction we can go from
> >>here
> >> > is to try to replicate the visuals you created in CSS in a way that
> >>can
> >> be
> >> > re-used via the Apache Way. I think we'd learn about themes as we
> >>try to
> >> > do that. Could we get most of the way there in a couple of days?
> >>Then
> >> > others can offer fine-tuning via patches.
> >> >
> >> > And yes, WP is tuned towards templated content in a consistent way,
> >>but
> >> it
> >> > would be interesting to build Royale components that do something
> >> similar.
> >> >
> >> > Thoughts?
> >> > -Alex
> >> >
> >> > On 10/26/17, 1:12 AM, "carlos.rovira@gmail.com on behalf of Carlos
> >> Rovira"
> >> > <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> >> wrote:
> >> >
> >> >> Harbs is right,
> >> >>
> >> >> to get something that looks cool and consistent is difficult and for
> >> this
> >> >> reason I use wordpress+theme (in this case movedo). Is the same
> >>thing as
> >> >> why people use flex or royale. Is the way to start from a point where
> >> you
> >> >> are more efficient and maintenance can be assumed.
> >> >>
> >> >> Alex, you see lots of difference since I customized via movedo
> >>interface
> >> >> but as well did some tweaks in custom css (for example the footer
> >>column
> >> >> menus)
> >> >>
> >> >> So could we rework the site without wp and movedo. Sure, as I stated
> >>all
> >> >> sites can be write in different ways, but the long term reason to
> >>adopt
> >> a
> >> >> CMS like WP is to have a backend to introduce content of quality in
> >>the
> >> >> most easy way while preserving quality on presentation (styles,
> >>fonts,
> >> >> effects...)
> >> >>
> >> >> I think we are in a situation where "the Apache way" fails completely
> >> >> since
> >> >> we should be able to make this quick and easy and concentrate in our
> >> >> Royale
> >> >> code, that is why we are here, and why I tried to go this path: to
> >>get
> >> >> something that looks good and professional but to spend very few time
> >> for
> >> >> our part.
> >> >>
> >> >> I'm very pragmatic, and like to go to the point. All Apache rules
> >>should
> >> >> be
> >> >> focused in protect the code we release, and we should have less
> >>trouble
> >> >> with tools like WP, Jira, Nexus, and the rest. In fact Apache is
> >>using
> >> >> those tools all along the way, why is so hard to do this?
> >> >>
> >> >> We only need:
> >> >>
> >> >> * Some host for a Wordpress instance: this could be the current
> >> >> Codeoscopic
> >> >> subdomain or whatever people like. I'd be more happy if the wp
> >>instance
> >> is
> >> >> in some server that could be controlled and maintained by ASF. I
> >>don't
> >> >> know
> >> >> if this could be WP.com or some ASF's virtual machine that could host
> >> >> that.
> >> >>
> >> >> * The Movedo theme: I write to Dimitri, from greatives. He is very
> >> >> supportive and very like the idea, but is not in their hands. He
> >>point
> >> me
> >> >> to talk with envato, and I write to them, but still doesn't have a
> >> >> response. My thinking here is that we really don't need nothing of
> >>this.
> >> >> Envato could donate a license but is only 59$, so is something
> >> affordable
> >> >> by a simple donation.
> >> >>
> >> >> * Finaly to generate an static site from WP. This is as well not
> >>needed,
> >> >> but we can do it. People use to generate wp static version in order
> >>to
> >> >> protect their sites from hacking. That's the only relevant point to
> >>do
> >> >> this. So for me is something we can do if the rest of community wants
> >> it.
> >> >> Is very easy to do.
> >> >>
> >> >>
> >> >> Additionaly: As we are not uploading any website code to any ASF
> >>repo,
> >> >> since as I said, it would be like to upload the JIRA source code to
> >>our
> >> >> repos, and that doesn't give us anything (we're here to release only
> >> >> apache
> >> >> royale code). we can :
> >> >>
> >> >> 1.- Use the royale.codeoscopic.com wp instance as the tool for us to
> >> >> modify
> >> >> the site (people in our community will have user/pass in this wp
> >> instance
> >> >> to create post and pages)
> >> >> (in this way is similar to the server Alex had on his own to make
> >>some
> >> >> apache flex task, correct me if I'm wrong)
> >> >> Again, it can be royale.codeoscopic.com or other hosting ASF wants.
> >> >>
> >> >> 2.- Each time something changes: generate static site and deploy to
> >> >> royale.apache.org
> >> >> (in this case the set of static generated html/js/css could not be
> >> >> uploaded
> >> >> to any ASF repo since we don't want to release the website code, that
> >> must
> >> >> be served in the same way ASF serves JIRA, or whatever other
> >>commercial
> >> >> tool
> >> >>
> >> >> Hosting a generated site with a movedo commercial theme needs of a
> >>59$
> >> >> license that could be donated by envato or donated for other
> >> >> person/company
> >> >> (for example Codeoscopic)
> >> >>
> >> >> For me this is quick and easy and I think we're not making something
> >> wrong
> >> >> in legal terms
> >> >>
> >> >> Carlos
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> 2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
> >> >>
> >> >>> It’s using greatives’ CSS and JS files for styling, layout and
> >>effects.
> >> >>>
> >> >>> Generally, these themes have a lot of flexibility to change the
> >>look of
> >> >>> a
> >> >>> site without messing with CSS and JS.
> >> >>>
> >> >>> Can we re-write the CSS and JS to do the same kind of thing?
> >>Probably.
> >> >>> But
> >> >>> it would be a considerable amount of work.
> >> >>>
> >> >>> What’s included in the license? I’m really not sure.
> >> >>>
> >> >>> It gives rights to us the theme in WordPress. Does that allow
> >> >>> repurposing
> >> >>> the CSS and JS files for use elsewhere? I don’t know.
> >> >>>
> >> >>> Harbs
> >> >>>
> >> >>>> On Oct 26, 2017, at 9:56 AM, Alex Harui <ah...@adobe.com.INVALID>
> >> >>> wrote:
> >> >>>>
> >> >>>> I'm still confused about something.
> >> >>>>
> >> >>>> Can someone explain how creativity and licensing are
> >>interconnected?
> >> >>> I'm not familiar with WP themes, but I think they are templates with
> >> >>> placeholders for particular aspects of a web page/blog. I've been
> >>told
> >> >>> that this Royale site prototype is based on the Movedo theme. When
> >>I
> >> >>> searched for it on the internet I ended up here:
> >> >>> https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fgreatives
> >> >>> .eu%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b344
> >> >>> 38794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> VI0EOLywsaxbKgmhAe
> >> >>> F08cdZNQjcgtIjyFvJ2R33hlo%3D&reserved=0
> >> >>> themeforest/themeswitcher/?product=movedo#movedo
> >> >>>>
> >> >>>> It doesn't look at all like the prototype at
> >> >>>
> >> >>> https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Froyale.co
> >> >>> deoscopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b
> >> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=3GHfDzdFp6B
> >> >>> 4RQMLuP00jKAHmwQ1QMubUd4dgz3FdTA%3D&reserved=0. Maybe the menu bar
> >> >>> along the top?
> >> >>>>
> >> >>>> So what did we license from greatives? Can Carlos or someone else
> >> >>> try
> >> >>> to reproduce the prototype without looking at the current CSS and
> >>maybe
> >> >>> use
> >> >>> AL licensed fonts or something like that?
> >> >>>>
> >> >>>> Thanks,
> >> >>>> -Alex
> >> >>>>
> >> >>>> From: Dave Fisher
> >> >>> <da...@comcast.net>>
> >> >>>> Reply-To: <de...@royale.apache.org>>
> >> >>>> Date: Tuesday, October 24, 2017 at 11:06 AM
> >> >>>> To: <de...@royale.apache.org>>
> >> >>>> Subject: Re: Apache Royale static web site
> >> >>>>
> >> >>>> Hi Alex,
> >> >>>>
> >> >>>> We will need to ask Carlos to list out all of the themes he uses
> >>and
> >> >>> then we will need to track things down and ask questions.
> >> >>>>
> >> >>>> Here is the site for what looks like the main theme:
> >> >>>
> >> >>> https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fgreative
> >> >>> s.ticksy.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b
> >> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=KBxlYi2QO
> >> >>> PDqNGhTsU6GJMhdUggdHVZjiYetcIcE8vE%3D&reserved=0
> >> >>>>
> >> >>>> It is the Move Do theme.
> >> >>>>
> >> >>>> Regards,
> >> >>>> Dave
> >> >>>>
> >> >>>> On Oct 24, 2017, at 10:56 AM, Alex Harui <aharui@adobe.com.INVALID
> <
> >> >>> mailto:aharui@adobe.com.INVALID>> wrote:
> >> >>>>
> >> >>>> Hi Dave,
> >> >>>>
> >> >>>> I'm still wondering, even if we can see and reuse the CSS/JS/HTML,
> >>do
> >> >>> we
> >> >>> have the rights to replicate use of that look-and-feel elsewhere? I
> >> >>> don't
> >> >>> understand who owns the creative content.
> >> >>>>
> >> >>>> Thoughts?
> >> >>>> -Alex
> >> >>>>
> >> >>>> From: Dave Fisher
> >><dave2wave@comcast.net<mailto:dave2wave@comcast.net
> >> >>>> <ma...@comcast.net>>
> >> >>>> Reply-To: <dev@royale.apache.org<mailto:dev@royale.apache.org
> >> ><mailto:
> >> >>> dev@royale.apache.org>>
> >> >>>> Date: Tuesday, October 24, 2017 at 10:50 AM
> >> >>>> To: <de...@royale.apache.org><mailto:
> >> >>> dev@royale.apache.org>>
> >> >>>> Subject: Re: Apache Royale static web site
> >> >>>>
> >> >>>> Hi Alex,
> >> >>>>
> >> >>>> On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID
> <
> >> >>> mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>>>
> >> >>> wrote:
> >> >>>>
> >> >>>> There is something I don't think I understand. AIUI, at some
> >>point,
> >> >>> we
> >> >>>> will want the Apache Royale site to include actual Royale
> >> >>> applications,
> >> >>>> right? And I would think we would want the styling of those
> >> >>> applications
> >> >>>> to be consistent with the rest of the site. So I'm not clear how
> >>we
> >> >>> will
> >> >>>> be able to implement the styling/theme of these Royale applications
> >> >>> if we
> >> >>>> don't have rights to the styling. I don't understand how WP themes
> >> >>> and
> >> >>>> commercial licensing works if we want to replicate that user
> >> >>> experience
> >> >>>> outside of WP.
> >> >>>>
> >> >>>> We need to examine the static export of the CSS and HTML.
> >> >>>>
> >> >>>>
> >> >>>> If we can use those visuals outside of WP, then why must we
> >>continue
> >> >>> to
> >> >>>> use WP to generate the site? I would hope the theme would be
> >> >>> implemented
> >> >>>> as CSS and some templates we could use without WP.
> >> >>>>
> >> >>>> We should be able to adapt. Site building in the CMS can get
> >>complex
> >> >>> if
> >> >>> needed. For
> >> >>>
> >>OpenOffice.org<https://na01.safelinks.protection.outlook.
> com/?url=https%3
> >>A%2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f49
> >>2c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636446392
> >>882621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
> S9p2zHjJMq%2FnM%3D&reserved
> >>=0.
> >> com/?url=http%3A
> >> >>> %2F%2FOpenOffice.org&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7
> >> >>>
> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> m3Mv
> >> >>> XfpJIZbB4u1Zhr0AB%2B%2BVI5uPKwu7N33MkPuovjs%3D&reserved=0><
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fna01.s&d
> >>ata=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
> 4cfc%7Cfa7b1b5a7b34438794aed
> >>2c178decee1%7C0%7C0%7C636446392882621163&sdata=
> hxky0LHm5GqF8zMjFHm3bXfugJ
> >>xCS6qWPoG%2FbWItNgQ%3D&reserved=0
> >> >>> afelinks.protection.outlook.com/?url=http%3A%2F%
> >> 2FOpenOffice.org&data=02%
> >> >>> 7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
> >> 7Cfa7b1b5a7b34438794aed2c178de
> >> >>> cee1%7C0%7C0%7C636446023931803217&sdata=m3MvXfpJIZbB4u1Zhr0AB%2B%
> >> 2BVI5uPK
> >> >>> wu7N33MkPuovjs%3D&reserved=0>
> >> >>> we use the legacy html pulling out the title and content body and
> >>place
> >> >>> it
> >> >>> within a markdown template.
> >> >>>>
> >> >>>>
> >> >>>> Also, if someone wants to patch the site, they can't just offer a
> >> >>> patch
> >> >>> of
> >> >>>> the HTML right? They would need to figure out where in WP it comes
> >> >>> from?
> >> >>>> Is there a patch process for WP content?
> >> >>>>
> >> >>>> Possibly.
> >> >>>>
> >> >>>>
> >> >>>> Sorry if there is some basic thing I am missing.
> >> >>>>
> >> >>>> It will get complex first as we figure out how to embed and then it
> >> >>> will
> >> >>> get simplified as we find the best way.
> >> >>>>
> >> >>>> Regards,
> >> >>>> Dave
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> Thanks,
> >> >>>> -Alex
> >> >>>>
> >> >>>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
> >> >>> carlos.rovira@gmail.com><ma...@gmail.com> on behalf
> >>of
> >> >>> Carlos
> >> >>>> Rovira"
> >> >>> <ca...@gmail.com><mailto:
> >> >>> carlos.rovira@gmail.com> on behalf of
> >> >>>> carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
> >> >>>> <ma...@codeoscopic.com>> wrote:
> >> >>>>
> >> >>>> Thanks Dave,
> >> >>>>
> >> >>>> I'll write an email to trademarks to start with the process. I
> >>think
> >> >>> is
> >> >>>> better to migrate to
> >> >>> WP.com<https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2FWP
> >> >>> .com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b34438
> >> >>> 794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> pPTlG8DjwzO%2FN%2B0r
> >> >>> euRRSegBNuKdtuonR2fro55wfgs%3D&reserved=0><https://na01.
> >> safelinks.protect
> >> >>> ion.outlook.com/?url=http%3A%2F%2FWP.com&data=02%7C01%7C%
> >> 7Cdb97bd994ab24e
> >> >>> e2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C636446023
> >> >>> 931803217&sdata=pPTlG8DjwzO%2FN%2B0reuRRSegBNuKdtuonR2fro55wfg
> >> s%3D&reserv
> >> >>> ed=0> before
> >> >>> continue working on content so we can
> >> >>>> detect whatever issue we could get.
> >> >>>>
> >> >>>> Thanks!
> >> >>>>
> >> >>>> Carlos
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> 2017-10-24 18:56 GMT+02:00 Dave Fisher
> >><dave2wave@comcast.net<mailto:
> >> >>> dave2wave@comcast.net><ma...@comcast.net>>:
> >> >>>>
> >> >>>> Hi Carlos,
> >> >>>>
> >> >>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira
> >><carlosrovira@apache.org<
> >> >>> mailto:carlosrovira@apache.org><ma...@apache.org>>>
> >> >>>> wrote:
> >> >>>>
> >> >>>> Hi,
> >> >>>>
> >> >>>> just let you know that I tried to create an static version of the
> >> >>>> preview
> >> >>>> site with success. I use this plugin :
> >> >>>>
> >> >>>> https://na01.safelinks.protection.outlook.com/?url=
> >> >>> https%3A%2F%2Fwordpres
> >> >>>>
> >> >>> s.org<https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fs.o
> >> >>> rg%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b3443
> >> >>> 8794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> 6zrqW3l9%2BJqeOxjih
> >> >>> uPWtMuguPsUDWnbqhyRxVXiTfI%3D&reserved=0>%2Fplugins%
> >> 2Fsimply-static%2F&da
> >> >>> ta=02%7C01%7C%
> >> >>> 7Cb448363ee5984b3b3e0f
> >> >>>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
> >> >>> cee1%7C0%7C0%7C636444624020033
> >> >>>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpn
> rieARat1lz2bk%3D&reserved=0
> >> >>>>
> >> >>>> and we can generate all static content with relative or absolute
> >>urls.
> >> >>>> The
> >> >>>> final preview site in static is 134mb
> >> >>>>
> >> >>>> Another thing I was searching was to use a WP to Jekyll exporter
> >>but
> >> >>>> this
> >> >>>> is not what I wanted since it seems Jekyll is all about markdown
> >>and
> >> >>>> we
> >> >>>> want a full html site with all the eye candy JS+CSS resources. In
> >>the
> >> >>>> end,
> >> >>>> and thinking more about it, is not what we want since although the
> >> >>>> site
> >> >>>> would be exported ok, we don't want to upload it to the GitHub
> >>pages
> >> >>>> like
> >> >>>> we discusses in the other thread due to expose part of the code of
> >>a
> >> >>>> commercial wp theme.
> >> >>>>
> >> >>>> So, the workflow we can use is: Use the WP backend to enter new
> >> >>>> content
> >> >>>> and
> >> >>>> modify existing want with ease (this is important is we want people
> >> >>>> contributing here). Next, with all changes done, generate a static
> >> >>>> version
> >> >>>> and replace the entire site with a fresh generated static site at
> >> >>>>
> >> >>>
> >>royale.apache.org<https://na01.safelinks.protection.
> outlook.com/?url=http
> >>s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%
> 7Cf48589d8bd1f492c5fa
> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63644639288262
> >>1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
> >> outlook.com/?url=http
> >> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
> >> 7Cdb97bd994ab24ee2f91c08d51
> >> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&s
> >> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&
> reserved=0>.
> >> and
> >> >>> as well route the
> >> >>> more friendly domain to this
> >> >>>> if
> >> >>>> board is ok with that.
> >> >>>>
> >> >>>> Yes! External domain
> >> >>>
> >>royalysdk.org<https://na01.safelinks.protection.outlook.
> com/?url=https%3A
> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f492
> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364463928
> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
> S9p2zHjJMq%2FnM%3D&reserved=
> >>0.
> >> com/?url=http%3A%
> >> >>> 2F%2Froyalysdk.org%2F&data=02%7C01%7C%
> 7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%
> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&sdata=Dmo
> >> >>> CAUlAVHkkOp0uFdDH0%2FoUUU9qwdl00M8fWRe888Q%3D&reserved=0> is
> >> redirected
> >> >>> to
> >> >>>
> >>royale.apache.org<https://na01.safelinks.protection.
> outlook.com/?url=http
> >>s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%
> 7Cf48589d8bd1f492c5fa
> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63644639288262
> >>1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
> >> outlook.com/?url=http
> >> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
> >> 7Cdb97bd994ab24ee2f91c08d51
> >> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&s
> >> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>
> >>as
> >> >>>> discussed.
> >> >>>>
> >> >>>>
> >> >>>> We can check with apache board or trademarks what they propose
> >>about
> >> >>>> to
> >> >>>> create a
> >> >>>
> >>Wordpress.com<https://na01.safelinks.protection.outlook.
> com/?url=https%3A
> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f492
> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364463928
> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
> S9p2zHjJMq%2FnM%3D&reserved=
> >>0.
> >> com/?url=http%3A%
> >> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%
> 7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%
> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&sdata=%2B
> >> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
> >>account
> >> >>> managed by Apache
> >> >>> and migrate from my
> >> >>>> server
> >> >>>> to that account, and all this stuff from there, since if I remember
> >> >>>> some
> >> >>>> people said that would be more ok with Apache.I'd end removing my
> >>temp
> >> >>>> subdomain after this.
> >> >>>>
> >> >>>> The advantage of using the
> >> >>>
> >>Wordpress.com<https://na01.safelinks.protection.outlook.
> com/?url=https%3A
> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f492
> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364463928
> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
> S9p2zHjJMq%2FnM%3D&reserved=
> >>0.
> >> com/?url=http%3A%
> >> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%
> 7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%
> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&sdata=%2B
> >> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
> >> >>> location is twofold:
> >> >>>>
> >> >>>> (1) Wordpress keeps security up to date.
> >> >>>> (2) If something happens to you or your company then we have better
> >> >>>> access.
> >> >>>>
> >> >>>> I suspect though that with the status export method this will not
> >>be
> >> >>> as
> >> >>>> great a concern.
> >> >>>>
> >> >>>>
> >> >>>> What do you think? Can I move this with the people we were talking
> >> >>>> some
> >> >>>> weeks ago?
> >> >>>>
> >> >>>> Either you or I can email Trademarks with the plan.
> >> >>>>
> >> >>>> We can then discuss the redirection with Infrastructure and get the
> >> >>> site
> >> >>>> checked in.
> >> >>>>
> >> >>>> Regards,
> >> >>>> Dave
> >> >>>>
> >> >>>>
> >> >>>> Let me know in order to start making the next steps
> >> >>>>
> >> >>>> Thanks
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Carlos Rovira
> >> >>>>
> >> >>>> https://na01.safelinks.protection.outlook.com/?url=
> >> >>> http%3A%2F%2Fabout.me%
> >> >>>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> >> >>> 73f8%7Cfa7b1
> >> >>>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >> >>> sdata=1q5B1u1lLR
> >> >>>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>>
> >> >>>> <https://na01.safelinks.protection.outlook.com/?url=
> >> >>> http%3A%2F%2Fwww.codeo
> >> >>>>
> >> >>>
> >>scopic.com<https://na01.safelinks.protection.outlook.
> com/?url=https%3A%2F
> >>%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f492c5f
> >>aa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364463928826
> >>21163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0.
> >> com/?url=http%3A%2F%
> >> >>> 2Fscopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b
> >> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=oG9idkXzU
> >> >>> tg91G5vhl5P0Dn2u8gXX55UvN172PAlPXs%3D&reserved=0>&data=02%7C01%7C%
> >> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> >> >>>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >> >>> sdata=Y%2Fkytu4lJUWu5H
> >> >>>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<https://na01.safelinks.protection.outlook.
> com/?url=https%3A%2F%
> >>2Fna01.safelinks.protection.outlook&data=02%7C01%7C%
> 7Cf48589d8bd1f492c5fa
> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63644639288262
> >>1163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0.
> >> com/?url=http%3A%2F%2
> >> >>> Fcopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b
> >> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=ZPPDqp5SNhK
> >> >>> C2rzYxfzkSV7f8lDtLmaRyyaMAlvtRcw%3D&reserved=0>&data=02%7C01%7C%
> >> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> >> >>>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
> >> >>> 2Fkytu4lJUWu5Hz
> >> >>>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
> >> >>>>
> >> >>>>
> >> >>>> Conocenos Avant2 en 1 minuto!
> >> >>>> <https://na01.safelinks.protection.outlook.com/?url=
> >> >>> https%3A%2F%2Favant2.e
> >> >>>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> >> >>> 73f8%7Cfa7b1b5a
> >> >>>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >> >>> sdata=SJmmZQTVSb0tmX
> >> >>>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> >> >>>> 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.
> >> >>>>
> >> >>>>
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> <https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fwww.codeo
> >> >> scopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b
> >> >> 34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=ZPowinnGs4jxxXQ4
> >> >> hULLfJLfWsGXx9zNLKnS9W7JoNY%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%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b3
> >> >> 4438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> ZPowinnGs4jxxXQ4h
> >> >> ULLfJLfWsGXx9zNLKnS9W7JoNY%3D&reserved=0
> >> >>
> >> >>
> >> >> Conocenos Avant2 en 1 minuto!
> >> >> <https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Favant2.e
> >> >> s%2F%23video&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a
> >> >> 7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=ZiX3l%2FtQwsOG
> >> >> QN%2BibIJ5pxYpI5UboaH26BzM%2F9AtaLg%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
> >> >> 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.
> >> >
> >>
> >>
> >
> >
> >--
> >
> ><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo
> >scopic.com&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
> 4cfc%7Cfa7b1b5a7b
> >34438794aed2c178decee1%7C0%7C0%7C636446392882621163&
> sdata=lKI9XjSOeXi%2Brk
> >UN0qJG%2F57in9KVLsXMs2yU56LYHmk%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%7Cf48589d8bd1f492c5faa08d51c9f
> 4cfc%7Cfa7b1b5a7b3
> >4438794aed2c178decee1%7C0%7C0%7C636446392882621163&
> sdata=lKI9XjSOeXi%2BrkU
> >N0qJG%2F57in9KVLsXMs2yU56LYHmk%3D&reserved=0
> >
> >
> >Conocenos Avant2 en 1 minuto!
> ><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant2.e
> >s%2F%23video&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
> 4cfc%7Cfa7b1b5a
> >7b34438794aed2c178decee1%7C0%7C0%7C636446392882621163&
> sdata=H2q8lqkz3DT6UD
> >tSbrEjUPjektN2ii9zreOhSmlCdB0%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
> >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.
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Alex,
2017-10-26 22:06 GMT+02:00 Alex Harui <ah...@adobe.com.invalid>:
> Hi Carlos,
>
> I have a WP-based blog, so I understand how easy it is to write some text
> and have it look nice. But I'm still confused about who owns what. Does
> Envato/Greatives own the look and feel of royale.codeoscopic.com or do
> you?
codeoscopic owns a license of movedo theme.
anyone that buys the license (59$) will own it, so I think it's not a huge
quantity of money
> I understand that Royale is tuned more towards web applications but
> to my mind, I see more and more web sites being about interactivity rather
> than just displaying text and images. Even blog commenting and upvoting
> looks like an app to me.
>
The two worlds interesect, that's evidently, but are different beast. I
tried to make in the past
some website with Flex, and although I did it and we get some cool effects,
in the end it wasn't the
right tool for the job. I did as well an Application in wordpress with some
plugins due to time restrictions
and while I did it, again it was not the right tool for the job and many
things was very limited.
>
> I would like to some day use Royale to create the page you've prototyped
> at royale.codeoscopic.com and maybe enhance it by having a Royale news
> feed or some other backend connectivity for some of the content. But can
> we replicate the look and feel of what you have prototyped and put that
> under ALv2? I think we have to find a way to make that possible. The
> theme or CSS that we use to replicate your prototype may not be our
> default theme/CSS, but it should still be a valid theme or CSS file and
> components.
>
without doubt, but for me this is not the right time to do it. As Harbs
already agree, we need
to put a website online ASAP.
We can always come back and with time, can make that work. But IMHO, we
need to choose
an strategy and see what things are needed first and organize efforts. For
me UI theme is more need than replicate something that we already have.
>
> That's why I'm concerned that working from Movedo is going to leak into
> other things we want to do. But if we start from scratch and try to
> replicate the visuals you've chosen, I would hope we can get something
> that looks similar quickly and then invite more folks to help tune it.
> And as Harbs says, I'm not asking you to do that work, someone else can.
> What you've done already is significant and very helpful and I think you
> made the right choice of using your WP skills to create it quickly.
Right, but for me that work could fit into Royale examples, but would not
be of much use in the framework
> If we were to reproduce your prototype in Royale, I would want to create
> re-usable components such as:
> MenuBar
> SearchShareUserProfileMoreMenuBar
> TopBar (that holds all of the icon, title, MenuBar and
> SearchShareProfileButtonBar)
> IconTitleTextPanel
> And more...
>
>
I think you are right if we want to recreate the website and make Royale
components...again for me this is and example.
But, if I start to create a styling that could fit more use cases and be
the default Express Component Set face? Don't you think that work would be
more valuable? I think so, and is what I want to contribute next.
That would be more "application" style and less "web" style. based on that
work we can make more theme projects like Apache Flex already has and have
an Application property "theme" to switch between themes. I think that is
what I think people migrating from Apache Flex SDK expects.
> Then someone else can come along and assemble their own site from these
> pieces.
>
completely right, but expect many few people doing that since, or at least
very residual, since there are other tools far better to do the job. If we
want to go that route I think we will need to focus in many task that will
ease that kind of target and make Apache Royale good in that area. For
example, routing. For Royale to make good websites, routing is essential,
and no body will use it without be able to configure deep linking in a
reliable and useful way.
>
> Back in the Adobe days, some folks actually took the FlexStore example,
> modified it slightly and deployed it in production for their own products.
> We didn't care that they pretty much used the same look-and-feel. I think
> we want to make the same sort of thing possible for Royale.
>
Alex, I think this is possible. In fact, all you expose is completely
right, but I want you to think in how many hands have we now. Many of this
things can be done if we get more people on board, but for this to happen
we need to unblock what we have, and go to other things we need. If I need
two things (website and themes), I prefer to have 1-1 than 2-0. And in some
months from now, we always can come back and make the website in our
technology, and maybe even change it for something fresh again.
That's my 2ctns.
Carlos
>
> Thoughts?
> -Alex
>
> On 10/26/17, 11:27 AM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira" <carlos.rovira@gmail.com on behalf of
> carlos.rovira@codeoscopic.com> wrote:
>
> >Hi,
> >
> >in order to help you, Alex and Harbs (others could join as well) to
> >understand all the picture, I could create an account for you in
> >royale.codeoscopic.com
> >
> >In this way you could see point 1 of Alex's list (how integrate some new
> >content in website). and most important, you will see the visual tool to
> >edit and mount a new content in pages or posts.
> >
> >This last thing is one of the main reasons I want to use WP in the day by
> >day. If you want to create some content, doing manually is a nightmare.
> >
> >I'll send you admin users to your accounts and you're free to enter and
> >watch, (but please don't modify anything to avoid break the actual site)
> >
> >In order to create some default theme (point 2), again here I think we
> >talking about different things. I think we don't want to base our default
> >theme for UI controls in apache royale in what I did in the theme. That
> >would be a mistake in since movedo principles are based on website look
> >and
> >usability. Fonts and spacing is huge to express content in a modern
> >website. To make a comparative, if you take MDL and movedo side by side,
> >the first is for applications while the second is to present text and
> >images in a website.
> >
> >My plan, as I mention before, is to start creating a UI component styles
> >that could be programed in a theme. I have in mind to make two of them: a
> >wireframe theme and a full default theme. The first one could have the
> >same
> >sizes and fonts but with only outlines and black and white (like the flex
> >wireframe to avoid style and application when you're prototyping.
> >
> >Regarding time to replicate movedo theme with our own styling, I'm sure is
> >not a two day task, but more, there's so much there, and only to get
> >something that only will be a shadow of the original.
> >
> >As Harbs mention there's people making styling, but as they are not
> >commenting in this list we don't know anything about if they are doing
> >something this days, or maybe they couldn't use that time to work on this.
> >
> >For last (point 3), I did wordpress themes some years ago, and is a huge
> >task to do, in time and effort. And with time you can get something of
> >quality, but again, why we want to spend our time in something we already
> >have? I don't find anything here, since we are not here to create WP
> >themes, I prefer to use that time to create an Apache Royale UI theme and
> >even help to program it, because that is what we really need to make more
> >people join us.
> >
> >
> >
> >
> >2017-10-26 19:37 GMT+02:00 Harbs <ha...@gmail.com>:
> >
> >> Another point to consider:
> >>
> >> We’ve had some folks offer to help with skinning Royale components. It
> >> should be pretty straightforward to give them (and anyone else who
> >>wants to
> >> help) committer rights to the website repo. If we have more people
> >>working
> >> on it, the task of recreating the appearance achieved through the Movedo
> >> CSS should be al lot easier.
> >>
> >> I don’t feel comfortable asking Carlos to do more work than he’s
> >>offered,
> >> but with help from others, it might be a lot easier.
> >>
> >> Harbs
> >>
> >> > On Oct 26, 2017, at 7:41 PM, Alex Harui <ah...@adobe.com.INVALID>
> >> wrote:
> >> >
> >> > Hi Carlos,
> >> >
> >> > I don't know if the "Apache Way" is a problem here. So far I think we
> >> > have heard opinions and concerns but AFAICT no hard policy has been
> >> quoted
> >> > that prevents having royale.a.o point to WP.com.
> >> >
> >> > But I am still unclear if hosting our site on WP is really the best
> >> > strategy. I have the following concerns:
> >> >
> >> > 1) How would be include a Royale application in our site?
> >> > 2) How would we style the Royale application to look consistent with
> >>the
> >> > rest of the site?
> >> > 3) Could we ever create a theme based on this styling?
> >> >
> >> > I didn't, and still don't, understand how WP themes and their
> >>licensing
> >> > work, otherwise I think I would have asked more questions up front. I
> >> > thought you would own copyright on the results, just like using Adobe
> >> > Dreamweaver and Adobe Illustrator to build out a site doesn't put the
> >> > content under Adobe licensing.
> >> >
> >> > That doesn't appear to be the case here, but I think we do need to
> >> > consider the 3 concerns I've listed.
> >> >
> >> > Both you and Harbs claim that replicating your prototype's look and
> >>feel
> >> > will be a lot of work, but how much work are really talking about,
> >>and do
> >> > we have to exactly replicate it (and should we)? If you think about
> >>how
> >> > Royale components are created, they work with some default CSS. I
> >>think
> >> > if we implement themes, we'll end up with components with particular
> >> > "sub-DOMs" and CSS that dictates the visuals on those sub-DOMs.
> >>AIUI, we
> >> > are expecting artwork from some designers about other default looks
> >>for
> >> > Royale components. Won't we be facing a similar challenge of trying
> >>to
> >> > figure out the CSS that best matches what we see on a screen?
> >> >
> >> > So, I think it is great that WP and MoveDo helped you create this
> >> > fantastic looking prototype. But, IMO, one direction we can go from
> >>here
> >> > is to try to replicate the visuals you created in CSS in a way that
> >>can
> >> be
> >> > re-used via the Apache Way. I think we'd learn about themes as we
> >>try to
> >> > do that. Could we get most of the way there in a couple of days?
> >>Then
> >> > others can offer fine-tuning via patches.
> >> >
> >> > And yes, WP is tuned towards templated content in a consistent way,
> >>but
> >> it
> >> > would be interesting to build Royale components that do something
> >> similar.
> >> >
> >> > Thoughts?
> >> > -Alex
> >> >
> >> > On 10/26/17, 1:12 AM, "carlos.rovira@gmail.com on behalf of Carlos
> >> Rovira"
> >> > <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> >> wrote:
> >> >
> >> >> Harbs is right,
> >> >>
> >> >> to get something that looks cool and consistent is difficult and for
> >> this
> >> >> reason I use wordpress+theme (in this case movedo). Is the same
> >>thing as
> >> >> why people use flex or royale. Is the way to start from a point where
> >> you
> >> >> are more efficient and maintenance can be assumed.
> >> >>
> >> >> Alex, you see lots of difference since I customized via movedo
> >>interface
> >> >> but as well did some tweaks in custom css (for example the footer
> >>column
> >> >> menus)
> >> >>
> >> >> So could we rework the site without wp and movedo. Sure, as I stated
> >>all
> >> >> sites can be write in different ways, but the long term reason to
> >>adopt
> >> a
> >> >> CMS like WP is to have a backend to introduce content of quality in
> >>the
> >> >> most easy way while preserving quality on presentation (styles,
> >>fonts,
> >> >> effects...)
> >> >>
> >> >> I think we are in a situation where "the Apache way" fails completely
> >> >> since
> >> >> we should be able to make this quick and easy and concentrate in our
> >> >> Royale
> >> >> code, that is why we are here, and why I tried to go this path: to
> >>get
> >> >> something that looks good and professional but to spend very few time
> >> for
> >> >> our part.
> >> >>
> >> >> I'm very pragmatic, and like to go to the point. All Apache rules
> >>should
> >> >> be
> >> >> focused in protect the code we release, and we should have less
> >>trouble
> >> >> with tools like WP, Jira, Nexus, and the rest. In fact Apache is
> >>using
> >> >> those tools all along the way, why is so hard to do this?
> >> >>
> >> >> We only need:
> >> >>
> >> >> * Some host for a Wordpress instance: this could be the current
> >> >> Codeoscopic
> >> >> subdomain or whatever people like. I'd be more happy if the wp
> >>instance
> >> is
> >> >> in some server that could be controlled and maintained by ASF. I
> >>don't
> >> >> know
> >> >> if this could be WP.com or some ASF's virtual machine that could host
> >> >> that.
> >> >>
> >> >> * The Movedo theme: I write to Dimitri, from greatives. He is very
> >> >> supportive and very like the idea, but is not in their hands. He
> >>point
> >> me
> >> >> to talk with envato, and I write to them, but still doesn't have a
> >> >> response. My thinking here is that we really don't need nothing of
> >>this.
> >> >> Envato could donate a license but is only 59$, so is something
> >> affordable
> >> >> by a simple donation.
> >> >>
> >> >> * Finaly to generate an static site from WP. This is as well not
> >>needed,
> >> >> but we can do it. People use to generate wp static version in order
> >>to
> >> >> protect their sites from hacking. That's the only relevant point to
> >>do
> >> >> this. So for me is something we can do if the rest of community wants
> >> it.
> >> >> Is very easy to do.
> >> >>
> >> >>
> >> >> Additionaly: As we are not uploading any website code to any ASF
> >>repo,
> >> >> since as I said, it would be like to upload the JIRA source code to
> >>our
> >> >> repos, and that doesn't give us anything (we're here to release only
> >> >> apache
> >> >> royale code). we can :
> >> >>
> >> >> 1.- Use the royale.codeoscopic.com wp instance as the tool for us to
> >> >> modify
> >> >> the site (people in our community will have user/pass in this wp
> >> instance
> >> >> to create post and pages)
> >> >> (in this way is similar to the server Alex had on his own to make
> >>some
> >> >> apache flex task, correct me if I'm wrong)
> >> >> Again, it can be royale.codeoscopic.com or other hosting ASF wants.
> >> >>
> >> >> 2.- Each time something changes: generate static site and deploy to
> >> >> royale.apache.org
> >> >> (in this case the set of static generated html/js/css could not be
> >> >> uploaded
> >> >> to any ASF repo since we don't want to release the website code, that
> >> must
> >> >> be served in the same way ASF serves JIRA, or whatever other
> >>commercial
> >> >> tool
> >> >>
> >> >> Hosting a generated site with a movedo commercial theme needs of a
> >>59$
> >> >> license that could be donated by envato or donated for other
> >> >> person/company
> >> >> (for example Codeoscopic)
> >> >>
> >> >> For me this is quick and easy and I think we're not making something
> >> wrong
> >> >> in legal terms
> >> >>
> >> >> Carlos
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >>
> >> >> 2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
> >> >>
> >> >>> It’s using greatives’ CSS and JS files for styling, layout and
> >>effects.
> >> >>>
> >> >>> Generally, these themes have a lot of flexibility to change the
> >>look of
> >> >>> a
> >> >>> site without messing with CSS and JS.
> >> >>>
> >> >>> Can we re-write the CSS and JS to do the same kind of thing?
> >>Probably.
> >> >>> But
> >> >>> it would be a considerable amount of work.
> >> >>>
> >> >>> What’s included in the license? I’m really not sure.
> >> >>>
> >> >>> It gives rights to us the theme in WordPress. Does that allow
> >> >>> repurposing
> >> >>> the CSS and JS files for use elsewhere? I don’t know.
> >> >>>
> >> >>> Harbs
> >> >>>
> >> >>>> On Oct 26, 2017, at 9:56 AM, Alex Harui <ah...@adobe.com.INVALID>
> >> >>> wrote:
> >> >>>>
> >> >>>> I'm still confused about something.
> >> >>>>
> >> >>>> Can someone explain how creativity and licensing are
> >>interconnected?
> >> >>> I'm not familiar with WP themes, but I think they are templates with
> >> >>> placeholders for particular aspects of a web page/blog. I've been
> >>told
> >> >>> that this Royale site prototype is based on the Movedo theme. When
> >>I
> >> >>> searched for it on the internet I ended up here:
> >> >>> https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fgreatives
> >> >>> .eu%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b344
> >> >>> 38794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> VI0EOLywsaxbKgmhAe
> >> >>> F08cdZNQjcgtIjyFvJ2R33hlo%3D&reserved=0
> >> >>> themeforest/themeswitcher/?product=movedo#movedo
> >> >>>>
> >> >>>> It doesn't look at all like the prototype at
> >> >>>
> >> >>> https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Froyale.co
> >> >>> deoscopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b
> >> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=3GHfDzdFp6B
> >> >>> 4RQMLuP00jKAHmwQ1QMubUd4dgz3FdTA%3D&reserved=0. Maybe the menu bar
> >> >>> along the top?
> >> >>>>
> >> >>>> So what did we license from greatives? Can Carlos or someone else
> >> >>> try
> >> >>> to reproduce the prototype without looking at the current CSS and
> >>maybe
> >> >>> use
> >> >>> AL licensed fonts or something like that?
> >> >>>>
> >> >>>> Thanks,
> >> >>>> -Alex
> >> >>>>
> >> >>>> From: Dave Fisher
> >> >>> <da...@comcast.net>>
> >> >>>> Reply-To: <de...@royale.apache.org>>
> >> >>>> Date: Tuesday, October 24, 2017 at 11:06 AM
> >> >>>> To: <de...@royale.apache.org>>
> >> >>>> Subject: Re: Apache Royale static web site
> >> >>>>
> >> >>>> Hi Alex,
> >> >>>>
> >> >>>> We will need to ask Carlos to list out all of the themes he uses
> >>and
> >> >>> then we will need to track things down and ask questions.
> >> >>>>
> >> >>>> Here is the site for what looks like the main theme:
> >> >>>
> >> >>> https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Fgreative
> >> >>> s.ticksy.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b
> >> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=KBxlYi2QO
> >> >>> PDqNGhTsU6GJMhdUggdHVZjiYetcIcE8vE%3D&reserved=0
> >> >>>>
> >> >>>> It is the Move Do theme.
> >> >>>>
> >> >>>> Regards,
> >> >>>> Dave
> >> >>>>
> >> >>>> On Oct 24, 2017, at 10:56 AM, Alex Harui <aharui@adobe.com.INVALID
> <
> >> >>> mailto:aharui@adobe.com.INVALID>> wrote:
> >> >>>>
> >> >>>> Hi Dave,
> >> >>>>
> >> >>>> I'm still wondering, even if we can see and reuse the CSS/JS/HTML,
> >>do
> >> >>> we
> >> >>> have the rights to replicate use of that look-and-feel elsewhere? I
> >> >>> don't
> >> >>> understand who owns the creative content.
> >> >>>>
> >> >>>> Thoughts?
> >> >>>> -Alex
> >> >>>>
> >> >>>> From: Dave Fisher
> >><dave2wave@comcast.net<mailto:dave2wave@comcast.net
> >> >>>> <ma...@comcast.net>>
> >> >>>> Reply-To: <dev@royale.apache.org<mailto:dev@royale.apache.org
> >> ><mailto:
> >> >>> dev@royale.apache.org>>
> >> >>>> Date: Tuesday, October 24, 2017 at 10:50 AM
> >> >>>> To: <de...@royale.apache.org><mailto:
> >> >>> dev@royale.apache.org>>
> >> >>>> Subject: Re: Apache Royale static web site
> >> >>>>
> >> >>>> Hi Alex,
> >> >>>>
> >> >>>> On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID
> <
> >> >>> mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>>
> >> >>> wrote:
> >> >>>>
> >> >>>> There is something I don't think I understand. AIUI, at some
> >>point,
> >> >>> we
> >> >>>> will want the Apache Royale site to include actual Royale
> >> >>> applications,
> >> >>>> right? And I would think we would want the styling of those
> >> >>> applications
> >> >>>> to be consistent with the rest of the site. So I'm not clear how
> >>we
> >> >>> will
> >> >>>> be able to implement the styling/theme of these Royale applications
> >> >>> if we
> >> >>>> don't have rights to the styling. I don't understand how WP themes
> >> >>> and
> >> >>>> commercial licensing works if we want to replicate that user
> >> >>> experience
> >> >>>> outside of WP.
> >> >>>>
> >> >>>> We need to examine the static export of the CSS and HTML.
> >> >>>>
> >> >>>>
> >> >>>> If we can use those visuals outside of WP, then why must we
> >>continue
> >> >>> to
> >> >>>> use WP to generate the site? I would hope the theme would be
> >> >>> implemented
> >> >>>> as CSS and some templates we could use without WP.
> >> >>>>
> >> >>>> We should be able to adapt. Site building in the CMS can get
> >>complex
> >> >>> if
> >> >>> needed. For
> >> >>>
> >>OpenOffice.org<https://na01.safelinks.protection.outlook.
> com/?url=https%3
> >>A%2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f49
> >>2c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636446392
> >>882621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
> S9p2zHjJMq%2FnM%3D&reserved
> >>=0.
> >> com/?url=http%3A
> >> >>> %2F%2FOpenOffice.org&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7
> >> >>>
> >>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> m3Mv
> >> >>> XfpJIZbB4u1Zhr0AB%2B%2BVI5uPKwu7N33MkPuovjs%3D&reserved=0><
> >>
> >>https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fna01.s&d
> >>ata=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
> 4cfc%7Cfa7b1b5a7b34438794aed
> >>2c178decee1%7C0%7C0%7C636446392882621163&sdata=
> hxky0LHm5GqF8zMjFHm3bXfugJ
> >>xCS6qWPoG%2FbWItNgQ%3D&reserved=0
> >> >>> afelinks.protection.outlook.com/?url=http%3A%2F%
> >> 2FOpenOffice.org&data=02%
> >> >>> 7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
> >> 7Cfa7b1b5a7b34438794aed2c178de
> >> >>> cee1%7C0%7C0%7C636446023931803217&sdata=m3MvXfpJIZbB4u1Zhr0AB%2B%
> >> 2BVI5uPK
> >> >>> wu7N33MkPuovjs%3D&reserved=0>
> >> >>> we use the legacy html pulling out the title and content body and
> >>place
> >> >>> it
> >> >>> within a markdown template.
> >> >>>>
> >> >>>>
> >> >>>> Also, if someone wants to patch the site, they can't just offer a
> >> >>> patch
> >> >>> of
> >> >>>> the HTML right? They would need to figure out where in WP it comes
> >> >>> from?
> >> >>>> Is there a patch process for WP content?
> >> >>>>
> >> >>>> Possibly.
> >> >>>>
> >> >>>>
> >> >>>> Sorry if there is some basic thing I am missing.
> >> >>>>
> >> >>>> It will get complex first as we figure out how to embed and then it
> >> >>> will
> >> >>> get simplified as we find the best way.
> >> >>>>
> >> >>>> Regards,
> >> >>>> Dave
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> Thanks,
> >> >>>> -Alex
> >> >>>>
> >> >>>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
> >> >>> carlos.rovira@gmail.com><ma...@gmail.com> on behalf
> >>of
> >> >>> Carlos
> >> >>>> Rovira"
> >> >>> <ca...@gmail.com><mailto:
> >> >>> carlos.rovira@gmail.com> on behalf of
> >> >>>> carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
> >> >>>> <ma...@codeoscopic.com>> wrote:
> >> >>>>
> >> >>>> Thanks Dave,
> >> >>>>
> >> >>>> I'll write an email to trademarks to start with the process. I
> >>think
> >> >>> is
> >> >>>> better to migrate to
> >> >>> WP.com<https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2FWP
> >> >>> .com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b34438
> >> >>> 794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> pPTlG8DjwzO%2FN%2B0r
> >> >>> euRRSegBNuKdtuonR2fro55wfgs%3D&reserved=0><https://na01.
> >> safelinks.protect
> >> >>> ion.outlook.com/?url=http%3A%2F%2FWP.com&data=02%7C01%7C%
> >> 7Cdb97bd994ab24e
> >> >>> e2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178de
> >> cee1%7C0%7C0%7C636446023
> >> >>> 931803217&sdata=pPTlG8DjwzO%2FN%2B0reuRRSegBNuKdtuonR2fro55wfg
> >> s%3D&reserv
> >> >>> ed=0> before
> >> >>> continue working on content so we can
> >> >>>> detect whatever issue we could get.
> >> >>>>
> >> >>>> Thanks!
> >> >>>>
> >> >>>> Carlos
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> 2017-10-24 18:56 GMT+02:00 Dave Fisher
> >><dave2wave@comcast.net<mailto:
> >> >>> dave2wave@comcast.net><ma...@comcast.net>>:
> >> >>>>
> >> >>>> Hi Carlos,
> >> >>>>
> >> >>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira
> >><carlosrovira@apache.org<
> >> >>> mailto:carlosrovira@apache.org><ma...@apache.org>>
> >> >>>> wrote:
> >> >>>>
> >> >>>> Hi,
> >> >>>>
> >> >>>> just let you know that I tried to create an static version of the
> >> >>>> preview
> >> >>>> site with success. I use this plugin :
> >> >>>>
> >> >>>> https://na01.safelinks.protection.outlook.com/?url=
> >> >>> https%3A%2F%2Fwordpres
> >> >>>>
> >> >>> s.org<https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fs.o
> >> >>> rg%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b3443
> >> >>> 8794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> 6zrqW3l9%2BJqeOxjih
> >> >>> uPWtMuguPsUDWnbqhyRxVXiTfI%3D&reserved=0>%2Fplugins%
> >> 2Fsimply-static%2F&da
> >> >>> ta=02%7C01%7C%
> >> >>> 7Cb448363ee5984b3b3e0f
> >> >>>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
> >> >>> cee1%7C0%7C0%7C636444624020033
> >> >>>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpn
> rieARat1lz2bk%3D&reserved=0
> >> >>>>
> >> >>>> and we can generate all static content with relative or absolute
> >>urls.
> >> >>>> The
> >> >>>> final preview site in static is 134mb
> >> >>>>
> >> >>>> Another thing I was searching was to use a WP to Jekyll exporter
> >>but
> >> >>>> this
> >> >>>> is not what I wanted since it seems Jekyll is all about markdown
> >>and
> >> >>>> we
> >> >>>> want a full html site with all the eye candy JS+CSS resources. In
> >>the
> >> >>>> end,
> >> >>>> and thinking more about it, is not what we want since although the
> >> >>>> site
> >> >>>> would be exported ok, we don't want to upload it to the GitHub
> >>pages
> >> >>>> like
> >> >>>> we discusses in the other thread due to expose part of the code of
> >>a
> >> >>>> commercial wp theme.
> >> >>>>
> >> >>>> So, the workflow we can use is: Use the WP backend to enter new
> >> >>>> content
> >> >>>> and
> >> >>>> modify existing want with ease (this is important is we want people
> >> >>>> contributing here). Next, with all changes done, generate a static
> >> >>>> version
> >> >>>> and replace the entire site with a fresh generated static site at
> >> >>>>
> >> >>>
> >>royale.apache.org<https://na01.safelinks.protection.
> outlook.com/?url=http
> >>s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%
> 7Cf48589d8bd1f492c5fa
> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63644639288262
> >>1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
> >> outlook.com/?url=http
> >> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
> >> 7Cdb97bd994ab24ee2f91c08d51
> >> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&s
> >> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&
> reserved=0>.
> >> and
> >> >>> as well route the
> >> >>> more friendly domain to this
> >> >>>> if
> >> >>>> board is ok with that.
> >> >>>>
> >> >>>> Yes! External domain
> >> >>>
> >>royalysdk.org<https://na01.safelinks.protection.outlook.
> com/?url=https%3A
> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f492
> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364463928
> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
> S9p2zHjJMq%2FnM%3D&reserved=
> >>0.
> >> com/?url=http%3A%
> >> >>> 2F%2Froyalysdk.org%2F&data=02%7C01%7C%
> 7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%
> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&sdata=Dmo
> >> >>> CAUlAVHkkOp0uFdDH0%2FoUUU9qwdl00M8fWRe888Q%3D&reserved=0> is
> >> redirected
> >> >>> to
> >> >>>
> >>royale.apache.org<https://na01.safelinks.protection.
> outlook.com/?url=http
> >>s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%
> 7Cf48589d8bd1f492c5fa
> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63644639288262
> >>1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
> >> outlook.com/?url=http
> >> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
> >> 7Cdb97bd994ab24ee2f91c08d51
> >> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&s
> >> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>
> >>as
> >> >>>> discussed.
> >> >>>>
> >> >>>>
> >> >>>> We can check with apache board or trademarks what they propose
> >>about
> >> >>>> to
> >> >>>> create a
> >> >>>
> >>Wordpress.com<https://na01.safelinks.protection.outlook.
> com/?url=https%3A
> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f492
> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364463928
> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
> S9p2zHjJMq%2FnM%3D&reserved=
> >>0.
> >> com/?url=http%3A%
> >> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%
> 7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%
> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&sdata=%2B
> >> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
> >>account
> >> >>> managed by Apache
> >> >>> and migrate from my
> >> >>>> server
> >> >>>> to that account, and all this stuff from there, since if I remember
> >> >>>> some
> >> >>>> people said that would be more ok with Apache.I'd end removing my
> >>temp
> >> >>>> subdomain after this.
> >> >>>>
> >> >>>> The advantage of using the
> >> >>>
> >>Wordpress.com<https://na01.safelinks.protection.outlook.
> com/?url=https%3A
> >>%2F%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f492
> >>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364463928
> >>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COr
> S9p2zHjJMq%2FnM%3D&reserved=
> >>0.
> >> com/?url=http%3A%
> >> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%
> 7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%
> >> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> >> 7C636446023931803217&sdata=%2B
> >> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
> >> >>> location is twofold:
> >> >>>>
> >> >>>> (1) Wordpress keeps security up to date.
> >> >>>> (2) If something happens to you or your company then we have better
> >> >>>> access.
> >> >>>>
> >> >>>> I suspect though that with the status export method this will not
> >>be
> >> >>> as
> >> >>>> great a concern.
> >> >>>>
> >> >>>>
> >> >>>> What do you think? Can I move this with the people we were talking
> >> >>>> some
> >> >>>> weeks ago?
> >> >>>>
> >> >>>> Either you or I can email Trademarks with the plan.
> >> >>>>
> >> >>>> We can then discuss the redirection with Infrastructure and get the
> >> >>> site
> >> >>>> checked in.
> >> >>>>
> >> >>>> Regards,
> >> >>>> Dave
> >> >>>>
> >> >>>>
> >> >>>> Let me know in order to start making the next steps
> >> >>>>
> >> >>>> Thanks
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>> Carlos Rovira
> >> >>>>
> >> >>>> https://na01.safelinks.protection.outlook.com/?url=
> >> >>> http%3A%2F%2Fabout.me%
> >> >>>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> >> >>> 73f8%7Cfa7b1
> >> >>>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >> >>> sdata=1q5B1u1lLR
> >> >>>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>>
> >> >>>> --
> >> >>>>
> >> >>>> <https://na01.safelinks.protection.outlook.com/?url=
> >> >>> http%3A%2F%2Fwww.codeo
> >> >>>>
> >> >>>
> >>scopic.com<https://na01.safelinks.protection.outlook.
> com/?url=https%3A%2F
> >>%2Fna01.safelinks.protection.outlook&data=02%
> 7C01%7C%7Cf48589d8bd1f492c5f
> >>aa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C6364463928826
> >>21163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0.
> >> com/?url=http%3A%2F%
> >> >>> 2Fscopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b
> >> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=oG9idkXzU
> >> >>> tg91G5vhl5P0Dn2u8gXX55UvN172PAlPXs%3D&reserved=0>&data=02%7C01%7C%
> >> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> >> >>>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >> >>> sdata=Y%2Fkytu4lJUWu5H
> >> >>>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<https://na01.safelinks.protection.outlook.
> com/?url=https%3A%2F%
> >>2Fna01.safelinks.protection.outlook&data=02%7C01%7C%
> 7Cf48589d8bd1f492c5fa
> >>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C63644639288262
> >>1163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0.
> >> com/?url=http%3A%2F%2
> >> >>> Fcopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b
> >> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=ZPPDqp5SNhK
> >> >>> C2rzYxfzkSV7f8lDtLmaRyyaMAlvtRcw%3D&reserved=0>&data=02%7C01%7C%
> >> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> >> >>>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
> >> >>> 2Fkytu4lJUWu5Hz
> >> >>>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
> >> >>>>
> >> >>>>
> >> >>>> Conocenos Avant2 en 1 minuto!
> >> >>>> <https://na01.safelinks.protection.outlook.com/?url=
> >> >>> https%3A%2F%2Favant2.e
> >> >>>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> >> >>> 73f8%7Cfa7b1b5a
> >> >>>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >> >>> sdata=SJmmZQTVSb0tmX
> >> >>>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> >> >>>> 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.
> >> >>>>
> >> >>>>
> >> >>>
> >> >>>
> >> >>
> >> >>
> >> >> --
> >> >>
> >> >> <https://na01.safelinks.protection.outlook.com/?url=
> >> http%3A%2F%2Fwww.codeo
> >> >> scopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b
> >> >> 34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=ZPowinnGs4jxxXQ4
> >> >> hULLfJLfWsGXx9zNLKnS9W7JoNY%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%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a7b3
> >> >> 4438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> >> ZPowinnGs4jxxXQ4h
> >> >> ULLfJLfWsGXx9zNLKnS9W7JoNY%3D&reserved=0
> >> >>
> >> >>
> >> >> Conocenos Avant2 en 1 minuto!
> >> >> <https://na01.safelinks.protection.outlook.com/?url=
> >> https%3A%2F%2Favant2.e
> >> >> s%2F%23video&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> >> 6496%7Cfa7b1b5a
> >> >> 7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> >> sdata=ZiX3l%2FtQwsOG
> >> >> QN%2BibIJ5pxYpI5UboaH26BzM%2F9AtaLg%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
> >> >> 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.
> >> >
> >>
> >>
> >
> >
> >--
> >
> ><https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo
> >scopic.com&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
> 4cfc%7Cfa7b1b5a7b
> >34438794aed2c178decee1%7C0%7C0%7C636446392882621163&
> sdata=lKI9XjSOeXi%2Brk
> >UN0qJG%2F57in9KVLsXMs2yU56LYHmk%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%7Cf48589d8bd1f492c5faa08d51c9f
> 4cfc%7Cfa7b1b5a7b3
> >4438794aed2c178decee1%7C0%7C0%7C636446392882621163&
> sdata=lKI9XjSOeXi%2BrkU
> >N0qJG%2F57in9KVLsXMs2yU56LYHmk%3D&reserved=0
> >
> >
> >Conocenos Avant2 en 1 minuto!
> ><https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant2.e
> >s%2F%23video&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f
> 4cfc%7Cfa7b1b5a
> >7b34438794aed2c178decee1%7C0%7C0%7C636446392882621163&
> sdata=H2q8lqkz3DT6UD
> >tSbrEjUPjektN2ii9zreOhSmlCdB0%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
> >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.
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi Carlos,
I have a WP-based blog, so I understand how easy it is to write some text
and have it look nice. But I'm still confused about who owns what. Does
Envato/Greatives own the look and feel of royale.codeoscopic.com or do
you? I understand that Royale is tuned more towards web applications but
to my mind, I see more and more web sites being about interactivity rather
than just displaying text and images. Even blog commenting and upvoting
looks like an app to me.
I would like to some day use Royale to create the page you've prototyped
at royale.codeoscopic.com and maybe enhance it by having a Royale news
feed or some other backend connectivity for some of the content. But can
we replicate the look and feel of what you have prototyped and put that
under ALv2? I think we have to find a way to make that possible. The
theme or CSS that we use to replicate your prototype may not be our
default theme/CSS, but it should still be a valid theme or CSS file and
components.
That's why I'm concerned that working from Movedo is going to leak into
other things we want to do. But if we start from scratch and try to
replicate the visuals you've chosen, I would hope we can get something
that looks similar quickly and then invite more folks to help tune it.
And as Harbs says, I'm not asking you to do that work, someone else can.
What you've done already is significant and very helpful and I think you
made the right choice of using your WP skills to create it quickly.
If we were to reproduce your prototype in Royale, I would want to create
re-usable components such as:
MenuBar
SearchShareUserProfileMoreMenuBar
TopBar (that holds all of the icon, title, MenuBar and
SearchShareProfileButtonBar)
IconTitleTextPanel
And more...
Then someone else can come along and assemble their own site from these
pieces.
Back in the Adobe days, some folks actually took the FlexStore example,
modified it slightly and deployed it in production for their own products.
We didn't care that they pretty much used the same look-and-feel. I think
we want to make the same sort of thing possible for Royale.
Thoughts?
-Alex
On 10/26/17, 11:27 AM, "carlos.rovira@gmail.com on behalf of Carlos
Rovira" <carlos.rovira@gmail.com on behalf of
carlos.rovira@codeoscopic.com> wrote:
>Hi,
>
>in order to help you, Alex and Harbs (others could join as well) to
>understand all the picture, I could create an account for you in
>royale.codeoscopic.com
>
>In this way you could see point 1 of Alex's list (how integrate some new
>content in website). and most important, you will see the visual tool to
>edit and mount a new content in pages or posts.
>
>This last thing is one of the main reasons I want to use WP in the day by
>day. If you want to create some content, doing manually is a nightmare.
>
>I'll send you admin users to your accounts and you're free to enter and
>watch, (but please don't modify anything to avoid break the actual site)
>
>In order to create some default theme (point 2), again here I think we
>talking about different things. I think we don't want to base our default
>theme for UI controls in apache royale in what I did in the theme. That
>would be a mistake in since movedo principles are based on website look
>and
>usability. Fonts and spacing is huge to express content in a modern
>website. To make a comparative, if you take MDL and movedo side by side,
>the first is for applications while the second is to present text and
>images in a website.
>
>My plan, as I mention before, is to start creating a UI component styles
>that could be programed in a theme. I have in mind to make two of them: a
>wireframe theme and a full default theme. The first one could have the
>same
>sizes and fonts but with only outlines and black and white (like the flex
>wireframe to avoid style and application when you're prototyping.
>
>Regarding time to replicate movedo theme with our own styling, I'm sure is
>not a two day task, but more, there's so much there, and only to get
>something that only will be a shadow of the original.
>
>As Harbs mention there's people making styling, but as they are not
>commenting in this list we don't know anything about if they are doing
>something this days, or maybe they couldn't use that time to work on this.
>
>For last (point 3), I did wordpress themes some years ago, and is a huge
>task to do, in time and effort. And with time you can get something of
>quality, but again, why we want to spend our time in something we already
>have? I don't find anything here, since we are not here to create WP
>themes, I prefer to use that time to create an Apache Royale UI theme and
>even help to program it, because that is what we really need to make more
>people join us.
>
>
>
>
>2017-10-26 19:37 GMT+02:00 Harbs <ha...@gmail.com>:
>
>> Another point to consider:
>>
>> We’ve had some folks offer to help with skinning Royale components. It
>> should be pretty straightforward to give them (and anyone else who
>>wants to
>> help) committer rights to the website repo. If we have more people
>>working
>> on it, the task of recreating the appearance achieved through the Movedo
>> CSS should be al lot easier.
>>
>> I don’t feel comfortable asking Carlos to do more work than he’s
>>offered,
>> but with help from others, it might be a lot easier.
>>
>> Harbs
>>
>> > On Oct 26, 2017, at 7:41 PM, Alex Harui <ah...@adobe.com.INVALID>
>> wrote:
>> >
>> > Hi Carlos,
>> >
>> > I don't know if the "Apache Way" is a problem here. So far I think we
>> > have heard opinions and concerns but AFAICT no hard policy has been
>> quoted
>> > that prevents having royale.a.o point to WP.com.
>> >
>> > But I am still unclear if hosting our site on WP is really the best
>> > strategy. I have the following concerns:
>> >
>> > 1) How would be include a Royale application in our site?
>> > 2) How would we style the Royale application to look consistent with
>>the
>> > rest of the site?
>> > 3) Could we ever create a theme based on this styling?
>> >
>> > I didn't, and still don't, understand how WP themes and their
>>licensing
>> > work, otherwise I think I would have asked more questions up front. I
>> > thought you would own copyright on the results, just like using Adobe
>> > Dreamweaver and Adobe Illustrator to build out a site doesn't put the
>> > content under Adobe licensing.
>> >
>> > That doesn't appear to be the case here, but I think we do need to
>> > consider the 3 concerns I've listed.
>> >
>> > Both you and Harbs claim that replicating your prototype's look and
>>feel
>> > will be a lot of work, but how much work are really talking about,
>>and do
>> > we have to exactly replicate it (and should we)? If you think about
>>how
>> > Royale components are created, they work with some default CSS. I
>>think
>> > if we implement themes, we'll end up with components with particular
>> > "sub-DOMs" and CSS that dictates the visuals on those sub-DOMs.
>>AIUI, we
>> > are expecting artwork from some designers about other default looks
>>for
>> > Royale components. Won't we be facing a similar challenge of trying
>>to
>> > figure out the CSS that best matches what we see on a screen?
>> >
>> > So, I think it is great that WP and MoveDo helped you create this
>> > fantastic looking prototype. But, IMO, one direction we can go from
>>here
>> > is to try to replicate the visuals you created in CSS in a way that
>>can
>> be
>> > re-used via the Apache Way. I think we'd learn about themes as we
>>try to
>> > do that. Could we get most of the way there in a couple of days?
>>Then
>> > others can offer fine-tuning via patches.
>> >
>> > And yes, WP is tuned towards templated content in a consistent way,
>>but
>> it
>> > would be interesting to build Royale components that do something
>> similar.
>> >
>> > Thoughts?
>> > -Alex
>> >
>> > On 10/26/17, 1:12 AM, "carlos.rovira@gmail.com on behalf of Carlos
>> Rovira"
>> > <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
>> wrote:
>> >
>> >> Harbs is right,
>> >>
>> >> to get something that looks cool and consistent is difficult and for
>> this
>> >> reason I use wordpress+theme (in this case movedo). Is the same
>>thing as
>> >> why people use flex or royale. Is the way to start from a point where
>> you
>> >> are more efficient and maintenance can be assumed.
>> >>
>> >> Alex, you see lots of difference since I customized via movedo
>>interface
>> >> but as well did some tweaks in custom css (for example the footer
>>column
>> >> menus)
>> >>
>> >> So could we rework the site without wp and movedo. Sure, as I stated
>>all
>> >> sites can be write in different ways, but the long term reason to
>>adopt
>> a
>> >> CMS like WP is to have a backend to introduce content of quality in
>>the
>> >> most easy way while preserving quality on presentation (styles,
>>fonts,
>> >> effects...)
>> >>
>> >> I think we are in a situation where "the Apache way" fails completely
>> >> since
>> >> we should be able to make this quick and easy and concentrate in our
>> >> Royale
>> >> code, that is why we are here, and why I tried to go this path: to
>>get
>> >> something that looks good and professional but to spend very few time
>> for
>> >> our part.
>> >>
>> >> I'm very pragmatic, and like to go to the point. All Apache rules
>>should
>> >> be
>> >> focused in protect the code we release, and we should have less
>>trouble
>> >> with tools like WP, Jira, Nexus, and the rest. In fact Apache is
>>using
>> >> those tools all along the way, why is so hard to do this?
>> >>
>> >> We only need:
>> >>
>> >> * Some host for a Wordpress instance: this could be the current
>> >> Codeoscopic
>> >> subdomain or whatever people like. I'd be more happy if the wp
>>instance
>> is
>> >> in some server that could be controlled and maintained by ASF. I
>>don't
>> >> know
>> >> if this could be WP.com or some ASF's virtual machine that could host
>> >> that.
>> >>
>> >> * The Movedo theme: I write to Dimitri, from greatives. He is very
>> >> supportive and very like the idea, but is not in their hands. He
>>point
>> me
>> >> to talk with envato, and I write to them, but still doesn't have a
>> >> response. My thinking here is that we really don't need nothing of
>>this.
>> >> Envato could donate a license but is only 59$, so is something
>> affordable
>> >> by a simple donation.
>> >>
>> >> * Finaly to generate an static site from WP. This is as well not
>>needed,
>> >> but we can do it. People use to generate wp static version in order
>>to
>> >> protect their sites from hacking. That's the only relevant point to
>>do
>> >> this. So for me is something we can do if the rest of community wants
>> it.
>> >> Is very easy to do.
>> >>
>> >>
>> >> Additionaly: As we are not uploading any website code to any ASF
>>repo,
>> >> since as I said, it would be like to upload the JIRA source code to
>>our
>> >> repos, and that doesn't give us anything (we're here to release only
>> >> apache
>> >> royale code). we can :
>> >>
>> >> 1.- Use the royale.codeoscopic.com wp instance as the tool for us to
>> >> modify
>> >> the site (people in our community will have user/pass in this wp
>> instance
>> >> to create post and pages)
>> >> (in this way is similar to the server Alex had on his own to make
>>some
>> >> apache flex task, correct me if I'm wrong)
>> >> Again, it can be royale.codeoscopic.com or other hosting ASF wants.
>> >>
>> >> 2.- Each time something changes: generate static site and deploy to
>> >> royale.apache.org
>> >> (in this case the set of static generated html/js/css could not be
>> >> uploaded
>> >> to any ASF repo since we don't want to release the website code, that
>> must
>> >> be served in the same way ASF serves JIRA, or whatever other
>>commercial
>> >> tool
>> >>
>> >> Hosting a generated site with a movedo commercial theme needs of a
>>59$
>> >> license that could be donated by envato or donated for other
>> >> person/company
>> >> (for example Codeoscopic)
>> >>
>> >> For me this is quick and easy and I think we're not making something
>> wrong
>> >> in legal terms
>> >>
>> >> Carlos
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >>
>> >> 2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
>> >>
>> >>> It’s using greatives’ CSS and JS files for styling, layout and
>>effects.
>> >>>
>> >>> Generally, these themes have a lot of flexibility to change the
>>look of
>> >>> a
>> >>> site without messing with CSS and JS.
>> >>>
>> >>> Can we re-write the CSS and JS to do the same kind of thing?
>>Probably.
>> >>> But
>> >>> it would be a considerable amount of work.
>> >>>
>> >>> What’s included in the license? I’m really not sure.
>> >>>
>> >>> It gives rights to us the theme in WordPress. Does that allow
>> >>> repurposing
>> >>> the CSS and JS files for use elsewhere? I don’t know.
>> >>>
>> >>> Harbs
>> >>>
>> >>>> On Oct 26, 2017, at 9:56 AM, Alex Harui <ah...@adobe.com.INVALID>
>> >>> wrote:
>> >>>>
>> >>>> I'm still confused about something.
>> >>>>
>> >>>> Can someone explain how creativity and licensing are
>>interconnected?
>> >>> I'm not familiar with WP themes, but I think they are templates with
>> >>> placeholders for particular aspects of a web page/blog. I've been
>>told
>> >>> that this Royale site prototype is based on the Movedo theme. When
>>I
>> >>> searched for it on the internet I ended up here:
>> >>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fgreatives
>> >>> .eu%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b1b5a7b344
>> >>> 38794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> VI0EOLywsaxbKgmhAe
>> >>> F08cdZNQjcgtIjyFvJ2R33hlo%3D&reserved=0
>> >>> themeforest/themeswitcher/?product=movedo#movedo
>> >>>>
>> >>>> It doesn't look at all like the prototype at
>> >>>
>> >>> https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Froyale.co
>> >>> deoscopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b1b
>> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> sdata=3GHfDzdFp6B
>> >>> 4RQMLuP00jKAHmwQ1QMubUd4dgz3FdTA%3D&reserved=0. Maybe the menu bar
>> >>> along the top?
>> >>>>
>> >>>> So what did we license from greatives? Can Carlos or someone else
>> >>> try
>> >>> to reproduce the prototype without looking at the current CSS and
>>maybe
>> >>> use
>> >>> AL licensed fonts or something like that?
>> >>>>
>> >>>> Thanks,
>> >>>> -Alex
>> >>>>
>> >>>> From: Dave Fisher
>> >>> <da...@comcast.net>>
>> >>>> Reply-To: <de...@royale.apache.org>>
>> >>>> Date: Tuesday, October 24, 2017 at 11:06 AM
>> >>>> To: <de...@royale.apache.org>>
>> >>>> Subject: Re: Apache Royale static web site
>> >>>>
>> >>>> Hi Alex,
>> >>>>
>> >>>> We will need to ask Carlos to list out all of the themes he uses
>>and
>> >>> then we will need to track things down and ask questions.
>> >>>>
>> >>>> Here is the site for what looks like the main theme:
>> >>>
>> >>> https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fgreative
>> >>> s.ticksy.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b
>> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> sdata=KBxlYi2QO
>> >>> PDqNGhTsU6GJMhdUggdHVZjiYetcIcE8vE%3D&reserved=0
>> >>>>
>> >>>> It is the Move Do theme.
>> >>>>
>> >>>> Regards,
>> >>>> Dave
>> >>>>
>> >>>> On Oct 24, 2017, at 10:56 AM, Alex Harui <aharui@adobe.com.INVALID<
>> >>> mailto:aharui@adobe.com.INVALID>> wrote:
>> >>>>
>> >>>> Hi Dave,
>> >>>>
>> >>>> I'm still wondering, even if we can see and reuse the CSS/JS/HTML,
>>do
>> >>> we
>> >>> have the rights to replicate use of that look-and-feel elsewhere? I
>> >>> don't
>> >>> understand who owns the creative content.
>> >>>>
>> >>>> Thoughts?
>> >>>> -Alex
>> >>>>
>> >>>> From: Dave Fisher
>><dave2wave@comcast.net<mailto:dave2wave@comcast.net
>> >>>> <ma...@comcast.net>>
>> >>>> Reply-To: <dev@royale.apache.org<mailto:dev@royale.apache.org
>> ><mailto:
>> >>> dev@royale.apache.org>>
>> >>>> Date: Tuesday, October 24, 2017 at 10:50 AM
>> >>>> To: <de...@royale.apache.org><mailto:
>> >>> dev@royale.apache.org>>
>> >>>> Subject: Re: Apache Royale static web site
>> >>>>
>> >>>> Hi Alex,
>> >>>>
>> >>>> On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID<
>> >>> mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>>
>> >>> wrote:
>> >>>>
>> >>>> There is something I don't think I understand. AIUI, at some
>>point,
>> >>> we
>> >>>> will want the Apache Royale site to include actual Royale
>> >>> applications,
>> >>>> right? And I would think we would want the styling of those
>> >>> applications
>> >>>> to be consistent with the rest of the site. So I'm not clear how
>>we
>> >>> will
>> >>>> be able to implement the styling/theme of these Royale applications
>> >>> if we
>> >>>> don't have rights to the styling. I don't understand how WP themes
>> >>> and
>> >>>> commercial licensing works if we want to replicate that user
>> >>> experience
>> >>>> outside of WP.
>> >>>>
>> >>>> We need to examine the static export of the CSS and HTML.
>> >>>>
>> >>>>
>> >>>> If we can use those visuals outside of WP, then why must we
>>continue
>> >>> to
>> >>>> use WP to generate the site? I would hope the theme would be
>> >>> implemented
>> >>>> as CSS and some templates we could use without WP.
>> >>>>
>> >>>> We should be able to adapt. Site building in the CMS can get
>>complex
>> >>> if
>> >>> needed. For
>> >>>
>>OpenOffice.org<https://na01.safelinks.protection.outlook.com/?url=https%3
>>A%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7Cf48589d8bd1f49
>>2c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446392
>>882621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved
>>=0.
>> com/?url=http%3A
>> >>> %2F%2FOpenOffice.org&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7
>> >>>
>>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> m3Mv
>> >>> XfpJIZbB4u1Zhr0AB%2B%2BVI5uPKwu7N33MkPuovjs%3D&reserved=0><
>>
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fna01.s&d
>>ata=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed
>>2c178decee1%7C0%7C0%7C636446392882621163&sdata=hxky0LHm5GqF8zMjFHm3bXfugJ
>>xCS6qWPoG%2FbWItNgQ%3D&reserved=0
>> >>> afelinks.protection.outlook.com/?url=http%3A%2F%
>> 2FOpenOffice.org&data=02%
>> >>> 7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>> 7Cfa7b1b5a7b34438794aed2c178de
>> >>> cee1%7C0%7C0%7C636446023931803217&sdata=m3MvXfpJIZbB4u1Zhr0AB%2B%
>> 2BVI5uPK
>> >>> wu7N33MkPuovjs%3D&reserved=0>
>> >>> we use the legacy html pulling out the title and content body and
>>place
>> >>> it
>> >>> within a markdown template.
>> >>>>
>> >>>>
>> >>>> Also, if someone wants to patch the site, they can't just offer a
>> >>> patch
>> >>> of
>> >>>> the HTML right? They would need to figure out where in WP it comes
>> >>> from?
>> >>>> Is there a patch process for WP content?
>> >>>>
>> >>>> Possibly.
>> >>>>
>> >>>>
>> >>>> Sorry if there is some basic thing I am missing.
>> >>>>
>> >>>> It will get complex first as we figure out how to embed and then it
>> >>> will
>> >>> get simplified as we find the best way.
>> >>>>
>> >>>> Regards,
>> >>>> Dave
>> >>>>
>> >>>>
>> >>>>
>> >>>> Thanks,
>> >>>> -Alex
>> >>>>
>> >>>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
>> >>> carlos.rovira@gmail.com><ma...@gmail.com> on behalf
>>of
>> >>> Carlos
>> >>>> Rovira"
>> >>> <ca...@gmail.com><mailto:
>> >>> carlos.rovira@gmail.com> on behalf of
>> >>>> carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
>> >>>> <ma...@codeoscopic.com>> wrote:
>> >>>>
>> >>>> Thanks Dave,
>> >>>>
>> >>>> I'll write an email to trademarks to start with the process. I
>>think
>> >>> is
>> >>>> better to migrate to
>> >>> WP.com<https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2FWP
>> >>> .com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b1b5a7b34438
>> >>> 794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> pPTlG8DjwzO%2FN%2B0r
>> >>> euRRSegBNuKdtuonR2fro55wfgs%3D&reserved=0><https://na01.
>> safelinks.protect
>> >>> ion.outlook.com/?url=http%3A%2F%2FWP.com&data=02%7C01%7C%
>> 7Cdb97bd994ab24e
>> >>> e2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636446023
>> >>> 931803217&sdata=pPTlG8DjwzO%2FN%2B0reuRRSegBNuKdtuonR2fro55wfg
>> s%3D&reserv
>> >>> ed=0> before
>> >>> continue working on content so we can
>> >>>> detect whatever issue we could get.
>> >>>>
>> >>>> Thanks!
>> >>>>
>> >>>> Carlos
>> >>>>
>> >>>>
>> >>>>
>> >>>> 2017-10-24 18:56 GMT+02:00 Dave Fisher
>><dave2wave@comcast.net<mailto:
>> >>> dave2wave@comcast.net><ma...@comcast.net>>:
>> >>>>
>> >>>> Hi Carlos,
>> >>>>
>> >>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira
>><carlosrovira@apache.org<
>> >>> mailto:carlosrovira@apache.org><ma...@apache.org>>
>> >>>> wrote:
>> >>>>
>> >>>> Hi,
>> >>>>
>> >>>> just let you know that I tried to create an static version of the
>> >>>> preview
>> >>>> site with success. I use this plugin :
>> >>>>
>> >>>> https://na01.safelinks.protection.outlook.com/?url=
>> >>> https%3A%2F%2Fwordpres
>> >>>>
>> >>> s.org<https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fs.o
>> >>> rg%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b1b5a7b3443
>> >>> 8794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> 6zrqW3l9%2BJqeOxjih
>> >>> uPWtMuguPsUDWnbqhyRxVXiTfI%3D&reserved=0>%2Fplugins%
>> 2Fsimply-static%2F&da
>> >>> ta=02%7C01%7C%
>> >>> 7Cb448363ee5984b3b3e0f
>> >>>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
>> >>> cee1%7C0%7C0%7C636444624020033
>> >>>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>> >>>>
>> >>>> and we can generate all static content with relative or absolute
>>urls.
>> >>>> The
>> >>>> final preview site in static is 134mb
>> >>>>
>> >>>> Another thing I was searching was to use a WP to Jekyll exporter
>>but
>> >>>> this
>> >>>> is not what I wanted since it seems Jekyll is all about markdown
>>and
>> >>>> we
>> >>>> want a full html site with all the eye candy JS+CSS resources. In
>>the
>> >>>> end,
>> >>>> and thinking more about it, is not what we want since although the
>> >>>> site
>> >>>> would be exported ok, we don't want to upload it to the GitHub
>>pages
>> >>>> like
>> >>>> we discusses in the other thread due to expose part of the code of
>>a
>> >>>> commercial wp theme.
>> >>>>
>> >>>> So, the workflow we can use is: Use the WP backend to enter new
>> >>>> content
>> >>>> and
>> >>>> modify existing want with ease (this is important is we want people
>> >>>> contributing here). Next, with all changes done, generate a static
>> >>>> version
>> >>>> and replace the entire site with a fresh generated static site at
>> >>>>
>> >>>
>>royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=http
>>s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%7Cf48589d8bd1f492c5fa
>>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644639288262
>>1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
>> outlook.com/?url=http
>> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
>> 7Cdb97bd994ab24ee2f91c08d51
>> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636446023931803217&s
>> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>.
>> and
>> >>> as well route the
>> >>> more friendly domain to this
>> >>>> if
>> >>>> board is ok with that.
>> >>>>
>> >>>> Yes! External domain
>> >>>
>>royalysdk.org<https://na01.safelinks.protection.outlook.com/?url=https%3A
>>%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7Cf48589d8bd1f492
>>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364463928
>>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=
>>0.
>> com/?url=http%3A%
>> >>> 2F%2Froyalysdk.org%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%
>> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636446023931803217&sdata=Dmo
>> >>> CAUlAVHkkOp0uFdDH0%2FoUUU9qwdl00M8fWRe888Q%3D&reserved=0> is
>> redirected
>> >>> to
>> >>>
>>royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=http
>>s%3A%2F%2Fna01.safelinks.protection&data=02%7C01%7C%7Cf48589d8bd1f492c5fa
>>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644639288262
>>1163&sdata=sGpOejdnYm9ethgBTpcH6BOWqrk03uUUxEuLBqdARrs%3D&reserved=0.
>> outlook.com/?url=http
>> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
>> 7Cdb97bd994ab24ee2f91c08d51
>> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636446023931803217&s
>> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>
>>as
>> >>>> discussed.
>> >>>>
>> >>>>
>> >>>> We can check with apache board or trademarks what they propose
>>about
>> >>>> to
>> >>>> create a
>> >>>
>>Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=https%3A
>>%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7Cf48589d8bd1f492
>>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364463928
>>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=
>>0.
>> com/?url=http%3A%
>> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%
>> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636446023931803217&sdata=%2B
>> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
>>account
>> >>> managed by Apache
>> >>> and migrate from my
>> >>>> server
>> >>>> to that account, and all this stuff from there, since if I remember
>> >>>> some
>> >>>> people said that would be more ok with Apache.I'd end removing my
>>temp
>> >>>> subdomain after this.
>> >>>>
>> >>>> The advantage of using the
>> >>>
>>Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=https%3A
>>%2F%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7Cf48589d8bd1f492
>>c5faa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364463928
>>82621163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=
>>0.
>> com/?url=http%3A%
>> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%
>> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
>> 7C636446023931803217&sdata=%2B
>> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
>> >>> location is twofold:
>> >>>>
>> >>>> (1) Wordpress keeps security up to date.
>> >>>> (2) If something happens to you or your company then we have better
>> >>>> access.
>> >>>>
>> >>>> I suspect though that with the status export method this will not
>>be
>> >>> as
>> >>>> great a concern.
>> >>>>
>> >>>>
>> >>>> What do you think? Can I move this with the people we were talking
>> >>>> some
>> >>>> weeks ago?
>> >>>>
>> >>>> Either you or I can email Trademarks with the plan.
>> >>>>
>> >>>> We can then discuss the redirection with Infrastructure and get the
>> >>> site
>> >>>> checked in.
>> >>>>
>> >>>> Regards,
>> >>>> Dave
>> >>>>
>> >>>>
>> >>>> Let me know in order to start making the next steps
>> >>>>
>> >>>> Thanks
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Carlos Rovira
>> >>>>
>> >>>> https://na01.safelinks.protection.outlook.com/?url=
>> >>> http%3A%2F%2Fabout.me%
>> >>>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>> >>> 73f8%7Cfa7b1
>> >>>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> >>> sdata=1q5B1u1lLR
>> >>>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>> >>>>
>> >>>>
>> >>>>
>> >>>>
>> >>>> --
>> >>>>
>> >>>> <https://na01.safelinks.protection.outlook.com/?url=
>> >>> http%3A%2F%2Fwww.codeo
>> >>>>
>> >>>
>>scopic.com<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F
>>%2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7Cf48589d8bd1f492c5f
>>aa08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C6364463928826
>>21163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0.
>> com/?url=http%3A%2F%
>> >>> 2Fscopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b
>> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> sdata=oG9idkXzU
>> >>> tg91G5vhl5P0Dn2u8gXX55UvN172PAlPXs%3D&reserved=0>&data=02%7C01%7C%
>> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>> >>>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> >>> sdata=Y%2Fkytu4lJUWu5H
>> >>>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%
>>2Fna01.safelinks.protection.outlook&data=02%7C01%7C%7Cf48589d8bd1f492c5fa
>>a08d51c9f4cfc%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C63644639288262
>>1163&sdata=RNMeqD3EctghlnHrEBOG3x27PD7COrS9p2zHjJMq%2FnM%3D&reserved=0.
>> com/?url=http%3A%2F%2
>> >>> Fcopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b1b
>> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> sdata=ZPPDqp5SNhK
>> >>> C2rzYxfzkSV7f8lDtLmaRyyaMAlvtRcw%3D&reserved=0>&data=02%7C01%7C%
>> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>> >>>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
>> >>> 2Fkytu4lJUWu5Hz
>> >>>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>> >>>>
>> >>>>
>> >>>> Conocenos Avant2 en 1 minuto!
>> >>>> <https://na01.safelinks.protection.outlook.com/?url=
>> >>> https%3A%2F%2Favant2.e
>> >>>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>> >>> 73f8%7Cfa7b1b5a
>> >>>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> >>> sdata=SJmmZQTVSb0tmX
>> >>>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>> >>>> 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.
>> >>>>
>> >>>>
>> >>>
>> >>>
>> >>
>> >>
>> >> --
>> >>
>> >> <https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.codeo
>> >> scopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b1b5a7b
>> >> 34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> sdata=ZPowinnGs4jxxXQ4
>> >> hULLfJLfWsGXx9zNLKnS9W7JoNY%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%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b1b5a7b3
>> >> 4438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
>> ZPowinnGs4jxxXQ4h
>> >> ULLfJLfWsGXx9zNLKnS9W7JoNY%3D&reserved=0
>> >>
>> >>
>> >> Conocenos Avant2 en 1 minuto!
>> >> <https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Favant2.e
>> >> s%2F%23video&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
>> 6496%7Cfa7b1b5a
>> >> 7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
>> sdata=ZiX3l%2FtQwsOG
>> >> QN%2BibIJ5pxYpI5UboaH26BzM%2F9AtaLg%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
>> >> 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.
>> >
>>
>>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f4cfc%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636446392882621163&sdata=lKI9XjSOeXi%2Brk
>UN0qJG%2F57in9KVLsXMs2yU56LYHmk%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%7Cf48589d8bd1f492c5faa08d51c9f4cfc%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636446392882621163&sdata=lKI9XjSOeXi%2BrkU
>N0qJG%2F57in9KVLsXMs2yU56LYHmk%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7Cf48589d8bd1f492c5faa08d51c9f4cfc%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636446392882621163&sdata=H2q8lqkz3DT6UD
>tSbrEjUPjektN2ii9zreOhSmlCdB0%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
>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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi,
in order to help you, Alex and Harbs (others could join as well) to
understand all the picture, I could create an account for you in
royale.codeoscopic.com
In this way you could see point 1 of Alex's list (how integrate some new
content in website). and most important, you will see the visual tool to
edit and mount a new content in pages or posts.
This last thing is one of the main reasons I want to use WP in the day by
day. If you want to create some content, doing manually is a nightmare.
I'll send you admin users to your accounts and you're free to enter and
watch, (but please don't modify anything to avoid break the actual site)
In order to create some default theme (point 2), again here I think we
talking about different things. I think we don't want to base our default
theme for UI controls in apache royale in what I did in the theme. That
would be a mistake in since movedo principles are based on website look and
usability. Fonts and spacing is huge to express content in a modern
website. To make a comparative, if you take MDL and movedo side by side,
the first is for applications while the second is to present text and
images in a website.
My plan, as I mention before, is to start creating a UI component styles
that could be programed in a theme. I have in mind to make two of them: a
wireframe theme and a full default theme. The first one could have the same
sizes and fonts but with only outlines and black and white (like the flex
wireframe to avoid style and application when you're prototyping.
Regarding time to replicate movedo theme with our own styling, I'm sure is
not a two day task, but more, there's so much there, and only to get
something that only will be a shadow of the original.
As Harbs mention there's people making styling, but as they are not
commenting in this list we don't know anything about if they are doing
something this days, or maybe they couldn't use that time to work on this.
For last (point 3), I did wordpress themes some years ago, and is a huge
task to do, in time and effort. And with time you can get something of
quality, but again, why we want to spend our time in something we already
have? I don't find anything here, since we are not here to create WP
themes, I prefer to use that time to create an Apache Royale UI theme and
even help to program it, because that is what we really need to make more
people join us.
2017-10-26 19:37 GMT+02:00 Harbs <ha...@gmail.com>:
> Another point to consider:
>
> We’ve had some folks offer to help with skinning Royale components. It
> should be pretty straightforward to give them (and anyone else who wants to
> help) committer rights to the website repo. If we have more people working
> on it, the task of recreating the appearance achieved through the Movedo
> CSS should be al lot easier.
>
> I don’t feel comfortable asking Carlos to do more work than he’s offered,
> but with help from others, it might be a lot easier.
>
> Harbs
>
> > On Oct 26, 2017, at 7:41 PM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > Hi Carlos,
> >
> > I don't know if the "Apache Way" is a problem here. So far I think we
> > have heard opinions and concerns but AFAICT no hard policy has been
> quoted
> > that prevents having royale.a.o point to WP.com.
> >
> > But I am still unclear if hosting our site on WP is really the best
> > strategy. I have the following concerns:
> >
> > 1) How would be include a Royale application in our site?
> > 2) How would we style the Royale application to look consistent with the
> > rest of the site?
> > 3) Could we ever create a theme based on this styling?
> >
> > I didn't, and still don't, understand how WP themes and their licensing
> > work, otherwise I think I would have asked more questions up front. I
> > thought you would own copyright on the results, just like using Adobe
> > Dreamweaver and Adobe Illustrator to build out a site doesn't put the
> > content under Adobe licensing.
> >
> > That doesn't appear to be the case here, but I think we do need to
> > consider the 3 concerns I've listed.
> >
> > Both you and Harbs claim that replicating your prototype's look and feel
> > will be a lot of work, but how much work are really talking about, and do
> > we have to exactly replicate it (and should we)? If you think about how
> > Royale components are created, they work with some default CSS. I think
> > if we implement themes, we'll end up with components with particular
> > "sub-DOMs" and CSS that dictates the visuals on those sub-DOMs. AIUI, we
> > are expecting artwork from some designers about other default looks for
> > Royale components. Won't we be facing a similar challenge of trying to
> > figure out the CSS that best matches what we see on a screen?
> >
> > So, I think it is great that WP and MoveDo helped you create this
> > fantastic looking prototype. But, IMO, one direction we can go from here
> > is to try to replicate the visuals you created in CSS in a way that can
> be
> > re-used via the Apache Way. I think we'd learn about themes as we try to
> > do that. Could we get most of the way there in a couple of days? Then
> > others can offer fine-tuning via patches.
> >
> > And yes, WP is tuned towards templated content in a consistent way, but
> it
> > would be interesting to build Royale components that do something
> similar.
> >
> > Thoughts?
> > -Alex
> >
> > On 10/26/17, 1:12 AM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira"
> > <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com>
> wrote:
> >
> >> Harbs is right,
> >>
> >> to get something that looks cool and consistent is difficult and for
> this
> >> reason I use wordpress+theme (in this case movedo). Is the same thing as
> >> why people use flex or royale. Is the way to start from a point where
> you
> >> are more efficient and maintenance can be assumed.
> >>
> >> Alex, you see lots of difference since I customized via movedo interface
> >> but as well did some tweaks in custom css (for example the footer column
> >> menus)
> >>
> >> So could we rework the site without wp and movedo. Sure, as I stated all
> >> sites can be write in different ways, but the long term reason to adopt
> a
> >> CMS like WP is to have a backend to introduce content of quality in the
> >> most easy way while preserving quality on presentation (styles, fonts,
> >> effects...)
> >>
> >> I think we are in a situation where "the Apache way" fails completely
> >> since
> >> we should be able to make this quick and easy and concentrate in our
> >> Royale
> >> code, that is why we are here, and why I tried to go this path: to get
> >> something that looks good and professional but to spend very few time
> for
> >> our part.
> >>
> >> I'm very pragmatic, and like to go to the point. All Apache rules should
> >> be
> >> focused in protect the code we release, and we should have less trouble
> >> with tools like WP, Jira, Nexus, and the rest. In fact Apache is using
> >> those tools all along the way, why is so hard to do this?
> >>
> >> We only need:
> >>
> >> * Some host for a Wordpress instance: this could be the current
> >> Codeoscopic
> >> subdomain or whatever people like. I'd be more happy if the wp instance
> is
> >> in some server that could be controlled and maintained by ASF. I don't
> >> know
> >> if this could be WP.com or some ASF's virtual machine that could host
> >> that.
> >>
> >> * The Movedo theme: I write to Dimitri, from greatives. He is very
> >> supportive and very like the idea, but is not in their hands. He point
> me
> >> to talk with envato, and I write to them, but still doesn't have a
> >> response. My thinking here is that we really don't need nothing of this.
> >> Envato could donate a license but is only 59$, so is something
> affordable
> >> by a simple donation.
> >>
> >> * Finaly to generate an static site from WP. This is as well not needed,
> >> but we can do it. People use to generate wp static version in order to
> >> protect their sites from hacking. That's the only relevant point to do
> >> this. So for me is something we can do if the rest of community wants
> it.
> >> Is very easy to do.
> >>
> >>
> >> Additionaly: As we are not uploading any website code to any ASF repo,
> >> since as I said, it would be like to upload the JIRA source code to our
> >> repos, and that doesn't give us anything (we're here to release only
> >> apache
> >> royale code). we can :
> >>
> >> 1.- Use the royale.codeoscopic.com wp instance as the tool for us to
> >> modify
> >> the site (people in our community will have user/pass in this wp
> instance
> >> to create post and pages)
> >> (in this way is similar to the server Alex had on his own to make some
> >> apache flex task, correct me if I'm wrong)
> >> Again, it can be royale.codeoscopic.com or other hosting ASF wants.
> >>
> >> 2.- Each time something changes: generate static site and deploy to
> >> royale.apache.org
> >> (in this case the set of static generated html/js/css could not be
> >> uploaded
> >> to any ASF repo since we don't want to release the website code, that
> must
> >> be served in the same way ASF serves JIRA, or whatever other commercial
> >> tool
> >>
> >> Hosting a generated site with a movedo commercial theme needs of a 59$
> >> license that could be donated by envato or donated for other
> >> person/company
> >> (for example Codeoscopic)
> >>
> >> For me this is quick and easy and I think we're not making something
> wrong
> >> in legal terms
> >>
> >> Carlos
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> 2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
> >>
> >>> It’s using greatives’ CSS and JS files for styling, layout and effects.
> >>>
> >>> Generally, these themes have a lot of flexibility to change the look of
> >>> a
> >>> site without messing with CSS and JS.
> >>>
> >>> Can we re-write the CSS and JS to do the same kind of thing? Probably.
> >>> But
> >>> it would be a considerable amount of work.
> >>>
> >>> What’s included in the license? I’m really not sure.
> >>>
> >>> It gives rights to us the theme in WordPress. Does that allow
> >>> repurposing
> >>> the CSS and JS files for use elsewhere? I don’t know.
> >>>
> >>> Harbs
> >>>
> >>>> On Oct 26, 2017, at 9:56 AM, Alex Harui <ah...@adobe.com.INVALID>
> >>> wrote:
> >>>>
> >>>> I'm still confused about something.
> >>>>
> >>>> Can someone explain how creativity and licensing are interconnected?
> >>> I'm not familiar with WP themes, but I think they are templates with
> >>> placeholders for particular aspects of a web page/blog. I've been told
> >>> that this Royale site prototype is based on the Movedo theme. When I
> >>> searched for it on the internet I ended up here:
> >>> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fgreatives
> >>> .eu%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b1b5a7b344
> >>> 38794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> VI0EOLywsaxbKgmhAe
> >>> F08cdZNQjcgtIjyFvJ2R33hlo%3D&reserved=0
> >>> themeforest/themeswitcher/?product=movedo#movedo
> >>>>
> >>>> It doesn't look at all like the prototype at
> >>>
> >>> https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Froyale.co
> >>> deoscopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b1b
> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> sdata=3GHfDzdFp6B
> >>> 4RQMLuP00jKAHmwQ1QMubUd4dgz3FdTA%3D&reserved=0. Maybe the menu bar
> >>> along the top?
> >>>>
> >>>> So what did we license from greatives? Can Carlos or someone else
> >>> try
> >>> to reproduce the prototype without looking at the current CSS and maybe
> >>> use
> >>> AL licensed fonts or something like that?
> >>>>
> >>>> Thanks,
> >>>> -Alex
> >>>>
> >>>> From: Dave Fisher
> >>> <da...@comcast.net>>
> >>>> Reply-To: <de...@royale.apache.org>>
> >>>> Date: Tuesday, October 24, 2017 at 11:06 AM
> >>>> To: <de...@royale.apache.org>>
> >>>> Subject: Re: Apache Royale static web site
> >>>>
> >>>> Hi Alex,
> >>>>
> >>>> We will need to ask Carlos to list out all of the themes he uses and
> >>> then we will need to track things down and ask questions.
> >>>>
> >>>> Here is the site for what looks like the main theme:
> >>>
> >>> https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fgreative
> >>> s.ticksy.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b
> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> sdata=KBxlYi2QO
> >>> PDqNGhTsU6GJMhdUggdHVZjiYetcIcE8vE%3D&reserved=0
> >>>>
> >>>> It is the Move Do theme.
> >>>>
> >>>> Regards,
> >>>> Dave
> >>>>
> >>>> On Oct 24, 2017, at 10:56 AM, Alex Harui <aharui@adobe.com.INVALID<
> >>> mailto:aharui@adobe.com.INVALID>> wrote:
> >>>>
> >>>> Hi Dave,
> >>>>
> >>>> I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do
> >>> we
> >>> have the rights to replicate use of that look-and-feel elsewhere? I
> >>> don't
> >>> understand who owns the creative content.
> >>>>
> >>>> Thoughts?
> >>>> -Alex
> >>>>
> >>>> From: Dave Fisher <dave2wave@comcast.net<mailto:dave2wave@comcast.net
> >>>> <ma...@comcast.net>>
> >>>> Reply-To: <dev@royale.apache.org<mailto:dev@royale.apache.org
> ><mailto:
> >>> dev@royale.apache.org>>
> >>>> Date: Tuesday, October 24, 2017 at 10:50 AM
> >>>> To: <de...@royale.apache.org><mailto:
> >>> dev@royale.apache.org>>
> >>>> Subject: Re: Apache Royale static web site
> >>>>
> >>>> Hi Alex,
> >>>>
> >>>> On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID<
> >>> mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>>
> >>> wrote:
> >>>>
> >>>> There is something I don't think I understand. AIUI, at some point,
> >>> we
> >>>> will want the Apache Royale site to include actual Royale
> >>> applications,
> >>>> right? And I would think we would want the styling of those
> >>> applications
> >>>> to be consistent with the rest of the site. So I'm not clear how we
> >>> will
> >>>> be able to implement the styling/theme of these Royale applications
> >>> if we
> >>>> don't have rights to the styling. I don't understand how WP themes
> >>> and
> >>>> commercial licensing works if we want to replicate that user
> >>> experience
> >>>> outside of WP.
> >>>>
> >>>> We need to examine the static export of the CSS and HTML.
> >>>>
> >>>>
> >>>> If we can use those visuals outside of WP, then why must we continue
> >>> to
> >>>> use WP to generate the site? I would hope the theme would be
> >>> implemented
> >>>> as CSS and some templates we could use without WP.
> >>>>
> >>>> We should be able to adapt. Site building in the CMS can get complex
> >>> if
> >>> needed. For
> >>> OpenOffice.org<https://na01.safelinks.protection.outlook.
> com/?url=http%3A
> >>> %2F%2FOpenOffice.org&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7
> >>> Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> m3Mv
> >>> XfpJIZbB4u1Zhr0AB%2B%2BVI5uPKwu7N33MkPuovjs%3D&reserved=0><
> https://na01.s
> >>> afelinks.protection.outlook.com/?url=http%3A%2F%
> 2FOpenOffice.org&data=02%
> >>> 7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
> 7Cfa7b1b5a7b34438794aed2c178de
> >>> cee1%7C0%7C0%7C636446023931803217&sdata=m3MvXfpJIZbB4u1Zhr0AB%2B%
> 2BVI5uPK
> >>> wu7N33MkPuovjs%3D&reserved=0>
> >>> we use the legacy html pulling out the title and content body and place
> >>> it
> >>> within a markdown template.
> >>>>
> >>>>
> >>>> Also, if someone wants to patch the site, they can't just offer a
> >>> patch
> >>> of
> >>>> the HTML right? They would need to figure out where in WP it comes
> >>> from?
> >>>> Is there a patch process for WP content?
> >>>>
> >>>> Possibly.
> >>>>
> >>>>
> >>>> Sorry if there is some basic thing I am missing.
> >>>>
> >>>> It will get complex first as we figure out how to embed and then it
> >>> will
> >>> get simplified as we find the best way.
> >>>>
> >>>> Regards,
> >>>> Dave
> >>>>
> >>>>
> >>>>
> >>>> Thanks,
> >>>> -Alex
> >>>>
> >>>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
> >>> carlos.rovira@gmail.com><ma...@gmail.com> on behalf of
> >>> Carlos
> >>>> Rovira"
> >>> <ca...@gmail.com><mailto:
> >>> carlos.rovira@gmail.com> on behalf of
> >>>> carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
> >>>> <ma...@codeoscopic.com>> wrote:
> >>>>
> >>>> Thanks Dave,
> >>>>
> >>>> I'll write an email to trademarks to start with the process. I think
> >>> is
> >>>> better to migrate to
> >>> WP.com<https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2FWP
> >>> .com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b1b5a7b34438
> >>> 794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> pPTlG8DjwzO%2FN%2B0r
> >>> euRRSegBNuKdtuonR2fro55wfgs%3D&reserved=0><https://na01.
> safelinks.protect
> >>> ion.outlook.com/?url=http%3A%2F%2FWP.com&data=02%7C01%7C%
> 7Cdb97bd994ab24e
> >>> e2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636446023
> >>> 931803217&sdata=pPTlG8DjwzO%2FN%2B0reuRRSegBNuKdtuonR2fro55wfg
> s%3D&reserv
> >>> ed=0> before
> >>> continue working on content so we can
> >>>> detect whatever issue we could get.
> >>>>
> >>>> Thanks!
> >>>>
> >>>> Carlos
> >>>>
> >>>>
> >>>>
> >>>> 2017-10-24 18:56 GMT+02:00 Dave Fisher <dave2wave@comcast.net<mailto:
> >>> dave2wave@comcast.net><ma...@comcast.net>>:
> >>>>
> >>>> Hi Carlos,
> >>>>
> >>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <carlosrovira@apache.org<
> >>> mailto:carlosrovira@apache.org><ma...@apache.org>>
> >>>> wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> just let you know that I tried to create an static version of the
> >>>> preview
> >>>> site with success. I use this plugin :
> >>>>
> >>>> https://na01.safelinks.protection.outlook.com/?url=
> >>> https%3A%2F%2Fwordpres
> >>>>
> >>> s.org<https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fs.o
> >>> rg%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b1b5a7b3443
> >>> 8794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> 6zrqW3l9%2BJqeOxjih
> >>> uPWtMuguPsUDWnbqhyRxVXiTfI%3D&reserved=0>%2Fplugins%
> 2Fsimply-static%2F&da
> >>> ta=02%7C01%7C%
> >>> 7Cb448363ee5984b3b3e0f
> >>>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
> >>> cee1%7C0%7C0%7C636444624020033
> >>>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
> >>>>
> >>>> and we can generate all static content with relative or absolute urls.
> >>>> The
> >>>> final preview site in static is 134mb
> >>>>
> >>>> Another thing I was searching was to use a WP to Jekyll exporter but
> >>>> this
> >>>> is not what I wanted since it seems Jekyll is all about markdown and
> >>>> we
> >>>> want a full html site with all the eye candy JS+CSS resources. In the
> >>>> end,
> >>>> and thinking more about it, is not what we want since although the
> >>>> site
> >>>> would be exported ok, we don't want to upload it to the GitHub pages
> >>>> like
> >>>> we discusses in the other thread due to expose part of the code of a
> >>>> commercial wp theme.
> >>>>
> >>>> So, the workflow we can use is: Use the WP backend to enter new
> >>>> content
> >>>> and
> >>>> modify existing want with ease (this is important is we want people
> >>>> contributing here). Next, with all changes done, generate a static
> >>>> version
> >>>> and replace the entire site with a fresh generated static site at
> >>>>
> >>> royale.apache.org<https://na01.safelinks.protection.
> outlook.com/?url=http
> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
> 7Cdb97bd994ab24ee2f91c08d51
> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636446023931803217&s
> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>.
> and
> >>> as well route the
> >>> more friendly domain to this
> >>>> if
> >>>> board is ok with that.
> >>>>
> >>>> Yes! External domain
> >>> royalysdk.org<https://na01.safelinks.protection.outlook.
> com/?url=http%3A%
> >>> 2F%2Froyalysdk.org%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%
> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636446023931803217&sdata=Dmo
> >>> CAUlAVHkkOp0uFdDH0%2FoUUU9qwdl00M8fWRe888Q%3D&reserved=0> is
> redirected
> >>> to
> >>> royale.apache.org<https://na01.safelinks.protection.
> outlook.com/?url=http
> >>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%
> 7Cdb97bd994ab24ee2f91c08d51
> >>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636446023931803217&s
> >>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0> as
> >>>> discussed.
> >>>>
> >>>>
> >>>> We can check with apache board or trademarks what they propose about
> >>>> to
> >>>> create a
> >>> Wordpress.com<https://na01.safelinks.protection.outlook.
> com/?url=http%3A%
> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%
> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636446023931803217&sdata=%2B
> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0> account
> >>> managed by Apache
> >>> and migrate from my
> >>>> server
> >>>> to that account, and all this stuff from there, since if I remember
> >>>> some
> >>>> people said that would be more ok with Apache.I'd end removing my temp
> >>>> subdomain after this.
> >>>>
> >>>> The advantage of using the
> >>> Wordpress.com<https://na01.safelinks.protection.outlook.
> com/?url=http%3A%
> >>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%
> >>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%
> 7C636446023931803217&sdata=%2B
> >>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
> >>> location is twofold:
> >>>>
> >>>> (1) Wordpress keeps security up to date.
> >>>> (2) If something happens to you or your company then we have better
> >>>> access.
> >>>>
> >>>> I suspect though that with the status export method this will not be
> >>> as
> >>>> great a concern.
> >>>>
> >>>>
> >>>> What do you think? Can I move this with the people we were talking
> >>>> some
> >>>> weeks ago?
> >>>>
> >>>> Either you or I can email Trademarks with the plan.
> >>>>
> >>>> We can then discuss the redirection with Infrastructure and get the
> >>> site
> >>>> checked in.
> >>>>
> >>>> Regards,
> >>>> Dave
> >>>>
> >>>>
> >>>> Let me know in order to start making the next steps
> >>>>
> >>>> Thanks
> >>>>
> >>>>
> >>>> --
> >>>> Carlos Rovira
> >>>>
> >>>> https://na01.safelinks.protection.outlook.com/?url=
> >>> http%3A%2F%2Fabout.me%
> >>>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> >>> 73f8%7Cfa7b1
> >>>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >>> sdata=1q5B1u1lLR
> >>>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>>
> >>>> <https://na01.safelinks.protection.outlook.com/?url=
> >>> http%3A%2F%2Fwww.codeo
> >>>>
> >>> scopic.com<https://na01.safelinks.protection.outlook.
> com/?url=http%3A%2F%
> >>> 2Fscopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b
> >>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> sdata=oG9idkXzU
> >>> tg91G5vhl5P0Dn2u8gXX55UvN172PAlPXs%3D&reserved=0>&data=02%7C01%7C%
> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> >>>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >>> sdata=Y%2Fkytu4lJUWu5H
> >>>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<https://na01.safelinks.protection.outlook.
> com/?url=http%3A%2F%2
> >>> Fcopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b1b
> >>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> sdata=ZPPDqp5SNhK
> >>> C2rzYxfzkSV7f8lDtLmaRyyaMAlvtRcw%3D&reserved=0>&data=02%7C01%7C%
> >>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> >>>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
> >>> 2Fkytu4lJUWu5Hz
> >>>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
> >>>>
> >>>>
> >>>> Conocenos Avant2 en 1 minuto!
> >>>> <https://na01.safelinks.protection.outlook.com/?url=
> >>> https%3A%2F%2Favant2.e
> >>>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> >>> 73f8%7Cfa7b1b5a
> >>>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> >>> sdata=SJmmZQTVSb0tmX
> >>>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> >>>> 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.
> >>>>
> >>>>
> >>>
> >>>
> >>
> >>
> >> --
> >>
> >> <https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo
> >> scopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b1b5a7b
> >> 34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> sdata=ZPowinnGs4jxxXQ4
> >> hULLfJLfWsGXx9zNLKnS9W7JoNY%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%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b1b5a7b3
> >> 4438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=
> ZPowinnGs4jxxXQ4h
> >> ULLfJLfWsGXx9zNLKnS9W7JoNY%3D&reserved=0
> >>
> >>
> >> Conocenos Avant2 en 1 minuto!
> >> <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant2.e
> >> s%2F%23video&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c49
> 6496%7Cfa7b1b5a
> >> 7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&
> sdata=ZiX3l%2FtQwsOG
> >> QN%2BibIJ5pxYpI5UboaH26BzM%2F9AtaLg%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
> >> 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.
> >
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Harbs <ha...@gmail.com>.
Another point to consider:
We’ve had some folks offer to help with skinning Royale components. It should be pretty straightforward to give them (and anyone else who wants to help) committer rights to the website repo. If we have more people working on it, the task of recreating the appearance achieved through the Movedo CSS should be al lot easier.
I don’t feel comfortable asking Carlos to do more work than he’s offered, but with help from others, it might be a lot easier.
Harbs
> On Oct 26, 2017, at 7:41 PM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Hi Carlos,
>
> I don't know if the "Apache Way" is a problem here. So far I think we
> have heard opinions and concerns but AFAICT no hard policy has been quoted
> that prevents having royale.a.o point to WP.com.
>
> But I am still unclear if hosting our site on WP is really the best
> strategy. I have the following concerns:
>
> 1) How would be include a Royale application in our site?
> 2) How would we style the Royale application to look consistent with the
> rest of the site?
> 3) Could we ever create a theme based on this styling?
>
> I didn't, and still don't, understand how WP themes and their licensing
> work, otherwise I think I would have asked more questions up front. I
> thought you would own copyright on the results, just like using Adobe
> Dreamweaver and Adobe Illustrator to build out a site doesn't put the
> content under Adobe licensing.
>
> That doesn't appear to be the case here, but I think we do need to
> consider the 3 concerns I've listed.
>
> Both you and Harbs claim that replicating your prototype's look and feel
> will be a lot of work, but how much work are really talking about, and do
> we have to exactly replicate it (and should we)? If you think about how
> Royale components are created, they work with some default CSS. I think
> if we implement themes, we'll end up with components with particular
> "sub-DOMs" and CSS that dictates the visuals on those sub-DOMs. AIUI, we
> are expecting artwork from some designers about other default looks for
> Royale components. Won't we be facing a similar challenge of trying to
> figure out the CSS that best matches what we see on a screen?
>
> So, I think it is great that WP and MoveDo helped you create this
> fantastic looking prototype. But, IMO, one direction we can go from here
> is to try to replicate the visuals you created in CSS in a way that can be
> re-used via the Apache Way. I think we'd learn about themes as we try to
> do that. Could we get most of the way there in a couple of days? Then
> others can offer fine-tuning via patches.
>
> And yes, WP is tuned towards templated content in a consistent way, but it
> would be interesting to build Royale components that do something similar.
>
> Thoughts?
> -Alex
>
> On 10/26/17, 1:12 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
> <carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>
>> Harbs is right,
>>
>> to get something that looks cool and consistent is difficult and for this
>> reason I use wordpress+theme (in this case movedo). Is the same thing as
>> why people use flex or royale. Is the way to start from a point where you
>> are more efficient and maintenance can be assumed.
>>
>> Alex, you see lots of difference since I customized via movedo interface
>> but as well did some tweaks in custom css (for example the footer column
>> menus)
>>
>> So could we rework the site without wp and movedo. Sure, as I stated all
>> sites can be write in different ways, but the long term reason to adopt a
>> CMS like WP is to have a backend to introduce content of quality in the
>> most easy way while preserving quality on presentation (styles, fonts,
>> effects...)
>>
>> I think we are in a situation where "the Apache way" fails completely
>> since
>> we should be able to make this quick and easy and concentrate in our
>> Royale
>> code, that is why we are here, and why I tried to go this path: to get
>> something that looks good and professional but to spend very few time for
>> our part.
>>
>> I'm very pragmatic, and like to go to the point. All Apache rules should
>> be
>> focused in protect the code we release, and we should have less trouble
>> with tools like WP, Jira, Nexus, and the rest. In fact Apache is using
>> those tools all along the way, why is so hard to do this?
>>
>> We only need:
>>
>> * Some host for a Wordpress instance: this could be the current
>> Codeoscopic
>> subdomain or whatever people like. I'd be more happy if the wp instance is
>> in some server that could be controlled and maintained by ASF. I don't
>> know
>> if this could be WP.com or some ASF's virtual machine that could host
>> that.
>>
>> * The Movedo theme: I write to Dimitri, from greatives. He is very
>> supportive and very like the idea, but is not in their hands. He point me
>> to talk with envato, and I write to them, but still doesn't have a
>> response. My thinking here is that we really don't need nothing of this.
>> Envato could donate a license but is only 59$, so is something affordable
>> by a simple donation.
>>
>> * Finaly to generate an static site from WP. This is as well not needed,
>> but we can do it. People use to generate wp static version in order to
>> protect their sites from hacking. That's the only relevant point to do
>> this. So for me is something we can do if the rest of community wants it.
>> Is very easy to do.
>>
>>
>> Additionaly: As we are not uploading any website code to any ASF repo,
>> since as I said, it would be like to upload the JIRA source code to our
>> repos, and that doesn't give us anything (we're here to release only
>> apache
>> royale code). we can :
>>
>> 1.- Use the royale.codeoscopic.com wp instance as the tool for us to
>> modify
>> the site (people in our community will have user/pass in this wp instance
>> to create post and pages)
>> (in this way is similar to the server Alex had on his own to make some
>> apache flex task, correct me if I'm wrong)
>> Again, it can be royale.codeoscopic.com or other hosting ASF wants.
>>
>> 2.- Each time something changes: generate static site and deploy to
>> royale.apache.org
>> (in this case the set of static generated html/js/css could not be
>> uploaded
>> to any ASF repo since we don't want to release the website code, that must
>> be served in the same way ASF serves JIRA, or whatever other commercial
>> tool
>>
>> Hosting a generated site with a movedo commercial theme needs of a 59$
>> license that could be donated by envato or donated for other
>> person/company
>> (for example Codeoscopic)
>>
>> For me this is quick and easy and I think we're not making something wrong
>> in legal terms
>>
>> Carlos
>>
>>
>>
>>
>>
>>
>>
>> 2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
>>
>>> It’s using greatives’ CSS and JS files for styling, layout and effects.
>>>
>>> Generally, these themes have a lot of flexibility to change the look of
>>> a
>>> site without messing with CSS and JS.
>>>
>>> Can we re-write the CSS and JS to do the same kind of thing? Probably.
>>> But
>>> it would be a considerable amount of work.
>>>
>>> What’s included in the license? I’m really not sure.
>>>
>>> It gives rights to us the theme in WordPress. Does that allow
>>> repurposing
>>> the CSS and JS files for use elsewhere? I don’t know.
>>>
>>> Harbs
>>>
>>>> On Oct 26, 2017, at 9:56 AM, Alex Harui <ah...@adobe.com.INVALID>
>>> wrote:
>>>>
>>>> I'm still confused about something.
>>>>
>>>> Can someone explain how creativity and licensing are interconnected?
>>> I'm not familiar with WP themes, but I think they are templates with
>>> placeholders for particular aspects of a web page/blog. I've been told
>>> that this Royale site prototype is based on the Movedo theme. When I
>>> searched for it on the internet I ended up here:
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgreatives
>>> .eu%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b344
>>> 38794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=VI0EOLywsaxbKgmhAe
>>> F08cdZNQjcgtIjyFvJ2R33hlo%3D&reserved=0
>>> themeforest/themeswitcher/?product=movedo#movedo
>>>>
>>>> It doesn't look at all like the prototype at
>>>
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.co
>>> deoscopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b
>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=3GHfDzdFp6B
>>> 4RQMLuP00jKAHmwQ1QMubUd4dgz3FdTA%3D&reserved=0. Maybe the menu bar
>>> along the top?
>>>>
>>>> So what did we license from greatives? Can Carlos or someone else
>>> try
>>> to reproduce the prototype without looking at the current CSS and maybe
>>> use
>>> AL licensed fonts or something like that?
>>>>
>>>> Thanks,
>>>> -Alex
>>>>
>>>> From: Dave Fisher
>>> <da...@comcast.net>>
>>>> Reply-To: <de...@royale.apache.org>>
>>>> Date: Tuesday, October 24, 2017 at 11:06 AM
>>>> To: <de...@royale.apache.org>>
>>>> Subject: Re: Apache Royale static web site
>>>>
>>>> Hi Alex,
>>>>
>>>> We will need to ask Carlos to list out all of the themes he uses and
>>> then we will need to track things down and ask questions.
>>>>
>>>> Here is the site for what looks like the main theme:
>>>
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgreative
>>> s.ticksy.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b
>>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=KBxlYi2QO
>>> PDqNGhTsU6GJMhdUggdHVZjiYetcIcE8vE%3D&reserved=0
>>>>
>>>> It is the Move Do theme.
>>>>
>>>> Regards,
>>>> Dave
>>>>
>>>> On Oct 24, 2017, at 10:56 AM, Alex Harui <aharui@adobe.com.INVALID<
>>> mailto:aharui@adobe.com.INVALID>> wrote:
>>>>
>>>> Hi Dave,
>>>>
>>>> I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do
>>> we
>>> have the rights to replicate use of that look-and-feel elsewhere? I
>>> don't
>>> understand who owns the creative content.
>>>>
>>>> Thoughts?
>>>> -Alex
>>>>
>>>> From: Dave Fisher <dave2wave@comcast.net<mailto:dave2wave@comcast.net
>>>> <ma...@comcast.net>>
>>>> Reply-To: <de...@royale.apache.org><mailto:
>>> dev@royale.apache.org>>
>>>> Date: Tuesday, October 24, 2017 at 10:50 AM
>>>> To: <de...@royale.apache.org><mailto:
>>> dev@royale.apache.org>>
>>>> Subject: Re: Apache Royale static web site
>>>>
>>>> Hi Alex,
>>>>
>>>> On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID<
>>> mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>>
>>> wrote:
>>>>
>>>> There is something I don't think I understand. AIUI, at some point,
>>> we
>>>> will want the Apache Royale site to include actual Royale
>>> applications,
>>>> right? And I would think we would want the styling of those
>>> applications
>>>> to be consistent with the rest of the site. So I'm not clear how we
>>> will
>>>> be able to implement the styling/theme of these Royale applications
>>> if we
>>>> don't have rights to the styling. I don't understand how WP themes
>>> and
>>>> commercial licensing works if we want to replicate that user
>>> experience
>>>> outside of WP.
>>>>
>>>> We need to examine the static export of the CSS and HTML.
>>>>
>>>>
>>>> If we can use those visuals outside of WP, then why must we continue
>>> to
>>>> use WP to generate the site? I would hope the theme would be
>>> implemented
>>>> as CSS and some templates we could use without WP.
>>>>
>>>> We should be able to adapt. Site building in the CMS can get complex
>>> if
>>> needed. For
>>> OpenOffice.org<https://na01.safelinks.protection.outlook.com/?url=http%3A
>>> %2F%2FOpenOffice.org&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7
>>> Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=m3Mv
>>> XfpJIZbB4u1Zhr0AB%2B%2BVI5uPKwu7N33MkPuovjs%3D&reserved=0><https://na01.s
>>> afelinks.protection.outlook.com/?url=http%3A%2F%2FOpenOffice.org&data=02%
>>> 7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C636446023931803217&sdata=m3MvXfpJIZbB4u1Zhr0AB%2B%2BVI5uPK
>>> wu7N33MkPuovjs%3D&reserved=0>
>>> we use the legacy html pulling out the title and content body and place
>>> it
>>> within a markdown template.
>>>>
>>>>
>>>> Also, if someone wants to patch the site, they can't just offer a
>>> patch
>>> of
>>>> the HTML right? They would need to figure out where in WP it comes
>>> from?
>>>> Is there a patch process for WP content?
>>>>
>>>> Possibly.
>>>>
>>>>
>>>> Sorry if there is some basic thing I am missing.
>>>>
>>>> It will get complex first as we figure out how to embed and then it
>>> will
>>> get simplified as we find the best way.
>>>>
>>>> Regards,
>>>> Dave
>>>>
>>>>
>>>>
>>>> Thanks,
>>>> -Alex
>>>>
>>>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
>>> carlos.rovira@gmail.com><ma...@gmail.com> on behalf of
>>> Carlos
>>>> Rovira"
>>> <ca...@gmail.com><mailto:
>>> carlos.rovira@gmail.com> on behalf of
>>>> carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
>>>> <ma...@codeoscopic.com>> wrote:
>>>>
>>>> Thanks Dave,
>>>>
>>>> I'll write an email to trademarks to start with the process. I think
>>> is
>>>> better to migrate to
>>> WP.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2FWP
>>> .com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b34438
>>> 794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=pPTlG8DjwzO%2FN%2B0r
>>> euRRSegBNuKdtuonR2fro55wfgs%3D&reserved=0><https://na01.safelinks.protect
>>> ion.outlook.com/?url=http%3A%2F%2FWP.com&data=02%7C01%7C%7Cdb97bd994ab24e
>>> e2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023
>>> 931803217&sdata=pPTlG8DjwzO%2FN%2B0reuRRSegBNuKdtuonR2fro55wfgs%3D&reserv
>>> ed=0> before
>>> continue working on content so we can
>>>> detect whatever issue we could get.
>>>>
>>>> Thanks!
>>>>
>>>> Carlos
>>>>
>>>>
>>>>
>>>> 2017-10-24 18:56 GMT+02:00 Dave Fisher <dave2wave@comcast.net<mailto:
>>> dave2wave@comcast.net><ma...@comcast.net>>:
>>>>
>>>> Hi Carlos,
>>>>
>>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <carlosrovira@apache.org<
>>> mailto:carlosrovira@apache.org><ma...@apache.org>>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> just let you know that I tried to create an static version of the
>>>> preview
>>>> site with success. I use this plugin :
>>>>
>>>> https://na01.safelinks.protection.outlook.com/?url=
>>> https%3A%2F%2Fwordpres
>>>>
>>> s.org<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fs.o
>>> rg%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b3443
>>> 8794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=6zrqW3l9%2BJqeOxjih
>>> uPWtMuguPsUDWnbqhyRxVXiTfI%3D&reserved=0>%2Fplugins%2Fsimply-static%2F&da
>>> ta=02%7C01%7C%
>>> 7Cb448363ee5984b3b3e0f
>>>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
>>> cee1%7C0%7C0%7C636444624020033
>>>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>>>>
>>>> and we can generate all static content with relative or absolute urls.
>>>> The
>>>> final preview site in static is 134mb
>>>>
>>>> Another thing I was searching was to use a WP to Jekyll exporter but
>>>> this
>>>> is not what I wanted since it seems Jekyll is all about markdown and
>>>> we
>>>> want a full html site with all the eye candy JS+CSS resources. In the
>>>> end,
>>>> and thinking more about it, is not what we want since although the
>>>> site
>>>> would be exported ok, we don't want to upload it to the GitHub pages
>>>> like
>>>> we discusses in the other thread due to expose part of the code of a
>>>> commercial wp theme.
>>>>
>>>> So, the workflow we can use is: Use the WP backend to enter new
>>>> content
>>>> and
>>>> modify existing want with ease (this is important is we want people
>>>> contributing here). Next, with all changes done, generate a static
>>>> version
>>>> and replace the entire site with a fresh generated static site at
>>>>
>>> royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=http
>>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51
>>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&s
>>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>. and
>>> as well route the
>>> more friendly domain to this
>>>> if
>>>> board is ok with that.
>>>>
>>>> Yes! External domain
>>> royalysdk.org<https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>> 2F%2Froyalysdk.org%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=Dmo
>>> CAUlAVHkkOp0uFdDH0%2FoUUU9qwdl00M8fWRe888Q%3D&reserved=0> is redirected
>>> to
>>> royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=http
>>> %3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51
>>> c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&s
>>> data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0> as
>>>> discussed.
>>>>
>>>>
>>>> We can check with apache board or trademarks what they propose about
>>>> to
>>>> create a
>>> Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=%2B
>>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0> account
>>> managed by Apache
>>> and migrate from my
>>>> server
>>>> to that account, and all this stuff from there, since if I remember
>>>> some
>>>> people said that would be more ok with Apache.I'd end removing my temp
>>>> subdomain after this.
>>>>
>>>> The advantage of using the
>>> Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>> 2F%2Fwordpress.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>>> 7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=%2B
>>> xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
>>> location is twofold:
>>>>
>>>> (1) Wordpress keeps security up to date.
>>>> (2) If something happens to you or your company then we have better
>>>> access.
>>>>
>>>> I suspect though that with the status export method this will not be
>>> as
>>>> great a concern.
>>>>
>>>>
>>>> What do you think? Can I move this with the people we were talking
>>>> some
>>>> weeks ago?
>>>>
>>>> Either you or I can email Trademarks with the plan.
>>>>
>>>> We can then discuss the redirection with Infrastructure and get the
>>> site
>>>> checked in.
>>>>
>>>> Regards,
>>>> Dave
>>>>
>>>>
>>>> Let me know in order to start making the next steps
>>>>
>>>> Thanks
>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>>
>>>> https://na01.safelinks.protection.outlook.com/?url=
>>> http%3A%2F%2Fabout.me%
>>>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>>> 73f8%7Cfa7b1
>>>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>>> sdata=1q5B1u1lLR
>>>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>>>>
>>>>
>>>>
>>>>
>>>> --
>>>>
>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>> http%3A%2F%2Fwww.codeo
>>>>
>>> scopic.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%
>>> 2Fscopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b
>>> 1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=oG9idkXzU
>>> tg91G5vhl5P0Dn2u8gXX55UvN172PAlPXs%3D&reserved=0>&data=02%7C01%7C%
>>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>>>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>>> sdata=Y%2Fkytu4lJUWu5H
>>>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2
>>> Fcopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b
>>> 5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=ZPPDqp5SNhK
>>> C2rzYxfzkSV7f8lDtLmaRyyaMAlvtRcw%3D&reserved=0>&data=02%7C01%7C%
>>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>>>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
>>> 2Fkytu4lJUWu5Hz
>>>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>>>>
>>>>
>>>> Conocenos Avant2 en 1 minuto!
>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>> https%3A%2F%2Favant2.e
>>>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>>> 73f8%7Cfa7b1b5a
>>>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>>> sdata=SJmmZQTVSb0tmX
>>>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>>>> 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.
>>>>
>>>>
>>>
>>>
>>
>>
>> --
>>
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>> scopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=ZPowinnGs4jxxXQ4
>> hULLfJLfWsGXx9zNLKnS9W7JoNY%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%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=ZPowinnGs4jxxXQ4h
>> ULLfJLfWsGXx9zNLKnS9W7JoNY%3D&reserved=0
>>
>>
>> Conocenos Avant2 en 1 minuto!
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>> s%2F%23video&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a
>> 7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=ZiX3l%2FtQwsOG
>> QN%2BibIJ5pxYpI5UboaH26BzM%2F9AtaLg%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
>> 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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi Carlos,
I don't know if the "Apache Way" is a problem here. So far I think we
have heard opinions and concerns but AFAICT no hard policy has been quoted
that prevents having royale.a.o point to WP.com.
But I am still unclear if hosting our site on WP is really the best
strategy. I have the following concerns:
1) How would be include a Royale application in our site?
2) How would we style the Royale application to look consistent with the
rest of the site?
3) Could we ever create a theme based on this styling?
I didn't, and still don't, understand how WP themes and their licensing
work, otherwise I think I would have asked more questions up front. I
thought you would own copyright on the results, just like using Adobe
Dreamweaver and Adobe Illustrator to build out a site doesn't put the
content under Adobe licensing.
That doesn't appear to be the case here, but I think we do need to
consider the 3 concerns I've listed.
Both you and Harbs claim that replicating your prototype's look and feel
will be a lot of work, but how much work are really talking about, and do
we have to exactly replicate it (and should we)? If you think about how
Royale components are created, they work with some default CSS. I think
if we implement themes, we'll end up with components with particular
"sub-DOMs" and CSS that dictates the visuals on those sub-DOMs. AIUI, we
are expecting artwork from some designers about other default looks for
Royale components. Won't we be facing a similar challenge of trying to
figure out the CSS that best matches what we see on a screen?
So, I think it is great that WP and MoveDo helped you create this
fantastic looking prototype. But, IMO, one direction we can go from here
is to try to replicate the visuals you created in CSS in a way that can be
re-used via the Apache Way. I think we'd learn about themes as we try to
do that. Could we get most of the way there in a couple of days? Then
others can offer fine-tuning via patches.
And yes, WP is tuned towards templated content in a consistent way, but it
would be interesting to build Royale components that do something similar.
Thoughts?
-Alex
On 10/26/17, 1:12 AM, "carlos.rovira@gmail.com on behalf of Carlos Rovira"
<carlos.rovira@gmail.com on behalf of carlos.rovira@codeoscopic.com> wrote:
>Harbs is right,
>
>to get something that looks cool and consistent is difficult and for this
>reason I use wordpress+theme (in this case movedo). Is the same thing as
>why people use flex or royale. Is the way to start from a point where you
>are more efficient and maintenance can be assumed.
>
>Alex, you see lots of difference since I customized via movedo interface
>but as well did some tweaks in custom css (for example the footer column
>menus)
>
>So could we rework the site without wp and movedo. Sure, as I stated all
>sites can be write in different ways, but the long term reason to adopt a
>CMS like WP is to have a backend to introduce content of quality in the
>most easy way while preserving quality on presentation (styles, fonts,
>effects...)
>
>I think we are in a situation where "the Apache way" fails completely
>since
>we should be able to make this quick and easy and concentrate in our
>Royale
>code, that is why we are here, and why I tried to go this path: to get
>something that looks good and professional but to spend very few time for
>our part.
>
>I'm very pragmatic, and like to go to the point. All Apache rules should
>be
>focused in protect the code we release, and we should have less trouble
>with tools like WP, Jira, Nexus, and the rest. In fact Apache is using
>those tools all along the way, why is so hard to do this?
>
>We only need:
>
>* Some host for a Wordpress instance: this could be the current
>Codeoscopic
>subdomain or whatever people like. I'd be more happy if the wp instance is
>in some server that could be controlled and maintained by ASF. I don't
>know
>if this could be WP.com or some ASF's virtual machine that could host
>that.
>
>* The Movedo theme: I write to Dimitri, from greatives. He is very
>supportive and very like the idea, but is not in their hands. He point me
>to talk with envato, and I write to them, but still doesn't have a
>response. My thinking here is that we really don't need nothing of this.
>Envato could donate a license but is only 59$, so is something affordable
>by a simple donation.
>
>* Finaly to generate an static site from WP. This is as well not needed,
>but we can do it. People use to generate wp static version in order to
>protect their sites from hacking. That's the only relevant point to do
>this. So for me is something we can do if the rest of community wants it.
>Is very easy to do.
>
>
>Additionaly: As we are not uploading any website code to any ASF repo,
>since as I said, it would be like to upload the JIRA source code to our
>repos, and that doesn't give us anything (we're here to release only
>apache
>royale code). we can :
>
>1.- Use the royale.codeoscopic.com wp instance as the tool for us to
>modify
>the site (people in our community will have user/pass in this wp instance
>to create post and pages)
>(in this way is similar to the server Alex had on his own to make some
>apache flex task, correct me if I'm wrong)
>Again, it can be royale.codeoscopic.com or other hosting ASF wants.
>
>2.- Each time something changes: generate static site and deploy to
>royale.apache.org
>(in this case the set of static generated html/js/css could not be
>uploaded
>to any ASF repo since we don't want to release the website code, that must
>be served in the same way ASF serves JIRA, or whatever other commercial
>tool
>
>Hosting a generated site with a movedo commercial theme needs of a 59$
>license that could be donated by envato or donated for other
>person/company
>(for example Codeoscopic)
>
>For me this is quick and easy and I think we're not making something wrong
>in legal terms
>
>Carlos
>
>
>
>
>
>
>
>2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
>
>> It’s using greatives’ CSS and JS files for styling, layout and effects.
>>
>> Generally, these themes have a lot of flexibility to change the look of
>>a
>> site without messing with CSS and JS.
>>
>> Can we re-write the CSS and JS to do the same kind of thing? Probably.
>>But
>> it would be a considerable amount of work.
>>
>> What’s included in the license? I’m really not sure.
>>
>> It gives rights to us the theme in WordPress. Does that allow
>>repurposing
>> the CSS and JS files for use elsewhere? I don’t know.
>>
>> Harbs
>>
>> > On Oct 26, 2017, at 9:56 AM, Alex Harui <ah...@adobe.com.INVALID>
>> wrote:
>> >
>> > I'm still confused about something.
>> >
>> > Can someone explain how creativity and licensing are interconnected?
>> I'm not familiar with WP themes, but I think they are templates with
>> placeholders for particular aspects of a web page/blog. I've been told
>> that this Royale site prototype is based on the Movedo theme. When I
>> searched for it on the internet I ended up here:
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fgreatives
>>.eu%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b344
>>38794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=VI0EOLywsaxbKgmhAe
>>F08cdZNQjcgtIjyFvJ2R33hlo%3D&reserved=0
>> themeforest/themeswitcher/?product=movedo#movedo
>> >
>> > It doesn't look at all like the prototype at
>>
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Froyale.co
>>deoscopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b
>>5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=3GHfDzdFp6B
>>4RQMLuP00jKAHmwQ1QMubUd4dgz3FdTA%3D&reserved=0. Maybe the menu bar
>>along the top?
>> >
>> > So what did we license from greatives? Can Carlos or someone else
>>try
>> to reproduce the prototype without looking at the current CSS and maybe
>>use
>> AL licensed fonts or something like that?
>> >
>> > Thanks,
>> > -Alex
>> >
>> > From: Dave Fisher
>><da...@comcast.net>>
>> > Reply-To: <de...@royale.apache.org>>
>> > Date: Tuesday, October 24, 2017 at 11:06 AM
>> > To: <de...@royale.apache.org>>
>> > Subject: Re: Apache Royale static web site
>> >
>> > Hi Alex,
>> >
>> > We will need to ask Carlos to list out all of the themes he uses and
>> then we will need to track things down and ask questions.
>> >
>> > Here is the site for what looks like the main theme:
>>
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgreative
>>s.ticksy.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b
>>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=KBxlYi2QO
>>PDqNGhTsU6GJMhdUggdHVZjiYetcIcE8vE%3D&reserved=0
>> >
>> > It is the Move Do theme.
>> >
>> > Regards,
>> > Dave
>> >
>> > On Oct 24, 2017, at 10:56 AM, Alex Harui <aharui@adobe.com.INVALID<
>> mailto:aharui@adobe.com.INVALID>> wrote:
>> >
>> > Hi Dave,
>> >
>> > I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do
>>we
>> have the rights to replicate use of that look-and-feel elsewhere? I
>>don't
>> understand who owns the creative content.
>> >
>> > Thoughts?
>> > -Alex
>> >
>> > From: Dave Fisher <dave2wave@comcast.net<mailto:dave2wave@comcast.net
>> ><ma...@comcast.net>>
>> > Reply-To: <de...@royale.apache.org><mailto:
>> dev@royale.apache.org>>
>> > Date: Tuesday, October 24, 2017 at 10:50 AM
>> > To: <de...@royale.apache.org><mailto:
>> dev@royale.apache.org>>
>> > Subject: Re: Apache Royale static web site
>> >
>> > Hi Alex,
>> >
>> > On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID<
>> mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>>
>>wrote:
>> >
>> > There is something I don't think I understand. AIUI, at some point,
>>we
>> > will want the Apache Royale site to include actual Royale
>>applications,
>> > right? And I would think we would want the styling of those
>>applications
>> > to be consistent with the rest of the site. So I'm not clear how we
>>will
>> > be able to implement the styling/theme of these Royale applications
>>if we
>> > don't have rights to the styling. I don't understand how WP themes
>>and
>> > commercial licensing works if we want to replicate that user
>>experience
>> > outside of WP.
>> >
>> > We need to examine the static export of the CSS and HTML.
>> >
>> >
>> > If we can use those visuals outside of WP, then why must we continue
>>to
>> > use WP to generate the site? I would hope the theme would be
>>implemented
>> > as CSS and some templates we could use without WP.
>> >
>> > We should be able to adapt. Site building in the CMS can get complex
>>if
>> needed. For
>>OpenOffice.org<https://na01.safelinks.protection.outlook.com/?url=http%3A
>>%2F%2FOpenOffice.org&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7
>>Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=m3Mv
>>XfpJIZbB4u1Zhr0AB%2B%2BVI5uPKwu7N33MkPuovjs%3D&reserved=0><https://na01.s
>>afelinks.protection.outlook.com/?url=http%3A%2F%2FOpenOffice.org&data=02%
>>7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178de
>>cee1%7C0%7C0%7C636446023931803217&sdata=m3MvXfpJIZbB4u1Zhr0AB%2B%2BVI5uPK
>>wu7N33MkPuovjs%3D&reserved=0>
>> we use the legacy html pulling out the title and content body and place
>>it
>> within a markdown template.
>> >
>> >
>> > Also, if someone wants to patch the site, they can't just offer a
>>patch
>> of
>> > the HTML right? They would need to figure out where in WP it comes
>>from?
>> > Is there a patch process for WP content?
>> >
>> > Possibly.
>> >
>> >
>> > Sorry if there is some basic thing I am missing.
>> >
>> > It will get complex first as we figure out how to embed and then it
>>will
>> get simplified as we find the best way.
>> >
>> > Regards,
>> > Dave
>> >
>> >
>> >
>> > Thanks,
>> > -Alex
>> >
>> > On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
>> carlos.rovira@gmail.com><ma...@gmail.com> on behalf of
>> Carlos
>> > Rovira"
>><ca...@gmail.com><mailto:
>> carlos.rovira@gmail.com> on behalf of
>> > carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
>> ><ma...@codeoscopic.com>> wrote:
>> >
>> > Thanks Dave,
>> >
>> > I'll write an email to trademarks to start with the process. I think
>>is
>> > better to migrate to
>>WP.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2FWP
>>.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b34438
>>794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=pPTlG8DjwzO%2FN%2B0r
>>euRRSegBNuKdtuonR2fro55wfgs%3D&reserved=0><https://na01.safelinks.protect
>>ion.outlook.com/?url=http%3A%2F%2FWP.com&data=02%7C01%7C%7Cdb97bd994ab24e
>>e2f91c08d51c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023
>>931803217&sdata=pPTlG8DjwzO%2FN%2B0reuRRSegBNuKdtuonR2fro55wfgs%3D&reserv
>>ed=0> before
>> continue working on content so we can
>> > detect whatever issue we could get.
>> >
>> > Thanks!
>> >
>> > Carlos
>> >
>> >
>> >
>> > 2017-10-24 18:56 GMT+02:00 Dave Fisher <dave2wave@comcast.net<mailto:
>> dave2wave@comcast.net><ma...@comcast.net>>:
>> >
>> > Hi Carlos,
>> >
>> > On Oct 24, 2017, at 9:30 AM, Carlos Rovira <carlosrovira@apache.org<
>> mailto:carlosrovira@apache.org><ma...@apache.org>>
>> > wrote:
>> >
>> > Hi,
>> >
>> > just let you know that I tried to create an static version of the
>> > preview
>> > site with success. I use this plugin :
>> >
>> > https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Fwordpres
>> >
>>s.org<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fs.o
>>rg%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b3443
>>8794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=6zrqW3l9%2BJqeOxjih
>>uPWtMuguPsUDWnbqhyRxVXiTfI%3D&reserved=0>%2Fplugins%2Fsimply-static%2F&da
>>ta=02%7C01%7C%
>> 7Cb448363ee5984b3b3e0f
>> > 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
>> cee1%7C0%7C0%7C636444624020033
>> > 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>> >
>> > and we can generate all static content with relative or absolute urls.
>> > The
>> > final preview site in static is 134mb
>> >
>> > Another thing I was searching was to use a WP to Jekyll exporter but
>> > this
>> > is not what I wanted since it seems Jekyll is all about markdown and
>> > we
>> > want a full html site with all the eye candy JS+CSS resources. In the
>> > end,
>> > and thinking more about it, is not what we want since although the
>> > site
>> > would be exported ok, we don't want to upload it to the GitHub pages
>> > like
>> > we discusses in the other thread due to expose part of the code of a
>> > commercial wp theme.
>> >
>> > So, the workflow we can use is: Use the WP backend to enter new
>> > content
>> > and
>> > modify existing want with ease (this is important is we want people
>> > contributing here). Next, with all changes done, generate a static
>> > version
>> > and replace the entire site with a fresh generated static site at
>> >
>>royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=http
>>%3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51
>>c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&s
>>data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0>. and
>>as well route the
>> more friendly domain to this
>> > if
>> > board is ok with that.
>> >
>> > Yes! External domain
>>royalysdk.org<https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>2F%2Froyalysdk.org%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=Dmo
>>CAUlAVHkkOp0uFdDH0%2FoUUU9qwdl00M8fWRe888Q%3D&reserved=0> is redirected
>> to
>>royale.apache.org<https://na01.safelinks.protection.outlook.com/?url=http
>>%3A%2F%2Froyale.apache.org%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51
>>c496496%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&s
>>data=QlbAmzJ21HAYHnJk6PhyGBH9%2Fp8e0afhsur%2B6uYGutU%3D&reserved=0> as
>> > discussed.
>> >
>> >
>> > We can check with apache board or trademarks what they propose about
>> > to
>> > create a
>>Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>2F%2Fwordpress.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=%2B
>>xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0> account
>>managed by Apache
>> and migrate from my
>> > server
>> > to that account, and all this stuff from there, since if I remember
>> > some
>> > people said that would be more ok with Apache.I'd end removing my temp
>> > subdomain after this.
>> >
>> > The advantage of using the
>>Wordpress.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%
>>2F%2Fwordpress.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%
>>7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=%2B
>>xX2xQ5c8v87RU%2Fj94l28qKtyHtXlRTfyII%2FHRNDyoI%3D&reserved=0>
>> location is twofold:
>> >
>> > (1) Wordpress keeps security up to date.
>> > (2) If something happens to you or your company then we have better
>> > access.
>> >
>> > I suspect though that with the status export method this will not be
>>as
>> > great a concern.
>> >
>> >
>> > What do you think? Can I move this with the people we were talking
>> > some
>> > weeks ago?
>> >
>> > Either you or I can email Trademarks with the plan.
>> >
>> > We can then discuss the redirection with Infrastructure and get the
>>site
>> > checked in.
>> >
>> > Regards,
>> > Dave
>> >
>> >
>> > Let me know in order to start making the next steps
>> >
>> > Thanks
>> >
>> >
>> > --
>> > Carlos Rovira
>> >
>> > https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fabout.me%
>> > 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>> 73f8%7Cfa7b1
>> > b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> sdata=1q5B1u1lLR
>> > HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>> >
>> >
>> >
>> >
>> > --
>> >
>> > <https://na01.safelinks.protection.outlook.com/?url=
>> http%3A%2F%2Fwww.codeo
>> >
>>scopic.com<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%
>>2Fscopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b
>>1b5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=oG9idkXzU
>>tg91G5vhl5P0Dn2u8gXX55UvN172PAlPXs%3D&reserved=0>&data=02%7C01%7C%
>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>> > 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> sdata=Y%2Fkytu4lJUWu5H
>> > zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2
>>Fcopic.com%2F&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b
>>5a7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=ZPPDqp5SNhK
>>C2rzYxfzkSV7f8lDtLmaRyyaMAlvtRcw%3D&reserved=0>&data=02%7C01%7C%
>> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>> > 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
>> 2Fkytu4lJUWu5Hz
>> > inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>> >
>> >
>> > Conocenos Avant2 en 1 minuto!
>> > <https://na01.safelinks.protection.outlook.com/?url=
>> https%3A%2F%2Favant2.e
>> > s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
>> 73f8%7Cfa7b1b5a
>> > 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
>> sdata=SJmmZQTVSb0tmX
>> > r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>> > 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.
>> >
>> >
>>
>>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=ZPowinnGs4jxxXQ4
>hULLfJLfWsGXx9zNLKnS9W7JoNY%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%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=ZPowinnGs4jxxXQ4h
>ULLfJLfWsGXx9zNLKnS9W7JoNY%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7Cdb97bd994ab24ee2f91c08d51c496496%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636446023931803217&sdata=ZiX3l%2FtQwsOG
>QN%2BibIJ5pxYpI5UboaH26BzM%2F9AtaLg%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
>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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Harbs is right,
to get something that looks cool and consistent is difficult and for this
reason I use wordpress+theme (in this case movedo). Is the same thing as
why people use flex or royale. Is the way to start from a point where you
are more efficient and maintenance can be assumed.
Alex, you see lots of difference since I customized via movedo interface
but as well did some tweaks in custom css (for example the footer column
menus)
So could we rework the site without wp and movedo. Sure, as I stated all
sites can be write in different ways, but the long term reason to adopt a
CMS like WP is to have a backend to introduce content of quality in the
most easy way while preserving quality on presentation (styles, fonts,
effects...)
I think we are in a situation where "the Apache way" fails completely since
we should be able to make this quick and easy and concentrate in our Royale
code, that is why we are here, and why I tried to go this path: to get
something that looks good and professional but to spend very few time for
our part.
I'm very pragmatic, and like to go to the point. All Apache rules should be
focused in protect the code we release, and we should have less trouble
with tools like WP, Jira, Nexus, and the rest. In fact Apache is using
those tools all along the way, why is so hard to do this?
We only need:
* Some host for a Wordpress instance: this could be the current Codeoscopic
subdomain or whatever people like. I'd be more happy if the wp instance is
in some server that could be controlled and maintained by ASF. I don't know
if this could be WP.com or some ASF's virtual machine that could host that.
* The Movedo theme: I write to Dimitri, from greatives. He is very
supportive and very like the idea, but is not in their hands. He point me
to talk with envato, and I write to them, but still doesn't have a
response. My thinking here is that we really don't need nothing of this.
Envato could donate a license but is only 59$, so is something affordable
by a simple donation.
* Finaly to generate an static site from WP. This is as well not needed,
but we can do it. People use to generate wp static version in order to
protect their sites from hacking. That's the only relevant point to do
this. So for me is something we can do if the rest of community wants it.
Is very easy to do.
Additionaly: As we are not uploading any website code to any ASF repo,
since as I said, it would be like to upload the JIRA source code to our
repos, and that doesn't give us anything (we're here to release only apache
royale code). we can :
1.- Use the royale.codeoscopic.com wp instance as the tool for us to modify
the site (people in our community will have user/pass in this wp instance
to create post and pages)
(in this way is similar to the server Alex had on his own to make some
apache flex task, correct me if I'm wrong)
Again, it can be royale.codeoscopic.com or other hosting ASF wants.
2.- Each time something changes: generate static site and deploy to
royale.apache.org
(in this case the set of static generated html/js/css could not be uploaded
to any ASF repo since we don't want to release the website code, that must
be served in the same way ASF serves JIRA, or whatever other commercial tool
Hosting a generated site with a movedo commercial theme needs of a 59$
license that could be donated by envato or donated for other person/company
(for example Codeoscopic)
For me this is quick and easy and I think we're not making something wrong
in legal terms
Carlos
2017-10-26 9:24 GMT+02:00 Harbs <ha...@gmail.com>:
> It’s using greatives’ CSS and JS files for styling, layout and effects.
>
> Generally, these themes have a lot of flexibility to change the look of a
> site without messing with CSS and JS.
>
> Can we re-write the CSS and JS to do the same kind of thing? Probably. But
> it would be a considerable amount of work.
>
> What’s included in the license? I’m really not sure.
>
> It gives rights to us the theme in WordPress. Does that allow repurposing
> the CSS and JS files for use elsewhere? I don’t know.
>
> Harbs
>
> > On Oct 26, 2017, at 9:56 AM, Alex Harui <ah...@adobe.com.INVALID>
> wrote:
> >
> > I'm still confused about something.
> >
> > Can someone explain how creativity and licensing are interconnected?
> I'm not familiar with WP themes, but I think they are templates with
> placeholders for particular aspects of a web page/blog. I've been told
> that this Royale site prototype is based on the Movedo theme. When I
> searched for it on the internet I ended up here: http://greatives.eu/
> themeforest/themeswitcher/?product=movedo#movedo
> >
> > It doesn't look at all like the prototype at
> http://royale.codeoscopic.com. Maybe the menu bar along the top?
> >
> > So what did we license from greatives? Can Carlos or someone else try
> to reproduce the prototype without looking at the current CSS and maybe use
> AL licensed fonts or something like that?
> >
> > Thanks,
> > -Alex
> >
> > From: Dave Fisher <da...@comcast.net>>
> > Reply-To: <de...@royale.apache.org>>
> > Date: Tuesday, October 24, 2017 at 11:06 AM
> > To: <de...@royale.apache.org>>
> > Subject: Re: Apache Royale static web site
> >
> > Hi Alex,
> >
> > We will need to ask Carlos to list out all of the themes he uses and
> then we will need to track things down and ask questions.
> >
> > Here is the site for what looks like the main theme:
> https://greatives.ticksy.com/
> >
> > It is the Move Do theme.
> >
> > Regards,
> > Dave
> >
> > On Oct 24, 2017, at 10:56 AM, Alex Harui <aharui@adobe.com.INVALID<
> mailto:aharui@adobe.com.INVALID>> wrote:
> >
> > Hi Dave,
> >
> > I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we
> have the rights to replicate use of that look-and-feel elsewhere? I don't
> understand who owns the creative content.
> >
> > Thoughts?
> > -Alex
> >
> > From: Dave Fisher <dave2wave@comcast.net<mailto:dave2wave@comcast.net
> ><ma...@comcast.net>>
> > Reply-To: <de...@royale.apache.org><mailto:
> dev@royale.apache.org>>
> > Date: Tuesday, October 24, 2017 at 10:50 AM
> > To: <de...@royale.apache.org><mailto:
> dev@royale.apache.org>>
> > Subject: Re: Apache Royale static web site
> >
> > Hi Alex,
> >
> > On Oct 24, 2017, at 10:43 AM, Alex Harui <aharui@adobe.com.INVALID<
> mailto:aharui@adobe.com.INVALID><ma...@adobe.com.INVALID>> wrote:
> >
> > There is something I don't think I understand. AIUI, at some point, we
> > will want the Apache Royale site to include actual Royale applications,
> > right? And I would think we would want the styling of those applications
> > to be consistent with the rest of the site. So I'm not clear how we will
> > be able to implement the styling/theme of these Royale applications if we
> > don't have rights to the styling. I don't understand how WP themes and
> > commercial licensing works if we want to replicate that user experience
> > outside of WP.
> >
> > We need to examine the static export of the CSS and HTML.
> >
> >
> > If we can use those visuals outside of WP, then why must we continue to
> > use WP to generate the site? I would hope the theme would be implemented
> > as CSS and some templates we could use without WP.
> >
> > We should be able to adapt. Site building in the CMS can get complex if
> needed. For OpenOffice.org<http://OpenOffice.org><http://OpenOffice.org>
> we use the legacy html pulling out the title and content body and place it
> within a markdown template.
> >
> >
> > Also, if someone wants to patch the site, they can't just offer a patch
> of
> > the HTML right? They would need to figure out where in WP it comes from?
> > Is there a patch process for WP content?
> >
> > Possibly.
> >
> >
> > Sorry if there is some basic thing I am missing.
> >
> > It will get complex first as we figure out how to embed and then it will
> get simplified as we find the best way.
> >
> > Regards,
> > Dave
> >
> >
> >
> > Thanks,
> > -Alex
> >
> > On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<mailto:
> carlos.rovira@gmail.com><ma...@gmail.com> on behalf of
> Carlos
> > Rovira" <ca...@gmail.com><mailto:
> carlos.rovira@gmail.com> on behalf of
> > carlos.rovira@codeoscopic.com<mailto:carlos.rovira@codeoscopic.com
> ><ma...@codeoscopic.com>> wrote:
> >
> > Thanks Dave,
> >
> > I'll write an email to trademarks to start with the process. I think is
> > better to migrate to WP.com<http://WP.com><http://WP.com> before
> continue working on content so we can
> > detect whatever issue we could get.
> >
> > Thanks!
> >
> > Carlos
> >
> >
> >
> > 2017-10-24 18:56 GMT+02:00 Dave Fisher <dave2wave@comcast.net<mailto:
> dave2wave@comcast.net><ma...@comcast.net>>:
> >
> > Hi Carlos,
> >
> > On Oct 24, 2017, at 9:30 AM, Carlos Rovira <carlosrovira@apache.org<
> mailto:carlosrovira@apache.org><ma...@apache.org>>
> > wrote:
> >
> > Hi,
> >
> > just let you know that I tried to create an static version of the
> > preview
> > site with success. I use this plugin :
> >
> > https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Fwordpres
> > s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%
> 7Cb448363ee5984b3b3e0f
> > 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178de
> cee1%7C0%7C0%7C636444624020033
> > 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
> >
> > and we can generate all static content with relative or absolute urls.
> > The
> > final preview site in static is 134mb
> >
> > Another thing I was searching was to use a WP to Jekyll exporter but
> > this
> > is not what I wanted since it seems Jekyll is all about markdown and
> > we
> > want a full html site with all the eye candy JS+CSS resources. In the
> > end,
> > and thinking more about it, is not what we want since although the
> > site
> > would be exported ok, we don't want to upload it to the GitHub pages
> > like
> > we discusses in the other thread due to expose part of the code of a
> > commercial wp theme.
> >
> > So, the workflow we can use is: Use the WP backend to enter new
> > content
> > and
> > modify existing want with ease (this is important is we want people
> > contributing here). Next, with all changes done, generate a static
> > version
> > and replace the entire site with a fresh generated static site at
> > royale.apache.org<http://royale.apache.org/>. and as well route the
> more friendly domain to this
> > if
> > board is ok with that.
> >
> > Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected
> to royale.apache.org<http://royale.apache.org/> as
> > discussed.
> >
> >
> > We can check with apache board or trademarks what they propose about
> > to
> > create a Wordpress.com<http://wordpress.com/> account managed by Apache
> and migrate from my
> > server
> > to that account, and all this stuff from there, since if I remember
> > some
> > people said that would be more ok with Apache.I'd end removing my temp
> > subdomain after this.
> >
> > The advantage of using the Wordpress.com<http://wordpress.com/>
> location is twofold:
> >
> > (1) Wordpress keeps security up to date.
> > (2) If something happens to you or your company then we have better
> > access.
> >
> > I suspect though that with the status export method this will not be as
> > great a concern.
> >
> >
> > What do you think? Can I move this with the people we were talking
> > some
> > weeks ago?
> >
> > Either you or I can email Trademarks with the plan.
> >
> > We can then discuss the redirection with Infrastructure and get the site
> > checked in.
> >
> > Regards,
> > Dave
> >
> >
> > Let me know in order to start making the next steps
> >
> > Thanks
> >
> >
> > --
> > Carlos Rovira
> >
> > https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fabout.me%
> > 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> 73f8%7Cfa7b1
> > b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> sdata=1q5B1u1lLR
> > HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
> >
> >
> >
> >
> > --
> >
> > <https://na01.safelinks.protection.outlook.com/?url=
> http%3A%2F%2Fwww.codeo
> > scopic.com<http://scopic.com/>&data=02%7C01%7C%
> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> > 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> sdata=Y%2Fkytu4lJUWu5H
> > zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%
> 7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> > 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%
> 2Fkytu4lJUWu5Hz
> > inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
> >
> >
> > Conocenos Avant2 en 1 minuto!
> > <https://na01.safelinks.protection.outlook.com/?url=
> https%3A%2F%2Favant2.e
> > s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b03
> 73f8%7Cfa7b1b5a
> > 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&
> sdata=SJmmZQTVSb0tmX
> > r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> > 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.
> >
> >
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Harbs <ha...@gmail.com>.
It’s using greatives’ CSS and JS files for styling, layout and effects.
Generally, these themes have a lot of flexibility to change the look of a site without messing with CSS and JS.
Can we re-write the CSS and JS to do the same kind of thing? Probably. But it would be a considerable amount of work.
What’s included in the license? I’m really not sure.
It gives rights to us the theme in WordPress. Does that allow repurposing the CSS and JS files for use elsewhere? I don’t know.
Harbs
> On Oct 26, 2017, at 9:56 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> I'm still confused about something.
>
> Can someone explain how creativity and licensing are interconnected? I'm not familiar with WP themes, but I think they are templates with placeholders for particular aspects of a web page/blog. I've been told that this Royale site prototype is based on the Movedo theme. When I searched for it on the internet I ended up here: http://greatives.eu/themeforest/themeswitcher/?product=movedo#movedo
>
> It doesn't look at all like the prototype at http://royale.codeoscopic.com. Maybe the menu bar along the top?
>
> So what did we license from greatives? Can Carlos or someone else try to reproduce the prototype without looking at the current CSS and maybe use AL licensed fonts or something like that?
>
> Thanks,
> -Alex
>
> From: Dave Fisher <da...@comcast.net>>
> Reply-To: <de...@royale.apache.org>>
> Date: Tuesday, October 24, 2017 at 11:06 AM
> To: <de...@royale.apache.org>>
> Subject: Re: Apache Royale static web site
>
> Hi Alex,
>
> We will need to ask Carlos to list out all of the themes he uses and then we will need to track things down and ask questions.
>
> Here is the site for what looks like the main theme: https://greatives.ticksy.com/
>
> It is the Move Do theme.
>
> Regards,
> Dave
>
> On Oct 24, 2017, at 10:56 AM, Alex Harui <ah...@adobe.com.INVALID>> wrote:
>
> Hi Dave,
>
> I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we have the rights to replicate use of that look-and-feel elsewhere? I don't understand who owns the creative content.
>
> Thoughts?
> -Alex
>
> From: Dave Fisher <da...@comcast.net>>
> Reply-To: <de...@royale.apache.org>>
> Date: Tuesday, October 24, 2017 at 10:50 AM
> To: <de...@royale.apache.org>>
> Subject: Re: Apache Royale static web site
>
> Hi Alex,
>
> On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID>> wrote:
>
> There is something I don't think I understand. AIUI, at some point, we
> will want the Apache Royale site to include actual Royale applications,
> right? And I would think we would want the styling of those applications
> to be consistent with the rest of the site. So I'm not clear how we will
> be able to implement the styling/theme of these Royale applications if we
> don't have rights to the styling. I don't understand how WP themes and
> commercial licensing works if we want to replicate that user experience
> outside of WP.
>
> We need to examine the static export of the CSS and HTML.
>
>
> If we can use those visuals outside of WP, then why must we continue to
> use WP to generate the site? I would hope the theme would be implemented
> as CSS and some templates we could use without WP.
>
> We should be able to adapt. Site building in the CMS can get complex if needed. For OpenOffice.org<http://OpenOffice.org><http://OpenOffice.org> we use the legacy html pulling out the title and content body and place it within a markdown template.
>
>
> Also, if someone wants to patch the site, they can't just offer a patch of
> the HTML right? They would need to figure out where in WP it comes from?
> Is there a patch process for WP content?
>
> Possibly.
>
>
> Sorry if there is some basic thing I am missing.
>
> It will get complex first as we figure out how to embed and then it will get simplified as we find the best way.
>
> Regards,
> Dave
>
>
>
> Thanks,
> -Alex
>
> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<ma...@gmail.com> on behalf of Carlos
> Rovira" <ca...@gmail.com> on behalf of
> carlos.rovira@codeoscopic.com<ma...@codeoscopic.com>> wrote:
>
> Thanks Dave,
>
> I'll write an email to trademarks to start with the process. I think is
> better to migrate to WP.com<http://WP.com><http://WP.com> before continue working on content so we can
> detect whatever issue we could get.
>
> Thanks!
>
> Carlos
>
>
>
> 2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>>:
>
> Hi Carlos,
>
> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>>
> wrote:
>
> Hi,
>
> just let you know that I tried to create an static version of the
> preview
> site with success. I use this plugin :
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
> s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>
> and we can generate all static content with relative or absolute urls.
> The
> final preview site in static is 134mb
>
> Another thing I was searching was to use a WP to Jekyll exporter but
> this
> is not what I wanted since it seems Jekyll is all about markdown and
> we
> want a full html site with all the eye candy JS+CSS resources. In the
> end,
> and thinking more about it, is not what we want since although the
> site
> would be exported ok, we don't want to upload it to the GitHub pages
> like
> we discusses in the other thread due to expose part of the code of a
> commercial wp theme.
>
> So, the workflow we can use is: Use the WP backend to enter new
> content
> and
> modify existing want with ease (this is important is we want people
> contributing here). Next, with all changes done, generate a static
> version
> and replace the entire site with a fresh generated static site at
> royale.apache.org<http://royale.apache.org/>. and as well route the more friendly domain to this
> if
> board is ok with that.
>
> Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected to royale.apache.org<http://royale.apache.org/> as
> discussed.
>
>
> We can check with apache board or trademarks what they propose about
> to
> create a Wordpress.com<http://wordpress.com/> account managed by Apache and migrate from my
> server
> to that account, and all this stuff from there, since if I remember
> some
> people said that would be more ok with Apache.I'd end removing my temp
> subdomain after this.
>
> The advantage of using the Wordpress.com<http://wordpress.com/> location is twofold:
>
> (1) Wordpress keeps security up to date.
> (2) If something happens to you or your company then we have better
> access.
>
> I suspect though that with the status export method this will not be as
> great a concern.
>
>
> What do you think? Can I move this with the people we were talking
> some
> weeks ago?
>
> Either you or I can email Trademarks with the plan.
>
> We can then discuss the redirection with Infrastructure and get the site
> checked in.
>
> Regards,
> Dave
>
>
> Let me know in order to start making the next steps
>
> Thanks
>
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>
>
>
>
> --
>
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
> scopic.com<http://scopic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>
>
> Conocenos Avant2 en 1 minuto!
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> 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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
I'm still confused about something.
Can someone explain how creativity and licensing are interconnected? I'm not familiar with WP themes, but I think they are templates with placeholders for particular aspects of a web page/blog. I've been told that this Royale site prototype is based on the Movedo theme. When I searched for it on the internet I ended up here: http://greatives.eu/themeforest/themeswitcher/?product=movedo#movedo
It doesn't look at all like the prototype at http://royale.codeoscopic.com. Maybe the menu bar along the top?
So what did we license from greatives? Can Carlos or someone else try to reproduce the prototype without looking at the current CSS and maybe use AL licensed fonts or something like that?
Thanks,
-Alex
From: Dave Fisher <da...@comcast.net>>
Reply-To: <de...@royale.apache.org>>
Date: Tuesday, October 24, 2017 at 11:06 AM
To: <de...@royale.apache.org>>
Subject: Re: Apache Royale static web site
Hi Alex,
We will need to ask Carlos to list out all of the themes he uses and then we will need to track things down and ask questions.
Here is the site for what looks like the main theme: https://greatives.ticksy.com/
It is the Move Do theme.
Regards,
Dave
On Oct 24, 2017, at 10:56 AM, Alex Harui <ah...@adobe.com.INVALID>> wrote:
Hi Dave,
I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we have the rights to replicate use of that look-and-feel elsewhere? I don't understand who owns the creative content.
Thoughts?
-Alex
From: Dave Fisher <da...@comcast.net>>
Reply-To: <de...@royale.apache.org>>
Date: Tuesday, October 24, 2017 at 10:50 AM
To: <de...@royale.apache.org>>
Subject: Re: Apache Royale static web site
Hi Alex,
On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID>> wrote:
There is something I don't think I understand. AIUI, at some point, we
will want the Apache Royale site to include actual Royale applications,
right? And I would think we would want the styling of those applications
to be consistent with the rest of the site. So I'm not clear how we will
be able to implement the styling/theme of these Royale applications if we
don't have rights to the styling. I don't understand how WP themes and
commercial licensing works if we want to replicate that user experience
outside of WP.
We need to examine the static export of the CSS and HTML.
If we can use those visuals outside of WP, then why must we continue to
use WP to generate the site? I would hope the theme would be implemented
as CSS and some templates we could use without WP.
We should be able to adapt. Site building in the CMS can get complex if needed. For OpenOffice.org<http://OpenOffice.org><http://OpenOffice.org> we use the legacy html pulling out the title and content body and place it within a markdown template.
Also, if someone wants to patch the site, they can't just offer a patch of
the HTML right? They would need to figure out where in WP it comes from?
Is there a patch process for WP content?
Possibly.
Sorry if there is some basic thing I am missing.
It will get complex first as we figure out how to embed and then it will get simplified as we find the best way.
Regards,
Dave
Thanks,
-Alex
On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<ma...@gmail.com> on behalf of Carlos
Rovira" <ca...@gmail.com> on behalf of
carlos.rovira@codeoscopic.com<ma...@codeoscopic.com>> wrote:
Thanks Dave,
I'll write an email to trademarks to start with the process. I think is
better to migrate to WP.com<http://WP.com><http://WP.com> before continue working on content so we can
detect whatever issue we could get.
Thanks!
Carlos
2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>>:
Hi Carlos,
On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>>
wrote:
Hi,
just let you know that I tried to create an static version of the
preview
site with success. I use this plugin :
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
and we can generate all static content with relative or absolute urls.
The
final preview site in static is 134mb
Another thing I was searching was to use a WP to Jekyll exporter but
this
is not what I wanted since it seems Jekyll is all about markdown and
we
want a full html site with all the eye candy JS+CSS resources. In the
end,
and thinking more about it, is not what we want since although the
site
would be exported ok, we don't want to upload it to the GitHub pages
like
we discusses in the other thread due to expose part of the code of a
commercial wp theme.
So, the workflow we can use is: Use the WP backend to enter new
content
and
modify existing want with ease (this is important is we want people
contributing here). Next, with all changes done, generate a static
version
and replace the entire site with a fresh generated static site at
royale.apache.org<http://royale.apache.org/>. and as well route the more friendly domain to this
if
board is ok with that.
Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected to royale.apache.org<http://royale.apache.org/> as
discussed.
We can check with apache board or trademarks what they propose about
to
create a Wordpress.com<http://wordpress.com/> account managed by Apache and migrate from my
server
to that account, and all this stuff from there, since if I remember
some
people said that would be more ok with Apache.I'd end removing my temp
subdomain after this.
The advantage of using the Wordpress.com<http://wordpress.com/> location is twofold:
(1) Wordpress keeps security up to date.
(2) If something happens to you or your company then we have better
access.
I suspect though that with the status export method this will not be as
great a concern.
What do you think? Can I move this with the people we were talking
some
weeks ago?
Either you or I can email Trademarks with the plan.
We can then discuss the redirection with Infrastructure and get the site
checked in.
Regards,
Dave
Let me know in order to start making the next steps
Thanks
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
--
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
scopic.com<http://scopic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
Conocenos Avant2 en 1 minuto!
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
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: Apache Royale static web site
Posted by Dave Fisher <da...@comcast.net>.
Hi Alex,
We will need to ask Carlos to list out all of the themes he uses and then we will need to track things down and ask questions.
Here is the site for what looks like the main theme: https://greatives.ticksy.com/ <https://greatives.ticksy.com/>
It is the Move Do theme.
Regards,
Dave
> On Oct 24, 2017, at 10:56 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> Hi Dave,
>
> I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we have the rights to replicate use of that look-and-feel elsewhere? I don't understand who owns the creative content.
>
> Thoughts?
> -Alex
>
> From: Dave Fisher <da...@comcast.net>>
> Reply-To: <de...@royale.apache.org>>
> Date: Tuesday, October 24, 2017 at 10:50 AM
> To: <de...@royale.apache.org>>
> Subject: Re: Apache Royale static web site
>
> Hi Alex,
>
> On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID>> wrote:
>
> There is something I don't think I understand. AIUI, at some point, we
> will want the Apache Royale site to include actual Royale applications,
> right? And I would think we would want the styling of those applications
> to be consistent with the rest of the site. So I'm not clear how we will
> be able to implement the styling/theme of these Royale applications if we
> don't have rights to the styling. I don't understand how WP themes and
> commercial licensing works if we want to replicate that user experience
> outside of WP.
>
> We need to examine the static export of the CSS and HTML.
>
>
> If we can use those visuals outside of WP, then why must we continue to
> use WP to generate the site? I would hope the theme would be implemented
> as CSS and some templates we could use without WP.
>
> We should be able to adapt. Site building in the CMS can get complex if needed. For OpenOffice.org<http://OpenOffice.org> we use the legacy html pulling out the title and content body and place it within a markdown template.
>
>
> Also, if someone wants to patch the site, they can't just offer a patch of
> the HTML right? They would need to figure out where in WP it comes from?
> Is there a patch process for WP content?
>
> Possibly.
>
>
> Sorry if there is some basic thing I am missing.
>
> It will get complex first as we figure out how to embed and then it will get simplified as we find the best way.
>
> Regards,
> Dave
>
>
>
> Thanks,
> -Alex
>
> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<ma...@gmail.com> on behalf of Carlos
> Rovira" <ca...@gmail.com> on behalf of
> carlos.rovira@codeoscopic.com<ma...@codeoscopic.com>> wrote:
>
> Thanks Dave,
>
> I'll write an email to trademarks to start with the process. I think is
> better to migrate to WP.com<http://WP.com> before continue working on content so we can
> detect whatever issue we could get.
>
> Thanks!
>
> Carlos
>
>
>
> 2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>>:
>
> Hi Carlos,
>
> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>>
> wrote:
>
> Hi,
>
> just let you know that I tried to create an static version of the
> preview
> site with success. I use this plugin :
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
> s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>
> and we can generate all static content with relative or absolute urls.
> The
> final preview site in static is 134mb
>
> Another thing I was searching was to use a WP to Jekyll exporter but
> this
> is not what I wanted since it seems Jekyll is all about markdown and
> we
> want a full html site with all the eye candy JS+CSS resources. In the
> end,
> and thinking more about it, is not what we want since although the
> site
> would be exported ok, we don't want to upload it to the GitHub pages
> like
> we discusses in the other thread due to expose part of the code of a
> commercial wp theme.
>
> So, the workflow we can use is: Use the WP backend to enter new
> content
> and
> modify existing want with ease (this is important is we want people
> contributing here). Next, with all changes done, generate a static
> version
> and replace the entire site with a fresh generated static site at
> royale.apache.org<http://royale.apache.org/>. and as well route the more friendly domain to this
> if
> board is ok with that.
>
> Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected to royale.apache.org<http://royale.apache.org/> as
> discussed.
>
>
> We can check with apache board or trademarks what they propose about
> to
> create a Wordpress.com<http://wordpress.com/> account managed by Apache and migrate from my
> server
> to that account, and all this stuff from there, since if I remember
> some
> people said that would be more ok with Apache.I'd end removing my temp
> subdomain after this.
>
> The advantage of using the Wordpress.com<http://wordpress.com/> location is twofold:
>
> (1) Wordpress keeps security up to date.
> (2) If something happens to you or your company then we have better
> access.
>
> I suspect though that with the status export method this will not be as
> great a concern.
>
>
> What do you think? Can I move this with the people we were talking
> some
> weeks ago?
>
> Either you or I can email Trademarks with the plan.
>
> We can then discuss the redirection with Infrastructure and get the site
> checked in.
>
> Regards,
> Dave
>
>
> Let me know in order to start making the next steps
>
> Thanks
>
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>
>
>
>
> --
>
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
> scopic.com<http://scopic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>
>
> Conocenos Avant2 en 1 minuto!
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> 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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
Hi Dave,
I'm still wondering, even if we can see and reuse the CSS/JS/HTML, do we have the rights to replicate use of that look-and-feel elsewhere? I don't understand who owns the creative content.
Thoughts?
-Alex
From: Dave Fisher <da...@comcast.net>>
Reply-To: <de...@royale.apache.org>>
Date: Tuesday, October 24, 2017 at 10:50 AM
To: <de...@royale.apache.org>>
Subject: Re: Apache Royale static web site
Hi Alex,
On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID>> wrote:
There is something I don't think I understand. AIUI, at some point, we
will want the Apache Royale site to include actual Royale applications,
right? And I would think we would want the styling of those applications
to be consistent with the rest of the site. So I'm not clear how we will
be able to implement the styling/theme of these Royale applications if we
don't have rights to the styling. I don't understand how WP themes and
commercial licensing works if we want to replicate that user experience
outside of WP.
We need to examine the static export of the CSS and HTML.
If we can use those visuals outside of WP, then why must we continue to
use WP to generate the site? I would hope the theme would be implemented
as CSS and some templates we could use without WP.
We should be able to adapt. Site building in the CMS can get complex if needed. For OpenOffice.org<http://OpenOffice.org> we use the legacy html pulling out the title and content body and place it within a markdown template.
Also, if someone wants to patch the site, they can't just offer a patch of
the HTML right? They would need to figure out where in WP it comes from?
Is there a patch process for WP content?
Possibly.
Sorry if there is some basic thing I am missing.
It will get complex first as we figure out how to embed and then it will get simplified as we find the best way.
Regards,
Dave
Thanks,
-Alex
On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com<ma...@gmail.com> on behalf of Carlos
Rovira" <ca...@gmail.com> on behalf of
carlos.rovira@codeoscopic.com<ma...@codeoscopic.com>> wrote:
Thanks Dave,
I'll write an email to trademarks to start with the process. I think is
better to migrate to WP.com<http://WP.com> before continue working on content so we can
detect whatever issue we could get.
Thanks!
Carlos
2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>>:
Hi Carlos,
On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>>
wrote:
Hi,
just let you know that I tried to create an static version of the
preview
site with success. I use this plugin :
https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
s.org<http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
and we can generate all static content with relative or absolute urls.
The
final preview site in static is 134mb
Another thing I was searching was to use a WP to Jekyll exporter but
this
is not what I wanted since it seems Jekyll is all about markdown and
we
want a full html site with all the eye candy JS+CSS resources. In the
end,
and thinking more about it, is not what we want since although the
site
would be exported ok, we don't want to upload it to the GitHub pages
like
we discusses in the other thread due to expose part of the code of a
commercial wp theme.
So, the workflow we can use is: Use the WP backend to enter new
content
and
modify existing want with ease (this is important is we want people
contributing here). Next, with all changes done, generate a static
version
and replace the entire site with a fresh generated static site at
royale.apache.org<http://royale.apache.org/>. and as well route the more friendly domain to this
if
board is ok with that.
Yes! External domain royalysdk.org<http://royalysdk.org/> is redirected to royale.apache.org<http://royale.apache.org/> as
discussed.
We can check with apache board or trademarks what they propose about
to
create a Wordpress.com<http://wordpress.com/> account managed by Apache and migrate from my
server
to that account, and all this stuff from there, since if I remember
some
people said that would be more ok with Apache.I'd end removing my temp
subdomain after this.
The advantage of using the Wordpress.com<http://wordpress.com/> location is twofold:
(1) Wordpress keeps security up to date.
(2) If something happens to you or your company then we have better
access.
I suspect though that with the status export method this will not be as
great a concern.
What do you think? Can I move this with the people we were talking
some
weeks ago?
Either you or I can email Trademarks with the plan.
We can then discuss the redirection with Infrastructure and get the site
checked in.
Regards,
Dave
Let me know in order to start making the next steps
Thanks
--
Carlos Rovira
https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
--
<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
scopic.com<http://scopic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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<http://copic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
Conocenos Avant2 en 1 minuto!
<https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
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: Apache Royale static web site
Posted by Dave Fisher <da...@comcast.net>.
Hi Carlos,
> On Oct 24, 2017, at 11:09 AM, Carlos Rovira <ca...@codeoscopic.com> wrote:
>
> Hi Alex, Dave,
>
> to create some Apps in Royale that conform to the actual theme is easy and
> while we make it with our own code it will be completly legal. This about a
> button. If we need to put a button that is equal to other button, we can
> create a CSS rule that makes that button looks almost equal to the other
> one, but with our own css classname. Being said that I think we don't need
> to create "try it now" app (for example) with the same branding, since is a
> tool inside, and you can see other similar efforts done by others (i.e:
> Typescript) where you are showing an app with a text editor and execution
> window. This should look as what it is...more like an editor of source code
> with pre and code tags and monospace fonts ;)
>
> regarding the rest of the site. As we talked in the other thread with
> Harbs, we don't need to upload source code of the site (I talked in some
> occasions about the JIRA similarity, of a tool that we use but we don't
> need to expose or upload to some repo the source code). So people will want
> instead to generate some article, a post or an example (like
> flexexamples.org from Peter's blog that we want to make at some time for
> Royale). So we already want to give folks some easy tool to make this
> community effort possible. For me actual Apache CMS content is what we want
> to avoid, since is something cumbersome and at least for me made me does
> not work on this before.
>
> With the path I propose, al people that wants to make something in the site
> will have a WP.com user with "EDITOR" profile that will allow them to
> create a post or a page and make some content.
>
> To go live we regenerate the site and publish in the production url.
>
> Hope you'll find this procedure ok? I think is the way more easy and will
> allow us to focus on what really matters: Apache Royale source code. At the
> end of the day, we don't want to spend more time in the web that absolutely
> needed since is not the product we develop.
Rather than republishing the whole site each time I would prefer that it be done as a diff. But that is a detail to work out later.
There may be parts of the site where we want the template to be the WP themed page with the content being something from the examples.
Regards,
Dave
>
> Thanks
>
>
>
>
>
>
> 2017-10-24 19:50 GMT+02:00 Dave Fisher <da...@comcast.net>:
>
>> Hi Alex,
>>
>> On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>>
>> There is something I don't think I understand. AIUI, at some point, we
>> will want the Apache Royale site to include actual Royale applications,
>> right? And I would think we would want the styling of those applications
>> to be consistent with the rest of the site. So I'm not clear how we will
>> be able to implement the styling/theme of these Royale applications if we
>> don't have rights to the styling. I don't understand how WP themes and
>> commercial licensing works if we want to replicate that user experience
>> outside of WP.
>>
>>
>> We need to examine the static export of the CSS and HTML.
>>
>>
>> If we can use those visuals outside of WP, then why must we continue to
>> use WP to generate the site? I would hope the theme would be implemented
>> as CSS and some templates we could use without WP.
>>
>>
>> We should be able to adapt. Site building in the CMS can get complex if
>> needed. For OpenOffice.org we use the legacy html pulling out the title
>> and content body and place it within a markdown template.
>>
>>
>> Also, if someone wants to patch the site, they can't just offer a patch of
>> the HTML right? They would need to figure out where in WP it comes from?
>> Is there a patch process for WP content?
>>
>>
>> Possibly.
>>
>>
>> Sorry if there is some basic thing I am missing.
>>
>>
>> It will get complex first as we figure out how to embed and then it will
>> get simplified as we find the best way.
>>
>> Regards,
>> Dave
>>
>>
>>
>> Thanks,
>> -Alex
>>
>> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com on behalf of Carlos
>> Rovira" <carlos.rovira@gmail.com on behalf of
>> carlos.rovira@codeoscopic.com> wrote:
>>
>> Thanks Dave,
>>
>> I'll write an email to trademarks to start with the process. I think is
>> better to migrate to WP.com before continue working on content so we can
>> detect whatever issue we could get.
>>
>> Thanks!
>>
>> Carlos
>>
>>
>>
>> 2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>:
>>
>> Hi Carlos,
>>
>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>
>>
>> wrote:
>>
>>
>> Hi,
>>
>> just let you know that I tried to create an static version of the
>>
>> preview
>>
>> site with success. I use this plugin :
>>
>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
>> s.org%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>>
>>
>> and we can generate all static content with relative or absolute urls.
>>
>> The
>>
>> final preview site in static is 134mb
>>
>> Another thing I was searching was to use a WP to Jekyll exporter but
>>
>> this
>>
>> is not what I wanted since it seems Jekyll is all about markdown and
>>
>> we
>>
>> want a full html site with all the eye candy JS+CSS resources. In the
>>
>> end,
>>
>> and thinking more about it, is not what we want since although the
>>
>> site
>>
>> would be exported ok, we don't want to upload it to the GitHub pages
>>
>> like
>>
>> we discusses in the other thread due to expose part of the code of a
>> commercial wp theme.
>>
>> So, the workflow we can use is: Use the WP backend to enter new
>>
>> content
>> and
>>
>> modify existing want with ease (this is important is we want people
>> contributing here). Next, with all changes done, generate a static
>>
>> version
>>
>> and replace the entire site with a fresh generated static site at
>> royale.apache.org. and as well route the more friendly domain to this
>>
>> if
>>
>> board is ok with that.
>>
>>
>> Yes! External domain royalysdk.org is redirected to royale.apache.org as
>> discussed.
>>
>>
>> We can check with apache board or trademarks what they propose about
>>
>> to
>>
>> create a Wordpress.com <http://wordpress.com/> account managed by Apache
>> and migrate from my
>>
>> server
>>
>> to that account, and all this stuff from there, since if I remember
>>
>> some
>>
>> people said that would be more ok with Apache.I'd end removing my temp
>> subdomain after this.
>>
>>
>> The advantage of using the Wordpress.com <http://wordpress.com/> location
>> is twofold:
>>
>> (1) Wordpress keeps security up to date.
>> (2) If something happens to you or your company then we have better
>> access.
>>
>> I suspect though that with the status export method this will not be as
>> great a concern.
>>
>>
>> What do you think? Can I move this with the people we were talking
>>
>> some
>>
>> weeks ago?
>>
>>
>> Either you or I can email Trademarks with the plan.
>>
>> We can then discuss the redirection with Infrastructure and get the site
>> checked in.
>>
>> Regards,
>> Dave
>>
>>
>> Let me know in order to start making the next steps
>>
>> Thanks
>>
>>
>> --
>> Carlos Rovira
>>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>>
>>
>>
>>
>> --
>>
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>> scopic.com&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0>
>>
>> Carlos Rovira
>>
>> Director General
>>
>> M: +34 607 22 60 05 <607%2022%2060%2005>
>>
>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
>> copic.com&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>>
>>
>> Conocenos Avant2 en 1 minuto!
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>> 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.
>>
>>
>>
>
>
> --
>
> <http://www.codeoscopic.com>
>
> Carlos Rovira
>
> Director General
>
> M: +34 607 22 60 05
>
> http://www.codeoscopic.com
>
>
> Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
>
>
> 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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Hi Alex, Dave,
to create some Apps in Royale that conform to the actual theme is easy and
while we make it with our own code it will be completly legal. This about a
button. If we need to put a button that is equal to other button, we can
create a CSS rule that makes that button looks almost equal to the other
one, but with our own css classname. Being said that I think we don't need
to create "try it now" app (for example) with the same branding, since is a
tool inside, and you can see other similar efforts done by others (i.e:
Typescript) where you are showing an app with a text editor and execution
window. This should look as what it is...more like an editor of source code
with pre and code tags and monospace fonts ;)
regarding the rest of the site. As we talked in the other thread with
Harbs, we don't need to upload source code of the site (I talked in some
occasions about the JIRA similarity, of a tool that we use but we don't
need to expose or upload to some repo the source code). So people will want
instead to generate some article, a post or an example (like
flexexamples.org from Peter's blog that we want to make at some time for
Royale). So we already want to give folks some easy tool to make this
community effort possible. For me actual Apache CMS content is what we want
to avoid, since is something cumbersome and at least for me made me does
not work on this before.
With the path I propose, al people that wants to make something in the site
will have a WP.com user with "EDITOR" profile that will allow them to
create a post or a page and make some content.
To go live we regenerate the site and publish in the production url.
Hope you'll find this procedure ok? I think is the way more easy and will
allow us to focus on what really matters: Apache Royale source code. At the
end of the day, we don't want to spend more time in the web that absolutely
needed since is not the product we develop.
Thanks
2017-10-24 19:50 GMT+02:00 Dave Fisher <da...@comcast.net>:
> Hi Alex,
>
> On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> There is something I don't think I understand. AIUI, at some point, we
> will want the Apache Royale site to include actual Royale applications,
> right? And I would think we would want the styling of those applications
> to be consistent with the rest of the site. So I'm not clear how we will
> be able to implement the styling/theme of these Royale applications if we
> don't have rights to the styling. I don't understand how WP themes and
> commercial licensing works if we want to replicate that user experience
> outside of WP.
>
>
> We need to examine the static export of the CSS and HTML.
>
>
> If we can use those visuals outside of WP, then why must we continue to
> use WP to generate the site? I would hope the theme would be implemented
> as CSS and some templates we could use without WP.
>
>
> We should be able to adapt. Site building in the CMS can get complex if
> needed. For OpenOffice.org we use the legacy html pulling out the title
> and content body and place it within a markdown template.
>
>
> Also, if someone wants to patch the site, they can't just offer a patch of
> the HTML right? They would need to figure out where in WP it comes from?
> Is there a patch process for WP content?
>
>
> Possibly.
>
>
> Sorry if there is some basic thing I am missing.
>
>
> It will get complex first as we figure out how to embed and then it will
> get simplified as we find the best way.
>
> Regards,
> Dave
>
>
>
> Thanks,
> -Alex
>
> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com on behalf of Carlos
> Rovira" <carlos.rovira@gmail.com on behalf of
> carlos.rovira@codeoscopic.com> wrote:
>
> Thanks Dave,
>
> I'll write an email to trademarks to start with the process. I think is
> better to migrate to WP.com before continue working on content so we can
> detect whatever issue we could get.
>
> Thanks!
>
> Carlos
>
>
>
> 2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>:
>
> Hi Carlos,
>
> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>
>
> wrote:
>
>
> Hi,
>
> just let you know that I tried to create an static version of the
>
> preview
>
> site with success. I use this plugin :
>
> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
> s.org%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>
>
> and we can generate all static content with relative or absolute urls.
>
> The
>
> final preview site in static is 134mb
>
> Another thing I was searching was to use a WP to Jekyll exporter but
>
> this
>
> is not what I wanted since it seems Jekyll is all about markdown and
>
> we
>
> want a full html site with all the eye candy JS+CSS resources. In the
>
> end,
>
> and thinking more about it, is not what we want since although the
>
> site
>
> would be exported ok, we don't want to upload it to the GitHub pages
>
> like
>
> we discusses in the other thread due to expose part of the code of a
> commercial wp theme.
>
> So, the workflow we can use is: Use the WP backend to enter new
>
> content
> and
>
> modify existing want with ease (this is important is we want people
> contributing here). Next, with all changes done, generate a static
>
> version
>
> and replace the entire site with a fresh generated static site at
> royale.apache.org. and as well route the more friendly domain to this
>
> if
>
> board is ok with that.
>
>
> Yes! External domain royalysdk.org is redirected to royale.apache.org as
> discussed.
>
>
> We can check with apache board or trademarks what they propose about
>
> to
>
> create a Wordpress.com <http://wordpress.com/> account managed by Apache
> and migrate from my
>
> server
>
> to that account, and all this stuff from there, since if I remember
>
> some
>
> people said that would be more ok with Apache.I'd end removing my temp
> subdomain after this.
>
>
> The advantage of using the Wordpress.com <http://wordpress.com/> location
> is twofold:
>
> (1) Wordpress keeps security up to date.
> (2) If something happens to you or your company then we have better
> access.
>
> I suspect though that with the status export method this will not be as
> great a concern.
>
>
> What do you think? Can I move this with the people we were talking
>
> some
>
> weeks ago?
>
>
> Either you or I can email Trademarks with the plan.
>
> We can then discuss the redirection with Infrastructure and get the site
> checked in.
>
> Regards,
> Dave
>
>
> Let me know in order to start making the next steps
>
> Thanks
>
>
> --
> Carlos Rovira
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>
>
>
>
> --
>
> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
> scopic.com&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0>
>
> Carlos Rovira
>
> Director General
>
> M: +34 607 22 60 05 <607%2022%2060%2005>
>
> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos
> copic.com&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>
>
> Conocenos Avant2 en 1 minuto!
> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
> 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.
>
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Dave Fisher <da...@comcast.net>.
Hi Alex,
> On Oct 24, 2017, at 10:43 AM, Alex Harui <ah...@adobe.com.INVALID> wrote:
>
> There is something I don't think I understand. AIUI, at some point, we
> will want the Apache Royale site to include actual Royale applications,
> right? And I would think we would want the styling of those applications
> to be consistent with the rest of the site. So I'm not clear how we will
> be able to implement the styling/theme of these Royale applications if we
> don't have rights to the styling. I don't understand how WP themes and
> commercial licensing works if we want to replicate that user experience
> outside of WP.
We need to examine the static export of the CSS and HTML.
>
> If we can use those visuals outside of WP, then why must we continue to
> use WP to generate the site? I would hope the theme would be implemented
> as CSS and some templates we could use without WP.
We should be able to adapt. Site building in the CMS can get complex if needed. For OpenOffice.org we use the legacy html pulling out the title and content body and place it within a markdown template.
>
> Also, if someone wants to patch the site, they can't just offer a patch of
> the HTML right? They would need to figure out where in WP it comes from?
> Is there a patch process for WP content?
Possibly.
>
> Sorry if there is some basic thing I am missing.
It will get complex first as we figure out how to embed and then it will get simplified as we find the best way.
Regards,
Dave
>
> Thanks,
> -Alex
>
> On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com <ma...@gmail.com> on behalf of Carlos
> Rovira" <carlos.rovira@gmail.com <ma...@gmail.com> on behalf of
> carlos.rovira@codeoscopic.com <ma...@codeoscopic.com>> wrote:
>
>> Thanks Dave,
>>
>> I'll write an email to trademarks to start with the process. I think is
>> better to migrate to WP.com before continue working on content so we can
>> detect whatever issue we could get.
>>
>> Thanks!
>>
>> Carlos
>>
>>
>>
>> 2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>:
>>
>>> Hi Carlos,
>>>
>>>> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> just let you know that I tried to create an static version of the
>>> preview
>>>> site with success. I use this plugin :
>>>>
>>> https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres>
>>> s.org <http://s.org/>%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
>>> 08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
>>> 702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>>>>
>>>> and we can generate all static content with relative or absolute urls.
>>> The
>>>> final preview site in static is 134mb
>>>>
>>>> Another thing I was searching was to use a WP to Jekyll exporter but
>>> this
>>>> is not what I wanted since it seems Jekyll is all about markdown and
>>> we
>>>> want a full html site with all the eye candy JS+CSS resources. In the
>>> end,
>>>> and thinking more about it, is not what we want since although the
>>> site
>>>> would be exported ok, we don't want to upload it to the GitHub pages
>>> like
>>>> we discusses in the other thread due to expose part of the code of a
>>>> commercial wp theme.
>>>>
>>>> So, the workflow we can use is: Use the WP backend to enter new
>>> content
>>> and
>>>> modify existing want with ease (this is important is we want people
>>>> contributing here). Next, with all changes done, generate a static
>>> version
>>>> and replace the entire site with a fresh generated static site at
>>>> royale.apache.org <http://royale.apache.org/>. and as well route the more friendly domain to this
>>> if
>>>> board is ok with that.
>>>
>>> Yes! External domain royalysdk.org <http://royalysdk.org/> is redirected to royale.apache.org <http://royale.apache.org/> as
>>> discussed.
>>>
>>>>
>>>> We can check with apache board or trademarks what they propose about
>>> to
>>>> create a Wordpress.com <http://wordpress.com/> account managed by Apache and migrate from my
>>> server
>>>> to that account, and all this stuff from there, since if I remember
>>> some
>>>> people said that would be more ok with Apache.I'd end removing my temp
>>>> subdomain after this.
>>>
>>> The advantage of using the Wordpress.com <http://wordpress.com/> location is twofold:
>>>
>>> (1) Wordpress keeps security up to date.
>>> (2) If something happens to you or your company then we have better
>>> access.
>>>
>>> I suspect though that with the status export method this will not be as
>>> great a concern.
>>>
>>>>
>>>> What do you think? Can I move this with the people we were talking
>>> some
>>>> weeks ago?
>>>
>>> Either you or I can email Trademarks with the plan.
>>>
>>> We can then discuss the redirection with Infrastructure and get the site
>>> checked in.
>>>
>>> Regards,
>>> Dave
>>>
>>>>
>>>> Let me know in order to start making the next steps
>>>>
>>>> Thanks
>>>>
>>>>
>>>> --
>>>> Carlos Rovira
>>>>
>>> https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me% <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%>
>>> 2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
>>> b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
>>> HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>>>
>>>
>>
>>
>> --
>>
>> <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo>
>> scopic.com <http://scopic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>> 34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
>> zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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 <https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeos>
>> copic.com <http://copic.com/>&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>> 4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
>> inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>>
>>
>> Conocenos Avant2 en 1 minuto!
>> <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e <https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e>
>> s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
>> 7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
>> r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>> 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: Apache Royale static web site
Posted by Alex Harui <ah...@adobe.com.INVALID>.
There is something I don't think I understand. AIUI, at some point, we
will want the Apache Royale site to include actual Royale applications,
right? And I would think we would want the styling of those applications
to be consistent with the rest of the site. So I'm not clear how we will
be able to implement the styling/theme of these Royale applications if we
don't have rights to the styling. I don't understand how WP themes and
commercial licensing works if we want to replicate that user experience
outside of WP.
If we can use those visuals outside of WP, then why must we continue to
use WP to generate the site? I would hope the theme would be implemented
as CSS and some templates we could use without WP.
Also, if someone wants to patch the site, they can't just offer a patch of
the HTML right? They would need to figure out where in WP it comes from?
Is there a patch process for WP content?
Sorry if there is some basic thing I am missing.
Thanks,
-Alex
On 10/24/17, 10:19 AM, "carlos.rovira@gmail.com on behalf of Carlos
Rovira" <carlos.rovira@gmail.com on behalf of
carlos.rovira@codeoscopic.com> wrote:
>Thanks Dave,
>
>I'll write an email to trademarks to start with the process. I think is
>better to migrate to WP.com before continue working on content so we can
>detect whatever issue we could get.
>
>Thanks!
>
>Carlos
>
>
>
>2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>:
>
>> Hi Carlos,
>>
>> > On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>
>> wrote:
>> >
>> > Hi,
>> >
>> > just let you know that I tried to create an static version of the
>>preview
>> > site with success. I use this plugin :
>> >
>>https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwordpres
>>s.org%2Fplugins%2Fsimply-static%2F&data=02%7C01%7C%7Cb448363ee5984b3b3e0f
>>08d51b0373f8%7Cfa7b1b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033
>>702&sdata=RPTFT7Qq0bq1AKmh1fqnLuMJ0hWIpnrieARat1lz2bk%3D&reserved=0
>> >
>> > and we can generate all static content with relative or absolute urls.
>> The
>> > final preview site in static is 134mb
>> >
>> > Another thing I was searching was to use a WP to Jekyll exporter but
>>this
>> > is not what I wanted since it seems Jekyll is all about markdown and
>>we
>> > want a full html site with all the eye candy JS+CSS resources. In the
>> end,
>> > and thinking more about it, is not what we want since although the
>>site
>> > would be exported ok, we don't want to upload it to the GitHub pages
>>like
>> > we discusses in the other thread due to expose part of the code of a
>> > commercial wp theme.
>> >
>> > So, the workflow we can use is: Use the WP backend to enter new
>>content
>> and
>> > modify existing want with ease (this is important is we want people
>> > contributing here). Next, with all changes done, generate a static
>> version
>> > and replace the entire site with a fresh generated static site at
>> > royale.apache.org. and as well route the more friendly domain to this
>>if
>> > board is ok with that.
>>
>> Yes! External domain royalysdk.org is redirected to royale.apache.org as
>> discussed.
>>
>> >
>> > We can check with apache board or trademarks what they propose about
>>to
>> > create a Wordpress.com account managed by Apache and migrate from my
>> server
>> > to that account, and all this stuff from there, since if I remember
>>some
>> > people said that would be more ok with Apache.I'd end removing my temp
>> > subdomain after this.
>>
>> The advantage of using the Wordpress.com location is twofold:
>>
>> (1) Wordpress keeps security up to date.
>> (2) If something happens to you or your company then we have better
>>access.
>>
>> I suspect though that with the status export method this will not be as
>> great a concern.
>>
>> >
>> > What do you think? Can I move this with the people we were talking
>>some
>> > weeks ago?
>>
>> Either you or I can email Trademarks with the plan.
>>
>> We can then discuss the redirection with Infrastructure and get the site
>> checked in.
>>
>> Regards,
>> Dave
>>
>> >
>> > Let me know in order to start making the next steps
>> >
>> > Thanks
>> >
>> >
>> > --
>> > Carlos Rovira
>> >
>>https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fabout.me%
>>2Fcarlosrovira&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1
>>b5a7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=1q5B1u1lLR
>>HGdnDh8VH9pkaTkdCPk51wt%2FCUJgzQo0c%3D&reserved=0
>>
>>
>
>
>--
>
><https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fwww.codeo
>scopic.com&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b
>34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5H
>zinyiNAxCBpRGAfK3GFX9REzYNI%2F0%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%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a7b3
>4438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=Y%2Fkytu4lJUWu5Hz
>inyiNAxCBpRGAfK3GFX9REzYNI%2F0%3D&reserved=0
>
>
>Conocenos Avant2 en 1 minuto!
><https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Favant2.e
>s%2F%23video&data=02%7C01%7C%7Cb448363ee5984b3b3e0f08d51b0373f8%7Cfa7b1b5a
>7b34438794aed2c178decee1%7C0%7C0%7C636444624020033702&sdata=SJmmZQTVSb0tmX
>r73WVQr%2BLVhv6%2BLRMgcQyhBgOo1KI%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
>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: Apache Royale static web site
Posted by Carlos Rovira <ca...@codeoscopic.com>.
Thanks Dave,
I'll write an email to trademarks to start with the process. I think is
better to migrate to WP.com before continue working on content so we can
detect whatever issue we could get.
Thanks!
Carlos
2017-10-24 18:56 GMT+02:00 Dave Fisher <da...@comcast.net>:
> Hi Carlos,
>
> > On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org>
> wrote:
> >
> > Hi,
> >
> > just let you know that I tried to create an static version of the preview
> > site with success. I use this plugin :
> > https://wordpress.org/plugins/simply-static/
> >
> > and we can generate all static content with relative or absolute urls.
> The
> > final preview site in static is 134mb
> >
> > Another thing I was searching was to use a WP to Jekyll exporter but this
> > is not what I wanted since it seems Jekyll is all about markdown and we
> > want a full html site with all the eye candy JS+CSS resources. In the
> end,
> > and thinking more about it, is not what we want since although the site
> > would be exported ok, we don't want to upload it to the GitHub pages like
> > we discusses in the other thread due to expose part of the code of a
> > commercial wp theme.
> >
> > So, the workflow we can use is: Use the WP backend to enter new content
> and
> > modify existing want with ease (this is important is we want people
> > contributing here). Next, with all changes done, generate a static
> version
> > and replace the entire site with a fresh generated static site at
> > royale.apache.org. and as well route the more friendly domain to this if
> > board is ok with that.
>
> Yes! External domain royalysdk.org is redirected to royale.apache.org as
> discussed.
>
> >
> > We can check with apache board or trademarks what they propose about to
> > create a Wordpress.com account managed by Apache and migrate from my
> server
> > to that account, and all this stuff from there, since if I remember some
> > people said that would be more ok with Apache.I'd end removing my temp
> > subdomain after this.
>
> The advantage of using the Wordpress.com location is twofold:
>
> (1) Wordpress keeps security up to date.
> (2) If something happens to you or your company then we have better access.
>
> I suspect though that with the status export method this will not be as
> great a concern.
>
> >
> > What do you think? Can I move this with the people we were talking some
> > weeks ago?
>
> Either you or I can email Trademarks with the plan.
>
> We can then discuss the redirection with Infrastructure and get the site
> checked in.
>
> Regards,
> Dave
>
> >
> > Let me know in order to start making the next steps
> >
> > Thanks
> >
> >
> > --
> > Carlos Rovira
> > http://about.me/carlosrovira
>
>
--
<http://www.codeoscopic.com>
Carlos Rovira
Director General
M: +34 607 22 60 05
http://www.codeoscopic.com
Conocenos Avant2 en 1 minuto! <https://avant2.es/#video>
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: Apache Royale static web site
Posted by Dave Fisher <da...@comcast.net>.
Hi Carlos,
> On Oct 24, 2017, at 9:30 AM, Carlos Rovira <ca...@apache.org> wrote:
>
> Hi,
>
> just let you know that I tried to create an static version of the preview
> site with success. I use this plugin :
> https://wordpress.org/plugins/simply-static/
>
> and we can generate all static content with relative or absolute urls. The
> final preview site in static is 134mb
>
> Another thing I was searching was to use a WP to Jekyll exporter but this
> is not what I wanted since it seems Jekyll is all about markdown and we
> want a full html site with all the eye candy JS+CSS resources. In the end,
> and thinking more about it, is not what we want since although the site
> would be exported ok, we don't want to upload it to the GitHub pages like
> we discusses in the other thread due to expose part of the code of a
> commercial wp theme.
>
> So, the workflow we can use is: Use the WP backend to enter new content and
> modify existing want with ease (this is important is we want people
> contributing here). Next, with all changes done, generate a static version
> and replace the entire site with a fresh generated static site at
> royale.apache.org. and as well route the more friendly domain to this if
> board is ok with that.
Yes! External domain royalysdk.org is redirected to royale.apache.org as discussed.
>
> We can check with apache board or trademarks what they propose about to
> create a Wordpress.com account managed by Apache and migrate from my server
> to that account, and all this stuff from there, since if I remember some
> people said that would be more ok with Apache.I'd end removing my temp
> subdomain after this.
The advantage of using the Wordpress.com location is twofold:
(1) Wordpress keeps security up to date.
(2) If something happens to you or your company then we have better access.
I suspect though that with the status export method this will not be as great a concern.
>
> What do you think? Can I move this with the people we were talking some
> weeks ago?
Either you or I can email Trademarks with the plan.
We can then discuss the redirection with Infrastructure and get the site checked in.
Regards,
Dave
>
> Let me know in order to start making the next steps
>
> Thanks
>
>
> --
> Carlos Rovira
> http://about.me/carlosrovira