Skip to content

Conversation

@dannyadair
Copy link
Member

@dannyadair dannyadair commented Aug 7, 2025

  • clauses 3.2. and 3.3. (deleted): no term limits (in constitution)
  • clause 4.1: add remaining purposes from former rule 2a
  • clause 6.2: society may borrow money through GM resolutions
  • clause 18.4: reduce minimum number of members for AGM from 15 to 10
  • clause 34.1.(v): remove unused option
  • clause 37.6 (added): member may apply to have their record deleted early
  • clause 54. (deleted): delete Common Seal section - won't have one anymore

Added TODO.md for tracking progress of remaining work.

* 4.1: add remaining purposes from former rule 2a
* 6.2: society may borrow money through GM resolutions
* 18.4: reduce minimum number of members for AGM from 15 to 10
* 34.1.(v): remove unused option
* 37.6 (added): member may apply to have their record deleted early
* 54. (deleted): delete Common Seal section - won't have one anymore

Added TODO.md for tracking progress of remaining work.
Oops was meant to be in the previous commit
Also stop recommending weasyprint (it does the bullet points wrong)
Empty for now but needed for pre-commit hook
The documents are correct and HTML/PDF end results look fine.
didn't end in underscore so linter escaped the starting underscore
@dannyadair
Copy link
Member Author

Note that Tom made comments to this PR in https://github.com/pythonnz/rules/issues/2 which relate to the version after f630415 is applied

@pengufrost
Copy link

Regarding term limits, I think if we were to have these I'd also want to consider how long a term is, say change from 1 year to 2 years, and then for the next election stagger half of the officer positions to 1 years terms, that way we don't get a complete rolling of the committee in one go nor have everyone in the committee be ineligible for the next term. In that case I'd set term limit to 2 or 3 and set limit for chair to 1 term

* added new questions for lawyer, esp. about collecting phone numbers
* term limits/rotation will be handled by bylaws, not in the constitution
* adjust election: GM elects committee, committee elects positions
@dannyadair dannyadair changed the title Adjust boiler plate text following committee meeting, add TODO Adjust boiler plate text following committee meetings, add TODO Aug 20, 2025
Following committee meeting 20 Aug 2025,
we won't be introducing term limits (in the constitution).
The GM elects the commitee, not specific positions - these
are elected from within the committee.
May introduce a bylaw to force/encourage rotation for key
positions (chair, deputy chair, treasurer, secretary).
This is a new requirement in the yearly charities return.
It can be as simple as a committee resolution "yes we
looked at the constitution and no it's fine as it is".
PENDING:
- 32.1.(i) "Any such appointment must be ratified at the next AGM"
  Possibly redundant, given we have 1 year terms. Committee to confirm.
- 37.6 lawyer suggested "12 months" instead of EOFY. Committee to confirm.
- 42.3.(iv) "or Member's rights or interests generally have been damaged"
  Lawyer's response unclear. Seeking clarification.

Committee decisions:
- 6.2 Borrowing via GM retained
- 33.2/33.3 Remove term limits, possibly introduce later as bylaw
- 37.6 Add "Right to be forgotten" clause, pending lawyer's confirmation wording

Lawyer responses:
- 15.1.(iv)(b), 34.1.(ii) Clarify that determining "direspute" triggers dispute resolution process
  prudent for both provisions to be amended to clarify that the dispute procedures can be invoked
  by an Officer or Member where the Committee proposes to pass a resolution about “disrepute”
- 11.1, 12.1, 12.3, 15.1.(i) "in writing" satisified by online forms and emails
- 37.6 wording suitable but maybe permit retention for "12 months" rather than EOFY
- 6.2 yes, delete "(if any)-"
- 13.1/37.2(iii)(b) this is a legislative requirement, see 5(2) of the Act
  https://www.legislation.govt.nz/act/public/2022/0012/latest/LMS100858.html

Actual implementation will follow
- 6.1: Remove "(if any)"
- 15.1.(iv)(b): Clarify that disrepute doesn't bypass dispute resolution process:
  (b) In the opinion of the **Committee** the **Member** has brought the **Society**
  into disrepute.
  Change to:
  (b) In the opinion of the **Committee**, the **Member** has brought the **Society**
  into disrepute, provided that any resolution to terminate membership on this ground
  may only be made following a dispute resolution process under this **Constitution**,
  which may be invoked by the **Committee** or by a **Member**.
- 32.1(i): Remove "Any such appointment must be ratified at the next **Annual General Meeting**."
- 34.1.(ii): Clarify that disrepute doesn't bypass dispute resolution process:
  (ii) The **Officer** has brought the **Society** into disrepute.
  Change to:
  (ii) The **Officer** has brought the **Society** into disrepute, provided that any
  resolution to remove an Officer on this ground may only be made following a dispute
  resolution process under this **Constitution**, which may be invoked by the
  **Committee** or by a **Member**.
- 37.6 avoid financial year cut-off timing issues for "right to forget":
  The society shall then delete their
  record at the end of the current financial year.
  Change to:
  The society shall then delete their
  record within 12 months.
As per lawyer's advice we can remove this - there is no
"timing issue with re-registration"
The "generally" is referring to the general membership,
not the individual member's general rights.

The Society may get involved when rights or interests "as a member"
are damaged, but not when e.g. one member allegedly damages
another member's rights "generally" (which could be completely
unrelated to the Society)
- Lawyer confirmed simplified wording of 2.1
- All bylaws have been drafted (in "bylaws" branch for review)
- General tidy up
The commitee confirmed all proposed changes.
@dannyadair dannyadair merged commit 5b49b5f into main Sep 25, 2025
1 check failed
@dannyadair dannyadair deleted the committee-adjustments branch September 25, 2025 02:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants