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
> > >>
> >
>
