Hi Beamers, The Git repo at https://git-wip-us.apache.org/repos/asf/incubator-beam-site.git is now populated and syncs with the website.
Cheers, Max On Mon, Mar 7, 2016 at 12:40 PM, Jean-Baptiste Onofré <[email protected]> wrote: > Hi Max, > > thanks for the update. > > I'm on the renaming and legal PR on my side. > > Regards > JB > > > On 03/07/2016 11:43 AM, Maximilian Michels wrote: >> >> Hi JB, >> >> I've pushed the web site to the empty repository and I'll tell Infra >> to switch to the new repository. >> >> Cheers, >> Max >> >> >> On Fri, Mar 4, 2016 at 5:00 PM, Jean-Baptiste Onofré <[email protected]> >> wrote: >>> >>> Hi Max, >>> >>> fair enough. >>> >>> Regards >>> JB >>> >>> >>> On 03/04/2016 03:52 PM, Maximilian Michels wrote: >>>> >>>> >>>> Hi JB, >>>> >>>> Good question. I didn't create the page but one problem about relative >>>> URLs is changing the root directory or switching to https. So instead >>>> of relative URLs which should use {{ site.baseurl }}/resource for all >>>> links. That way, we can simply change baseurl in the _config.yml and >>>> we're good to go. For local testing, we set jekyll --baseurl "". That >>>> approach has worked well for the Flink website which is also built >>>> with Jekyll. >>>> >>>> Cheers, >>>> Max >>>> >>>> On Fri, Mar 4, 2016 at 1:48 PM, Jean-Baptiste Onofré <[email protected]> >>>> wrote: >>>>> >>>>> >>>>> Hi Max, >>>>> >>>>> I just cloned your repo and built using jekyll. >>>>> >>>>> I just wonder why not using relative URL (for images and js location) >>>>> instead of absolute ? It would allow us to directly open the website in >>>>> a >>>>> browser. WDYT ? >>>>> >>>>> Regards >>>>> JB >>>>> >>>>> On 03/01/2016 01:59 PM, Maximilian Michels wrote: >>>>>> >>>>>> >>>>>> >>>>>> As a summary from >>>>>> >>>>>> https://issues.apache.org/jira/servicedesk/customer/portal/1/INFRA-11318 >>>>>> it would work as follows: >>>>>> >>>>>> We use the 'asf-site' branch of the repository. When we change the >>>>>> website, we execute "jekyll build" followed by "jekyll serve" to >>>>>> preview the site. Everything is generated in the 'content' directory. >>>>>> We then push the changes and they are deployed. >>>>>> >>>>>> I've prepared everything in my fork: >>>>>> https://github.com/mxm/beam-site/tree/asf-site >>>>>> >>>>>> Unfortunately, I couldn't push the changes to the new repository. The >>>>>> permissions don't seem to be set up correctly. >>>>>> >>>>>> On Tue, Mar 1, 2016 at 10:24 AM, Maximilian Michels <[email protected]> >>>>>> wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>> Quick update. The Git repository is ready under >>>>>>> https://git-wip-us.apache.org/repos/asf/incubator-beam-site.git >>>>>>> >>>>>>> I'm sorting out the last things and will push the website thereafter. >>>>>>> Infra can then proceed to do the pubsub switch to deploy the website >>>>>>> from there. >>>>>>> >>>>>>> On Thu, Feb 25, 2016 at 11:31 PM, Maximilian Michels <[email protected]> >>>>>>> wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Hi JB, >>>>>>>> >>>>>>>> Greetings to Mexico! I was using Infra's "SVN to Git migration" >>>>>>>> service desk. That seems like a standard way for migration to me. It >>>>>>>> has also worked fine in the past. >>>>>>>> >>>>>>>> Could you explain the role of the SCM-Publish Maven plugin? What >>>>>>>> would >>>>>>>> be different from just committing the changes of the website to the >>>>>>>> Git/SVN repository? Is it necessary that people use another wrapper >>>>>>>> around a version control system? >>>>>>>> >>>>>>>> After all, what counts is that we can use a Git repository to check >>>>>>>> in >>>>>>>> website changes and use the GitHub mirror. That is not only much >>>>>>>> faster (pushing in SVN takes a long time and there is no local >>>>>>>> repository) but also more convenient for most people that use Git on >>>>>>>> a >>>>>>>> daily basis. How the actual website is served, shouldn't matter to >>>>>>>> the >>>>>>>> developer. >>>>>>>> >>>>>>>> Cheers, >>>>>>>> Max >>>>>>>> >>>>>>>> On Thu, Feb 25, 2016 at 11:23 PM, Jean-Baptiste Onofré >>>>>>>> <[email protected]> >>>>>>>> wrote: >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> I agree and it's what we have: the website sources are on my github >>>>>>>>> and >>>>>>>>> we will move it on apache git. Anyway the source is not where you >>>>>>>>> promote >>>>>>>>> with the scm-publish. The PR or patches are not created based on >>>>>>>>> the >>>>>>>>> "resulting" location (on svn now) but on the sources (on my github >>>>>>>>> now). >>>>>>>>> That's why I didn't understand the jira. >>>>>>>>> I don't mind to move the "resulting/promotion" location from svn to >>>>>>>>> git, but I don't see how it changes for the devs. It would be >>>>>>>>> exactly >>>>>>>>> the >>>>>>>>> same workflow (using the scm-publish plugin). >>>>>>>>> Regards JB >>>>>>>>> >>>>>>>>> >>>>>>>>> Sent from my Samsung device >>>>>>>>> >>>>>>>>> -------- Original message -------- >>>>>>>>> From: James Malone <[email protected]> >>>>>>>>> Date: 25/02/2016 21:38 (GMT+01:00) >>>>>>>>> To: [email protected] >>>>>>>>> Subject: Re: New beam website! >>>>>>>>> >>>>>>>>> I'll chime in here - I'd greatly prefer a git-based repo for the >>>>>>>>> website. >>>>>>>>> If nothing else, it's what many of the committers on our side are >>>>>>>>> familiar >>>>>>>>> with. >>>>>>>>> >>>>>>>>> Cheers! >>>>>>>>> >>>>>>>>> James >>>>>>>>> >>>>>>>>> On Thu, Feb 25, 2016 at 10:49 AM, Henry Saputra >>>>>>>>> <[email protected]> >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Hi JB, >>>>>>>>>> >>>>>>>>>> ASF infra now offer Git pubsub to support website source code [1] >>>>>>>>>> >>>>>>>>>> I think this is what Max was trying to enable so instead of using >>>>>>>>>> svn >>>>>>>>>> for >>>>>>>>>> website it will be using Git that also allow pubsub to publish it. >>>>>>>>>> >>>>>>>>>> - Henry >>>>>>>>>> >>>>>>>>>> [1] >>>>>>>>>> https://blogs.apache.org/infra/entry/git_based_websites_available >>>>>>>>>> >>>>>>>>>> On Thu, Feb 25, 2016 at 4:38 AM, Jean-Baptiste Onofré >>>>>>>>>> <[email protected]> >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Hi guys >>>>>>>>>>> Max your jira doesn't make sense imho: the svn for the website is >>>>>>>>>>> for >>>>>>>>>>> pubsub, it's not where the website source has to be located. The >>>>>>>>>>> website >>>>>>>>>>> can be on git or where ever you want but the scm-publish has to >>>>>>>>>>> be >>>>>>>>>>> on >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> svn. >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Please close your jira and wait when I'm back to deal with that. >>>>>>>>>>> Regards JB from Mexico ;) >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Sent from my Samsung device >>>>>>>>>>> >>>>>>>>>>> -------- Original message -------- >>>>>>>>>>> From: Maximilian Michels <[email protected]> >>>>>>>>>>> Date: 25/02/2016 10:43 (GMT+01:00) >>>>>>>>>>> To: [email protected] >>>>>>>>>>> Subject: Re: New beam website! >>>>>>>>>>> >>>>>>>>>>> Alright, I've asked the Infra team to migrate the repository to >>>>>>>>>>> Git >>>>>>>>>>> and setup a GitHub sync. >>>>>>>>>>> >>>>>>>>>>> Git migration: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11318 >>>>>>>>>>> GitHub sync: >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> https://issues.apache.org/jira/servicedesk/agent/INFRA/issue/INFRA-11319 >>>>>>>>>>> >>>>>>>>>>> Cheers, >>>>>>>>>>> Max >>>>>>>>>>> >>>>>>>>>>> On Wed, Feb 24, 2016 at 9:00 PM, James Malone >>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> That would be awesome. Full disclosure - I </3 SVN but <3 git. >>>>>>>>>>>> >>>>>>>>>>>> Happy to help however I can and any experience anyone has for >>>>>>>>>>>> making >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> that >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> happen is welcomed. :) >>>>>>>>>>>> >>>>>>>>>>>> On Wed, Feb 24, 2016 at 9:05 AM, Maximilian Michels >>>>>>>>>>>> <[email protected]> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>>>> Hi James, >>>>>>>>>>>>> >>>>>>>>>>>>> The updated website looks good to me. I agree that it will >>>>>>>>>>>>> simplify >>>>>>>>>>>>> work for a lot of people who are used to Jekyll. >>>>>>>>>>>>> >>>>>>>>>>>>> The website is already in the SVN repository. After we have >>>>>>>>>>>>> sorted >>>>>>>>>>>>> out >>>>>>>>>>>>> the CCLAs, the only thing that is left is a GitHub sync to make >>>>>>>>>>>>> it >>>>>>>>>>>>> more accessible for contributors. The prerequisite for that is >>>>>>>>>>>>> that >>>>>>>>>>>>> we >>>>>>>>>>>>> change it to Git. Apache Infra can do that (we have done >>>>>>>>>>>>> likewise >>>>>>>>>>>>> for >>>>>>>>>>>>> the Flink website repository and it works great). >>>>>>>>>>>>> >>>>>>>>>>>>> Cheers, >>>>>>>>>>>>> Max >>>>>>>>>>>>> >>>>>>>>>>>>> On Wed, Feb 24, 2016 at 7:04 AM, James Malone >>>>>>>>>>>>> <[email protected]> wrote: >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> Hello everyone, >>>>>>>>>>>>>> >>>>>>>>>>>>>> Since we're in the process of getting bootstrapped, I wanted >>>>>>>>>>>>>> to >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> improve >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> on >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> our website a bit, especially since we have a new logo. >>>>>>>>>>>>>> >>>>>>>>>>>>>> The first site was built using Maven sites. To be honest, it >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> presented a >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> bit of a problem because many of the Beam committers have used >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> GitHub >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> docs >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> to date and wanted a system which was somewhat similar. Since >>>>>>>>>>>>>> GH >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> docs >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> is >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> built on Jekyll (as far as I know) I figured that might >>>>>>>>>>>>>> actually >>>>>>>>>>>>>> be >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> an >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> easier way to build the website anyway. >>>>>>>>>>>>>> >>>>>>>>>>>>>> So, I just updated the incubator website. with an exact copy >>>>>>>>>>>>>> of >>>>>>>>>>>>>> the >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> old >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> site but using Jekyll + Bootstrap 3. That should hopefully >>>>>>>>>>>>>> make >>>>>>>>>>>>>> it >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> easier >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> for anyone and everyone to work against (and to move existing >>>>>>>>>>>>>> docs.) >>>>>>>>>>>>>> >>>>>>>>>>>>>> The repository for the current site is here: >>>>>>>>>>>>>> >>>>>>>>>>>>>> https://github.com/evilsoapbox/beam-site >>>>>>>>>>>>>> >>>>>>>>>>>>>> I also have a tgz of the old site in case there's any concern >>>>>>>>>>>>>> or >>>>>>>>>>>>>> disagreement. Needless to say, when we sort out the CCLAs >>>>>>>>>>>>>> (which >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> should >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> be >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> very soon) I'd like to get this in a project repo somewhere so >>>>>>>>>>>>>> we >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> can >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> have >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> better version control and review. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Finally, the theme is basic bootstrap with a few changes (like >>>>>>>>>>>>>> using >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> Roboto >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> >>>>>>>>>>>>>> as the font to match the logo.) I figure if/when there's >>>>>>>>>>>>>> interest >>>>>>>>>>>>>> in >>>>>>>>>>>>>> detailed design, we can cover that as a seperate discussion. >>>>>>>>>>>>>> >>>>>>>>>>>>>> Cheers! >>>>>>>>>>>>>> >>>>>>>>>>>>>> James >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> >>>>> >>>>> -- >>>>> Jean-Baptiste Onofré >>>>> [email protected] >>>>> http://blog.nanthrax.net >>>>> Talend - http://www.talend.com >>> >>> >>> >>> -- >>> Jean-Baptiste Onofré >>> [email protected] >>> http://blog.nanthrax.net >>> Talend - http://www.talend.com > > > -- > Jean-Baptiste Onofré > [email protected] > http://blog.nanthrax.net > Talend - http://www.talend.com
