Well when I started as VP Fundraising, there was little committee functions per se so I recruited people to it, created the private mailing list, continued & expanded meetings with Virtual to include more people, created annual goals, created sponsor tracking spreadsheets, created agendas / minutes for committee meetings, setup a standing meeting and used g suite to draft my reports.
All my reports: board, quarterly and yearly, I drafted in g suite in advance so review, comments and additions were encouraged before they were submitted. I also put proposals on drive for creation as well for collaboration. I did the reports as running reports so one file with a the reports, new newest on top. I used a public team drive and a private team drive as there is a lot more for fundraising that requires privacy than most any place at the foundation. And any reports submitted would be ccd to a list. There had been complaints before that fundraising lacked transparency and I think this laid a good foundation. IMO Gris just needs a few months to go through the motions because she's not familiar with Apache processes. Fundraising uses a lot of g suite tooling which I think was the right tool chosen by the people doing the work. Gris right now is exploring our tools available be it Jira or confluence or G suite or o365. I am happy to advise her on what is best and how things work to the best of my capabilities. HTH, KAM On Mon, Jun 10, 2019, 17:15 Sam Ruby <[email protected]> wrote: > Kevin, when you were VP Fundraising, what process did you follow? > > On Mon, Jun 10, 2019, 5:01 PM Kevin A. McGrail <[email protected]> > wrote: > > > Thanks for helping guide Gris. She's just learning about how things > > work at the ASF. > > > > On 6/10/2019 4:48 PM, Naomi Slater wrote: > > > hey folks, > > > > > > two things that have happened in the past couple of days that concern > me > > > > > > the first is that a board report was prepared and sent to the board by > > the > > > Chair without any input from the committee. (Gris acknowledged this a > > > separate follow-up email she sent to dev@diversity) > > > > > > SIDE NOTE: I am subscribed to board@ but I didn't receive the original > > copy > > > of the board report. so I am wondering which list it was sent to. > > perhaps I > > > have a misconfigured email client? > > > > > > ANOTHER SIDE NOTE: it is generally a good idea to copy dev@ when > sending > > > the report to board@. that way, there is no need to send an additional > > > followup notification to dev@diversity > > > > > > my second concern is that I learned about a proposed D&I budget request > > > only because Jim copied in the private@diversity list on a thread that > > > seems to have been started on opperations@ (to which I am not > > subscribed) > > > > > > we had a brainstorming thread about our budget request last month, but > to > > > the best of my knowledge, there has been no chance for the committee to > > > work on the actual proposal that was sent. I have seen no emails about > > it, > > > no draft text, no requests for review, etc > > > > > > as far PMCs are concerned, Chairs (who also serve as the VP of the > > > respective project) are not "project leaders". they function as an > > elected > > > representative of the committee to the board and are responsible for > > > foundation-level admin but they do not hold any special decision-making > > > power above-and-beyond a regular committee member > > > > > > cf. https://couchdb.apache.org/bylaws.html#chair > > > > > > we are not a PMC, though. so I am not sure how things are meant to > > operate > > > with this committee. (this is one of the reasons I suggested that we > > draft > > > some bylaws that would clarify this sort of thing) > > > > > > I think that we should operate the way that a standard PMC does. that > is, > > > decisions are made on-list, *by the committee*, and the Chair (i.e., VP > > > D&I) has the primary function of interfacing with the board > > > > > > apologies, Gris, if we're on the same page and these were both just > > > procedural oversights!! most new committees have teething troubles and > > > there's no reason we should be any different. but I figure this is an > > > important issue and one we should get clarity on as early as possible > > > > > > > -- > > Kevin A. McGrail > > Member, Apache Software Foundation > > Chair Emeritus Apache SpamAssassin Project > > https://www.linkedin.com/in/kmcgrail - 703.798.0171 > > > > >
