This regular meeting of the F# Software Foundation Board was held over Slack (text chat) on January 13th, 2022, beginning at 4:00 PM UTC, ending at 5:00 PM UTC.
Votes are reported in the form “Y-N-A” (in favor-Y, opposed-N, abstentions-A; e.g. “5-1-2” means “5 in favor, 1 opposed, and 2 abstentions”).
Redactions may be used to protect information that has business sensitivity (e.g., negotiating positions), when a third party’s name is used without the third party’s knowledge (e.g., discussion of candidates for a volunteer position or award), or to protect the subject of personnel discussions.
The following members (6/6) were present at the meeting, for its entire duration, unless otherwise specified:
- Reed Copsey
- Ryan Coy
- Kevin Avignon
- Phillip Carter
- Janne Siera
- Houston Haynes
Since the last formal meeting was called before the holiday season, there was some "catch up" discourse today surrounding those informal discussions held in November - which also continued on Slack through December. Those discussions led the group to defer formalizing plans for educational efforts by the FSSF until 2022. In the interim, Philip Carter and Reed Copsey crafted an announcement that signaled the board's intent which was published here:
https://foundation.fsharp.org/welcome_to_2022
The board will continue to develop a plan for rolling out those informational/learning materials and will advise the broader community as they're formalized.
There were also two issues for consideration brought by Reed Copsey.
- A request came in to include "dotnetframework" as a co-owner for FSSF nuget packages, and
- Similar to the above, the board also discussed the long term governance surrounding dotnet/fsharp. Philip Carter offered some perspective - and mentioned the possibility of designating a few community members with permission to triage issues, close PRs, handle discussions, etc. The example he gave was that dotnet/roslyn has such a member and so should be met with little controversy.
While there were no formal votes taken on these two issues, there was general signals of support to the proposals by board members. The meeting closed with the understanding that the two issues above will proceed with the various parties involved, and that the board will be updated when there's progress to report.
NONE