You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tooling.apache.org by Craig Russell <ap...@gmail.com> on 2026/08/21 14:12:31 UTC

Improvement in board agenda

I'd like to suggest for future meetings where there is an attachment for a resolution, that the attachment be added as a discussion item instead of a project report.

That way the attachment will not have any metadata such as "not accepted" which is just not right.

WDYT?
Craig


> Begin forwarded message:
> 
> From: Craig Russell <ap...@gmail.com>
> Subject: Re: ASF Board Meeting Summary - August 19, 2026
> Date: August 20, 2026 at 16:38:51 PDT
> To: Steph van Schalkwyk <sv...@gmail.com>
> Cc: clr@apache.org
> 
>>> The following reports were not accepted:
>>> 
>>>   Report from the Apache Software Foundation Code of Conduct Project

Craig L Russell
clr@apache.org


Re: Improvement in board agenda

Posted by Shane Curcuru <as...@shanecurcuru.org>.
(Note mixed public/private mailing lists)

Craig Russell wrote on 8/21/26 10:12:
> I'd like to suggest for future meetings where there is an attachment for a resolution, that the attachment be added as a discussion item instead of a project report.

Indeed, that's the historical way; most past Budgets have had their 
detailed chart/explanation added as a Discussion Item, and then the 
Special Order might be a top-line budget for the formal vote.

> That way the attachment will not have any metadata such as "not accepted" which is just not right.

Agreed.  More to the point, thinking about all the features and 
processes the new BAT tool has implemented, a key feature would be an 
explicit way that any Agenda item could have metadata that's an explicit 
link to other agenda Item(s) (presuming there's interest and willingness 
to implement this, obv).

For example: when budgets come around, the President's report often has 
some commentary, and then says "See Special Order X to approve budget, 
and see detailed line items in Discussion Item Y".  If there were a way 
to mark those item connections with metadata, it would make automatic 
linking and other relationships easy in the future.

-- 
- Shane
   Member
   The Apache Software Foundation

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org


Re: Improvement in board agenda

Posted by Sander Striker <st...@apache.org>.
https://github.com/apache/tooling-agenda/issues/684 - it's implemented now

Cheers,

Sander

On Fri, Aug 21, 2026, 19:25 Rich Bowen <rb...@rcbowen.com> wrote:

>
>
> > On Aug 21, 2026, at 10:12 AM, Craig Russell <ap...@gmail.com>
> wrote:
> >
> > I'd like to suggest for future meetings where there is an attachment for
> a resolution, that the attachment be added as a discussion item instead of
> a project report.
> >
> > That way the attachment will not have any metadata such as "not
> accepted" which is just not right.
>
> Definitely a case of shoehorning something into a system that was not
> designed to accept it. Having a way to add an attachment, and link it to a
> report or resolution or discussion item would definitely be nice to have.
>
> —Rich
>
>

Re: Improvement in board agenda

Posted by Rich Bowen <rb...@rcbowen.com>.

> On Aug 21, 2026, at 10:12 AM, Craig Russell <ap...@gmail.com> wrote:
> 
> I'd like to suggest for future meetings where there is an attachment for a resolution, that the attachment be added as a discussion item instead of a project report.
> 
> That way the attachment will not have any metadata such as "not accepted" which is just not right.

Definitely a case of shoehorning something into a system that was not designed to accept it. Having a way to add an attachment, and link it to a report or resolution or discussion item would definitely be nice to have.

—Rich


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tooling.apache.org
For additional commands, e-mail: dev-help@tooling.apache.org