It's currently a brand new branch. You can check it in the repo. Best, tison.
sebb <seb...@gmail.com>于2024年2月22日 周四01:11写道： > On Wed, 21 Feb 2024 at 09:25, tison <wander4...@gmail.com> 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 created as a new branch. > > > 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 follow the context? If we agree, the context here can > be > > brought there. > > > > Best, > > tison. > > > > > > sebb <seb...@gmail.com>于2024年2月21日 周三16:27写道： > > > > > On Wed, 21 Feb 2024 at 00:28, tison <wander4...@gmail.com> 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 > > > > default branch containing README for redirects. > > > > > > However, if a repo is shared in this way, such disjoint branches > > > should be initially created as empty orphans. > > > Replacing all the files with different ones makes for a confusing > history. > > > > > > > From another perspective, it's still valuable to provide a template > > > > for new podlings to get started _now_, and if someone (in this case, > > > > it's me) volunteers to provide one for help, there is no reason we > > > > reject it by the tech will fade _years later_. > > > > > > > > Best, > > > > tison. > > > > > > > > Dave Fisher <w...@apache.org> 于2024年2月21日周三 08:17写道： > > > > > > > > > > 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, > > > > > Dave > > > > > > > > > > > On Feb 20, 2024, at 3:48 PM, tison <wander4...@gmail.com> wrote: > > > > > > > > > > > > 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; especially there can be some arguments. > > > > > > > > > > > > Best, > > > > > > tison. > > > > > > > > > > > > [1] > https://lists.apache.org/thread/tvry49gdclqqdtdcgk0x9hnl18vlxnm8 > > > > > > > > > > > > Dave Fisher <w...@apache.org> 于2024年2月21日周三 02:35写道： > > > > > >> > > > > > >> 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 > > > https://gitbox.apache.org/repos/asf/apache-website-template.git > > > > > >>> > > > > > >>> > > > > > >>> at f2f8a9e Update download page template > > > > > >>> > > > > > >>> No new revisions were added by this update. > > > > > >>> > > > > > >>> > > > > > >>> > > > --------------------------------------------------------------------- > > > > > >>> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org > > > > > >>> For additional commands, e-mail: cvs-h...@incubator.apache.org > > > > > >>> > > > > > >> > > > > > >> > > > > > >> > > > --------------------------------------------------------------------- > > > > > >> To unsubscribe, e-mail: > general-unsubscr...@incubator.apache.org > > > > > >> For additional commands, e-mail: > general-h...@incubator.apache.org > > > > > >> > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > > > > > > For additional commands, e-mail: dev-h...@community.apache.org > > > > > > > > > > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > > > > --------------------------------------------------------------------- > > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
