You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@logging.apache.org by Ralph Goers <ra...@dslextreme.com> on 2018/06/10 21:26:11 UTC
[VOTE] Release Log4j Audit 1.0.0 RC1
This is a vote to release Log4j-Audit 1.0.0, the first release of the Log4j Audit project.
Please download, test, and cast your votes on the log4j developers list.
[] +1, release the artifacts
[] -1, don't release because...
The vote will remain open for 72 hours (or more if required). All votes are welcome and we encourage everyone to test the release, but only Logging PMC votes are “officially” counted. As always, at least 3 +1 votes and more positive than negative votes are required.
Tag:
a) for a new copy do "git clone https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and then "git checkout tags/log4-audit-1.0.0-rc1”
b) for an existing working copy to “git pull” and then “git checkout tags/log4j-audit-1.0.0-rc1”
Web Site: http://rgoers.github.io/log4j-audit/index.html
Maven Artifacts: https://repository.apache.org/content/repositories/orgapachelogging-1035/
Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
You may download all the Maven artifacts by executing:
wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate https://repository.apache.org/content/repositories/orgapachelogging-1035/org/apache/logging/log4j/
Ralph
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
I’m not sure I was clear. Log4j Audit does not provide a UI to view audit events. It provides the catalog so anyone implementing a UI can do so.
Ultimately, Log4j Audit is sending Structured Data Messages through Log4j. Log4j can be configured to deliver them anywhere, including Splunk, an SIEM tool, or Hadoop or Elastic Search.
Ralph
> On Jun 21, 2018, at 11:43 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> I haven't had a chance to use it extensively, but the UI for searching and
> displaying audit events sounds like the key end user feature here. For
> instance, I could see this being useful for helping detect security
> breaches.
>
> On 21 June 2018 at 13:40, Ralph Goers <ra...@dslextreme.com> wrote:
>
>> One of the things I am not sure I highlighted enough is the main benefits
>> of the catalog. They are
>> Validating the data associated with an event.
>> Providing metadata to UIs that want to display the data.
>>
>> The first may be somewhat obvious since the data is use to generate the
>> event interfaces, but the second isn’t obvious until you have data and want
>> to build an application to search and display it.
>>
>> Ralph
>>
>>> On Jun 21, 2018, at 8:57 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> Good catch with the announcement. I've already started proposing projects
>>> around this: <
>>> https://groups.google.com/forum/#!topic/jenkinsci-dev/MCN7x4KSWes>
>>>
>>> On 21 June 2018 at 10:21, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>
>>>> I also have to send the announcement.
>>>>
>>>> Ralph
>>>>
>>>>> On Jun 21, 2018, at 8:21 AM, Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>>
>>>>> OK, thanks. If you have time to fix these please do. Otherwise I will
>>>> get to it tonight or over the weekend.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Jun 21, 2018, at 8:12 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>
>>>>>> Also just noticed the "getting started" link in the intro paragraph
>> is a
>>>>>> dead link. The sidebar link is correct, though.
>>>>>>
>>>>>> On 21 June 2018 at 10:11, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>
>>>>>>> Looks like we forgot an htaccess redirect here:
>> http://logging.apache.
>>>>>>> org/log4j-audit/
>>>>>>>
>>>>>>> On 18 June 2018 at 03:32, Remko Popma <re...@gmail.com> wrote:
>>>>>>>
>>>>>>>> It’s the one called logo.jpg.
>>>>>>>> All png logo files are our modified versions AFAICS.
>>>>>>>>
>>>>>>>>
>>>>>>>>> On Jun 18, 2018, at 13:08, Ralph Goers <ralph.goers@dslextreme.com
>>>
>>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> I’m OK with that, assuming I can remember which one it was.
>>>>>>>>>
>>>>>>>>> Ralph
>>>>>>>>>
>>>>>>>>>> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com>
>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> About the logo: I would prefer that everywhere we use it we stick
>> to
>>>>>>>> the Log4j 2 logo as it was designed and not change the colors or
>>>> pattern
>>>>>>>> any more.
>>>>>>>>>>
>>>>>>>>>> The original looks much more clean and professional.
>>>>>>>>>>
>>>>>>>>>>> On Jun 18, 2018, at 2:06, Ralph Goers <
>> ralph.goers@dslextreme.com>
>>>>>>>> wrote:
>>>>>>>>>>>
>>>>>>>>>>> Thanks Matt!
>>>>>>>>>>>
>>>>>>>>>>> Any help you want to provide would of course be welcome! If you
>>>> have
>>>>>>>> ideas on how to improve the documentation please go for it!
>>>>>>>>>>>
>>>>>>>>>>> As for the Log4j logo, I didn’t see any reason not to use it and
>>>>>>>> didn’t really want to spend the time creating a new one.
>>>>>>>>>>>
>>>>>>>>>>> Ralph
>>>>>>>>>>>
>>>>>>>>>>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com>
>>>> wrote:
>>>>>>>>>>>>
>>>>>>>>>>>> +1
>>>>>>>>>>>>
>>>>>>>>>>>> Notes:
>>>>>>>>>>>>
>>>>>>>>>>>> * The git checkout command only worked for me without the
>> "tags/"
>>>>>>>> prefix to
>>>>>>>>>>>> the tag name, not sure why.
>>>>>>>>>>>> * If you change the wget command to use --cut-dirs=5, you can
>> use
>>>>>>>> the same
>>>>>>>>>>>> command with the dist.a.o URL, pretty handy for verifying the
>>>>>>>> artifacts
>>>>>>>>>>>> * I recently discovered you can use gpg --verify-files to verify
>>>>>>>> multiple
>>>>>>>>>>>> files in a single command, so a helper for that would be "find .
>>>>>>>> -name
>>>>>>>>>>>> '*.asc' | gpg --verify-files". This might be worth noting on our
>>>>>>>> download
>>>>>>>>>>>> pages.
>>>>>>>>>>>> * After our recent conversation about other uses for audit
>>>> logging,
>>>>>>>> I'm
>>>>>>>>>>>> interesting in writing a blog post on how to use this with
>>>> something
>>>>>>>> like
>>>>>>>>>>>> Zipkin.
>>>>>>>>>>>>
>>>>>>>>>>>> Site notes:
>>>>>>>>>>>> * Home page title is wrong. It has an errant "Log4j_Audit" in
>> it.
>>>>>>>>>>>> * Do we want to reuse the Log4j 2 logo here?
>>>>>>>>>>>> * Something looks off in the getting started page for code
>>>>>>>> formatting.
>>>>>>>>>>>> * A similar issue I have with the main Log4j site: it would be
>>>> nice
>>>>>>>> if
>>>>>>>>>>>> references to class names were linked to their javadoc pages.
>> This
>>>>>>>> might be
>>>>>>>>>>>> easier to do with asciidoc since it has better macros than
>>>> velocity.
>>>>>>>>>>>> * Your examples make me envy your production logs. They must be
>>>>>>>> rather well
>>>>>>>>>>>> organized!
>>>>>>>>>>>> * It'd be nice to migrate the docs to asciidoc in the future. I
>>>> can
>>>>>>>> handle
>>>>>>>>>>>> that conversion if you want (though it'd be after the release
>>>> work I
>>>>>>>> have
>>>>>>>>>>>> queued).
>>>>>>>>>>>>
>>>>>>>>>>>>
>>>>>>>>>>>> --
>>>>>>>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>>>>>>
>>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Matt Sicker <bo...@gmail.com>.
I haven't had a chance to use it extensively, but the UI for searching and
displaying audit events sounds like the key end user feature here. For
instance, I could see this being useful for helping detect security
breaches.
On 21 June 2018 at 13:40, Ralph Goers <ra...@dslextreme.com> wrote:
> One of the things I am not sure I highlighted enough is the main benefits
> of the catalog. They are
> Validating the data associated with an event.
> Providing metadata to UIs that want to display the data.
>
> The first may be somewhat obvious since the data is use to generate the
> event interfaces, but the second isn’t obvious until you have data and want
> to build an application to search and display it.
>
> Ralph
>
> > On Jun 21, 2018, at 8:57 AM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > Good catch with the announcement. I've already started proposing projects
> > around this: <
> > https://groups.google.com/forum/#!topic/jenkinsci-dev/MCN7x4KSWes>
> >
> > On 21 June 2018 at 10:21, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> >> I also have to send the announcement.
> >>
> >> Ralph
> >>
> >>> On Jun 21, 2018, at 8:21 AM, Ralph Goers <ra...@dslextreme.com>
> >> wrote:
> >>>
> >>> OK, thanks. If you have time to fix these please do. Otherwise I will
> >> get to it tonight or over the weekend.
> >>>
> >>> Ralph
> >>>
> >>>> On Jun 21, 2018, at 8:12 AM, Matt Sicker <bo...@gmail.com> wrote:
> >>>>
> >>>> Also just noticed the "getting started" link in the intro paragraph
> is a
> >>>> dead link. The sidebar link is correct, though.
> >>>>
> >>>> On 21 June 2018 at 10:11, Matt Sicker <bo...@gmail.com> wrote:
> >>>>
> >>>>> Looks like we forgot an htaccess redirect here:
> http://logging.apache.
> >>>>> org/log4j-audit/
> >>>>>
> >>>>> On 18 June 2018 at 03:32, Remko Popma <re...@gmail.com> wrote:
> >>>>>
> >>>>>> It’s the one called logo.jpg.
> >>>>>> All png logo files are our modified versions AFAICS.
> >>>>>>
> >>>>>>
> >>>>>>> On Jun 18, 2018, at 13:08, Ralph Goers <ralph.goers@dslextreme.com
> >
> >>>>>> wrote:
> >>>>>>>
> >>>>>>> I’m OK with that, assuming I can remember which one it was.
> >>>>>>>
> >>>>>>> Ralph
> >>>>>>>
> >>>>>>>> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com>
> >>>>>> wrote:
> >>>>>>>>
> >>>>>>>> About the logo: I would prefer that everywhere we use it we stick
> to
> >>>>>> the Log4j 2 logo as it was designed and not change the colors or
> >> pattern
> >>>>>> any more.
> >>>>>>>>
> >>>>>>>> The original looks much more clean and professional.
> >>>>>>>>
> >>>>>>>>> On Jun 18, 2018, at 2:06, Ralph Goers <
> ralph.goers@dslextreme.com>
> >>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> Thanks Matt!
> >>>>>>>>>
> >>>>>>>>> Any help you want to provide would of course be welcome! If you
> >> have
> >>>>>> ideas on how to improve the documentation please go for it!
> >>>>>>>>>
> >>>>>>>>> As for the Log4j logo, I didn’t see any reason not to use it and
> >>>>>> didn’t really want to spend the time creating a new one.
> >>>>>>>>>
> >>>>>>>>> Ralph
> >>>>>>>>>
> >>>>>>>>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com>
> >> wrote:
> >>>>>>>>>>
> >>>>>>>>>> +1
> >>>>>>>>>>
> >>>>>>>>>> Notes:
> >>>>>>>>>>
> >>>>>>>>>> * The git checkout command only worked for me without the
> "tags/"
> >>>>>> prefix to
> >>>>>>>>>> the tag name, not sure why.
> >>>>>>>>>> * If you change the wget command to use --cut-dirs=5, you can
> use
> >>>>>> the same
> >>>>>>>>>> command with the dist.a.o URL, pretty handy for verifying the
> >>>>>> artifacts
> >>>>>>>>>> * I recently discovered you can use gpg --verify-files to verify
> >>>>>> multiple
> >>>>>>>>>> files in a single command, so a helper for that would be "find .
> >>>>>> -name
> >>>>>>>>>> '*.asc' | gpg --verify-files". This might be worth noting on our
> >>>>>> download
> >>>>>>>>>> pages.
> >>>>>>>>>> * After our recent conversation about other uses for audit
> >> logging,
> >>>>>> I'm
> >>>>>>>>>> interesting in writing a blog post on how to use this with
> >> something
> >>>>>> like
> >>>>>>>>>> Zipkin.
> >>>>>>>>>>
> >>>>>>>>>> Site notes:
> >>>>>>>>>> * Home page title is wrong. It has an errant "Log4j_Audit" in
> it.
> >>>>>>>>>> * Do we want to reuse the Log4j 2 logo here?
> >>>>>>>>>> * Something looks off in the getting started page for code
> >>>>>> formatting.
> >>>>>>>>>> * A similar issue I have with the main Log4j site: it would be
> >> nice
> >>>>>> if
> >>>>>>>>>> references to class names were linked to their javadoc pages.
> This
> >>>>>> might be
> >>>>>>>>>> easier to do with asciidoc since it has better macros than
> >> velocity.
> >>>>>>>>>> * Your examples make me envy your production logs. They must be
> >>>>>> rather well
> >>>>>>>>>> organized!
> >>>>>>>>>> * It'd be nice to migrate the docs to asciidoc in the future. I
> >> can
> >>>>>> handle
> >>>>>>>>>> that conversion if you want (though it'd be after the release
> >> work I
> >>>>>> have
> >>>>>>>>>> queued).
> >>>>>>>>>>
> >>>>>>>>>>
> >>>>>>>>>> --
> >>>>>>>>>> Matt Sicker <bo...@gmail.com>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Matt Sicker <bo...@gmail.com>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Matt Sicker <bo...@gmail.com>
> >>>
> >>
> >>
> >>
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
One of the things I am not sure I highlighted enough is the main benefits of the catalog. They are
Validating the data associated with an event.
Providing metadata to UIs that want to display the data.
The first may be somewhat obvious since the data is use to generate the event interfaces, but the second isn’t obvious until you have data and want to build an application to search and display it.
Ralph
> On Jun 21, 2018, at 8:57 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> Good catch with the announcement. I've already started proposing projects
> around this: <
> https://groups.google.com/forum/#!topic/jenkinsci-dev/MCN7x4KSWes>
>
> On 21 June 2018 at 10:21, Ralph Goers <ra...@dslextreme.com> wrote:
>
>> I also have to send the announcement.
>>
>> Ralph
>>
>>> On Jun 21, 2018, at 8:21 AM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>
>>> OK, thanks. If you have time to fix these please do. Otherwise I will
>> get to it tonight or over the weekend.
>>>
>>> Ralph
>>>
>>>> On Jun 21, 2018, at 8:12 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>
>>>> Also just noticed the "getting started" link in the intro paragraph is a
>>>> dead link. The sidebar link is correct, though.
>>>>
>>>> On 21 June 2018 at 10:11, Matt Sicker <bo...@gmail.com> wrote:
>>>>
>>>>> Looks like we forgot an htaccess redirect here: http://logging.apache.
>>>>> org/log4j-audit/
>>>>>
>>>>> On 18 June 2018 at 03:32, Remko Popma <re...@gmail.com> wrote:
>>>>>
>>>>>> It’s the one called logo.jpg.
>>>>>> All png logo files are our modified versions AFAICS.
>>>>>>
>>>>>>
>>>>>>> On Jun 18, 2018, at 13:08, Ralph Goers <ra...@dslextreme.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> I’m OK with that, assuming I can remember which one it was.
>>>>>>>
>>>>>>> Ralph
>>>>>>>
>>>>>>>> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com>
>>>>>> wrote:
>>>>>>>>
>>>>>>>> About the logo: I would prefer that everywhere we use it we stick to
>>>>>> the Log4j 2 logo as it was designed and not change the colors or
>> pattern
>>>>>> any more.
>>>>>>>>
>>>>>>>> The original looks much more clean and professional.
>>>>>>>>
>>>>>>>>> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com>
>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> Thanks Matt!
>>>>>>>>>
>>>>>>>>> Any help you want to provide would of course be welcome! If you
>> have
>>>>>> ideas on how to improve the documentation please go for it!
>>>>>>>>>
>>>>>>>>> As for the Log4j logo, I didn’t see any reason not to use it and
>>>>>> didn’t really want to spend the time creating a new one.
>>>>>>>>>
>>>>>>>>> Ralph
>>>>>>>>>
>>>>>>>>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com>
>> wrote:
>>>>>>>>>>
>>>>>>>>>> +1
>>>>>>>>>>
>>>>>>>>>> Notes:
>>>>>>>>>>
>>>>>>>>>> * The git checkout command only worked for me without the "tags/"
>>>>>> prefix to
>>>>>>>>>> the tag name, not sure why.
>>>>>>>>>> * If you change the wget command to use --cut-dirs=5, you can use
>>>>>> the same
>>>>>>>>>> command with the dist.a.o URL, pretty handy for verifying the
>>>>>> artifacts
>>>>>>>>>> * I recently discovered you can use gpg --verify-files to verify
>>>>>> multiple
>>>>>>>>>> files in a single command, so a helper for that would be "find .
>>>>>> -name
>>>>>>>>>> '*.asc' | gpg --verify-files". This might be worth noting on our
>>>>>> download
>>>>>>>>>> pages.
>>>>>>>>>> * After our recent conversation about other uses for audit
>> logging,
>>>>>> I'm
>>>>>>>>>> interesting in writing a blog post on how to use this with
>> something
>>>>>> like
>>>>>>>>>> Zipkin.
>>>>>>>>>>
>>>>>>>>>> Site notes:
>>>>>>>>>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
>>>>>>>>>> * Do we want to reuse the Log4j 2 logo here?
>>>>>>>>>> * Something looks off in the getting started page for code
>>>>>> formatting.
>>>>>>>>>> * A similar issue I have with the main Log4j site: it would be
>> nice
>>>>>> if
>>>>>>>>>> references to class names were linked to their javadoc pages. This
>>>>>> might be
>>>>>>>>>> easier to do with asciidoc since it has better macros than
>> velocity.
>>>>>>>>>> * Your examples make me envy your production logs. They must be
>>>>>> rather well
>>>>>>>>>> organized!
>>>>>>>>>> * It'd be nice to migrate the docs to asciidoc in the future. I
>> can
>>>>>> handle
>>>>>>>>>> that conversion if you want (though it'd be after the release
>> work I
>>>>>> have
>>>>>>>>>> queued).
>>>>>>>>>>
>>>>>>>>>>
>>>>>>>>>> --
>>>>>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>> --
>>>>> Matt Sicker <bo...@gmail.com>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Matt Sicker <bo...@gmail.com>.
Good catch with the announcement. I've already started proposing projects
around this: <
https://groups.google.com/forum/#!topic/jenkinsci-dev/MCN7x4KSWes>
On 21 June 2018 at 10:21, Ralph Goers <ra...@dslextreme.com> wrote:
> I also have to send the announcement.
>
> Ralph
>
> > On Jun 21, 2018, at 8:21 AM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > OK, thanks. If you have time to fix these please do. Otherwise I will
> get to it tonight or over the weekend.
> >
> > Ralph
> >
> >> On Jun 21, 2018, at 8:12 AM, Matt Sicker <bo...@gmail.com> wrote:
> >>
> >> Also just noticed the "getting started" link in the intro paragraph is a
> >> dead link. The sidebar link is correct, though.
> >>
> >> On 21 June 2018 at 10:11, Matt Sicker <bo...@gmail.com> wrote:
> >>
> >>> Looks like we forgot an htaccess redirect here: http://logging.apache.
> >>> org/log4j-audit/
> >>>
> >>> On 18 June 2018 at 03:32, Remko Popma <re...@gmail.com> wrote:
> >>>
> >>>> It’s the one called logo.jpg.
> >>>> All png logo files are our modified versions AFAICS.
> >>>>
> >>>>
> >>>>> On Jun 18, 2018, at 13:08, Ralph Goers <ra...@dslextreme.com>
> >>>> wrote:
> >>>>>
> >>>>> I’m OK with that, assuming I can remember which one it was.
> >>>>>
> >>>>> Ralph
> >>>>>
> >>>>>> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com>
> >>>> wrote:
> >>>>>>
> >>>>>> About the logo: I would prefer that everywhere we use it we stick to
> >>>> the Log4j 2 logo as it was designed and not change the colors or
> pattern
> >>>> any more.
> >>>>>>
> >>>>>> The original looks much more clean and professional.
> >>>>>>
> >>>>>>> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com>
> >>>> wrote:
> >>>>>>>
> >>>>>>> Thanks Matt!
> >>>>>>>
> >>>>>>> Any help you want to provide would of course be welcome! If you
> have
> >>>> ideas on how to improve the documentation please go for it!
> >>>>>>>
> >>>>>>> As for the Log4j logo, I didn’t see any reason not to use it and
> >>>> didn’t really want to spend the time creating a new one.
> >>>>>>>
> >>>>>>> Ralph
> >>>>>>>
> >>>>>>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com>
> wrote:
> >>>>>>>>
> >>>>>>>> +1
> >>>>>>>>
> >>>>>>>> Notes:
> >>>>>>>>
> >>>>>>>> * The git checkout command only worked for me without the "tags/"
> >>>> prefix to
> >>>>>>>> the tag name, not sure why.
> >>>>>>>> * If you change the wget command to use --cut-dirs=5, you can use
> >>>> the same
> >>>>>>>> command with the dist.a.o URL, pretty handy for verifying the
> >>>> artifacts
> >>>>>>>> * I recently discovered you can use gpg --verify-files to verify
> >>>> multiple
> >>>>>>>> files in a single command, so a helper for that would be "find .
> >>>> -name
> >>>>>>>> '*.asc' | gpg --verify-files". This might be worth noting on our
> >>>> download
> >>>>>>>> pages.
> >>>>>>>> * After our recent conversation about other uses for audit
> logging,
> >>>> I'm
> >>>>>>>> interesting in writing a blog post on how to use this with
> something
> >>>> like
> >>>>>>>> Zipkin.
> >>>>>>>>
> >>>>>>>> Site notes:
> >>>>>>>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
> >>>>>>>> * Do we want to reuse the Log4j 2 logo here?
> >>>>>>>> * Something looks off in the getting started page for code
> >>>> formatting.
> >>>>>>>> * A similar issue I have with the main Log4j site: it would be
> nice
> >>>> if
> >>>>>>>> references to class names were linked to their javadoc pages. This
> >>>> might be
> >>>>>>>> easier to do with asciidoc since it has better macros than
> velocity.
> >>>>>>>> * Your examples make me envy your production logs. They must be
> >>>> rather well
> >>>>>>>> organized!
> >>>>>>>> * It'd be nice to migrate the docs to asciidoc in the future. I
> can
> >>>> handle
> >>>>>>>> that conversion if you want (though it'd be after the release
> work I
> >>>> have
> >>>>>>>> queued).
> >>>>>>>>
> >>>>>>>>
> >>>>>>>> --
> >>>>>>>> Matt Sicker <bo...@gmail.com>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>
> >>>
> >>>
> >>>
> >>> --
> >>> Matt Sicker <bo...@gmail.com>
> >>>
> >>
> >>
> >>
> >> --
> >> Matt Sicker <bo...@gmail.com>
> >
>
>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
I also have to send the announcement.
Ralph
> On Jun 21, 2018, at 8:21 AM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> OK, thanks. If you have time to fix these please do. Otherwise I will get to it tonight or over the weekend.
>
> Ralph
>
>> On Jun 21, 2018, at 8:12 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> Also just noticed the "getting started" link in the intro paragraph is a
>> dead link. The sidebar link is correct, though.
>>
>> On 21 June 2018 at 10:11, Matt Sicker <bo...@gmail.com> wrote:
>>
>>> Looks like we forgot an htaccess redirect here: http://logging.apache.
>>> org/log4j-audit/
>>>
>>> On 18 June 2018 at 03:32, Remko Popma <re...@gmail.com> wrote:
>>>
>>>> It’s the one called logo.jpg.
>>>> All png logo files are our modified versions AFAICS.
>>>>
>>>>
>>>>> On Jun 18, 2018, at 13:08, Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>>
>>>>> I’m OK with that, assuming I can remember which one it was.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com>
>>>> wrote:
>>>>>>
>>>>>> About the logo: I would prefer that everywhere we use it we stick to
>>>> the Log4j 2 logo as it was designed and not change the colors or pattern
>>>> any more.
>>>>>>
>>>>>> The original looks much more clean and professional.
>>>>>>
>>>>>>> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>>>>
>>>>>>> Thanks Matt!
>>>>>>>
>>>>>>> Any help you want to provide would of course be welcome! If you have
>>>> ideas on how to improve the documentation please go for it!
>>>>>>>
>>>>>>> As for the Log4j logo, I didn’t see any reason not to use it and
>>>> didn’t really want to spend the time creating a new one.
>>>>>>>
>>>>>>> Ralph
>>>>>>>
>>>>>>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>>>
>>>>>>>> +1
>>>>>>>>
>>>>>>>> Notes:
>>>>>>>>
>>>>>>>> * The git checkout command only worked for me without the "tags/"
>>>> prefix to
>>>>>>>> the tag name, not sure why.
>>>>>>>> * If you change the wget command to use --cut-dirs=5, you can use
>>>> the same
>>>>>>>> command with the dist.a.o URL, pretty handy for verifying the
>>>> artifacts
>>>>>>>> * I recently discovered you can use gpg --verify-files to verify
>>>> multiple
>>>>>>>> files in a single command, so a helper for that would be "find .
>>>> -name
>>>>>>>> '*.asc' | gpg --verify-files". This might be worth noting on our
>>>> download
>>>>>>>> pages.
>>>>>>>> * After our recent conversation about other uses for audit logging,
>>>> I'm
>>>>>>>> interesting in writing a blog post on how to use this with something
>>>> like
>>>>>>>> Zipkin.
>>>>>>>>
>>>>>>>> Site notes:
>>>>>>>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
>>>>>>>> * Do we want to reuse the Log4j 2 logo here?
>>>>>>>> * Something looks off in the getting started page for code
>>>> formatting.
>>>>>>>> * A similar issue I have with the main Log4j site: it would be nice
>>>> if
>>>>>>>> references to class names were linked to their javadoc pages. This
>>>> might be
>>>>>>>> easier to do with asciidoc since it has better macros than velocity.
>>>>>>>> * Your examples make me envy your production logs. They must be
>>>> rather well
>>>>>>>> organized!
>>>>>>>> * It'd be nice to migrate the docs to asciidoc in the future. I can
>>>> handle
>>>>>>>> that conversion if you want (though it'd be after the release work I
>>>> have
>>>>>>>> queued).
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
OK, thanks. If you have time to fix these please do. Otherwise I will get to it tonight or over the weekend.
Ralph
> On Jun 21, 2018, at 8:12 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> Also just noticed the "getting started" link in the intro paragraph is a
> dead link. The sidebar link is correct, though.
>
> On 21 June 2018 at 10:11, Matt Sicker <bo...@gmail.com> wrote:
>
>> Looks like we forgot an htaccess redirect here: http://logging.apache.
>> org/log4j-audit/
>>
>> On 18 June 2018 at 03:32, Remko Popma <re...@gmail.com> wrote:
>>
>>> It’s the one called logo.jpg.
>>> All png logo files are our modified versions AFAICS.
>>>
>>>
>>>> On Jun 18, 2018, at 13:08, Ralph Goers <ra...@dslextreme.com>
>>> wrote:
>>>>
>>>> I’m OK with that, assuming I can remember which one it was.
>>>>
>>>> Ralph
>>>>
>>>>> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com>
>>> wrote:
>>>>>
>>>>> About the logo: I would prefer that everywhere we use it we stick to
>>> the Log4j 2 logo as it was designed and not change the colors or pattern
>>> any more.
>>>>>
>>>>> The original looks much more clean and professional.
>>>>>
>>>>>> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com>
>>> wrote:
>>>>>>
>>>>>> Thanks Matt!
>>>>>>
>>>>>> Any help you want to provide would of course be welcome! If you have
>>> ideas on how to improve the documentation please go for it!
>>>>>>
>>>>>> As for the Log4j logo, I didn’t see any reason not to use it and
>>> didn’t really want to spend the time creating a new one.
>>>>>>
>>>>>> Ralph
>>>>>>
>>>>>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> Notes:
>>>>>>>
>>>>>>> * The git checkout command only worked for me without the "tags/"
>>> prefix to
>>>>>>> the tag name, not sure why.
>>>>>>> * If you change the wget command to use --cut-dirs=5, you can use
>>> the same
>>>>>>> command with the dist.a.o URL, pretty handy for verifying the
>>> artifacts
>>>>>>> * I recently discovered you can use gpg --verify-files to verify
>>> multiple
>>>>>>> files in a single command, so a helper for that would be "find .
>>> -name
>>>>>>> '*.asc' | gpg --verify-files". This might be worth noting on our
>>> download
>>>>>>> pages.
>>>>>>> * After our recent conversation about other uses for audit logging,
>>> I'm
>>>>>>> interesting in writing a blog post on how to use this with something
>>> like
>>>>>>> Zipkin.
>>>>>>>
>>>>>>> Site notes:
>>>>>>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
>>>>>>> * Do we want to reuse the Log4j 2 logo here?
>>>>>>> * Something looks off in the getting started page for code
>>> formatting.
>>>>>>> * A similar issue I have with the main Log4j site: it would be nice
>>> if
>>>>>>> references to class names were linked to their javadoc pages. This
>>> might be
>>>>>>> easier to do with asciidoc since it has better macros than velocity.
>>>>>>> * Your examples make me envy your production logs. They must be
>>> rather well
>>>>>>> organized!
>>>>>>> * It'd be nice to migrate the docs to asciidoc in the future. I can
>>> handle
>>>>>>> that conversion if you want (though it'd be after the release work I
>>> have
>>>>>>> queued).
>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>>
>>>>>>
>>>>>
>>>>
>>>>
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Matt Sicker <bo...@gmail.com>.
Also just noticed the "getting started" link in the intro paragraph is a
dead link. The sidebar link is correct, though.
On 21 June 2018 at 10:11, Matt Sicker <bo...@gmail.com> wrote:
> Looks like we forgot an htaccess redirect here: http://logging.apache.
> org/log4j-audit/
>
> On 18 June 2018 at 03:32, Remko Popma <re...@gmail.com> wrote:
>
>> It’s the one called logo.jpg.
>> All png logo files are our modified versions AFAICS.
>>
>>
>> > On Jun 18, 2018, at 13:08, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>> >
>> > I’m OK with that, assuming I can remember which one it was.
>> >
>> > Ralph
>> >
>> >> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com>
>> wrote:
>> >>
>> >> About the logo: I would prefer that everywhere we use it we stick to
>> the Log4j 2 logo as it was designed and not change the colors or pattern
>> any more.
>> >>
>> >> The original looks much more clean and professional.
>> >>
>> >>> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>> >>>
>> >>> Thanks Matt!
>> >>>
>> >>> Any help you want to provide would of course be welcome! If you have
>> ideas on how to improve the documentation please go for it!
>> >>>
>> >>> As for the Log4j logo, I didn’t see any reason not to use it and
>> didn’t really want to spend the time creating a new one.
>> >>>
>> >>> Ralph
>> >>>
>> >>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com> wrote:
>> >>>>
>> >>>> +1
>> >>>>
>> >>>> Notes:
>> >>>>
>> >>>> * The git checkout command only worked for me without the "tags/"
>> prefix to
>> >>>> the tag name, not sure why.
>> >>>> * If you change the wget command to use --cut-dirs=5, you can use
>> the same
>> >>>> command with the dist.a.o URL, pretty handy for verifying the
>> artifacts
>> >>>> * I recently discovered you can use gpg --verify-files to verify
>> multiple
>> >>>> files in a single command, so a helper for that would be "find .
>> -name
>> >>>> '*.asc' | gpg --verify-files". This might be worth noting on our
>> download
>> >>>> pages.
>> >>>> * After our recent conversation about other uses for audit logging,
>> I'm
>> >>>> interesting in writing a blog post on how to use this with something
>> like
>> >>>> Zipkin.
>> >>>>
>> >>>> Site notes:
>> >>>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
>> >>>> * Do we want to reuse the Log4j 2 logo here?
>> >>>> * Something looks off in the getting started page for code
>> formatting.
>> >>>> * A similar issue I have with the main Log4j site: it would be nice
>> if
>> >>>> references to class names were linked to their javadoc pages. This
>> might be
>> >>>> easier to do with asciidoc since it has better macros than velocity.
>> >>>> * Your examples make me envy your production logs. They must be
>> rather well
>> >>>> organized!
>> >>>> * It'd be nice to migrate the docs to asciidoc in the future. I can
>> handle
>> >>>> that conversion if you want (though it'd be after the release work I
>> have
>> >>>> queued).
>> >>>>
>> >>>>
>> >>>> --
>> >>>> Matt Sicker <bo...@gmail.com>
>> >>>
>> >>>
>> >>
>> >
>> >
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Matt Sicker <bo...@gmail.com>.
Looks like we forgot an htaccess redirect here:
http://logging.apache.org/log4j-audit/
On 18 June 2018 at 03:32, Remko Popma <re...@gmail.com> wrote:
> It’s the one called logo.jpg.
> All png logo files are our modified versions AFAICS.
>
>
> > On Jun 18, 2018, at 13:08, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > I’m OK with that, assuming I can remember which one it was.
> >
> > Ralph
> >
> >> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com> wrote:
> >>
> >> About the logo: I would prefer that everywhere we use it we stick to
> the Log4j 2 logo as it was designed and not change the colors or pattern
> any more.
> >>
> >> The original looks much more clean and professional.
> >>
> >>> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >>>
> >>> Thanks Matt!
> >>>
> >>> Any help you want to provide would of course be welcome! If you have
> ideas on how to improve the documentation please go for it!
> >>>
> >>> As for the Log4j logo, I didn’t see any reason not to use it and
> didn’t really want to spend the time creating a new one.
> >>>
> >>> Ralph
> >>>
> >>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com> wrote:
> >>>>
> >>>> +1
> >>>>
> >>>> Notes:
> >>>>
> >>>> * The git checkout command only worked for me without the "tags/"
> prefix to
> >>>> the tag name, not sure why.
> >>>> * If you change the wget command to use --cut-dirs=5, you can use the
> same
> >>>> command with the dist.a.o URL, pretty handy for verifying the
> artifacts
> >>>> * I recently discovered you can use gpg --verify-files to verify
> multiple
> >>>> files in a single command, so a helper for that would be "find . -name
> >>>> '*.asc' | gpg --verify-files". This might be worth noting on our
> download
> >>>> pages.
> >>>> * After our recent conversation about other uses for audit logging,
> I'm
> >>>> interesting in writing a blog post on how to use this with something
> like
> >>>> Zipkin.
> >>>>
> >>>> Site notes:
> >>>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
> >>>> * Do we want to reuse the Log4j 2 logo here?
> >>>> * Something looks off in the getting started page for code formatting.
> >>>> * A similar issue I have with the main Log4j site: it would be nice if
> >>>> references to class names were linked to their javadoc pages. This
> might be
> >>>> easier to do with asciidoc since it has better macros than velocity.
> >>>> * Your examples make me envy your production logs. They must be
> rather well
> >>>> organized!
> >>>> * It'd be nice to migrate the docs to asciidoc in the future. I can
> handle
> >>>> that conversion if you want (though it'd be after the release work I
> have
> >>>> queued).
> >>>>
> >>>>
> >>>> --
> >>>> Matt Sicker <bo...@gmail.com>
> >>>
> >>>
> >>
> >
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Remko Popma <re...@gmail.com>.
It’s the one called logo.jpg.
All png logo files are our modified versions AFAICS.
> On Jun 18, 2018, at 13:08, Ralph Goers <ra...@dslextreme.com> wrote:
>
> I’m OK with that, assuming I can remember which one it was.
>
> Ralph
>
>> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com> wrote:
>>
>> About the logo: I would prefer that everywhere we use it we stick to the Log4j 2 logo as it was designed and not change the colors or pattern any more.
>>
>> The original looks much more clean and professional.
>>
>>> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com> wrote:
>>>
>>> Thanks Matt!
>>>
>>> Any help you want to provide would of course be welcome! If you have ideas on how to improve the documentation please go for it!
>>>
>>> As for the Log4j logo, I didn’t see any reason not to use it and didn’t really want to spend the time creating a new one.
>>>
>>> Ralph
>>>
>>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>
>>>> +1
>>>>
>>>> Notes:
>>>>
>>>> * The git checkout command only worked for me without the "tags/" prefix to
>>>> the tag name, not sure why.
>>>> * If you change the wget command to use --cut-dirs=5, you can use the same
>>>> command with the dist.a.o URL, pretty handy for verifying the artifacts
>>>> * I recently discovered you can use gpg --verify-files to verify multiple
>>>> files in a single command, so a helper for that would be "find . -name
>>>> '*.asc' | gpg --verify-files". This might be worth noting on our download
>>>> pages.
>>>> * After our recent conversation about other uses for audit logging, I'm
>>>> interesting in writing a blog post on how to use this with something like
>>>> Zipkin.
>>>>
>>>> Site notes:
>>>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
>>>> * Do we want to reuse the Log4j 2 logo here?
>>>> * Something looks off in the getting started page for code formatting.
>>>> * A similar issue I have with the main Log4j site: it would be nice if
>>>> references to class names were linked to their javadoc pages. This might be
>>>> easier to do with asciidoc since it has better macros than velocity.
>>>> * Your examples make me envy your production logs. They must be rather well
>>>> organized!
>>>> * It'd be nice to migrate the docs to asciidoc in the future. I can handle
>>>> that conversion if you want (though it'd be after the release work I have
>>>> queued).
>>>>
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>
>>>
>>
>
>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
I’m OK with that, assuming I can remember which one it was.
Ralph
> On Jun 17, 2018, at 3:53 PM, Remko Popma <re...@gmail.com> wrote:
>
> About the logo: I would prefer that everywhere we use it we stick to the Log4j 2 logo as it was designed and not change the colors or pattern any more.
>
> The original looks much more clean and professional.
>
>> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com> wrote:
>>
>> Thanks Matt!
>>
>> Any help you want to provide would of course be welcome! If you have ideas on how to improve the documentation please go for it!
>>
>> As for the Log4j logo, I didn’t see any reason not to use it and didn’t really want to spend the time creating a new one.
>>
>> Ralph
>>
>>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> +1
>>>
>>> Notes:
>>>
>>> * The git checkout command only worked for me without the "tags/" prefix to
>>> the tag name, not sure why.
>>> * If you change the wget command to use --cut-dirs=5, you can use the same
>>> command with the dist.a.o URL, pretty handy for verifying the artifacts
>>> * I recently discovered you can use gpg --verify-files to verify multiple
>>> files in a single command, so a helper for that would be "find . -name
>>> '*.asc' | gpg --verify-files". This might be worth noting on our download
>>> pages.
>>> * After our recent conversation about other uses for audit logging, I'm
>>> interesting in writing a blog post on how to use this with something like
>>> Zipkin.
>>>
>>> Site notes:
>>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
>>> * Do we want to reuse the Log4j 2 logo here?
>>> * Something looks off in the getting started page for code formatting.
>>> * A similar issue I have with the main Log4j site: it would be nice if
>>> references to class names were linked to their javadoc pages. This might be
>>> easier to do with asciidoc since it has better macros than velocity.
>>> * Your examples make me envy your production logs. They must be rather well
>>> organized!
>>> * It'd be nice to migrate the docs to asciidoc in the future. I can handle
>>> that conversion if you want (though it'd be after the release work I have
>>> queued).
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>
>>
>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Remko Popma <re...@gmail.com>.
About the logo: I would prefer that everywhere we use it we stick to the Log4j 2 logo as it was designed and not change the colors or pattern any more.
The original looks much more clean and professional.
> On Jun 18, 2018, at 2:06, Ralph Goers <ra...@dslextreme.com> wrote:
>
> Thanks Matt!
>
> Any help you want to provide would of course be welcome! If you have ideas on how to improve the documentation please go for it!
>
> As for the Log4j logo, I didn’t see any reason not to use it and didn’t really want to spend the time creating a new one.
>
> Ralph
>
>> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> +1
>>
>> Notes:
>>
>> * The git checkout command only worked for me without the "tags/" prefix to
>> the tag name, not sure why.
>> * If you change the wget command to use --cut-dirs=5, you can use the same
>> command with the dist.a.o URL, pretty handy for verifying the artifacts
>> * I recently discovered you can use gpg --verify-files to verify multiple
>> files in a single command, so a helper for that would be "find . -name
>> '*.asc' | gpg --verify-files". This might be worth noting on our download
>> pages.
>> * After our recent conversation about other uses for audit logging, I'm
>> interesting in writing a blog post on how to use this with something like
>> Zipkin.
>>
>> Site notes:
>> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
>> * Do we want to reuse the Log4j 2 logo here?
>> * Something looks off in the getting started page for code formatting.
>> * A similar issue I have with the main Log4j site: it would be nice if
>> references to class names were linked to their javadoc pages. This might be
>> easier to do with asciidoc since it has better macros than velocity.
>> * Your examples make me envy your production logs. They must be rather well
>> organized!
>> * It'd be nice to migrate the docs to asciidoc in the future. I can handle
>> that conversion if you want (though it'd be after the release work I have
>> queued).
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>
>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
Thanks Matt!
Any help you want to provide would of course be welcome! If you have ideas on how to improve the documentation please go for it!
As for the Log4j logo, I didn’t see any reason not to use it and didn’t really want to spend the time creating a new one.
Ralph
> On Jun 17, 2018, at 9:23 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> +1
>
> Notes:
>
> * The git checkout command only worked for me without the "tags/" prefix to
> the tag name, not sure why.
> * If you change the wget command to use --cut-dirs=5, you can use the same
> command with the dist.a.o URL, pretty handy for verifying the artifacts
> * I recently discovered you can use gpg --verify-files to verify multiple
> files in a single command, so a helper for that would be "find . -name
> '*.asc' | gpg --verify-files". This might be worth noting on our download
> pages.
> * After our recent conversation about other uses for audit logging, I'm
> interesting in writing a blog post on how to use this with something like
> Zipkin.
>
> Site notes:
> * Home page title is wrong. It has an errant "Log4j_Audit" in it.
> * Do we want to reuse the Log4j 2 logo here?
> * Something looks off in the getting started page for code formatting.
> * A similar issue I have with the main Log4j site: it would be nice if
> references to class names were linked to their javadoc pages. This might be
> easier to do with asciidoc since it has better macros than velocity.
> * Your examples make me envy your production logs. They must be rather well
> organized!
> * It'd be nice to migrate the docs to asciidoc in the future. I can handle
> that conversion if you want (though it'd be after the release work I have
> queued).
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Matt Sicker <bo...@gmail.com>.
+1
Notes:
* The git checkout command only worked for me without the "tags/" prefix to
the tag name, not sure why.
* If you change the wget command to use --cut-dirs=5, you can use the same
command with the dist.a.o URL, pretty handy for verifying the artifacts
* I recently discovered you can use gpg --verify-files to verify multiple
files in a single command, so a helper for that would be "find . -name
'*.asc' | gpg --verify-files". This might be worth noting on our download
pages.
* After our recent conversation about other uses for audit logging, I'm
interesting in writing a blog post on how to use this with something like
Zipkin.
Site notes:
* Home page title is wrong. It has an errant "Log4j_Audit" in it.
* Do we want to reuse the Log4j 2 logo here?
* Something looks off in the getting started page for code formatting.
* A similar issue I have with the main Log4j site: it would be nice if
references to class names were linked to their javadoc pages. This might be
easier to do with asciidoc since it has better macros than velocity.
* Your examples make me envy your production logs. They must be rather well
organized!
* It'd be nice to migrate the docs to asciidoc in the future. I can handle
that conversion if you want (though it'd be after the release work I have
queued).
--
Matt Sicker <bo...@gmail.com>
Re: [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
My +1. Remko voted +1 on a different thread. We still need one more vote.
Ralph
> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> This is a vote to release Log4j-Audit 1.0.0, the first release of the Log4j Audit project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
> The vote will remain open for 72 hours (or more if required). All votes are welcome and we encourage everyone to test the release, but only Logging PMC votes are “officially” counted. As always, at least 3 +1 votes and more positive than negative votes are required.
>
> Tag:
> a) for a new copy do "git clone https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and then "git checkout tags/log4-audit-1.0.0-rc1”
> b) for an existing working copy to “git pull” and then “git checkout tags/log4j-audit-1.0.0-rc1”
>
> Web Site: http://rgoers.github.io/log4j-audit/index.html
>
> Maven Artifacts: https://repository.apache.org/content/repositories/orgapachelogging-1035/
>
> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate https://repository.apache.org/content/repositories/orgapachelogging-1035/org/apache/logging/log4j/
>
> Ralph
>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Carter Kozak <ck...@apache.org>.
I didn't realize I was eligible to vote, I'll take a closer look
through the codebase tomorrow.
-ck
On Thu, Jun 14, 2018 at 8:08 PM, Ralph Goers <ra...@dslextreme.com> wrote:
> I should have also pointed out that ANY PMC member, committer or user is welcome to look at the project and vote on it, not just those who typically participate in Log4j.
>
> Ralph
>
>> On Jun 14, 2018, at 4:35 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>>
>> Thanks Matt. Gary replied that he had started reviewing it 2 days OK. Mikael’s vote also would count on this but he has been very quiet for the last several months. I hope all is well.
>>
>> Ralph
>>
>>> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>
>>> I'll be back home tomorrow where I have computers set up for testing Apache
>>> releases.
>>>
>>> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
>>>
>>>> +1
>>>>
>>>> (Shameless plug) Every java main() method deserves http://picocli.info
>>>>
>>>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com> wrote:
>>>>>
>>>>> I started reading the site, which is good so far... should be able to
>>>>> continue tomorrow...
>>>>>
>>>>> Gary
>>>>>
>>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>>>
>>>>>> 48 hours have passed with no votes or discussion.
>>>>>>
>>>>>> Ralph
>>>>>>
>>>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com>
>>>>>> wrote:
>>>>>>>
>>>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of the
>>>>>> Log4j Audit project.
>>>>>>>
>>>>>>> Please download, test, and cast your votes on the log4j developers
>>>> list.
>>>>>>> [] +1, release the artifacts
>>>>>>> [] -1, don't release because...
>>>>>>>
>>>>>>> The vote will remain open for 72 hours (or more if required). All votes
>>>>>> are welcome and we encourage everyone to test the release, but only
>>>> Logging
>>>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
>>>> more
>>>>>> positive than negative votes are required.
>>>>>>>
>>>>>>> Tag:
>>>>>>> a) for a new copy do "git clone
>>>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and
>>>> then
>>>>>> "git checkout tags/log4-audit-1.0.0-rc1”
>>>>>>> b) for an existing working copy to “git pull” and then “git checkout
>>>>>> tags/log4j-audit-1.0.0-rc1”
>>>>>>>
>>>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
>>>>>>>
>>>>>>> Maven Artifacts:
>>>>>> https://repository.apache.org/content/repositories/
>>>> orgapachelogging-1035/
>>>>>>>
>>>>>>> Distribution archives:
>>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>>>>>>>
>>>>>>> You may download all the Maven artifacts by executing:
>>>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>>>>> https://repository.apache.org/content/repositories/
>>>> orgapachelogging-1035/org/apache/logging/log4j/
>>>>>>>
>>>>>>> Ralph
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>
>>>
>>>
>>>
>>> --
>>> Matt Sicker <bo...@gmail.com>
>>
>>
>>
>
>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
I should have also pointed out that ANY PMC member, committer or user is welcome to look at the project and vote on it, not just those who typically participate in Log4j.
Ralph
> On Jun 14, 2018, at 4:35 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> Thanks Matt. Gary replied that he had started reviewing it 2 days OK. Mikael’s vote also would count on this but he has been very quiet for the last several months. I hope all is well.
>
> Ralph
>
>> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> I'll be back home tomorrow where I have computers set up for testing Apache
>> releases.
>>
>> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
>>
>>> +1
>>>
>>> (Shameless plug) Every java main() method deserves http://picocli.info
>>>
>>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com> wrote:
>>>>
>>>> I started reading the site, which is good so far... should be able to
>>>> continue tomorrow...
>>>>
>>>> Gary
>>>>
>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com>
>>> wrote:
>>>>>
>>>>> 48 hours have passed with no votes or discussion.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com>
>>>>> wrote:
>>>>>>
>>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of the
>>>>> Log4j Audit project.
>>>>>>
>>>>>> Please download, test, and cast your votes on the log4j developers
>>> list.
>>>>>> [] +1, release the artifacts
>>>>>> [] -1, don't release because...
>>>>>>
>>>>>> The vote will remain open for 72 hours (or more if required). All votes
>>>>> are welcome and we encourage everyone to test the release, but only
>>> Logging
>>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
>>> more
>>>>> positive than negative votes are required.
>>>>>>
>>>>>> Tag:
>>>>>> a) for a new copy do "git clone
>>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and
>>> then
>>>>> "git checkout tags/log4-audit-1.0.0-rc1”
>>>>>> b) for an existing working copy to “git pull” and then “git checkout
>>>>> tags/log4j-audit-1.0.0-rc1”
>>>>>>
>>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
>>>>>>
>>>>>> Maven Artifacts:
>>>>> https://repository.apache.org/content/repositories/
>>> orgapachelogging-1035/
>>>>>>
>>>>>> Distribution archives:
>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>>>>>>
>>>>>> You may download all the Maven artifacts by executing:
>>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>>>> https://repository.apache.org/content/repositories/
>>> orgapachelogging-1035/org/apache/logging/log4j/
>>>>>>
>>>>>> Ralph
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>
>
>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Gary Gregory <ga...@gmail.com>.
Hi Ralph, I hope to to a bit more tomorrow morning.
Gary
On Thu, Jun 14, 2018 at 5:36 PM Ralph Goers <ra...@dslextreme.com>
wrote:
> Thanks Matt. Gary replied that he had started reviewing it 2 days OK.
> Mikael’s vote also would count on this but he has been very quiet for the
> last several months. I hope all is well.
>
> Ralph
>
> > On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
> >
> > I'll be back home tomorrow where I have computers set up for testing
> Apache
> > releases.
> >
> > On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
> >
> >> +1
> >>
> >> (Shameless plug) Every java main() method deserves http://picocli.info
> >>
> >>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com> wrote:
> >>>
> >>> I started reading the site, which is good so far... should be able to
> >>> continue tomorrow...
> >>>
> >>> Gary
> >>>
> >>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com>
> >> wrote:
> >>>>
> >>>> 48 hours have passed with no votes or discussion.
> >>>>
> >>>> Ralph
> >>>>
> >>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ralph.goers@dslextreme.com
> >
> >>>> wrote:
> >>>>>
> >>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of the
> >>>> Log4j Audit project.
> >>>>>
> >>>>> Please download, test, and cast your votes on the log4j developers
> >> list.
> >>>>> [] +1, release the artifacts
> >>>>> [] -1, don't release because...
> >>>>>
> >>>>> The vote will remain open for 72 hours (or more if required). All
> votes
> >>>> are welcome and we encourage everyone to test the release, but only
> >> Logging
> >>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
> >> more
> >>>> positive than negative votes are required.
> >>>>>
> >>>>> Tag:
> >>>>> a) for a new copy do "git clone
> >>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and
> >> then
> >>>> "git checkout tags/log4-audit-1.0.0-rc1”
> >>>>> b) for an existing working copy to “git pull” and then “git checkout
> >>>> tags/log4j-audit-1.0.0-rc1”
> >>>>>
> >>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
> >>>>>
> >>>>> Maven Artifacts:
> >>>> https://repository.apache.org/content/repositories/
> >> orgapachelogging-1035/
> >>>>>
> >>>>> Distribution archives:
> >>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
> >>>>>
> >>>>> You may download all the Maven artifacts by executing:
> >>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> >>>> https://repository.apache.org/content/repositories/
> >> orgapachelogging-1035/org/apache/logging/log4j/
> >>>>>
> >>>>> Ralph
> >>>>>
> >>>>
> >>>>
> >>>>
> >>
> >
> >
> >
> > --
> > Matt Sicker <bo...@gmail.com>
>
>
>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Matt Sicker <bo...@gmail.com>.
Added my vote. Apologies for not getting to this sooner. I should've
brought an extra laptop with me on the trip.
On 17 June 2018 at 10:31, Matt Sicker <bo...@gmail.com> wrote:
> I’m back home now and will review this today.
>
> On Sun, Jun 17, 2018 at 08:59, Apache <ra...@dslextreme.com> wrote:
>
>> Today this vote will have been open 1 week. I would ask that you please
>> find the time to review it and vote.
>>
>> Ralph
>>
>> > On Jun 15, 2018, at 5:34 PM, Gary Gregory <ga...@gmail.com>
>> wrote:
>> >
>> > Good points.
>> >
>> > I see use cases for audit logging in at least two of my products at
>> work,
>> > so I have no doubts as to the usefulness of this project.
>> >
>> > Gary
>> >
>> > On Fri, Jun 15, 2018 at 6:10 PM Ralph Goers <ralph.goers@dslextreme.com
>> >
>> > wrote:
>> >
>> >> The only criteria I am aware of for voting for a release is that it has
>> >> the proper notice and license files and is properly signed. AFAIK
>> nothing
>> >> says it has to actually build. That said, voting on such a release
>> would be
>> >> stupid.
>> >>
>> >> Obviously, I would like others to use (and support) the project or I
>> >> wouldn’t have bothered creating it here. At the same time I really
>> wouldn’t
>> >> like to have the software just languish.
>> >>
>> >> The bottom line is you should use whatever criteria makes YOU
>> comfortable,
>> >> not me.
>> >>
>> >> Ralph
>> >>
>> >>> On Jun 15, 2018, at 4:29 PM, Gary Gregory <ga...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Ralph,
>> >>>
>> >>> I kind of feel bad just VOTing by running through the build motions
>> and
>> >> not
>> >>> having an application to actually test. That would just mean that I
>> can
>> >>> build the software and look at reports.
>> >>>
>> >>> Do you feel comfortable with this kind of VOTE?
>> >>>
>> >>> Gary
>> >>>
>> >>> On Fri, Jun 15, 2018 at 5:08 PM Ralph Goers <
>> ralph.goers@dslextreme.com>
>> >>> wrote:
>> >>>
>> >>>> This vote has now been open 5 days and needs one more +1 vote from a
>> PMC
>> >>>> member. Again, votes from everyone are welcome.
>> >>>>
>> >>>> Ralph
>> >>>>
>> >>>>> On Jun 14, 2018, at 4:35 PM, Ralph Goers <
>> ralph.goers@dslextreme.com>
>> >>>> wrote:
>> >>>>>
>> >>>>> Thanks Matt. Gary replied that he had started reviewing it 2 days
>> OK.
>> >>>> Mikael’s vote also would count on this but he has been very quiet for
>> >> the
>> >>>> last several months. I hope all is well.
>> >>>>>
>> >>>>> Ralph
>> >>>>>
>> >>>>>> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
>> >>>>>>
>> >>>>>> I'll be back home tomorrow where I have computers set up for
>> testing
>> >>>> Apache
>> >>>>>> releases.
>> >>>>>>
>> >>>>>>> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com>
>> wrote:
>> >>>>>>>
>> >>>>>>> +1
>> >>>>>>>
>> >>>>>>> (Shameless plug) Every java main() method deserves
>> >> http://picocli.info
>> >>>>>>>
>> >>>>>>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com>
>> >>>> wrote:
>> >>>>>>>>
>> >>>>>>>> I started reading the site, which is good so far... should be
>> able
>> >> to
>> >>>>>>>> continue tomorrow...
>> >>>>>>>>
>> >>>>>>>> Gary
>> >>>>>>>>
>> >>>>>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <
>> >> ralph.goers@dslextreme.com>
>> >>>>>>> wrote:
>> >>>>>>>>>
>> >>>>>>>>> 48 hours have passed with no votes or discussion.
>> >>>>>>>>>
>> >>>>>>>>> Ralph
>> >>>>>>>>>
>> >>>>>>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <
>> >>>> ralph.goers@dslextreme.com>
>> >>>>>>>>> wrote:
>> >>>>>>>>>>
>> >>>>>>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release
>> of
>> >>>> the
>> >>>>>>>>> Log4j Audit project.
>> >>>>>>>>>>
>> >>>>>>>>>> Please download, test, and cast your votes on the log4j
>> developers
>> >>>>>>> list.
>> >>>>>>>>>> [] +1, release the artifacts
>> >>>>>>>>>> [] -1, don't release because...
>> >>>>>>>>>>
>> >>>>>>>>>> The vote will remain open for 72 hours (or more if required).
>> All
>> >>>> votes
>> >>>>>>>>> are welcome and we encourage everyone to test the release, but
>> only
>> >>>>>>> Logging
>> >>>>>>>>> PMC votes are “officially” counted. As always, at least 3 +1
>> votes
>> >>>> and
>> >>>>>>> more
>> >>>>>>>>> positive than negative votes are required.
>> >>>>>>>>>>
>> >>>>>>>>>> Tag:
>> >>>>>>>>>> a) for a new copy do "git clone
>> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git
>> "
>> >> and
>> >>>>>>> then
>> >>>>>>>>> "git checkout tags/log4-audit-1.0.0-rc1”
>> >>>>>>>>>> b) for an existing working copy to “git pull” and then “git
>> >> checkout
>> >>>>>>>>> tags/log4j-audit-1.0.0-rc1”
>> >>>>>>>>>>
>> >>>>>>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
>> >>>>>>>>>>
>> >>>>>>>>>> Maven Artifacts:
>> >>>>>>>>> https://repository.apache.org/content/repositories/
>> >>>>>>> orgapachelogging-1035/
>> >>>>>>>>>>
>> >>>>>>>>>> Distribution archives:
>> >>>>>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>> >>>>>>>>>>
>> >>>>>>>>>> You may download all the Maven artifacts by executing:
>> >>>>>>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np
>> >> --no-check-certificate
>> >>>>>>>>> https://repository.apache.org/content/repositories/
>> >>>>>>> orgapachelogging-1035/org/apache/logging/log4j/
>> >>>>>>>>>>
>> >>>>>>>>>> Ralph
>> >>>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>>>
>> >>>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>>
>> >>>>>> --
>> >>>>>> Matt Sicker <bo...@gmail.com>
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>
>> >>>>
>> >>>>
>> >>
>> >>
>> >>
>>
>>
>> --
> Matt Sicker <bo...@gmail.com>
>
--
Matt Sicker <bo...@gmail.com>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Matt Sicker <bo...@gmail.com>.
I’m back home now and will review this today.
On Sun, Jun 17, 2018 at 08:59, Apache <ra...@dslextreme.com> wrote:
> Today this vote will have been open 1 week. I would ask that you please
> find the time to review it and vote.
>
> Ralph
>
> > On Jun 15, 2018, at 5:34 PM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > Good points.
> >
> > I see use cases for audit logging in at least two of my products at work,
> > so I have no doubts as to the usefulness of this project.
> >
> > Gary
> >
> > On Fri, Jun 15, 2018 at 6:10 PM Ralph Goers <ra...@dslextreme.com>
> > wrote:
> >
> >> The only criteria I am aware of for voting for a release is that it has
> >> the proper notice and license files and is properly signed. AFAIK
> nothing
> >> says it has to actually build. That said, voting on such a release
> would be
> >> stupid.
> >>
> >> Obviously, I would like others to use (and support) the project or I
> >> wouldn’t have bothered creating it here. At the same time I really
> wouldn’t
> >> like to have the software just languish.
> >>
> >> The bottom line is you should use whatever criteria makes YOU
> comfortable,
> >> not me.
> >>
> >> Ralph
> >>
> >>> On Jun 15, 2018, at 4:29 PM, Gary Gregory <ga...@gmail.com>
> >> wrote:
> >>>
> >>> Ralph,
> >>>
> >>> I kind of feel bad just VOTing by running through the build motions and
> >> not
> >>> having an application to actually test. That would just mean that I can
> >>> build the software and look at reports.
> >>>
> >>> Do you feel comfortable with this kind of VOTE?
> >>>
> >>> Gary
> >>>
> >>> On Fri, Jun 15, 2018 at 5:08 PM Ralph Goers <
> ralph.goers@dslextreme.com>
> >>> wrote:
> >>>
> >>>> This vote has now been open 5 days and needs one more +1 vote from a
> PMC
> >>>> member. Again, votes from everyone are welcome.
> >>>>
> >>>> Ralph
> >>>>
> >>>>> On Jun 14, 2018, at 4:35 PM, Ralph Goers <ralph.goers@dslextreme.com
> >
> >>>> wrote:
> >>>>>
> >>>>> Thanks Matt. Gary replied that he had started reviewing it 2 days OK.
> >>>> Mikael’s vote also would count on this but he has been very quiet for
> >> the
> >>>> last several months. I hope all is well.
> >>>>>
> >>>>> Ralph
> >>>>>
> >>>>>> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
> >>>>>>
> >>>>>> I'll be back home tomorrow where I have computers set up for testing
> >>>> Apache
> >>>>>> releases.
> >>>>>>
> >>>>>>> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com>
> wrote:
> >>>>>>>
> >>>>>>> +1
> >>>>>>>
> >>>>>>> (Shameless plug) Every java main() method deserves
> >> http://picocli.info
> >>>>>>>
> >>>>>>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com>
> >>>> wrote:
> >>>>>>>>
> >>>>>>>> I started reading the site, which is good so far... should be able
> >> to
> >>>>>>>> continue tomorrow...
> >>>>>>>>
> >>>>>>>> Gary
> >>>>>>>>
> >>>>>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <
> >> ralph.goers@dslextreme.com>
> >>>>>>> wrote:
> >>>>>>>>>
> >>>>>>>>> 48 hours have passed with no votes or discussion.
> >>>>>>>>>
> >>>>>>>>> Ralph
> >>>>>>>>>
> >>>>>>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <
> >>>> ralph.goers@dslextreme.com>
> >>>>>>>>> wrote:
> >>>>>>>>>>
> >>>>>>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release
> of
> >>>> the
> >>>>>>>>> Log4j Audit project.
> >>>>>>>>>>
> >>>>>>>>>> Please download, test, and cast your votes on the log4j
> developers
> >>>>>>> list.
> >>>>>>>>>> [] +1, release the artifacts
> >>>>>>>>>> [] -1, don't release because...
> >>>>>>>>>>
> >>>>>>>>>> The vote will remain open for 72 hours (or more if required).
> All
> >>>> votes
> >>>>>>>>> are welcome and we encourage everyone to test the release, but
> only
> >>>>>>> Logging
> >>>>>>>>> PMC votes are “officially” counted. As always, at least 3 +1
> votes
> >>>> and
> >>>>>>> more
> >>>>>>>>> positive than negative votes are required.
> >>>>>>>>>>
> >>>>>>>>>> Tag:
> >>>>>>>>>> a) for a new copy do "git clone
> >>>>>>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git"
> >> and
> >>>>>>> then
> >>>>>>>>> "git checkout tags/log4-audit-1.0.0-rc1”
> >>>>>>>>>> b) for an existing working copy to “git pull” and then “git
> >> checkout
> >>>>>>>>> tags/log4j-audit-1.0.0-rc1”
> >>>>>>>>>>
> >>>>>>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
> >>>>>>>>>>
> >>>>>>>>>> Maven Artifacts:
> >>>>>>>>> https://repository.apache.org/content/repositories/
> >>>>>>> orgapachelogging-1035/
> >>>>>>>>>>
> >>>>>>>>>> Distribution archives:
> >>>>>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
> >>>>>>>>>>
> >>>>>>>>>> You may download all the Maven artifacts by executing:
> >>>>>>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np
> >> --no-check-certificate
> >>>>>>>>> https://repository.apache.org/content/repositories/
> >>>>>>> orgapachelogging-1035/org/apache/logging/log4j/
> >>>>>>>>>>
> >>>>>>>>>> Ralph
> >>>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>> --
> >>>>>> Matt Sicker <bo...@gmail.com>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>
> >>
> >>
>
>
> --
Matt Sicker <bo...@gmail.com>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Apache <ra...@dslextreme.com>.
Today this vote will have been open 1 week. I would ask that you please find the time to review it and vote.
Ralph
> On Jun 15, 2018, at 5:34 PM, Gary Gregory <ga...@gmail.com> wrote:
>
> Good points.
>
> I see use cases for audit logging in at least two of my products at work,
> so I have no doubts as to the usefulness of this project.
>
> Gary
>
> On Fri, Jun 15, 2018 at 6:10 PM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> The only criteria I am aware of for voting for a release is that it has
>> the proper notice and license files and is properly signed. AFAIK nothing
>> says it has to actually build. That said, voting on such a release would be
>> stupid.
>>
>> Obviously, I would like others to use (and support) the project or I
>> wouldn’t have bothered creating it here. At the same time I really wouldn’t
>> like to have the software just languish.
>>
>> The bottom line is you should use whatever criteria makes YOU comfortable,
>> not me.
>>
>> Ralph
>>
>>> On Jun 15, 2018, at 4:29 PM, Gary Gregory <ga...@gmail.com>
>> wrote:
>>>
>>> Ralph,
>>>
>>> I kind of feel bad just VOTing by running through the build motions and
>> not
>>> having an application to actually test. That would just mean that I can
>>> build the software and look at reports.
>>>
>>> Do you feel comfortable with this kind of VOTE?
>>>
>>> Gary
>>>
>>> On Fri, Jun 15, 2018 at 5:08 PM Ralph Goers <ra...@dslextreme.com>
>>> wrote:
>>>
>>>> This vote has now been open 5 days and needs one more +1 vote from a PMC
>>>> member. Again, votes from everyone are welcome.
>>>>
>>>> Ralph
>>>>
>>>>> On Jun 14, 2018, at 4:35 PM, Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>>
>>>>> Thanks Matt. Gary replied that he had started reviewing it 2 days OK.
>>>> Mikael’s vote also would count on this but he has been very quiet for
>> the
>>>> last several months. I hope all is well.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>>>
>>>>>> I'll be back home tomorrow where I have computers set up for testing
>>>> Apache
>>>>>> releases.
>>>>>>
>>>>>>> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
>>>>>>>
>>>>>>> +1
>>>>>>>
>>>>>>> (Shameless plug) Every java main() method deserves
>> http://picocli.info
>>>>>>>
>>>>>>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com>
>>>> wrote:
>>>>>>>>
>>>>>>>> I started reading the site, which is good so far... should be able
>> to
>>>>>>>> continue tomorrow...
>>>>>>>>
>>>>>>>> Gary
>>>>>>>>
>>>>>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <
>> ralph.goers@dslextreme.com>
>>>>>>> wrote:
>>>>>>>>>
>>>>>>>>> 48 hours have passed with no votes or discussion.
>>>>>>>>>
>>>>>>>>> Ralph
>>>>>>>>>
>>>>>>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <
>>>> ralph.goers@dslextreme.com>
>>>>>>>>> wrote:
>>>>>>>>>>
>>>>>>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of
>>>> the
>>>>>>>>> Log4j Audit project.
>>>>>>>>>>
>>>>>>>>>> Please download, test, and cast your votes on the log4j developers
>>>>>>> list.
>>>>>>>>>> [] +1, release the artifacts
>>>>>>>>>> [] -1, don't release because...
>>>>>>>>>>
>>>>>>>>>> The vote will remain open for 72 hours (or more if required). All
>>>> votes
>>>>>>>>> are welcome and we encourage everyone to test the release, but only
>>>>>>> Logging
>>>>>>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes
>>>> and
>>>>>>> more
>>>>>>>>> positive than negative votes are required.
>>>>>>>>>>
>>>>>>>>>> Tag:
>>>>>>>>>> a) for a new copy do "git clone
>>>>>>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git"
>> and
>>>>>>> then
>>>>>>>>> "git checkout tags/log4-audit-1.0.0-rc1”
>>>>>>>>>> b) for an existing working copy to “git pull” and then “git
>> checkout
>>>>>>>>> tags/log4j-audit-1.0.0-rc1”
>>>>>>>>>>
>>>>>>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
>>>>>>>>>>
>>>>>>>>>> Maven Artifacts:
>>>>>>>>> https://repository.apache.org/content/repositories/
>>>>>>> orgapachelogging-1035/
>>>>>>>>>>
>>>>>>>>>> Distribution archives:
>>>>>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>>>>>>>>>>
>>>>>>>>>> You may download all the Maven artifacts by executing:
>>>>>>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np
>> --no-check-certificate
>>>>>>>>> https://repository.apache.org/content/repositories/
>>>>>>> orgapachelogging-1035/org/apache/logging/log4j/
>>>>>>>>>>
>>>>>>>>>> Ralph
>>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matt Sicker <bo...@gmail.com>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>
>>
>>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Gary Gregory <ga...@gmail.com>.
Good points.
I see use cases for audit logging in at least two of my products at work,
so I have no doubts as to the usefulness of this project.
Gary
On Fri, Jun 15, 2018 at 6:10 PM Ralph Goers <ra...@dslextreme.com>
wrote:
> The only criteria I am aware of for voting for a release is that it has
> the proper notice and license files and is properly signed. AFAIK nothing
> says it has to actually build. That said, voting on such a release would be
> stupid.
>
> Obviously, I would like others to use (and support) the project or I
> wouldn’t have bothered creating it here. At the same time I really wouldn’t
> like to have the software just languish.
>
> The bottom line is you should use whatever criteria makes YOU comfortable,
> not me.
>
> Ralph
>
> > On Jun 15, 2018, at 4:29 PM, Gary Gregory <ga...@gmail.com>
> wrote:
> >
> > Ralph,
> >
> > I kind of feel bad just VOTing by running through the build motions and
> not
> > having an application to actually test. That would just mean that I can
> > build the software and look at reports.
> >
> > Do you feel comfortable with this kind of VOTE?
> >
> > Gary
> >
> > On Fri, Jun 15, 2018 at 5:08 PM Ralph Goers <ra...@dslextreme.com>
> > wrote:
> >
> >> This vote has now been open 5 days and needs one more +1 vote from a PMC
> >> member. Again, votes from everyone are welcome.
> >>
> >> Ralph
> >>
> >>> On Jun 14, 2018, at 4:35 PM, Ralph Goers <ra...@dslextreme.com>
> >> wrote:
> >>>
> >>> Thanks Matt. Gary replied that he had started reviewing it 2 days OK.
> >> Mikael’s vote also would count on this but he has been very quiet for
> the
> >> last several months. I hope all is well.
> >>>
> >>> Ralph
> >>>
> >>>> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
> >>>>
> >>>> I'll be back home tomorrow where I have computers set up for testing
> >> Apache
> >>>> releases.
> >>>>
> >>>> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
> >>>>
> >>>>> +1
> >>>>>
> >>>>> (Shameless plug) Every java main() method deserves
> http://picocli.info
> >>>>>
> >>>>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com>
> >> wrote:
> >>>>>>
> >>>>>> I started reading the site, which is good so far... should be able
> to
> >>>>>> continue tomorrow...
> >>>>>>
> >>>>>> Gary
> >>>>>>
> >>>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <
> ralph.goers@dslextreme.com>
> >>>>> wrote:
> >>>>>>>
> >>>>>>> 48 hours have passed with no votes or discussion.
> >>>>>>>
> >>>>>>> Ralph
> >>>>>>>
> >>>>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <
> >> ralph.goers@dslextreme.com>
> >>>>>>> wrote:
> >>>>>>>>
> >>>>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of
> >> the
> >>>>>>> Log4j Audit project.
> >>>>>>>>
> >>>>>>>> Please download, test, and cast your votes on the log4j developers
> >>>>> list.
> >>>>>>>> [] +1, release the artifacts
> >>>>>>>> [] -1, don't release because...
> >>>>>>>>
> >>>>>>>> The vote will remain open for 72 hours (or more if required). All
> >> votes
> >>>>>>> are welcome and we encourage everyone to test the release, but only
> >>>>> Logging
> >>>>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes
> >> and
> >>>>> more
> >>>>>>> positive than negative votes are required.
> >>>>>>>>
> >>>>>>>> Tag:
> >>>>>>>> a) for a new copy do "git clone
> >>>>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git"
> and
> >>>>> then
> >>>>>>> "git checkout tags/log4-audit-1.0.0-rc1”
> >>>>>>>> b) for an existing working copy to “git pull” and then “git
> checkout
> >>>>>>> tags/log4j-audit-1.0.0-rc1”
> >>>>>>>>
> >>>>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
> >>>>>>>>
> >>>>>>>> Maven Artifacts:
> >>>>>>> https://repository.apache.org/content/repositories/
> >>>>> orgapachelogging-1035/
> >>>>>>>>
> >>>>>>>> Distribution archives:
> >>>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
> >>>>>>>>
> >>>>>>>> You may download all the Maven artifacts by executing:
> >>>>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np
> --no-check-certificate
> >>>>>>> https://repository.apache.org/content/repositories/
> >>>>> orgapachelogging-1035/org/apache/logging/log4j/
> >>>>>>>>
> >>>>>>>> Ralph
> >>>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Matt Sicker <bo...@gmail.com>
> >>>
> >>>
> >>>
> >>
> >>
> >>
>
>
>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
The only criteria I am aware of for voting for a release is that it has the proper notice and license files and is properly signed. AFAIK nothing says it has to actually build. That said, voting on such a release would be stupid.
Obviously, I would like others to use (and support) the project or I wouldn’t have bothered creating it here. At the same time I really wouldn’t like to have the software just languish.
The bottom line is you should use whatever criteria makes YOU comfortable, not me.
Ralph
> On Jun 15, 2018, at 4:29 PM, Gary Gregory <ga...@gmail.com> wrote:
>
> Ralph,
>
> I kind of feel bad just VOTing by running through the build motions and not
> having an application to actually test. That would just mean that I can
> build the software and look at reports.
>
> Do you feel comfortable with this kind of VOTE?
>
> Gary
>
> On Fri, Jun 15, 2018 at 5:08 PM Ralph Goers <ra...@dslextreme.com>
> wrote:
>
>> This vote has now been open 5 days and needs one more +1 vote from a PMC
>> member. Again, votes from everyone are welcome.
>>
>> Ralph
>>
>>> On Jun 14, 2018, at 4:35 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>
>>> Thanks Matt. Gary replied that he had started reviewing it 2 days OK.
>> Mikael’s vote also would count on this but he has been very quiet for the
>> last several months. I hope all is well.
>>>
>>> Ralph
>>>
>>>> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
>>>>
>>>> I'll be back home tomorrow where I have computers set up for testing
>> Apache
>>>> releases.
>>>>
>>>> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
>>>>
>>>>> +1
>>>>>
>>>>> (Shameless plug) Every java main() method deserves http://picocli.info
>>>>>
>>>>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com>
>> wrote:
>>>>>>
>>>>>> I started reading the site, which is good so far... should be able to
>>>>>> continue tomorrow...
>>>>>>
>>>>>> Gary
>>>>>>
>>>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com>
>>>>> wrote:
>>>>>>>
>>>>>>> 48 hours have passed with no votes or discussion.
>>>>>>>
>>>>>>> Ralph
>>>>>>>
>>>>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <
>> ralph.goers@dslextreme.com>
>>>>>>> wrote:
>>>>>>>>
>>>>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of
>> the
>>>>>>> Log4j Audit project.
>>>>>>>>
>>>>>>>> Please download, test, and cast your votes on the log4j developers
>>>>> list.
>>>>>>>> [] +1, release the artifacts
>>>>>>>> [] -1, don't release because...
>>>>>>>>
>>>>>>>> The vote will remain open for 72 hours (or more if required). All
>> votes
>>>>>>> are welcome and we encourage everyone to test the release, but only
>>>>> Logging
>>>>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes
>> and
>>>>> more
>>>>>>> positive than negative votes are required.
>>>>>>>>
>>>>>>>> Tag:
>>>>>>>> a) for a new copy do "git clone
>>>>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and
>>>>> then
>>>>>>> "git checkout tags/log4-audit-1.0.0-rc1”
>>>>>>>> b) for an existing working copy to “git pull” and then “git checkout
>>>>>>> tags/log4j-audit-1.0.0-rc1”
>>>>>>>>
>>>>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
>>>>>>>>
>>>>>>>> Maven Artifacts:
>>>>>>> https://repository.apache.org/content/repositories/
>>>>> orgapachelogging-1035/
>>>>>>>>
>>>>>>>> Distribution archives:
>>>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>>>>>>>>
>>>>>>>> You may download all the Maven artifacts by executing:
>>>>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>>>>>> https://repository.apache.org/content/repositories/
>>>>> orgapachelogging-1035/org/apache/logging/log4j/
>>>>>>>>
>>>>>>>> Ralph
>>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>> --
>>>> Matt Sicker <bo...@gmail.com>
>>>
>>>
>>>
>>
>>
>>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Gary Gregory <ga...@gmail.com>.
Ralph,
I kind of feel bad just VOTing by running through the build motions and not
having an application to actually test. That would just mean that I can
build the software and look at reports.
Do you feel comfortable with this kind of VOTE?
Gary
On Fri, Jun 15, 2018 at 5:08 PM Ralph Goers <ra...@dslextreme.com>
wrote:
> This vote has now been open 5 days and needs one more +1 vote from a PMC
> member. Again, votes from everyone are welcome.
>
> Ralph
>
> > On Jun 14, 2018, at 4:35 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > Thanks Matt. Gary replied that he had started reviewing it 2 days OK.
> Mikael’s vote also would count on this but he has been very quiet for the
> last several months. I hope all is well.
> >
> > Ralph
> >
> >> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
> >>
> >> I'll be back home tomorrow where I have computers set up for testing
> Apache
> >> releases.
> >>
> >> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
> >>
> >>> +1
> >>>
> >>> (Shameless plug) Every java main() method deserves http://picocli.info
> >>>
> >>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com>
> wrote:
> >>>>
> >>>> I started reading the site, which is good so far... should be able to
> >>>> continue tomorrow...
> >>>>
> >>>> Gary
> >>>>
> >>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com>
> >>> wrote:
> >>>>>
> >>>>> 48 hours have passed with no votes or discussion.
> >>>>>
> >>>>> Ralph
> >>>>>
> >>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <
> ralph.goers@dslextreme.com>
> >>>>> wrote:
> >>>>>>
> >>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of
> the
> >>>>> Log4j Audit project.
> >>>>>>
> >>>>>> Please download, test, and cast your votes on the log4j developers
> >>> list.
> >>>>>> [] +1, release the artifacts
> >>>>>> [] -1, don't release because...
> >>>>>>
> >>>>>> The vote will remain open for 72 hours (or more if required). All
> votes
> >>>>> are welcome and we encourage everyone to test the release, but only
> >>> Logging
> >>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes
> and
> >>> more
> >>>>> positive than negative votes are required.
> >>>>>>
> >>>>>> Tag:
> >>>>>> a) for a new copy do "git clone
> >>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and
> >>> then
> >>>>> "git checkout tags/log4-audit-1.0.0-rc1”
> >>>>>> b) for an existing working copy to “git pull” and then “git checkout
> >>>>> tags/log4j-audit-1.0.0-rc1”
> >>>>>>
> >>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
> >>>>>>
> >>>>>> Maven Artifacts:
> >>>>> https://repository.apache.org/content/repositories/
> >>> orgapachelogging-1035/
> >>>>>>
> >>>>>> Distribution archives:
> >>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
> >>>>>>
> >>>>>> You may download all the Maven artifacts by executing:
> >>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> >>>>> https://repository.apache.org/content/repositories/
> >>> orgapachelogging-1035/org/apache/logging/log4j/
> >>>>>>
> >>>>>> Ralph
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>
> >>
> >>
> >> --
> >> Matt Sicker <bo...@gmail.com>
> >
> >
> >
>
>
>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
This vote has now been open 5 days and needs one more +1 vote from a PMC member. Again, votes from everyone are welcome.
Ralph
> On Jun 14, 2018, at 4:35 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> Thanks Matt. Gary replied that he had started reviewing it 2 days OK. Mikael’s vote also would count on this but he has been very quiet for the last several months. I hope all is well.
>
> Ralph
>
>> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
>>
>> I'll be back home tomorrow where I have computers set up for testing Apache
>> releases.
>>
>> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
>>
>>> +1
>>>
>>> (Shameless plug) Every java main() method deserves http://picocli.info
>>>
>>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com> wrote:
>>>>
>>>> I started reading the site, which is good so far... should be able to
>>>> continue tomorrow...
>>>>
>>>> Gary
>>>>
>>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com>
>>> wrote:
>>>>>
>>>>> 48 hours have passed with no votes or discussion.
>>>>>
>>>>> Ralph
>>>>>
>>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com>
>>>>> wrote:
>>>>>>
>>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of the
>>>>> Log4j Audit project.
>>>>>>
>>>>>> Please download, test, and cast your votes on the log4j developers
>>> list.
>>>>>> [] +1, release the artifacts
>>>>>> [] -1, don't release because...
>>>>>>
>>>>>> The vote will remain open for 72 hours (or more if required). All votes
>>>>> are welcome and we encourage everyone to test the release, but only
>>> Logging
>>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
>>> more
>>>>> positive than negative votes are required.
>>>>>>
>>>>>> Tag:
>>>>>> a) for a new copy do "git clone
>>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and
>>> then
>>>>> "git checkout tags/log4-audit-1.0.0-rc1”
>>>>>> b) for an existing working copy to “git pull” and then “git checkout
>>>>> tags/log4j-audit-1.0.0-rc1”
>>>>>>
>>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
>>>>>>
>>>>>> Maven Artifacts:
>>>>> https://repository.apache.org/content/repositories/
>>> orgapachelogging-1035/
>>>>>>
>>>>>> Distribution archives:
>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>>>>>>
>>>>>> You may download all the Maven artifacts by executing:
>>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>>>> https://repository.apache.org/content/repositories/
>>> orgapachelogging-1035/org/apache/logging/log4j/
>>>>>>
>>>>>> Ralph
>>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>
>>
>>
>> --
>> Matt Sicker <bo...@gmail.com>
>
>
>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
Thanks Matt. Gary replied that he had started reviewing it 2 days OK. Mikael’s vote also would count on this but he has been very quiet for the last several months. I hope all is well.
Ralph
> On Jun 14, 2018, at 7:58 AM, Matt Sicker <bo...@gmail.com> wrote:
>
> I'll be back home tomorrow where I have computers set up for testing Apache
> releases.
>
> On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
>
>> +1
>>
>> (Shameless plug) Every java main() method deserves http://picocli.info
>>
>>> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com> wrote:
>>>
>>> I started reading the site, which is good so far... should be able to
>>> continue tomorrow...
>>>
>>> Gary
>>>
>>>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>>
>>>> 48 hours have passed with no votes or discussion.
>>>>
>>>> Ralph
>>>>
>>>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com>
>>>> wrote:
>>>>>
>>>>> This is a vote to release Log4j-Audit 1.0.0, the first release of the
>>>> Log4j Audit project.
>>>>>
>>>>> Please download, test, and cast your votes on the log4j developers
>> list.
>>>>> [] +1, release the artifacts
>>>>> [] -1, don't release because...
>>>>>
>>>>> The vote will remain open for 72 hours (or more if required). All votes
>>>> are welcome and we encourage everyone to test the release, but only
>> Logging
>>>> PMC votes are “officially” counted. As always, at least 3 +1 votes and
>> more
>>>> positive than negative votes are required.
>>>>>
>>>>> Tag:
>>>>> a) for a new copy do "git clone
>>>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and
>> then
>>>> "git checkout tags/log4-audit-1.0.0-rc1”
>>>>> b) for an existing working copy to “git pull” and then “git checkout
>>>> tags/log4j-audit-1.0.0-rc1”
>>>>>
>>>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
>>>>>
>>>>> Maven Artifacts:
>>>> https://repository.apache.org/content/repositories/
>> orgapachelogging-1035/
>>>>>
>>>>> Distribution archives:
>>>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>>>>>
>>>>> You may download all the Maven artifacts by executing:
>>>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>>>> https://repository.apache.org/content/repositories/
>> orgapachelogging-1035/org/apache/logging/log4j/
>>>>>
>>>>> Ralph
>>>>>
>>>>
>>>>
>>>>
>>
>
>
>
> --
> Matt Sicker <bo...@gmail.com>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Matt Sicker <bo...@gmail.com>.
I'll be back home tomorrow where I have computers set up for testing Apache
releases.
On 12 June 2018 at 22:10, Remko Popma <re...@gmail.com> wrote:
> +1
>
> (Shameless plug) Every java main() method deserves http://picocli.info
>
> > On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com> wrote:
> >
> > I started reading the site, which is good so far... should be able to
> > continue tomorrow...
> >
> > Gary
> >
> >> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com>
> wrote:
> >>
> >> 48 hours have passed with no votes or discussion.
> >>
> >> Ralph
> >>
> >>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com>
> >> wrote:
> >>>
> >>> This is a vote to release Log4j-Audit 1.0.0, the first release of the
> >> Log4j Audit project.
> >>>
> >>> Please download, test, and cast your votes on the log4j developers
> list.
> >>> [] +1, release the artifacts
> >>> [] -1, don't release because...
> >>>
> >>> The vote will remain open for 72 hours (or more if required). All votes
> >> are welcome and we encourage everyone to test the release, but only
> Logging
> >> PMC votes are “officially” counted. As always, at least 3 +1 votes and
> more
> >> positive than negative votes are required.
> >>>
> >>> Tag:
> >>> a) for a new copy do "git clone
> >> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and
> then
> >> "git checkout tags/log4-audit-1.0.0-rc1”
> >>> b) for an existing working copy to “git pull” and then “git checkout
> >> tags/log4j-audit-1.0.0-rc1”
> >>>
> >>> Web Site: http://rgoers.github.io/log4j-audit/index.html
> >>>
> >>> Maven Artifacts:
> >> https://repository.apache.org/content/repositories/
> orgapachelogging-1035/
> >>>
> >>> Distribution archives:
> >> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
> >>>
> >>> You may download all the Maven artifacts by executing:
> >>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> >> https://repository.apache.org/content/repositories/
> orgapachelogging-1035/org/apache/logging/log4j/
> >>>
> >>> Ralph
> >>>
> >>
> >>
> >>
>
--
Matt Sicker <bo...@gmail.com>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Remko Popma <re...@gmail.com>.
+1
(Shameless plug) Every java main() method deserves http://picocli.info
> On Jun 13, 2018, at 9:03, Gary Gregory <ga...@gmail.com> wrote:
>
> I started reading the site, which is good so far... should be able to
> continue tomorrow...
>
> Gary
>
>> On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com> wrote:
>>
>> 48 hours have passed with no votes or discussion.
>>
>> Ralph
>>
>>> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com>
>> wrote:
>>>
>>> This is a vote to release Log4j-Audit 1.0.0, the first release of the
>> Log4j Audit project.
>>>
>>> Please download, test, and cast your votes on the log4j developers list.
>>> [] +1, release the artifacts
>>> [] -1, don't release because...
>>>
>>> The vote will remain open for 72 hours (or more if required). All votes
>> are welcome and we encourage everyone to test the release, but only Logging
>> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
>> positive than negative votes are required.
>>>
>>> Tag:
>>> a) for a new copy do "git clone
>> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and then
>> "git checkout tags/log4-audit-1.0.0-rc1”
>>> b) for an existing working copy to “git pull” and then “git checkout
>> tags/log4j-audit-1.0.0-rc1”
>>>
>>> Web Site: http://rgoers.github.io/log4j-audit/index.html
>>>
>>> Maven Artifacts:
>> https://repository.apache.org/content/repositories/orgapachelogging-1035/
>>>
>>> Distribution archives:
>> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>>>
>>> You may download all the Maven artifacts by executing:
>>> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
>> https://repository.apache.org/content/repositories/orgapachelogging-1035/org/apache/logging/log4j/
>>>
>>> Ralph
>>>
>>
>>
>>
Re: Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Gary Gregory <ga...@gmail.com>.
I started reading the site, which is good so far... should be able to
continue tomorrow...
Gary
On Tue, Jun 12, 2018, 17:35 Ralph Goers <ra...@dslextreme.com> wrote:
> 48 hours have passed with no votes or discussion.
>
> Ralph
>
> > On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com>
> wrote:
> >
> > This is a vote to release Log4j-Audit 1.0.0, the first release of the
> Log4j Audit project.
> >
> > Please download, test, and cast your votes on the log4j developers list.
> > [] +1, release the artifacts
> > [] -1, don't release because...
> >
> > The vote will remain open for 72 hours (or more if required). All votes
> are welcome and we encourage everyone to test the release, but only Logging
> PMC votes are “officially” counted. As always, at least 3 +1 votes and more
> positive than negative votes are required.
> >
> > Tag:
> > a) for a new copy do "git clone
> https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and then
> "git checkout tags/log4-audit-1.0.0-rc1”
> > b) for an existing working copy to “git pull” and then “git checkout
> tags/log4j-audit-1.0.0-rc1”
> >
> > Web Site: http://rgoers.github.io/log4j-audit/index.html
> >
> > Maven Artifacts:
> https://repository.apache.org/content/repositories/orgapachelogging-1035/
> >
> > Distribution archives:
> https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
> >
> > You may download all the Maven artifacts by executing:
> > wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate
> https://repository.apache.org/content/repositories/orgapachelogging-1035/org/apache/logging/log4j/
> >
> > Ralph
> >
>
>
>
Reminder - [VOTE] Release Log4j Audit 1.0.0 RC1
Posted by Ralph Goers <ra...@dslextreme.com>.
48 hours have passed with no votes or discussion.
Ralph
> On Jun 10, 2018, at 2:26 PM, Ralph Goers <ra...@dslextreme.com> wrote:
>
> This is a vote to release Log4j-Audit 1.0.0, the first release of the Log4j Audit project.
>
> Please download, test, and cast your votes on the log4j developers list.
> [] +1, release the artifacts
> [] -1, don't release because...
>
> The vote will remain open for 72 hours (or more if required). All votes are welcome and we encourage everyone to test the release, but only Logging PMC votes are “officially” counted. As always, at least 3 +1 votes and more positive than negative votes are required.
>
> Tag:
> a) for a new copy do "git clone https://git-wip-us.apache.org/repos/asf/logging-log4j-audit.git" and then "git checkout tags/log4-audit-1.0.0-rc1”
> b) for an existing working copy to “git pull” and then “git checkout tags/log4j-audit-1.0.0-rc1”
>
> Web Site: http://rgoers.github.io/log4j-audit/index.html
>
> Maven Artifacts: https://repository.apache.org/content/repositories/orgapachelogging-1035/
>
> Distribution archives: https://dist.apache.org/repos/dist/dev/logging/log4j-audit/
>
> You may download all the Maven artifacts by executing:
> wget -e robots=off --cut-dirs=7 -nH -r -p -np --no-check-certificate https://repository.apache.org/content/repositories/orgapachelogging-1035/org/apache/logging/log4j/
>
> Ralph
>