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 <[email protected]> wrote: > I also have to send the announcement. > > Ralph > > > On Jun 21, 2018, at 8:21 AM, Ralph Goers <[email protected]> > 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 <[email protected]> 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 <[email protected]> wrote: > >> > >>> Looks like we forgot an htaccess redirect here: http://logging.apache. > >>> org/log4j-audit/ > >>> > >>> On 18 June 2018 at 03:32, Remko Popma <[email protected]> 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 <[email protected]> > >>>> 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 <[email protected]> > >>>> 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 <[email protected]> > >>>> 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 <[email protected]> > 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 <[email protected]> > >>>>>>> > >>>>>>> > >>>>>> > >>>>> > >>>>> > >>>> > >>> > >>> > >>> > >>> -- > >>> Matt Sicker <[email protected]> > >>> > >> > >> > >> > >> -- > >> Matt Sicker <[email protected]> > > > > > -- Matt Sicker <[email protected]>
