You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by Craig Russell <ap...@gmail.com> on 2022/03/17 03:38:41 UTC
Fwd: board: r106225 - /foundation/board/board_agenda_2022_03_16.txt
I think we need to disable write access to the board agenda once the meeting starts, or perhaps some time earlier?
Craig
> Begin forwarded message:
>
> From: kishorvpatil@apache.org
> Subject: board: r106225 - /foundation/board/board_agenda_2022_03_16.txt
> Date: March 16, 2022 at 7:53:40 PM PDT
> To: board-cvs@apache.org
> Reply-To: board@apache.org
>
> Author: kishorvpatil
> Date: Thu Mar 17 02:53:40 2022
> New Revision: 106225
>
> Log:
> Publishing report for storm via Reporter
>
> Modified:
> foundation/board/board_agenda_2022_03_16.txt
>
> Modified: foundation/board/board_agenda_2022_03_16.txt
> ==============================================================================
> --- foundation/board/board_agenda_2022_03_16.txt [utf-8] (original)
> +++ foundation/board/board_agenda_2022_03_16.txt [utf-8] Thu Mar 17 02:53:40 2022
> @@ -4777,6 +4777,30 @@ Paul Stead (pds) 23 March 2021
> -----------------------------------------
> Attachment BM: Report from the Apache Storm Project [Kishor Patil]
>
> +## Description:
> +The mission of Storm is the creation and maintenance of software related to
> +Distributed, real-time computation system
> +
> +## Issues:
> +Nothing to report at this point.
> +
> +## Membership Data:
> +Apache Storm was founded 2014-09-16 (8 years ago)
> +There are currently 42 committers and 41 PMC members in this project.
> +The Committer-to-PMC ratio is roughly 1:1.
> +
> +Community changes, past quarter:
> +- No new PMC members. Last addition was Bipin Prasad on 2020-11-15.
> +- No new committers. Last addition was Bipin Prasad on 2020-11-16.
> +
> +## Project Activity:
> +The log4j libraries are updated to address latest CVEs. The team is
> +currently working on certifying release candidate 2.4.0
> +
> +## Community Health:
> +It's all good. The next release 2.4.0 should be out soon.
> +There are newer PRs to address upgrading dependencies such as zookeeper.
> +
>
> -----------------------------------------
> Attachment BN: Report from the Apache Submarine Project [Liu Xun]
>
>
Craig L Russell
clr@apache.org
Re: Fwd: board: r106225 - /foundation/board/board_agenda_2022_03_16.txt
Posted by Shane Curcuru <as...@shanecurcuru.org>.
Craig Russell wrote on 3/16/22 11:38 PM:
> I think we need to disable write access to the board agenda once the
> meeting starts, or perhaps some time earlier?
Two important notes:
- What is the specific feature need, and why? While late-arriving
reports might not be wanted, there are plenty of times we have had
people - even beyond Secretary - make last-minute corrections to agenda
items.
- This is the wrong list; it's up to the board to decide if they
actually want that feature implemented.
- If the board really wants this feature, the place to implement will be
in the new infra-supported Agenda tool:
https://github.com/apache/infrastructure-agenda/blob/master/REQUIREMENTS.md
--
- Shane
Vice Chair
The Apache Software Foundation
> Craig
>
>> Begin forwarded message:
>>
>> *From: *kishorvpatil@apache.org <ma...@apache.org>
>> *Subject: **board: r106225 -
>> /foundation/board/board_agenda_2022_03_16.txt*
>> *Date: *March 16, 2022 at 7:53:40 PM PDT
>> *To: *board-cvs@apache.org <ma...@apache.org>
>> *Reply-To: *board@apache.org <ma...@apache.org>
>>
>> Author: kishorvpatil
>> Date: Thu Mar 17 02:53:40 2022
>> New Revision: 106225
>>
>> Log:
>> Publishing report for storm via Reporter
>>
>> Modified:
>> foundation/board/board_agenda_2022_03_16.txt
>>
>> Modified: foundation/board/board_agenda_2022_03_16.txt
>> ==============================================================================
>> --- foundation/board/board_agenda_2022_03_16.txt [utf-8] (original)
>> +++ foundation/board/board_agenda_2022_03_16.txt [utf-8] Thu Mar 17
>> 02:53:40 2022
>> @@ -4777,6 +4777,30 @@ Paul Stead (pds) 23 March 2021
>> -----------------------------------------
>> Attachment BM: Report from the Apache Storm Project [Kishor Patil]
>>
>> +## Description:
>> +The mission of Storm is the creation and maintenance of software
>> related to
>> +Distributed, real-time computation system
>> +
>> +## Issues:
>> +Nothing to report at this point.
>> +
>> +## Membership Data:
>> +Apache Storm was founded 2014-09-16 (8 years ago)
>> +There are currently 42 committers and 41 PMC members in this project.
>> +The Committer-to-PMC ratio is roughly 1:1.
>> +
>> +Community changes, past quarter:
>> +- No new PMC members. Last addition was Bipin Prasad on 2020-11-15.
>> +- No new committers. Last addition was Bipin Prasad on 2020-11-16.
>> +
>> +## Project Activity:
>> +The log4j libraries are updated to address latest CVEs. The team is
>> +currently working on certifying release candidate 2.4.0
>> +
>> +## Community Health:
>> +It's all good. The next release 2.4.0 should be out soon.
>> +There are newer PRs to address upgrading dependencies such as zookeeper.
>> +
>>
>> -----------------------------------------
>> Attachment BN: Report from the Apache Submarine Project [Liu Xun]
>>
>>
>
> Craig L Russell
> clr@apache.org <ma...@apache.org>
>
Re: board: r106225 - /foundation/board/board_agenda_2022_03_16.txt
Posted by Greg Stein <gs...@gmail.com>.
[dropping operations@ as we should not be cross-posting between private and
public]
On Fri, Mar 18, 2022 at 12:03 AM Craig McClanahan <cr...@apache.org>
wrote:
> On Thu, Mar 17, 2022 at 6:23 AM sebb <se...@gmail.com> wrote:
>
>> Whilst Whimsy could be updated to prevent updates, the board agenda
>> code is due to be replaced by another system.
>>
>> Also the agenda can be updated directly from SVN.
>
>
>> After using git for many many years, my SVN fu is out of date - but can
> SVN be told to prevent updates after a certain time?
>
svn does not provide for per-file access control (just per-dir and
per-repo). git provides no access control beyond per-repo. And I have never
seen an access control system that is time-based.
Cheers,
-g
Re: board: r106225 - /foundation/board/board_agenda_2022_03_16.txt
Posted by Craig McClanahan <cr...@apache.org>.
On Thu, Mar 17, 2022 at 6:23 AM sebb <se...@gmail.com> wrote:
> Whilst Whimsy could be updated to prevent updates, the board agenda
> code is due to be replaced by another system.
>
> Also the agenda can be updated directly from SVN.
> After using git for many many years, my SVN fu is out of date - but can
SVN be told to prevent updates after a certain time?
If so, the only thing an agenda tool would have to worry about is a nice
error message.
Craig
>
> Maybe the file could be renamed/moved to indicate frozen status?
>
> On Thu, 17 Mar 2022 at 03:38, Craig Russell <ap...@gmail.com> wrote:
> >
> > I think we need to disable write access to the board agenda once the
> meeting starts, or perhaps some time earlier?
> >
> > Craig
>
Re: board: r106225 - /foundation/board/board_agenda_2022_03_16.txt
Posted by sebb <se...@gmail.com>.
Whilst Whimsy could be updated to prevent updates, the board agenda
code is due to be replaced by another system.
Also the agenda can be updated directly from SVN.
Maybe the file could be renamed/moved to indicate frozen status?
On Thu, 17 Mar 2022 at 03:38, Craig Russell <ap...@gmail.com> wrote:
>
> I think we need to disable write access to the board agenda once the meeting starts, or perhaps some time earlier?
>
> Craig