meta merge requestshttps://gitlab.haskell.org/hf/meta/-/merge_requests2024-03-28T01:50:58Zhttps://gitlab.haskell.org/hf/meta/-/merge_requests/54Add mechanism for temporarily increasing board size2024-03-28T01:50:58ZRichard Eisenbergrae@richarde.devAdd mechanism for temporarily increasing board sizeThis is an alternative to #53 which allows us to temporarily increase board size, without simply removing the limit. It requires a consideration of board size every year in which the desired size is more than 14.
Please click the Approv...This is an alternative to #53 which allows us to temporarily increase board size, without simply removing the limit. It requires a consideration of board size every year in which the desired size is more than 14.
Please click the Approve button to vote in favor of this change, which we can also discuss at tomorrow's meeting. This will require a 2/3 vote to be approved.
Vote deadline: one week from today: March 20.https://gitlab.haskell.org/hf/meta/-/merge_requests/53Remove size limit of board2024-03-08T10:43:05ZRichard Eisenbergrae@richarde.devRemove size limit of boardAs discussed on our mailing list, we have a strong crop of new potential board members, and we may accordingly wish to increase the size of the board. This change to our bylaws removes the restriction to 14 members. Because it is a chang...As discussed on our mailing list, we have a strong crop of new potential board members, and we may accordingly wish to increase the size of the board. This change to our bylaws removes the restriction to 14 members. Because it is a change to our bylaws, this requires the vote of 2/3 of our current membership, at least 10 of us.
To vote in favor, you must click the blue Approve button in this Merge Request.https://gitlab.haskell.org/hf/meta/-/merge_requests/52Change "Task Force" to "Working Group"2023-04-19T17:31:47ZRichard Eisenbergrae@richarde.devChange "Task Force" to "Working Group"This was David's choice for group designation some time ago.
As this does not affect our bylaws or rules, I'm just going to go ahead and merge.This was David's choice for group designation some time ago.
As this does not affect our bylaws or rules, I'm just going to go ahead and merge.https://gitlab.haskell.org/hf/meta/-/merge_requests/51Formally disband the Transition Committee2023-04-19T17:27:40ZRichard Eisenbergrae@richarde.devFormally disband the Transition CommitteeHaving had our new ED for almost a year -- and having fulfilled the conditions for disbanding the Transition Committee -- this commit formally disbands the committee.
I will just go ahead and merge, because the document itself states th...Having had our new ED for almost a year -- and having fulfilled the conditions for disbanding the Transition Committee -- this commit formally disbands the committee.
I will just go ahead and merge, because the document itself states the (fulfilled!) conditions under which this should happen. No vote required, but posting as an MR for visibility.https://gitlab.haskell.org/hf/meta/-/merge_requests/50Rephrase board refreshment in terms of rerunning2023-03-09T20:47:26ZRichard Eisenbergrae@richarde.devRephrase board refreshment in terms of rerunningThis is a small tweak to our bylaws to allow retiring members to vote on the new board makeup, as long as they are not seeking another term.
Because this is a change to the bylaws, it requires a 2/3 majority vote (currently 9 members). ...This is a small tweak to our bylaws to allow retiring members to vote on the new board makeup, as long as they are not seeking another term.
Because this is a change to the bylaws, it requires a 2/3 majority vote (currently 9 members). Please click the blue Approve button to vote in support of this change.
According to our rules for Merge-Request-based voting, this vote will conclude two weeks from today, on Monday Feb 13. This comes after we put out the call for new applications, but I think that's fine. If we want to rush this vote, 2/3 of us can vote for early cloture, but I really don't think it's necessary here.https://gitlab.haskell.org/hf/meta/-/merge_requests/49Fix a few typos2022-06-02T21:51:29ZRichard Eisenbergrae@richarde.devFix a few typoshttps://gitlab.haskell.org/hf/meta/-/merge_requests/48Improve wording of new member selection2022-05-03T19:36:21ZRichard Eisenbergrae@richarde.devImprove wording of new member selectionThis really should have been part of !44, but I forgot to push.This really should have been part of !44, but I forgot to push.https://gitlab.haskell.org/hf/meta/-/merge_requests/47Updated Executive Committee2022-05-19T03:16:00ZRichard Eisenbergrae@richarde.devUpdated Executive CommitteeThis updates the Executive Committee (né Executive Oversight Committee) charter.
Due to the important nature of this committee, I would like to use normal voting rules here, not our MR rules. Accordingly:
- We will need at least 7 Appr...This updates the Executive Committee (né Executive Oversight Committee) charter.
Due to the important nature of this committee, I would like to use normal voting rules here, not our MR rules. Accordingly:
- We will need at least 7 Approvals to approve this update.
- The deadline of the vote will be next Monday, May 9, in order to allow the new committee to meet soon with David.https://gitlab.haskell.org/hf/meta/-/merge_requests/46Disband Ways of Working2022-05-03T19:27:41ZRichard Eisenbergrae@richarde.devDisband Ways of WorkingThis moves the charter to the new `disbanded` folder and notes how the committee was disbanded. Please Approve if you agree with this change.This moves the charter to the new `disbanded` folder and notes how the committee was disbanded. Please Approve if you agree with this change.https://gitlab.haskell.org/hf/meta/-/merge_requests/45Note about onboarding / offboarding2022-04-23T17:00:14ZRichard Eisenbergrae@richarde.devNote about onboarding / offboardinghttps://gitlab.haskell.org/hf/meta/-/merge_requests/44Clarify selection process of new board members2022-05-03T19:35:48ZRichard Eisenbergrae@richarde.devClarify selection process of new board membersThe most important part of this MR is to clarify that we select board members so that the size of the board at the end of April 1 is no more than 14.
This changes our board selection process and thus requires a 2/3 vote. As this is an M...The most important part of this MR is to clarify that we select board members so that the size of the board at the end of April 1 is no more than 14.
This changes our board selection process and thus requires a 2/3 vote. As this is an MR, however, we follow the rules for an MR vote (at the end of https://gitlab.haskell.org/hf/meta/-/blob/main/board.md), meaning that anyone who does not participate in the discussion, at all, abstains, meaning quorum is guaranteed.
The deadline for this vote is in two weeks, May 2.https://gitlab.haskell.org/hf/meta/-/merge_requests/43Add notes about email addresses and groups2022-05-03T19:37:53ZRichard Eisenbergrae@richarde.devAdd notes about email addresses and groupsThis adds a new section to our working conventions, describing how we use HF email addresses. There are a few policy prescriptions here, but nothing that would seem to require an official vote. I would love feedback on this, regardless.This adds a new section to our working conventions, describing how we use HF email addresses. There are a few policy prescriptions here, but nothing that would seem to require an official vote. I would love feedback on this, regardless.https://gitlab.haskell.org/hf/meta/-/merge_requests/42Remove "Holding ourselves accountable"2022-05-03T19:38:08ZRichard Eisenbergrae@richarde.devRemove "Holding ourselves accountable"We should, of course, hold ourselves accountable, but the
conventions described in this section never took root and
seem unlikely to.
An alternative to accepting this MR is to commit to using the structure written here.
I will merge af...We should, of course, hold ourselves accountable, but the
conventions described in this section never took root and
seem unlikely to.
An alternative to accepting this MR is to commit to using the structure written here.
I will merge after spotting a few approvals. This does not require an official Board Vote.https://gitlab.haskell.org/hf/meta/-/merge_requests/41Prepare conflict-of-interest statement for filling out2022-03-11T19:49:22ZRichard Eisenbergrae@richarde.devPrepare conflict-of-interest statement for filling outThis just clarifies some text in advance of us filling it out and creates an easier-to-edit version.This just clarifies some text in advance of us filling it out and creates an easier-to-edit version.https://gitlab.haskell.org/hf/meta/-/merge_requests/40Add publicity committee2022-05-03T19:43:47ZNikiAdd publicity committeeAdd publicity committeeAdd publicity committeehttps://gitlab.haskell.org/hf/meta/-/merge_requests/39Notes about private sessions2022-02-24T15:05:47ZRichard Eisenbergrae@richarde.devNotes about private sessionsLast month, we agreed on email to introduce a habit of reserving the final 15 minutes of board meetings for a private session, for Board members only. This MR codifies this decision (though does not mandate this new habit), and also stat...Last month, we agreed on email to introduce a habit of reserving the final 15 minutes of board meetings for a private session, for Board members only. This MR codifies this decision (though does not mandate this new habit), and also states that we keep minutes of private sessions (as we have also agreed to do).
I do not see this as a policy change, just some institutional memory. Accordingly, I do not see a need for a formal vote. This post is merely for review, and I will merge after an Approval or two.https://gitlab.haskell.org/hf/meta/-/merge_requests/38Final version of bylaws2022-03-10T16:45:45ZRichard Eisenbergrae@richarde.devFinal version of bylawsWe have been working out details of our official, legal bylaws for some time, on !25. Many of the Approvals there pre-date the conflict of interest policy we include in this final version. In order to make sure we had sufficient support ...We have been working out details of our official, legal bylaws for some time, on !25. Many of the Approvals there pre-date the conflict of interest policy we include in this final version. In order to make sure we had sufficient support of the Board for these bylaws, including the conflict-of-interest policy, it seems wise to start a fresh MR.
If you have Approved the previous MR (this includes @copton @tomjaguarpaw1 @ryantrinkle @Kleidukos @dreixel @rae @simonpj @snoyberg), you may wish to read the conflict of interest policy here and Approve this new MR. (The bylaws themselves have not substantively changed.)
For the rest of you, please do read through and weigh in, clicking the Approve button if you wish to vote these in.
We must approve these bylaws before we can apply for tax-privileged status with the US tax authority. (All of our financial transactions currently go via the Haskell.org committee previously-established non-profit.)
These bylaws require a 2/3 vote.
We will operate according to our [rules for MR voting](https://gitlab.haskell.org/hf/meta/-/blob/main/board.md#96-vote-descriptions):
* A "yes" vote requires clicking the blue Approve button.
* Any other action on the MR that does not include clicking the blue Approve button is a "no" vote. This includes statements like "This is utterly fantastic!". The only way to vote "yes" is to click the blue Approve button.
* Two weeks from today (Wednesday, 9 March) will be the deadline for this vote.
* Any board member who has not voted by the deadline will automatically abstain. This means we will automatically reach quorum.
* Any one board member can extend the deadline two 4 weeks (Wednesday, 23 March), simply by requesting to do so.
* Any two board members can deactivate the automatic-abstention rule, by requesting to do so (asynchronously).https://gitlab.haskell.org/hf/meta/-/merge_requests/37Add Transition Committee Charter2022-02-23T16:48:55ZRichard Eisenbergrae@richarde.devAdd Transition Committee CharterThis is taken from a previous document stored privately on our
Google Drive. It was created in private because Boardman's resignation
was not yet announced. Now, this can be public.
This was approved in a vote in the board-internal emai...This is taken from a previous document stored privately on our
Google Drive. It was created in private because Boardman's resignation
was not yet announced. Now, this can be public.
This was approved in a vote in the board-internal email list here: https://groups.google.com/u/2/a/haskell.foundation/g/board-internal/c/Y-WjFXiOKUc; voting continued on an amendment to the charter here: https://groups.google.com/u/2/a/haskell.foundation/g/board-internal/c/aJ5__v_L1RY. Everyone who voted was in support.https://gitlab.haskell.org/hf/meta/-/merge_requests/36Donations Committee to decide on questionable donations2022-05-19T03:14:38ZRichard Eisenbergrae@richarde.devDonations Committee to decide on questionable donationsAs part of the [Ways of Working Project Plan](https://docs.google.com/spreadsheets/d/1iG_HrYbaoQGodPioMINhtS9YxrRwNwI8roxuPlIylDI/edit?usp=sharing), we have to form a plan to deal with donations/sponsorships of a questionable nature. @co...As part of the [Ways of Working Project Plan](https://docs.google.com/spreadsheets/d/1iG_HrYbaoQGodPioMINhtS9YxrRwNwI8roxuPlIylDI/edit?usp=sharing), we have to form a plan to deal with donations/sponsorships of a questionable nature. @copton and I, at a recent meeting, decided that the best way forward was to form a standing committee which could adjudicate individual cases.
The idea is that the ED would flag specific donations as worthy of deliberation, and then the Donations Committee would meet on an ad-hoc basis to decide whether to accept or reject the donation.
The document ends with a number of specific considerations we felt would be helpful in making these decisions, but these are not definitive.
@copton and I together planned out the general shape of this approach, including the specific guidelines at the bottom. I worked alone to craft the text in this MR.https://gitlab.haskell.org/hf/meta/-/merge_requests/35Nominations list2022-02-07T23:32:57ZRichard Eisenbergrae@richarde.devNominations listRefreshing the nominations@hf list for the 2022 board member nominations process.
@Kleidukos @dreixel are our secretaries and have been added to the list.
This does not need full board approval.Refreshing the nominations@hf list for the 2022 board member nominations process.
@Kleidukos @dreixel are our secretaries and have been added to the list.
This does not need full board approval.