Hi Harbs 2017-10-24 20:10 GMT+02:00 Harbs <[email protected]>:
> 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 <[email protected]> > 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 <[email protected]<mailto:[email protected]>> > > Reply-To: <[email protected]<mailto:[email protected]>> > > Date: Tuesday, October 24, 2017 at 10:50 AM > > To: <[email protected]<mailto:[email protected]>> > > Subject: Re: Apache Royale static web site > > > > Hi Alex, > > > > On Oct 24, 2017, at 10:43 AM, Alex Harui <[email protected]< > mailto:[email protected]>> 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, "[email protected]<mailto: > [email protected]> on behalf of Carlos > > Rovira" <[email protected]<mailto:[email protected]> on > behalf of > > [email protected]<mailto:[email protected]>> > 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 <[email protected]<mailto: > [email protected]>>: > > > > Hi Carlos, > > > > On Oct 24, 2017, at 9:30 AM, Carlos Rovira <[email protected]< > mailto:[email protected]>> > > 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.
