Hi folks, I am very happy to see this discussion, it is part of defining ourselves.
Let's decide in how we want to continue with two things: 1) Reports to the president 2) Operational matters Please vote for 1 & 2 or suggest modifications ------------------------------------------------ 1) Reports I agree 100% with Ross, they should reflect what happened in the list. For this one I literally just curated it from conversations in the mailing list, stats from Pony Mail and Jira. My preference would be that *anyone* from the committee starts the draft 7 days before the board meeting and notifies dev@ with a call for comments. The call for comments should be open for 48h. Then that same person and I can work on finalizing the report and I'll send it via SVN and that person can send to dev@ on the Friday before the meeting (the deadline). I'd like to suggest we use GitHub***. 2) For operational matters such as the budget I'd open up a Jira for contributions. I will update that Jira and dev@ with a final write up of the proposal or the final decision *based on the input provided*. I personally don't see a need for more comments if input was considered. ****Why Github? It has a lower entry barrier for new folks to the ASF or software development in general. There is also more tutorials and in dif. Languages available. On Tue, Jun 11, 2019, 8:18 PM Ross Gardler <[email protected]> wrote: > I'll repeat what I said earlier... > > "That said, in order to build a strong team it would be wise to ensure that > the team is aware of what is being reported. Being involved in writing the > report is less important as it should be reflecting what we already see on > list." > > Thus, +1 to Sam's suggestion: > > "Nothing is preventing any of you from getting > started on next month's report today. I'm confident that Gris will > appreciate the help." > > That is, if active folks here consider the board report a collaborative > effort then make it so. > > Ross > > ________________________________ > From: Sam Ruby <[email protected]> > Sent: Tuesday, June 11, 2019 3:42 AM > To: [email protected] > Subject: Re: Concerns about process > > On Tue, Jun 11, 2019 at 5:03 AM Myrle Krantz <[email protected]> wrote: > > > > I agree in general, but I'd like to point out that reports can be edited > > after the fact. Posting a report to the board agenda, doesn't mean that > > further input isn't welcome from the group. > > I'll go further: CTR (commit then review) is not the same as making a > decision top down. That being said, CTR requires visibility, so some > tweaks to the process are in order as not everybody here can see the > board agenda. Gris has already indicated that she will share the > report earlier next month[1]. To date, I haven't seen any feedback on > the report itself. > > I'd like ask everybody for patience here. Gris is traveling on > business, and I'm insisting that she prioritize things like budget > input and ensuring that there was a report. If anyone here disagrees > with those priorities, then blame me. I don't intend to set direction > for D&I, but when the committee in general and Gris in particular are > being pulled in multiple directions, I intend to set priorities. The > timing for the budget both sucks (in that it essentially coincides > with the forming of this committee), and is ideal (in that the > committee doesn't have to wait a half a year or more to make a > request). > > I'll close this email with a suggestion: over the years I've had the > pleasure of observing a lot of communities within the ASF and how they > operate. Some develop their reports collaboratively and publicly on > places like a wiki. Nothing is preventing any of you from getting > started on next month's report today. I'm confident that Gris will > appreciate the help. Everybody here should be able to see the > calendar for board meetings[2]. Board meetings are on Wednesdays, and > I'm requesting that the report be posted to the agenda by the Friday > before the meeting. So please have the next board report posted by > the 12th of July. > > > Best, > > Myrle > > [1] > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fs.apache.org%2FlY4K&data=02%7C01%7CRoss.Gardler%40microsoft.com%7C8107a81cb22c499553e608d6ee5989ce%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636958465672001562&sdata=PTk%2FpkAOpf2H5LuKGfU8rGYlpllOTt0GFSAsWc7ALk8%3D&reserved=0 > [2] > https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fsvn.apache.org%2Frepos%2Fprivate%2Fcommitters%2Fboard%2Fcalendar.txt&data=02%7C01%7CRoss.Gardler%40microsoft.com%7C8107a81cb22c499553e608d6ee5989ce%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C636958465672001562&sdata=L0BoMOZLzBZ%2FojthH2E0X224rNYdQ4N87FX5dx9v7u8%3D&reserved=0 > > > On Tue, Jun 11, 2019 at 10:25 AM Bertrand Delacretaz < > [email protected]> > > wrote: > > > > > Hi, > > > > > > On 2019/06/10 23:18:02, Sam Ruby <[email protected]> wrote: > > > > ...Ross has it exactly right. Gris followed the process. As to the > steps > > > > before the report is filed... there is (dare I say it) a lot of > diversity > > > > in how those reports are developed. That's entirely up to the VP and > the > > > > committee... > > > > > > Yes, and as a committee member I strongly suggest that we operate like > a > > > PMC, where team members are consulted before sending important things > like > > > Board reports or budget requests. > > > > > > I'm not interested personally in being part of a committee where things > > > are decided top-down. I understand *in a minority of cases* this is > needed > > > to move fast but such cases should be an exception - in my view. > > > > > > Gris, please let us know how you see things! > > > > > > -Bertrand > > > >
