Add daily meeting notes from Google Doc

README.md

@@ -1,3 +1,6 @@
 # Haskell.org Committee Working Space
 
-A working space for haskell.org commitee proposals and working documents
+A working space for haskell.org commitee proposals and working documents.
+
+* [Committee Meeting minutes](./meeting-notes/)
+* [Proposals](./proposals): Policies, processes, guidelines and other public documents guiding the committee's work

meeting-notes/2024-05-29.md

@@ -0,0 +1,47 @@
+## May 29, 2024 | [Haskell.org Monthly Meeting](https://www.google.com/calendar/event?eid=MzB0dGhyOXBjM2RsMDJlcWYyOHE1OTRtdm9fMjAyNDA1MjlUMTQwMDAwWiByZWJlY2NhQHJlYmVjY2Fza2lubmVyLm5ldA)
+
+Attendees: Aaron Allen -   Jose Calderon -  Avi Press -  Moritz Angermann -  Matthías Páll Gissurarson -  Rebecca Skinner
+
+Notes
+
+* Rebecca forgot to send out an Agenda
+* Jose: Spoke with Davean about haskell.org emails. Currently the way that we've done this is that they aren't set up as email accounts, but they can be setup as aliases.
+* Rebecca: Email aliases are okay, it would be nice to be able to send email from those accounts. Bigger issue is the google accounts.
+* Keeping meeting notes:
+  * Currently the committee does not have a secretary. Do we want one? Who would volunteer for such a position?
+  * Jose is willing to keep the notes and share them as the default, as part of his observer status
+  * Where should we post the meeting notes? Github? Haskell.org?
+  * Moritz: Simplicity is valuable. Since we're taking the notes in Google Docs, maybe we can just have a public google drive.
+  * Rebecca: What about topics/discussions that we may not want to be public? There may be aspects of the conversation that should not be widely available.
+  * Moritz: We should aim to avoid capturing that sort of thing in the first place.
+  * Matthias \+ Avi are in agreement.
+  * Rebecca: And recording the meeting and publishing that?
+  * Moritz: I don't think we should do that.
+  * Idea of using AI tools to take minutes is brought up. Folks don't feel that there is a zero-work solution to the problem.
+  * Current plan: Take notes in a public google doc. If we need private notes for some reason, we can take non-public notes for that instance.
+* Matthias: We had the easter-egg logo. How did people feel about how we went about that?
+  * Avi: Main impression was that there was a lot of work/process for a trivial change. Are we over-engineering aspects of the process?
+  * Matthias: There seemed to be some disagreement about how much process was necessary. Perhaps we can have a simpler process for 'trivial changes'. If someone disagrees that the change is trivial, they can object.
+  * Rebecca: There is a process like this already. For trivial changes initiated by a committee member, they can merge changes with one other committee member as an approver. Question is really whether this was indeed trivial. Logos are potentially a big deal (trademark-y).
+  * Maybe the 'overweight' nature of the PR has more to do with a combination of new committee, misunderstanding of whether this was the new logo overall, and/or concerns of copyright.
+* Getting external PR was nice\!
+  * Moritz: The lengthy debates tend to turn off folks from submitting PRs. Making the \_process\_ more inviting is going to be a big part of getting more external PRs
+  * Matthias: The logo PR kinda went like a paper. There was some feedback, a member of the committee 'championed it'
+  * Avi: Are there other PRs that went down like this?
+  * Rebecca: There have been a few, especially when it comes to homepage issues (order of a year ago).
+  * Avi: Maybe we should just keep an eye out and see if this becomes a recurring issue.
+  * Rebecca: Are we fine that the last public PR was over a year ago? Maybe we want aspects of the site that get updated more frequently, like a 'news' or 'updates' section.
+  * Matthias: Danger there is that if you fall behind the language/ecosystem looks dead.
+* GHCUp telemetry
+  * Desire is to have more insight into what versions of GHC are actually being used.
+  * What's the relationship between Haskell.org and GHCUp?
+  * Moritz will be meeting Julian soon and will bring it up.
+* GSOC:
+  * Started this week.
+  * Payment docs are now all set.
+  * Jose: At the end of 2023 we had to find the participants that were US residents because the IRS required that we get W9s from them. Is that something we can inject into the process?
+  * Aaron: Last year was different because it wasn't the GOOGLE summer of code. This year Google is handling it.
+
+Action items
+
+- [ ]

meeting-notes/2024-06-26.md

