REMINDER: We now have 7 days to submit the ASF Board Report. Please provide your contributions for this report via the following file in the git repo:
https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt Bruce On Wed, Jan 25, 2023 at 5:30 PM Bruce Snyder <[email protected]> wrote: > And today the notification for the February board report just came out. I > will submit the report by Feb 7. > > Please provide your contributions for the board report by adding them to > the following file using git: > > > https://github.com/apache/activemq-website/blob/main/src/team/reports/DRAFT-ActiveMQ-board-report.txt > > > Bruce > > On Wed, Jan 25, 2023 at 11:02 AM Bruce Snyder <[email protected]> > wrote: > >> Ok, then let's use this file to gather contributions for next month's >> ActiveMQ board report. >> >> Bruce >> >> On Wed, Jan 25, 2023 at 2:13 AM Robbie Gemmell <[email protected]> >> wrote: >> >>> Yep, that is exactly what the file was added for and used to prepare >>> the previous board report draft, following previous discussions about >>> doing so. Its the one I was enquiring whether to delete or not earlier >>> in the thread. >>> >>> On Tue, 24 Jan 2023 at 18:26, Bruce Snyder <[email protected]> >>> wrote: >>> > >>> > There is a file at the following URL named >>> DRAFT-ActiveMQ-board-report.txt, >>> > can we use this for gathering contributions to the board report? >>> > >>> > https://github.com/apache/activemq-website/tree/main/src/team/reports >>> > >>> > If not this file, please provide a suggestion. >>> > >>> > Bruce >>> > >>> > On Wed, Jan 18, 2023 at 12:57 PM Justin Bertram <[email protected]> >>> wrote: >>> > >>> > > There's an ASF tool where you can add the release information [1] >>> and that >>> > > information is then available to Bruce and he just copies and pastes >>> it >>> > > into the report before he submits it. So the release process should >>> include >>> > > using this tool. >>> > > >>> > > >>> > > Justin >>> > > >>> > > [1] https://reporter.apache.org/addrelease.html?activemq >>> > > >>> > > On Wed, Jan 18, 2023 at 11:15 AM Clebert Suconic < >>> > > [email protected]> >>> > > wrote: >>> > > >>> > > > fine... we could start filling the draft as releases are done, as >>> part >>> > > > of the release procedure? >>> > > > >>> > > > On Wed, Jan 18, 2023 at 10:39 AM Bruce Snyder < >>> [email protected]> >>> > > > wrote: >>> > > > > >>> > > > > I would rather employ the prepare-draft-in-site-git-repo approach >>> > > because >>> > > > > it will result in a report format already prepared that can be >>> > > > copy/pasted >>> > > > > directly to Whimsy. I did not take steps to implement this >>> approach as >>> > > > > there were some strong opinions about it previously. If we'd >>> like to >>> > > > > utilize this approach, I'm all for it. >>> > > > > >>> > > > > Releases are already noted somewhere so they appear in the >>> Whimsy stats >>> > > > > already. >>> > > > > >>> > > > > Bruce >>> > > > > >>> > > > > On Wed, Jan 18, 2023 at 9:21 AM Clebert Suconic < >>> > > > [email protected]> >>> > > > > wrote: >>> > > > > >>> > > > > > Perhaps we should include a step in our release procedure to >>> update >>> > > > some >>> > > > > > document on every release we make? Like quarter releases on >>> our >>> > > > website >>> > > > > > so it’s always ready. (Which is most of what we do for the >>> report ) >>> > > > > > >>> > > > > > On Wed, Jan 18, 2023 at 4:58 AM Robbie Gemmell < >>> > > > [email protected]> >>> > > > > > wrote: >>> > > > > > >>> > > > > > > Are we dropping the prepare-draft-in-site-git-repo approach >>> > > > previously >>> > > > > > > discussed and put in place then used for the last report, and >>> > > > > > > switching entirely to email? >>> > > > > > > >>> > > > > > > I dont really mind which approach is used, as I said >>> personally I >>> > > > just >>> > > > > > > use email elsewhere, but asking to know whether to delete >>> the stale >>> > > > > > > file. >>> > > > > > > >>> > > > > > > Robbie >>> > > > > > > >>> > > > > > > On Wed, 18 Jan 2023 at 05:11, Bruce Snyder < >>> [email protected] >>> > > > >>> > > > > > wrote: >>> > > > > > > > >>> > > > > > > > Please consider this message a call for contribution to >>> the next >>> > > > board >>> > > > > > > > report! >>> > > > > > > > >>> > > > > > > > Kindly reply to this conversation with your contributions. >>> > > > > > > > >>> > > > > > > > Bruce >>> > > > > > > > >>> > > > > > > > On Tue, Jan 17, 2023 at 10:37 PM Jean-Baptiste Onofré < >>> > > > [email protected] >>> > > > > > > >>> > > > > > > > wrote: >>> > > > > > > > >>> > > > > > > > > Hi Bruce, >>> > > > > > > > > >>> > > > > > > > > I think replying to a "call for report" email is OK. >>> > > > > > > > > >>> > > > > > > > > Regards >>> > > > > > > > > JB >>> > > > > > > > > >>> > > > > > > > > On Tue, Jan 17, 2023 at 5:27 PM Bruce Snyder < >>> > > > [email protected] >>> > > > > > > >>> > > > > > > > > wrote: >>> > > > > > > > > > >>> > > > > > > > > > I just realized that we were notified about our board >>> report >>> > > > too >>> > > > > > > late to >>> > > > > > > > > > even submit the report as the meeting is scheduled to >>> take >>> > > > place >>> > > > > > > > > tomorrow. >>> > > > > > > > > > So, let's plan on submitting it for next month's ASF >>> board >>> > > > meeting. >>> > > > > > > > > > >>> > > > > > > > > > How do we want to go about gathering the board report >>> > > > contributions >>> > > > > > > for >>> > > > > > > > > > this and future reports? GitHub? Responses to this >>> message? >>> > > > > > > > > > >>> > > > > > > > > > Bruce >>> > > > > > > > > > >>> > > > > > > > > > -- >>> > > > > > > > > > perl -e 'print >>> > > > > > > > > > >>> > > > > > >>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" >>> > > > > > > );' >>> > > > > > > > > > http://bsnyder.org/ <http://bruceblog.org/> >>> > > > > > > > > >>> > > > > > > > >>> > > > > > > > >>> > > > > > > > -- >>> > > > > > > > perl -e 'print >>> > > > > > > > >>> > > > >>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" >>> > > > > > );' >>> > > > > > > > http://bsnyder.org/ <http://bruceblog.org/> >>> > > > > > > >>> > > > > > -- >>> > > > > > Clebert Suconic >>> > > > > > >>> > > > > >>> > > > > >>> > > > > -- >>> > > > > perl -e 'print >>> > > > > >>> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" >>> > > );' >>> > > > > http://bsnyder.org/ <http://bruceblog.org/> >>> > > > >>> > > > >>> > > > >>> > > > -- >>> > > > Clebert Suconic >>> > > > >>> > > > >>> > > >>> > >>> > >>> > -- >>> > perl -e 'print >>> > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" >>> );' >>> > http://bsnyder.org/ <http://bruceblog.org/> >>> >> >> >> -- >> perl -e 'print >> unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' >> http://bsnyder.org/ <http://bruceblog.org/> >> > > > -- > perl -e 'print > unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' > http://bsnyder.org/ <http://bruceblog.org/> > -- perl -e 'print unpack("u30","D0G)U8V4\@4VYY9&5R\"F)R=6-E+G-N>61E<D\!G;6%I;\"YC;VT*" );' http://bsnyder.org/ <http://bruceblog.org/>
