Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-21 Thread sebb
On Thu, 22 Feb 2024 at 00:08, tison wrote: > > It's currently a brand new branch. You can check it in the repo. OK, great. It seems I was misled by the summary page, which says: "This branch is 5 commits ahead of, 34 commits behind master." To me, that definitely implies a relationship. Very

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-21 Thread tison
It's currently a brand new branch. You can check it in the repo. Best, tison. sebb 于2024年2月22日 周四01:11写道: > On Wed, 21 Feb 2024 at 09:25, tison wrote: > > > > Hi sebb, > > > > Your comments sound like back to the switching default branch solution (a > > new branch with history only adding the

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-21 Thread sebb
On Wed, 21 Feb 2024 at 09:25, tison wrote: > > Hi sebb, > > Your comments sound like back to the switching default branch solution (a > new branch with history only adding the README becomes the default). I am saying that if the 3 branch solution is adopted the docusaurus branch should be

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-21 Thread tison
Hi sebb, Your comments sound like back to the switching default branch solution (a new branch with history only adding the README becomes the default). Or you prefer other ways to the same repo direction. Also is it possible we go back to the COMDEV dedicated thread so that people can easily

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-21 Thread sebb
On Wed, 21 Feb 2024 at 00:28, tison wrote: > > Hi Dave, > > > One approach is to find good examples of each build technique. If you look > > back at older projects you will see various historical waves of technique. > > I agree, and that's why I'd prefer a multi branches solution with a >

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-20 Thread tison
Hi Dave, > One approach is to find good examples of each build technique. If you look > back at older projects you will see various historical waves of technique. I agree, and that's why I'd prefer a multi branches solution with a default branch containing README for redirects. >From another

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-20 Thread Dave Fisher
Hi Tison, I’m following along. Infrastructure has a Pelican template site that is out of date: https://github.com/apache/template-site/ One approach is to find good examples of each build technique. If you look back at older projects you will see various historical waves of technique. Best,

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-20 Thread tison
Hi Dave, Thanks for picking up this commit. You may join the discussion at [1]. I have all the permission to follow what I want. But since apache-website-template is technically a foundation-wise repo and I'm a newcomer here, I'd like to listen to people's opinions before moving forward;

Re: (apache-website-template) branch jekyll created (now f2f8a9e)

2024-02-20 Thread Dave Fisher
From the commit email it looks like this repository belongs to the Incubator. > On Feb 14, 2024, at 2:27 AM, ti...@apache.org wrote: > > This is an automated email from the ASF dual-hosted git repository. > > tison pushed a change to branch jekyll > in repository