@@ -0,0 +1,17 @@
+## Jun 26, 2024 | [Haskell.org Monthly Meeting](https://www.google.com/calendar/event?eid=MzB0dGhyOXBjM2RsMDJlcWYyOHE1OTRtdm9fMjAyNDA2MjZUMTQwMDAwWiByZWJlY2NhQHJlYmVjY2Fza2lubmVyLm5ldA)
+
+Attendees: Théophile Choutri - Aaron Allen -  Avi Press -  Rebecca Skinner - Tom Ellis
+
+Notes
+
+* We don't have a lot of nix knowledge within the committee, is this any concern?
+  * Probably not, we have a couple of people on the committee who are comfortable with nix, and we could probably reach out to the community
+* Could we fall back to the non-nix build approach in CI if necessary?
+  * We could, but we'd need to set up new builders that have ghc and cabal
+* Runbooks to manage nix
+  * Let's set up some docs with common tasks and workarounds
+  * We don't need this repo to be a full nix tutorial
+
+Action items
+
+- [ ] Rebecca Skinner - put together some docs on nix and our build and deployment pipeline

meeting-notes/2024-07-31.md

@@ -0,0 +1,58 @@
+## Jul 31, 2024 | [Haskell.org Monthly Meeting](https://www.google.com/calendar/event?eid=MzB0dGhyOXBjM2RsMDJlcWYyOHE1OTRtdm9fMjAyNDA3MzFUMTQwMDAwWiByZWJlY2NhQHJlYmVjY2Fza2lubmVyLm5ldA)
+
+Attendees: Théophile Choutri -  Moritz Angermann -  Aaron Allen -  Avi Press -  Matthías Páll Gissurarson -  Rebecca Skinner -  Jose Calderon -  Tom Ellis -  Andres
+
+Agenda
+
+- Jose, Andres : How do we communicate the merger with the rest of the community
+- Haskell.org domain?
+- [https://github.com/haskell/meta/issues/1](https://github.com/haskell/meta/issues/1)
+- Azure token refresh coming up
+
+Notes
+**Merger Status and Comms**
+Jose: I don't think the wider community has a clear view of how HO and HF are related. Three years ago HF didn't exist, then HO and HF were separate, now they've legally merged and are somewhat together but HO is still independent.
+Since we're trying to communicate something to do with HO, we want to collaborate on that communication.
+Andres: The current situation is a bit of a risk because we haven't announced the merger in any official way, but it is observable from, e.g. the minutes of the meetings. If people are reading this now it might look like there is some sort of "power grab" or otherwise look worse than it really is. We've been *okay* for the last few months in this state, so it's not something that we need to deal with immediately, but we definitely need to address this.
+Rebecca: We should do an announcement. Should we have a marketing person write this?
+Tom: We should just do it, and not be overly cautious
+Avi: Agree with Tom. We can still look for someone to look for marketing copy, etc. on the side. With a lot of these changes, the way these things get delivered and communicated impacts the reception. If we find someone who is good at that it's going to help, but we shouldn't let that block anything.
+Matthias: Maybe we can use the HF marketing / community manager (Ida) to help us with this
+Andres: Also believe hiring someone for this is overthinking this. The most significant risk is if we wait too long then people will suddenly bring this up. There may be justifiable suspicion about why we waited so long to bring this up. We should have communication.
+Tom: It would make sense to put out an article about what HF does, what HO does, and say "for this reason, to make things simpler, we decided to make this a single organization".
+Jose: I can take on this high level description of what HO does, what HF does, and how we merged. HO can double-check it. That can be the starting point. Do both orgs just have the same announcement hosted on both websites.
+Andres: Let's make sure we loop in Mike Pilgrim to make sure that we're not stating anything that's not technically correct about the structure of the organizations.
+Rebecca: I'm not sure where exactly an announcement live, where should we put it so it's visible
+Tom: I suspect something will pop into mind when we have the copy.
+**Haskell.org Domain**
+Avi: I saw there was some discussion about this on the HF side. The original owners at Yale aren't around anymore.
+Jose: Historically the domain was owned by someone via the university, people outside of yale got access, yale doesn't have a haskell group anymore. There's a risk there. As far as we know there is no current discussion with the yale folks. This is something where I can offer my time.
+Tom: Have checked with Daven and Gershom. They presumably know something about where it's held. From the point of view of who has actual control of the domain they have control. We should get it transferred to HO.
+**Who owns the Haskell org on GH**
+Jose: The current HF position is that we don't want much to change. The people who control it control it.
+Rebecca: At first glance it seems to me like this should roll up to HF since there are things here that aren't under the purview of HO
+Tom: I'm more worried about the domain. Github is distributed, I don't think it's a big deal.
+**Azure Token Refresh:**
+Aaron: HLS team needs to publish a new version of the HLS extension. The token can only last for a year. I refreshed it mid-august last year. Just an action item for myself. There are instructions in the bitwarden.
+Rebecca: What exactly do we use this token for? Is this something that we can hand control of directly to the HLS team?
+Matthias: What does this token give you access to?
+Aaron: As far as I know, it's just to allow you to publish the VSCode extension
+Tom: I think that there's a haskell org that exists for the app store. If we want to say something officially comes from Haskell, we probably need to keep control of it unless we want to ask the HF to create a new organization.
+Matthias: It's good that it's not the HLS team then, we don't want any politics to be a problem. It would be good if we could set a reminder or something though.
+Jose: We just did the hackage key signing refresh. This seems to be at a similar time of year, maybe we should make it all part of the same "herding of cats".
+Mortiz: If we refresh everything at the same time does that create any risk?
+Matthias: Maybe
+Avi: I would imagine that the most likely risk is that we forget to do it and something bad happens, so my hunch is that making sure we get them all done is probably more important than ensuring individual changes are small.
+Andres: Increase redundancy? Keep separate people responsible but make sure they are in sync.
+**Google Apps:**
+Jose: It currently still costs us money to add users. There should be a way that we can do that as a non-profit but I haven't found it. This fell off my radar but I should get back on it.
+Tom: What's the rough cost?
+Jose: I'll get back to
+Rebecca: If it's just going to be a few months and it's $7-$14 per month, I'll personally donate a few months of cost to cover it for HO just to make life easier.
+
+**Action items**
+
+- [ ] Rebecca Skinner - and Jose Calderon - to collaborate primarily in a shared google doc on draft to be delivered for final review by August 16th. This should be on the merger of HO/HF
+- [ ] Jose Calderon - to reach out to start working on the haskell.org domain ownership
+- [ ] Aaron Allen - Set up a recurring reminder to refresh the azure token
+- [ ] Jose Calderon - Follow up with HO by the end of August with status on google apps for HO committee.Jose Calderon

meeting-notes/2024-08-28.md

@@ -0,0 +1,43 @@
+## Aug 28, 2024 | [Haskell.org Monthly Meeting](https://www.google.com/calendar/event?eid=MzB0dGhyOXBjM2RsMDJlcWYyOHE1OTRtdm9fMjAyNDA4MjhUMTQwMDAwWiByZWJlY2NhQHJlYmVjY2Fza2lubmVyLm5ldA)
+
+Attendees: Théophile Choutri -  Moritz Angermann -  Aaron Allen -  Avi Press -  Matthías Páll Gissurarson -  Rebecca Skinner -  Jose Calderon -  Tom Ellis -
+
+Notes
+
+* Agenda
+  * Hecate: Blog post sept 15
+    * No concerns, seems good
+  * Aaron: Azure token was refreshed- where should we update the calendar
+    * Let's just add it to a shared calendar with our new HF accounts
+  * Rebecca: Merger announcement doc
+    * How is this looking?
+      * Looking good so far.
+      * Tom: Happy for Rebecca to take all of the commentary and put together a proposed final draft
+    * What should the approval process look like here?
+      * HO board should vote on the final draft
+      * HF probably good to go, Jose will check in with them
+  * Jose: We should have all gotten invite for HF emails
+    * Let him know if we didn't get an invite
+  * Avi: GHCUp Fastly logs, and IP address collection
+    * We've been talking with the GHCUp folks about getting basic metrics in place. Talking with them, it sounds like the best way to do this will be ingesting the fastly logs. In the fastly account, IP addresses aren't being collected.
+    * Because of GDPR there was hesitation about collecting this data.
+    * Who has control over the fastly CDN?
+      * Julian and team set everything up- it's probably them?
+    * Any non-profit has a defensible legitimate basis for collecting the data
+    * Tom: Is this our business at all? We don't run GHCUp
+    * URL on haskell.org
+    * Tom: It's really unlikely that people will have any real issue with this, but it's better if we announce it ahead of time and let people object
+    * If we're going to collect this, should we have a policy about who has access to this data, and for what purpose?
+    * We need a process for people to delete their data, and to request access to their data due to GDPR
+    * Matthias: Do we need to keep the IP addresses?
+    * Are we looking at other data, e.g. geoip?
+      * Yes
+    * Can we hash them to make it unique?
+      * Scarf already does this
+  *
+
+Action items
+
+- [ ] Avi Press - research the deletion process if someone requests their data
+- [ ] Avi Press - draft an announcement
+- [ ] Rebecca Skinner - : Take all the feedback and put together a proposed final draft before the end of the week

meeting-notes/2024-09-25.md

@@ -0,0 +1,50 @@
+## Sep 25, 2024 | [Haskell.org Monthly Meeting](https://www.google.com/calendar/event?eid=MzB0dGhyOXBjM2RsMDJlcWYyOHE1OTRtdm9fMjAyNDA5MjVUMTQwMDAwWiByZWJlY2NhQHJlYmVjY2Fza2lubmVyLm5ldA)
+
+Attendees: Théophile Choutri -  Moritz Angermann -  Aaron Allen -  Matthías Páll Gissurarson -  Rebecca Skinner - Jose Calderon -  Tom Ellis -  ~~Avi Press~~
+
+Notes
+
+* Agenda
+  * Publish the merger announcement:
+    * When? Where? Who?
+      * Hécate: 'Where' could be both blog.haskell.org, and the Medium blog if HF still intends to keep using it. There is also [https://haskell.foundation/news/](https://haskell.foundation/news/) (which might be a tad redundant with the HF blog?)
+  * Hécate: Review needed: Clarification of who is intended to be posting on the blog: [https://github.com/haskell/blog.haskell.org/pull/6](https://github.com/haskell/blog.haskell.org/pull/6)
+  * GSoC update
+  * HF accounts for committee members?
+* Blog \- Commercial Entities
+  * HO committee should retain editorial control over the content
+  * Tom: Core teams are expected to post regularly, but we can invite others to occasionally post at our invitation
+    * Rebecca: Companies might not have something when we invite them
+    * Mortiz: Yes, let's have an open invitation but not necessarily actively solicit
+    * Jose has already received some requests for publishing on the blog
+    * What we do about sponsors who want to post something to the blog?
+      * We should still exercise the same editorial principles in places
+      * Let's make sure that we make it clear when someone is a sponsor- it's both good for transparency and good for donors
+* Blog \- Contents
+  * We should differentiate between teaching materials and announcements
+  * Let's not feel like we have to put all content into this blog for lack of another place to put things. We can have more sites.
+  * If HO wants to have teaching materials online that's nice and we should do it, but it should live somewhere separately from this blog
+* Blog \- Editorial Review
+  * We have editorial control, what should our editorial process be?
+    * Theophile: No, we shouldn't just post without editorial review
+  * We should have a submission process, then we review it and approve it
+    * If people aren't comfortable with working in public they could send us a link to a google doc
+  * Tom: If we say the committee is able to delegate those decisions, then we can rethink it.
+* Blog \- Haskell Interlude
+  * Good for announcements
+* GSoC Update
+  * All but one project is completed
+  * One project is on an extended timeline until November
+  * One contributor received a failure on their evaluation
+  * Rebecca: Should we put together a blog post summarizing GSoC
+* HF Accounts
+  * Aaron: Still need to create a reminder for tokens, not sure where we stand with committee member accounts
+  * Jose: Pretty short expiration on invitations
+*
+
+Action items
+
+- [ ] Everyone: Review the PR for who is able to publish to the blog
+- [ ] Email Jose if you don't have an account
+- [ ] Hécate - Get the initial blog post for the merger announcement and HO twitter
+- [ ] MPG - Request that we get a post to the social media accounts in the HF slack

meeting-notes/2024-10-30.md

@@ -0,0 +1,27 @@
+## Oct 30, 2024 | [Haskell.org Monthly Meeting](https://www.google.com/calendar/event?eid=MzB0dGhyOXBjM2RsMDJlcWYyOHE1OTRtdm9fMjAyNDEwMzBUMTQwMDAwWiByZWJlY2NhQHJlYmVjY2Fza2lubmVyLm5ldA)
+
+Attendees: Théophile Choutri -  Moritz Angermann -  Aaron Allen -  Matthías Páll Gissurarson -  Rebecca Skinner -  Jose Calderon -  Tom Ellis -  ~~Avi Press - ~~
+
+Notes
+
+* Agenda
+  * HF Fundraising and Budget
+* HF Budget
+  * Needs around $200,000 per year to operate
+    * Biggest cost: salaries
+      * ED, CTO, Devops
+    * Projects, server costs
+  * While we may not be able to afford staff, the bank account doesn't go to zero
+    * We will still have enough cash on reserve that we can pay for the things we're paying for (other than staff) for 8-10 years
+  * A majority of compute infrastructure is donated
+    * Stackage and some GHC build infra is paid for
+    * The donated infrastructure could stop at any point
+  * Hécate -  Take point on reaching out to GHCUp about donation levels / expected outcomes
+
+Action items
+
+- [ ] Rebecca Skinner -  WIll create an invite from the HF account and invite everyone using both personal \+ HF emails.
+- [ ] Tom Ellis -  The HF website has some outdated information about how to donate, we need to update that
+- [ ] Hécate -  social media fundraising
+- [ ] Rebecca Skinner -  news section or link to HF news section on HO site, publish financial report
+- [ ] Matti: check interest for fundraising stream participation.