Re: [DISCUSS] Building the brand for Royale

Hi, One thing we could do with an external Wordpress is have tooling which captures posts and checks these into git. We can probably do it with a WP addin. I've used a variation of this approach to provide content to an iOS app. Regards, Dave Sent from my iPhone > On Sep 20, 2017, at 1:51 PM

Re: [DISCUSS] Building the brand for Royale

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

Re: [DISCUSS] Building the brand for Royale

AIUI, one of the other "rules" for royale.apache.org is that it cannot run web servers, so JSFiddle type of things may not be possible without calling out to a server outside apache.org and thus facing cross-domain issues. I've seen some recent mention that Apache project can now get their own VM,

Re: [DISCUSS] Building the brand for Royale

I think that's right Alex, I think I can start creating as we get boards approval for "Royale" Thanks 2017-09-20 20:08 GMT+02:00 Alex Harui : > AIUI, we are going to build at least three sites: > > 1) Royale.apache.org is a requirement. And I think we have to use ASF CMS > and whatever markup

Re: [DISCUSS] Building the brand for Royale

I use to update my WP installations regularly. I did it just minutes ago ;) I get notifications when some update is ready. As others in the team will have admin privileges in the installation, we can organice us easily to see how is in charge of doing updates. Others in the team could only have edi

Re: [DISCUSS] Building the brand for Royale

AIUI, we are going to build at least three sites: 1) Royale.apache.org is a requirement. And I think we have to use ASF CMS and whatever markup language it requires unless we generate html and js elsewhere and copy it in, which would be the case for any FlexJS/Royale apps. 2) https://github.com/

Re: [DISCUSS] Building the brand for Royale

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

Re: [DISCUSS] Building the brand for Royale

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

Re: [DISCUSS] Building the brand for Royale

Alex, I would like to see getting the website done in FlexJS for a long time. If Carlos will design the things, let's see what can we actually do. It just would be awesome not waiting half year or so to launch our website. +1 for building it in FlexJS, but before that we should have some start -

Re: [DISCUSS] Building the brand for Royale

Hi, as Erik stated, apache put stones on our road, and we must look more careful were you step. @Om, my problem with gihub pages is that I can't get the same product that I could do in WP. Take a look at one of my websites (i.e https://www.avant2.es). Maybe I could get a final static page, but in

Re: [DISCUSS] Building the brand for Royale

True, that's a lot of rules. Part of that is because we owe our hosts (the ASF) some "props". But that may be why it is easier for us to approve Carlos to do what we wants outside the project. It will free him most of these rules. AIUI, the only rules would then be: 1) make sure Apache is menti

Re: [DISCUSS] Building the brand for Royale

> I think if we grab a domain and donate it to the ASF, that it can't be > hosted on non-ASF hardware. That would need to be verified. > Maybe it would be better for the Royale PMC to approve Royale.xx as a > third-party domain under Carlos's control. I think that's allowed. The > policy [1] say

Re: [DISCUSS] Building the brand for Royale

I would stay away from WordPress just because of all the security issues and maintenance required. Github pages should be a better place. Thanks, Om On Sep 20, 2017 10:26 AM, "Alex Harui" wrote: > Hmm. > > I think if we grab a domain and donate it to the ASF, that it can't be > hosted on non-A

Re: [DISCUSS] Building the brand for Royale

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

Re: [DISCUSS] Building the brand for Royale

Hi Piotr, as you said, I'll go for WP, but we can point to some GitHub pages if we need. That would be more clear as we start the website development 2017-09-20 18:56 GMT+02:00 Piotr Zarzycki : > I think Carlos's idea with using wordpress can be better one. He can build > based on that system ou

Re: [DISCUSS] Building the brand for Royale

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

Re: [DISCUSS] Building the brand for Royale

I think Carlos's idea with using wordpress can be better one. He can build based on that system our website much faster. I don't think we will have so much possibility visually using github pages. Although in githubpages I would see Olaf's documentation [1]. [1] https://github.com/ok-at-github/fl

Re: [DISCUSS] Building the brand for Royale

Hi Carlos, We can go grab some royale. domains. Apache will have some rules about what can go on them. At the worst it will have to be a straight redirect to royale.apache.org, but I think we might be able to have at least a landing page. I think the goal is that Apache wants strong association

Re: [DISCUSS] Building the brand for Royale

Hi, as Alex and Dave said, we should wait for board approval. @Harbs, I was using "xxx" to refer to "whatever domain extension out there that would fit for us" ;) @Dave, I understand that we should use the apache domain for the service apache provide (i.e: store code, mailing list, releases...),

Re: [DISCUSS] Building the brand for Royale

Guys, congrats for selecting the new project name. Still not sure how Royale resonates with me, but like it much more than the 1st runner up. Non English speakers would pretty often confuse beads with beds and job ads might sound strange. Just imagine: "Looking for an amazing Beads expert to jo

Re: [DISCUSS] Building the brand for Royale

As an Apache project the domain would be: Royale.apache.org I can write a long discussion about policy later but there are reasons, requirements, approvals around use of other domains. I know everyone is enthusiastic but let's get approved by the board first. Regards, Dave Sent from my iPhone

Re: [DISCUSS] Building the brand for Royale

Definitely not royale.xxx. We’re trying to steer clear of adult sites. :-D I think an apache.org site is totally fine. FWIW, royalesdk.io royalesdk.com , etc. are all available. Harbs > On Sep 20, 2017, at 1:33 PM, Erik de Bruin wrote: > >> >> *

Re: [DISCUSS] Building the brand for Royale

> > * Domain: We must find a good and simple domain for Royale. I think if we > can find something short like "royale.XXX" would be great over > "apacheroyale.XXX". > .com, .org, .net, .io etc. all seem to be either in use or squatted upon. Am I forgetting memorable TLP extensions? I assume we don

[DISCUSS] Building the brand for Royale

Hi all, now that we decided to change our name to Royale. we must to make some serious work in the next weeks. We talked about: * Logo: We need to design logo to make Royale attractive at first sight * Website: A new name, and logo requires a good, clean and beautiful website that make us be eleg