OK. So you are proposing that instead of documenting the plugin in the Log4j 
web site that we create a new site for it using GitHub Pages?

Ralph

> On Oct 18, 2021, at 12:45 PM, Matt Sicker <boa...@gmail.com> wrote:
> 
> The Maven shade plugin thing.
> 
> On Mon, Oct 18, 2021 at 2:44 PM Apache <ralph.go...@dslextreme.com> wrote:
>> 
>> What new plug-in?
>> 
>> Ralph
>> 
>>> On Oct 18, 2021, at 12:32 PM, Matt Sicker <boa...@gmail.com> wrote:
>>> 
>>> Testing the website publishing from the new plugin. It’s probably easier 
>>> to keep it under the ASF pages thing than it is to combine it with GH 
>>> pages. Since it’s storing generated markup in a git repo, it doesn’t matter 
>>> much which system it’s using besides whatever integration we already have 
>>> set up.
>>> 
>>> Matt Sicker
>>> 
>>>> On Oct 18, 2021, at 14:16, Ralph Goers <ralph.go...@dslextreme.com> wrote:
>>>> 
>>>> I feel like I am going in circles.
>>>> 
>>>> Testing of what? I still don’t understand what the use case is for GitHub 
>>>> Pages. What problem is it solving?
>>>> 
>>>> Ralph
>>>> 
>>>>>> On Oct 18, 2021, at 12:05 PM, Matt Sicker <boa...@gmail.com> wrote:
>>>>> 
>>>>> I’d imagine it’s for testing purposes initially. We should integrate it 
>>>>> into the main domain when it’s ready for release. This should all be 
>>>>> controllable via the .asf.yaml file.
>>>>> 
>>>>> Matt Sicker
>>>>> 
>>>>>>> On Oct 18, 2021, at 12:32, Ralph Goers <ralph.go...@dslextreme.com> 
>>>>>>> wrote:
>>>>>> 
>>>>>> Why?
>>>>>> 
>>>>>> Ralph
>>>>>> 
>>>>>>> On Oct 18, 2021, at 8:40 AM, Volkan Yazıcı <vol...@yazi.ci> wrote:
>>>>>>> 
>>>>>>> For the moment, I just want the `gh-pages` branch of the logging-log4j2
>>>>>>> GitHub project to be accessible at "a" URL – just like any other non-ASF
>>>>>>> GitHub project.
>>>>>>> 
>>>>>>>> On Mon, Oct 18, 2021 at 5:38 PM Ralph Goers 
>>>>>>>> <ralph.go...@dslextreme.com>
>>>>>>>> wrote:
>>>>>>>> 
>>>>>>>> OK. That page didn’t exist when I migrated the site from the CMS. That
>>>>>>>> still leaves
>>>>>>>> the second question. What are you proposing? I don’t really see the 
>>>>>>>> point
>>>>>>>> of moving
>>>>>>>> the existing site to GitHub Pages.
>>>>>>>> 
>>>>>>>> Ralph
>>>>>>>> 
>>>>>>>>> On Oct 18, 2021, at 8:31 AM, Volkan Yazıcı <vol...@yazi.ci> wrote:
>>>>>>>>> 
>>>>>>>>> GitHub Pages look pretty doable to me:
>>>>>>>>> https://cwiki.apache.org/confluence/display/INFRA/GitHub+Pages
>>>>>>>>> 
>>>>>>>>> On Fri, Oct 15, 2021 at 6:35 PM Ralph Goers 
>>>>>>>>> <ralph.go...@dslextreme.com>
>>>>>>>>> wrote:
>>>>>>>>> 
>>>>>>>>>> I don’t really understand this. When I was migrating the web site 
>>>>>>>>>> from
>>>>>>>> the
>>>>>>>>>> ASF CMS to GitHub
>>>>>>>>>> it was made clear that web site hosting using GitHub Pages wasn’t
>>>>>>>>>> supported. I am not sure
>>>>>>>>>> what the proposal here is.
>>>>>>>>>> 
>>>>>>>>>> Ralph
>>>>>>>>>> 
>>>>>>>>>>> On Oct 15, 2021, at 8:27 AM, Matt Sicker <boa...@gmail.com> wrote:
>>>>>>>>>>> 
>>>>>>>>>>> I’m not exactly sure how we can get a beta subdomain, though the
>>>>>>>> staging
>>>>>>>>>> one is built in. And while it would be great to automate as much as
>>>>>>>>>> possible about the release process in GHA, the code signing aspect is
>>>>>>>> still
>>>>>>>>>> not possible (though we might be able to integrate with another 
>>>>>>>>>> service
>>>>>>>> at
>>>>>>>>>> Apache for that, but it doesn’t cover the GPG signature). There’s 
>>>>>>>>>> also
>>>>>>>> some
>>>>>>>>>> ASF rule I think about releases needing to be done by a human, but 
>>>>>>>>>> that
>>>>>>>>>> might be more about reproducible builds.
>>>>>>>>>>> 
>>>>>>>>>>> Matt Sicker
>>>>>>>>>>> 
>>>>>>>>>>>> On Oct 15, 2021, at 05:57, Volkan Yazıcı <vol...@yazi.ci> wrote:
>>>>>>>>>>>> 
>>>>>>>>>>>> I long had the ambition to move the entire site & manual to 
>>>>>>>>>>>> gh-pages.
>>>>>>>>>>>> In an ideal world, I would even move the release process to GitHub
>>>>>>>>>> Actions
>>>>>>>>>>>> too.
>>>>>>>>>>>> But these are, for now, pretty ambitious goals.
>>>>>>>>>>>> What I would really appreciate is to access gh-pages content via, 
>>>>>>>>>>>> say,
>>>>>>>>>>>> https://beta.logging.apache.org/log4j URL.
>>>>>>>>>>>> Matt, mind helping me with setting this up please?
>>>>>>>>>>>> 
>>>>>>>>>>>>> On Wed, Oct 13, 2021 at 7:12 PM Matt Sicker <boa...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>>>> 
>>>>>>>>>>>>> That's really cool! Do note that we can publish to the 
>>>>>>>>>>>>> ASF-specific
>>>>>>>>>>>>> branches, too, for hosting a site.
>>>>>>>>>>>>> 
>>>>>>>>>>>>>> On Wed, Oct 13, 2021 at 10:37 AM Volkan Yazıcı <vol...@yazi.ci>
>>>>>>>>>> wrote:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> Do this:
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> git fetch -p
>>>>>>>>>>>>>> git checkout -B gh-pages origin/gh-pages
>>>>>>>>>>>>>> python -m http.server
>>>>>>>>>>>>>> open http://localhost:8000/benchmark/results/index.html
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> *The magic:*
>>>>>>>>>>>>>> 
>>>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> https://github.com/apache/logging-log4j2/blob/release-2.x/.github/workflows/benchmark.yml
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> *Disadvantages:* Runner specs are on the flux, though mostly 
>>>>>>>>>>>>>> pretty
>>>>>>>>>>>>> stable.
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> *Future work:*
>>>>>>>>>>>>>> 
>>>>>>>>>>>>>> - Enable GitHub pages for the project?
>>>>>>>>>>>>>> - Incorporate more from log4j-perf to here.
>>>>>>>>>>>>>> - Put the workflow onto a cron schedule.
>>>>>>>>>>>>> 
>>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>>>> 
>>>>>> 
>>>>>> 
>>>>> 
>>>> 
>>>> 
>>> 
>> 
>> 
> 


Reply via email to