Re: (apache-website-template) branch jekyll created (now f2f8a9e)
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 confusing. However, try a compare, and it says: "master and docusaurus are entirely different commit histories." > 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 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 于2024年2月21日 周三16:27写道： > > > > > > > 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 > > > > > 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 于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 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 于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 > > > > > > > > > > > > > > > > > > > > > > > > > > >
Re: (apache-website-template) branch jekyll created (now f2f8a9e)
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 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 于2024年2月21日 周三16:27写道： > > > > > 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 > > > > 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 于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 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 于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
Re: [DISCUSS] Create a new repo for website template
On Wed, Feb 21, 2024, at 10:43, tison wrote: > Hi Chris, > > Thanks you. Now we found a volunteer to improve the jekyll template and > it's good :D Haha ok great, I will send a patch as suggested. I can also commit directly if this repo is using CTR > > Daniel wrote: >> This feels like we are over-engineering the solution to a simple >> problem. Just use the existing website-template repository, have the >> default branch be an empty branch with a README that tells you what the >> different examples are, each in their own branch or directory. > > I'm OK with this. And it seems a solution that no direct reasonable > objection. > > Although Sebb comments in the other thread [1] that such a Rip Down commit > can be suboptimal due to the irrelevant history, with INFRA's help we can > use a brand new README branch and make it the default. > > I'm going to move forward with the development in docusaurus branch and > recommend Chris to send the patch against the jekyll branch (I'll review it > if you need). > > For the master branch tech solution, I'm fine to wait a minutes to rip it > down, switch with a brand new history, or any other suggestions. > > Best, > tison. > > [1] > https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq > > > Christian Grobmeier 于2024年2月21日 周三16:07写道： > >> Hello, >> >> I love we are picking up this template idea again. >> >> Previously I proposed to add some Docker files to help with quick setup. >> I could add this straightaway to the Jekyll branch. >> >> Does this sound like a good idea? >> >> It could look like what I did for Privacy: >> https://github.com/apache/privacy-website >> >> Please let me know, then I will add it (or forget about it) >> >> Kind regards, >> Christian >> >> On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: >> > From my recent experience, it could save the developer lots of time if >> > they can work on the website's content by adding some markdown files >> > directly. >> > Following the website policy and turning the features of the website >> > engine are one-time work. The ROI would be good if we could share >> > these through the website template. >> > >> > Thanks, >> > >> > Willem Jiang >> > >> > On Tue, Feb 20, 2024 at 8:20 PM tison wrote: >> >> >> >> > And/or just point to the source code of existing ASF websites which >> >> > can serve as living examples. >> >> >> >> You can check the original mailing list thread [1]. I recommend Fury as >> an >> >> example there because it's just started. Living examples can be >> supplements >> >> but customized a lot to prevent new podlings from catching up. >> >> >> >> This is my initial motivation to create a template and even >> self-contained >> >> docs to share how to switch features while being compliant with ASF >> >> policies :D >> >> >> >> Best, >> >> tison. >> >> >> >> [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx >> >> >> >> >> >> Bertrand Delacretaz 于2024年2月20日周二 19:32写道： >> >> >> >> > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno >> >> > wrote: >> >> > > ...Just use the existing website-template repository, have the >> >> > > default branch be an empty branch with a README that tells you what >> the >> >> > > different examples are, each in their own branch or directory... >> >> > >> >> > And/or just point to the source code of existing ASF websites which >> >> > can serve as living examples. >> >> > >> >> > And encourage people to add GitHub topics to their website >> >> > repositories, so that queries like >> >> > >> >> > >> https://github.com/search?q=topic%3Ahugo+org%3Aapache=Repositories >> >> > >> >> > can give you a list of real live examples that use your favorite >> >> > website generation tool, "hugo" in this example. >> >> > >> >> > -Bertrand >> >> > >> >> > - >> >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> >> > For additional commands, e-mail: dev-h...@community.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: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
Hi On Wed, Feb 21, 2024, at 17:06, Dave Fisher wrote: > Hi Tison, > > Some future ideas. > > (1) The web templates - html, js, css, and fonts are likely to be > similar between the branches. (Well not all the js that docusaurus > produces, but the site design will be similar.) This could lead to a > branch with multiple designs. The question is what template language is > used by docusaurus and jekyl? JINJA2? Jekyll uses Liquid, Docusaurus uses a JSX like thing. I never used it, but it is basically a React application that is rendered to static files. I don’t think templates can be reused Kind regards Christian > > (2) Once those two examples are complete. I think that an ASF Pelican > example can be done as well. There are a number of examples like > apache.org, http.apache.org, etc. > > I’m following along and will have a look later on. > > Best, > Dave > >> On Feb 21, 2024, at 1:43 AM, tison wrote: >> >> Hi Chris, >> >> Thanks you. Now we found a volunteer to improve the jekyll template and >> it's good :D >> >> Daniel wrote: >>> This feels like we are over-engineering the solution to a simple >>> problem. Just use the existing website-template repository, have the >>> default branch be an empty branch with a README that tells you what the >>> different examples are, each in their own branch or directory. >> >> I'm OK with this. And it seems a solution that no direct reasonable >> objection. >> >> Although Sebb comments in the other thread [1] that such a Rip Down commit >> can be suboptimal due to the irrelevant history, with INFRA's help we can >> use a brand new README branch and make it the default. >> >> I'm going to move forward with the development in docusaurus branch and >> recommend Chris to send the patch against the jekyll branch (I'll review it >> if you need). >> >> For the master branch tech solution, I'm fine to wait a minutes to rip it >> down, switch with a brand new history, or any other suggestions. >> >> Best, >> tison. >> >> [1] >> https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq >> >> >> Christian Grobmeier 于2024年2月21日 周三16:07写道： >> >>> Hello, >>> >>> I love we are picking up this template idea again. >>> >>> Previously I proposed to add some Docker files to help with quick setup. >>> I could add this straightaway to the Jekyll branch. >>> >>> Does this sound like a good idea? >>> >>> It could look like what I did for Privacy: >>> https://github.com/apache/privacy-website >>> >>> Please let me know, then I will add it (or forget about it) >>> >>> Kind regards, >>> Christian >>> >>> On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: From my recent experience, it could save the developer lots of time if they can work on the website's content by adding some markdown files directly. Following the website policy and turning the features of the website engine are one-time work. The ROI would be good if we could share these through the website template. Thanks, Willem Jiang On Tue, Feb 20, 2024 at 8:20 PM tison wrote: > >> And/or just point to the source code of existing ASF websites which >> can serve as living examples. > > You can check the original mailing list thread [1]. I recommend Fury as >>> an > example there because it's just started. Living examples can be >>> supplements > but customized a lot to prevent new podlings from catching up. > > This is my initial motivation to create a template and even >>> self-contained > docs to share how to switch features while being compliant with ASF > policies :D > > Best, > tison. > > [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx > > > Bertrand Delacretaz 于2024年2月20日周二 19:32写道： > >> On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno >> wrote: >>> ...Just use the existing website-template repository, have the >>> default branch be an empty branch with a README that tells you what >>> the >>> different examples are, each in their own branch or directory... >> >> And/or just point to the source code of existing ASF websites which >> can serve as living examples. >> >> And encourage people to add GitHub topics to their website >> repositories, so that queries like >> >> >>> https://github.com/search?q=topic%3Ahugo+org%3Aapache=Repositories >> >> can give you a list of real live examples that use your favorite >> website generation tool, "hugo" in this example. >> >> -Bertrand >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> - To unsubscribe, e-mail:
Re: (apache-website-template) branch jekyll created (now f2f8a9e)
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 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 于2024年2月21日 周三16:27写道： > > > 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 > > > 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 于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 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 于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
Re: [DISCUSS] Create a new repo for website template
Hi Tison, Some future ideas. (1) The web templates - html, js, css, and fonts are likely to be similar between the branches. (Well not all the js that docusaurus produces, but the site design will be similar.) This could lead to a branch with multiple designs. The question is what template language is used by docusaurus and jekyl? JINJA2? (2) Once those two examples are complete. I think that an ASF Pelican example can be done as well. There are a number of examples like apache.org, http.apache.org, etc. I’m following along and will have a look later on. Best, Dave > On Feb 21, 2024, at 1:43 AM, tison wrote: > > Hi Chris, > > Thanks you. Now we found a volunteer to improve the jekyll template and > it's good :D > > Daniel wrote: >> This feels like we are over-engineering the solution to a simple >> problem. Just use the existing website-template repository, have the >> default branch be an empty branch with a README that tells you what the >> different examples are, each in their own branch or directory. > > I'm OK with this. And it seems a solution that no direct reasonable > objection. > > Although Sebb comments in the other thread [1] that such a Rip Down commit > can be suboptimal due to the irrelevant history, with INFRA's help we can > use a brand new README branch and make it the default. > > I'm going to move forward with the development in docusaurus branch and > recommend Chris to send the patch against the jekyll branch (I'll review it > if you need). > > For the master branch tech solution, I'm fine to wait a minutes to rip it > down, switch with a brand new history, or any other suggestions. > > Best, > tison. > > [1] > https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq > > > Christian Grobmeier 于2024年2月21日 周三16:07写道： > >> Hello, >> >> I love we are picking up this template idea again. >> >> Previously I proposed to add some Docker files to help with quick setup. >> I could add this straightaway to the Jekyll branch. >> >> Does this sound like a good idea? >> >> It could look like what I did for Privacy: >> https://github.com/apache/privacy-website >> >> Please let me know, then I will add it (or forget about it) >> >> Kind regards, >> Christian >> >> On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: >>> From my recent experience, it could save the developer lots of time if >>> they can work on the website's content by adding some markdown files >>> directly. >>> Following the website policy and turning the features of the website >>> engine are one-time work. The ROI would be good if we could share >>> these through the website template. >>> >>> Thanks, >>> >>> Willem Jiang >>> >>> On Tue, Feb 20, 2024 at 8:20 PM tison wrote: > And/or just point to the source code of existing ASF websites which > can serve as living examples. You can check the original mailing list thread [1]. I recommend Fury as >> an example there because it's just started. Living examples can be >> supplements but customized a lot to prevent new podlings from catching up. This is my initial motivation to create a template and even >> self-contained docs to share how to switch features while being compliant with ASF policies :D Best, tison. [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx Bertrand Delacretaz 于2024年2月20日周二 19:32写道： > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno > wrote: >> ...Just use the existing website-template repository, have the >> default branch be an empty branch with a README that tells you what >> the >> different examples are, each in their own branch or directory... > > And/or just point to the source code of existing ASF websites which > can serve as living examples. > > And encourage people to add GitHub topics to their website > repositories, so that queries like > > >> https://github.com/search?q=topic%3Ahugo+org%3Aapache=Repositories > > can give you a list of real live examples that use your favorite > website generation tool, "hugo" in this example. > > -Bertrand > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.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: dev-unsubscr...@community.apache.org >> For additional commands, e-mail: dev-h...@community.apache.org >> >> - To unsubscribe, e-mail:
Re: ASF on Redbubble
On 21/02/2024 14:44, Richard Zowalla wrote: Hey Mark, I am unable to find the ComDev store on Redbubble at all. My previous orders from ComDev are gone (or I ordered from the wrong people in the recent years). So if you have a link for me, would be great :) Sigh. Redbubble have suspended our account. I'll see what I can do to fix that. Mark Best Richard Am Mittwoch, dem 21.02.2024 um 08:46 + schrieb Mark Thomas: On 20/02/2024 21:55, Jeff Zemerick wrote: Hi all, Hopefully this list is the best place for this. I have ordered several OpenNLP shirts in the past from Redbubble. I did a recent order for OpenNLP, Airflow, Solr, and NiFi shirts (can never have enough, right?) and RedBubble canceled the OpenNLP and Airflow ones due to Redbubble’s IP/Publicity Rights Policy [1]. I only see Solr in the ComDev store. It may be the case that RedBubble is (finally) taking steps against sellers that sell items using logos they don't have the rights to. Last time I went looking there were a LOT of items with logos for commercial software. You might have got caught up in that. I just wanted to bring it to the ASF's attention. Is Redbubble still the place to get ASF swag? It is the place ComDev maintains although some projects may have set up alternatives. The simplest solution may be to get those PMCs to request that the relevant logos are added to the ComDev store. It just needs an email from someone on the PMC to this list confirming that the PMC would like the logo added. Mark - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.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: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: ASF on Redbubble
Hey Mark, I am unable to find the ComDev store on Redbubble at all. My previous orders from ComDev are gone (or I ordered from the wrong people in the recent years). So if you have a link for me, would be great :) Best Richard Am Mittwoch, dem 21.02.2024 um 08:46 + schrieb Mark Thomas: > On 20/02/2024 21:55, Jeff Zemerick wrote: > > Hi all, > > > > Hopefully this list is the best place for this. > > > > I have ordered several OpenNLP shirts in the past from Redbubble. I > > did a > > recent order for OpenNLP, Airflow, Solr, and NiFi shirts (can never > > have > > enough, right?) and RedBubble canceled the OpenNLP and Airflow ones > > due to > > Redbubble’s IP/Publicity Rights Policy [1]. > > I only see Solr in the ComDev store. It may be the case that > RedBubble > is (finally) taking steps against sellers that sell items using logos > they don't have the rights to. Last time I went looking there were a > LOT > of items with logos for commercial software. You might have got > caught > up in that. > > > I just wanted to bring it to the ASF's attention. Is Redbubble > > still the > > place to get ASF swag? > > It is the place ComDev maintains although some projects may have set > up > alternatives. > > The simplest solution may be to get those PMCs to request that the > relevant logos are added to the ComDev store. It just needs an email > from someone on the PMC to this list confirming that the PMC would > like > the logo added. > > Mark > > - > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
Hi Chris, Thanks you. Now we found a volunteer to improve the jekyll template and it's good :D Daniel wrote: > This feels like we are over-engineering the solution to a simple > problem. Just use the existing website-template repository, have the > default branch be an empty branch with a README that tells you what the > different examples are, each in their own branch or directory. I'm OK with this. And it seems a solution that no direct reasonable objection. Although Sebb comments in the other thread [1] that such a Rip Down commit can be suboptimal due to the irrelevant history, with INFRA's help we can use a brand new README branch and make it the default. I'm going to move forward with the development in docusaurus branch and recommend Chris to send the patch against the jekyll branch (I'll review it if you need). For the master branch tech solution, I'm fine to wait a minutes to rip it down, switch with a brand new history, or any other suggestions. Best, tison. [1] https://lists.apache.org/thread/jjmb1jnl67rr5qnhdb047tms9ksd0yqq Christian Grobmeier 于2024年2月21日 周三16:07写道： > Hello, > > I love we are picking up this template idea again. > > Previously I proposed to add some Docker files to help with quick setup. > I could add this straightaway to the Jekyll branch. > > Does this sound like a good idea? > > It could look like what I did for Privacy: > https://github.com/apache/privacy-website > > Please let me know, then I will add it (or forget about it) > > Kind regards, > Christian > > On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: > > From my recent experience, it could save the developer lots of time if > > they can work on the website's content by adding some markdown files > > directly. > > Following the website policy and turning the features of the website > > engine are one-time work. The ROI would be good if we could share > > these through the website template. > > > > Thanks, > > > > Willem Jiang > > > > On Tue, Feb 20, 2024 at 8:20 PM tison wrote: > >> > >> > And/or just point to the source code of existing ASF websites which > >> > can serve as living examples. > >> > >> You can check the original mailing list thread [1]. I recommend Fury as > an > >> example there because it's just started. Living examples can be > supplements > >> but customized a lot to prevent new podlings from catching up. > >> > >> This is my initial motivation to create a template and even > self-contained > >> docs to share how to switch features while being compliant with ASF > >> policies :D > >> > >> Best, > >> tison. > >> > >> [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx > >> > >> > >> Bertrand Delacretaz 于2024年2月20日周二 19:32写道： > >> > >> > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno > >> > wrote: > >> > > ...Just use the existing website-template repository, have the > >> > > default branch be an empty branch with a README that tells you what > the > >> > > different examples are, each in their own branch or directory... > >> > > >> > And/or just point to the source code of existing ASF websites which > >> > can serve as living examples. > >> > > >> > And encourage people to add GitHub topics to their website > >> > repositories, so that queries like > >> > > >> > > https://github.com/search?q=topic%3Ahugo+org%3Aapache=Repositories > >> > > >> > can give you a list of real live examples that use your favorite > >> > website generation tool, "hugo" in this example. > >> > > >> > -Bertrand > >> > > >> > - > >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org > >> > For additional commands, e-mail: dev-h...@community.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: dev-unsubscr...@community.apache.org > For additional commands, e-mail: dev-h...@community.apache.org > >
Re: (apache-website-template) branch jekyll created (now f2f8a9e)
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 follow the context? If we agree, the context here can be brought there. Best, tison. sebb 于2024年2月21日 周三16:27写道： > 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 > > 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 于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 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 于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 > >
Re: ASF on Redbubble
On 20/02/2024 21:55, Jeff Zemerick wrote: Hi all, Hopefully this list is the best place for this. I have ordered several OpenNLP shirts in the past from Redbubble. I did a recent order for OpenNLP, Airflow, Solr, and NiFi shirts (can never have enough, right?) and RedBubble canceled the OpenNLP and Airflow ones due to Redbubble’s IP/Publicity Rights Policy [1]. I only see Solr in the ComDev store. It may be the case that RedBubble is (finally) taking steps against sellers that sell items using logos they don't have the rights to. Last time I went looking there were a LOT of items with logos for commercial software. You might have got caught up in that. I just wanted to bring it to the ASF's attention. Is Redbubble still the place to get ASF swag? It is the place ComDev maintains although some projects may have set up alternatives. The simplest solution may be to get those PMCs to request that the relevant logos are added to the ComDev store. It just needs an email from someone on the PMC to this list confirming that the PMC would like the logo added. Mark - To unsubscribe, e-mail: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: (apache-website-template) branch jekyll created (now f2f8a9e)
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 > 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 于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 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 于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: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
Re: [DISCUSS] Create a new repo for website template
Hello, I love we are picking up this template idea again. Previously I proposed to add some Docker files to help with quick setup. I could add this straightaway to the Jekyll branch. Does this sound like a good idea? It could look like what I did for Privacy: https://github.com/apache/privacy-website Please let me know, then I will add it (or forget about it) Kind regards, Christian On Tue, Feb 20, 2024, at 23:38, Willem Jiang wrote: > From my recent experience, it could save the developer lots of time if > they can work on the website's content by adding some markdown files > directly. > Following the website policy and turning the features of the website > engine are one-time work. The ROI would be good if we could share > these through the website template. > > Thanks, > > Willem Jiang > > On Tue, Feb 20, 2024 at 8:20 PM tison wrote: >> >> > And/or just point to the source code of existing ASF websites which >> > can serve as living examples. >> >> You can check the original mailing list thread [1]. I recommend Fury as an >> example there because it's just started. Living examples can be supplements >> but customized a lot to prevent new podlings from catching up. >> >> This is my initial motivation to create a template and even self-contained >> docs to share how to switch features while being compliant with ASF >> policies :D >> >> Best, >> tison. >> >> [1] https://lists.apache.org/thread/nzzvz0j6mlgfn4pldxg6988oqw20b0bx >> >> >> Bertrand Delacretaz 于2024年2月20日周二 19:32写道： >> >> > On Tue, Feb 20, 2024 at 10:45 AM Daniel Gruno >> > wrote: >> > > ...Just use the existing website-template repository, have the >> > > default branch be an empty branch with a README that tells you what the >> > > different examples are, each in their own branch or directory... >> > >> > And/or just point to the source code of existing ASF websites which >> > can serve as living examples. >> > >> > And encourage people to add GitHub topics to their website >> > repositories, so that queries like >> > >> > https://github.com/search?q=topic%3Ahugo+org%3Aapache=Repositories >> > >> > can give you a list of real live examples that use your favorite >> > website generation tool, "hugo" in this example. >> > >> > -Bertrand >> > >> > - >> > To unsubscribe, e-mail: dev-unsubscr...@community.apache.org >> > For additional commands, e-mail: dev-h...@community.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: dev-unsubscr...@community.apache.org For additional commands, e-mail: dev-h...@community.apache.org
