2017-10-22 23:58 GMT+02:00 Harbs <[email protected]>: > > I don't think so, since Codeoscopic buyed the license already > > Just to be clear: You bought the license for the Royale site? Or are you > saying that Royale is a “client” of Codeoscopic? >
I buyed a license, is not a client :) so I can use the license to make this site. At least that is what I think about this, but let's what others have to say (Specialy Dave Fisher) on this regard. > > > I think there's an Jekyll exporter too but we need to check it and see > how it behaves. > > Sounds interesting! > > >> 3. What (if any) of the theme can be placed in a public repository to > make > >> the main site a non-WordPress one? I imagine we’d need to ask both the > >> publisher of the theme and Apache legal. > >> > > > > I think we should doesn't do that, since is not what we want, following > the > > example exposed before, is like if we use JIRA and for that reason want > to > > upload the JIRA code to some of our repos...don't see any reason to do > > that. The site is only for marketing purposes and a tool. The rest: > source > > code, binaries, wiki, issues, ... is what we produce and we deliver to > our > > users. > > What I mean is like this: > > Currently, the royale.apache.org <http://royale.apache.org/> is built > automatically by committing code here: https://github.com/apache/ > royale-website/tree/asf-site <https://github.com/apache/ > royale-website/tree/asf-site> > > Ideally, our main site should be editable by folks simply applying a pull > request on Github. I’m not clear whether the license for the theme would > allow us to do that by adapting the CSS and JS for a static site. The > WordPress theme would still be useful as a theme for parts of the site such > as a blog (and that would not be on a public repo), but I do think we want > consistent styling across everything. > > Makes sense? > Lots of sense, Harbs, but in this case we can change that. If we get and static site, that site will have code that is from a commercial product, so we can't upload nothing. That's what I think. In the other hand, we talked about to have a VM with Wordpress and there we can easily (and thanks to what WP offers in terms of ease), create post, modify web parts, change home, and so on, quickly, then export to static and put on royale.apache.org (that is what we really need and is required by our apache policies). We don't need to upload the code site to our repo. That, in my opinion is something that apache offers as a service for each project for people that wants to develop the entire site and doesn't have any commercial piece. But in our case, using a commercial WP theme can do, but repeat, I think is not what we do. the website, in Royale, Struts, or other projects is only a tool to connect users and developers with the code, docs, wiki, binaries, issues, mailing list and so on. So is not mandatory to anyone to develop something from scratch and upload to an apache repo. Thanks! Carlos > > Harbs > > > On Oct 23, 2017, at 12:47 AM, Carlos Rovira <[email protected]> > wrote: > > > > Hi Harbs, > > > > > > 2017-10-22 23:00 GMT+02:00 Harbs <[email protected]>: > > > >> Hi Carlos, > >> > >> Very impressive! > >> > >> The direction is great! Awesome work! > >> > > > > Thanks for the Kindly words! :) > > > > > >> > >> I do have some questions which I think we need to address: > >> > >> It looks like you used the Movedo WordPress theme for this[1] which is a > >> commercial WordPress theme. > >> > >> This brings up some questions: > >> > >> 1. Presumably we’d need to buy a license to use it for the project. We’d > >> need to ask exactly what the right procedure is for doing so. > >> > > > > I don't think so, since Codeoscopic buyed the license already, and as > David > > Fisher said we can use a commercial projects to market this project, > since > > is not part of the code of the project, just a tool, like if we use JIRA > or > > Itellij IDEA, or other think like that > > > > > > > >> 2. Does this lock us into WordPress? Would we be able to use these > design > >> elements for a “normal” site? > >> > > > > I want to try to use a plugin to export it and create an static site, > > sincerely I never try that before. I think there's an Jekyll exporter too > > but we need to check it and see how it behaves. In that case, we can > > operate in Wordpress and then export to our production site. > > > > > >> 3. What (if any) of the theme can be placed in a public repository to > make > >> the main site a non-WordPress one? I imagine we’d need to ask both the > >> publisher of the theme and Apache legal. > >> > > > > I think we should doesn't do that, since is not what we want, following > the > > example exposed before, is like if we use JIRA and for that reason want > to > > upload the JIRA code to some of our repos...don't see any reason to do > > that. The site is only for marketing purposes and a tool. The rest: > source > > code, binaries, wiki, issues, ... is what we produce and we deliver to > our > > users. > > > > > >> 4. Have any other projects done something similar to use as a policy > >> trendsetter? > >> > > > > Don't know, but what made me work on this was some words from Dave Fisher > > in the same line of what I exposed here. > > > > Let's see the rest competing about this :) > > > > Carlos > > > > > > > >> > >> Harbs > >> > >> [1]https://themeforest.net/item/movedo-we-do-move-your-world/17923709 < > >> https://themeforest.net/item/movedo-we-do-move-your-world/17923709> > >> > >> > > -- Carlos Rovira http://about.me/carlosrovira
