Add publicity committee
Add publicity committee
Merge request reports
Activity
committees/meta/committees/publicity.md 0 → 10064430 ## Membership Rules 31 32 The chair of the committee must be member of the board. 33 34 ## Voting Procedure 35 36 The voting procedure of this committee is the same as the procedure for the 37 Board itself. 38 39 ## Reporting 40 41 The Committee will report to the Board regularly. 42 43 ## Documents 44 45 Haskell'd Foundation website which is publicly available. @simonpj we can have this as issues in the website repo (with tags for priority and assign people to execute). So, I do not think we need a document.
changed this line in version 3 of the diff
- committees/meta/committees/publicity.md 0 → 100644
2 3 ## Purpose 4 5 Ensure that the Haskell Foundations website and tweeter is updated. 6 7 ## Responsibilities 8 9 1. Ensure that the website and tweeter is up to date by the Executive Director 10 2. Merge website's pull requests 11 12 13 ### Approach 14 15 The members of this committee will collaborate with the Executive Director to ensure that 16 the website and tweeter account of Haskell Foundation is regularly updates to ensure transparency 17 of the prodecures and propotion of Haskell Foundation. changed this line in version 2 of the diff
- committees/meta/committees/publicity.md 0 → 100644
1 # Publicity Committee 2 3 ## Purpose 4 5 Ensure that the Haskell Foundations website and tweeter is updated. 6 7 ## Responsibilities 8 9 1. Ensure that the website and tweeter is up to date by the Executive Director 10 2. Merge website's pull requests 11 changed this line in version 9 of the diff
- committees/meta/committees/publicity.md 0 → 100644
1 # Publicity Committee 2 3 ## Purpose 4 5 Ensure that the Haskell Foundations website and tweeter is updated. 6 7 ## Responsibilities 8 9 1. Ensure that the website and tweeter is up to date by the Executive Director 10 2. Merge website's pull requests 11 12 13 ### Approach 14 15 The members of this committee will collaborate with the Executive Director to ensure that 16 the website and tweeter account of Haskell Foundation is regularly updates to ensure transparency changed this line in version 2 of the diff
- committees/meta/committees/publicity.md 0 → 100644
5 Ensure that the Haskell Foundations website and tweeter is updated. 6 7 ## Responsibilities 8 9 1. Ensure that the website and tweeter is up to date by the Executive Director 10 2. Merge website's pull requests 11 12 13 ### Approach 14 15 The members of this committee will collaborate with the Executive Director to ensure that 16 the website and tweeter account of Haskell Foundation is regularly updates to ensure transparency 17 of the prodecures and propotion of Haskell Foundation. 18 19 ## Delegated powers 20 The conversation today suggested that there should indeed be delegated powers, such as the ability to direct the Executive Director to address website issues and make decisions about e.g. how best to credit our sponsors, with the expectation that really controversial questions should be directed to the full Board.
I don't know how it best fits into this document, but I would also say that these kinds of questions could also be decided by the ED. Others might feel differently on this point.
I would be cautious about powers to "direct" the ED. I would see it as a group that can offer
- ideas
- guidance
- a sounding board for discussion
- person-power for execution
But I would see the ED as primarily responsible for their own prioritisation and time management, informed by guidance from the Publicity Committee among other subcommittees. But if he or she thinks that their time is best spent in some other way, so be it. We need to trust our ED.
If there really is a disagreement about the ED's priorities, we should not have a bunch of committees giving different and perhaps conflicting directions. Rather, it's the job of the Executive Committee (and, ultimately, of the board) to resolve such choices.
TL;DR. I'd say "invite the ED" or "suggest to the ED".
Apart from anything else, if I was the ED that sort of language suggests a more collaborative and supportive relationship than does "direct".
- committees/meta/committees/publicity.md 0 → 100644
17 of the prodecures and propotion of Haskell Foundation. 18 19 ## Delegated powers 20 21 22 ## Term 23 24 This is a standing (permanent) committee 25 26 ## Membership 27 28 1. Niki Vazou (chair) 29 30 ## Membership Rules 31 32 The chair of the committee must be member of the board. changed this line in version 10 of the diff
- committees/meta/committees/publicity.md 0 → 100644
22 ## Term 23 24 This is a standing (permanent) committee 25 26 ## Membership 27 28 1. Niki Vazou (chair) 29 30 ## Membership Rules 31 32 The chair of the committee must be member of the board. 33 34 ## Voting Procedure 35 36 The voting procedure of this committee is the same as the procedure for the 37 Board itself.
