As long as have a process to change these articles, then we can change it.

• Setup process to change Articles of Association: #63
• Draft Articles: #66
• Get them reviewed by lawyers: #67

End result should be good enough to start.

Add purpose & principles.

move content from Miro.
consolidate content from google docs.

Currently the Meetup group is called the Wardley Maps Foundation while the GitHub org is called the Wardley Mapping Foundation.

These should match, so we should update the Meetup group to match that of the GitHub org.

(split from #11)

Organise another weekly call for others in different timezones to attend.

eg: Krzysztof can make: Tues 1hr earlier, or Wed same time

will do: UK Morning, UK afternoon

Considering Wed @ 11

How about using wmf- as a prefix for the names of the repositories?

Repos would look like this:

• wmf-operating-model
• wmf-body-of-knowledge
• wmf-branding

Adding a prefix makes the repositories clearer, especially when cloned to our local machines.

Which license should we add to this repository? I'm guessing each repository will have its own license.

GitHub has a guide: https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/licensing-a-repository#choosing-the-right-license

We expect an increasing number of volunteers with various levels of commitment, some will have more time to dedicate, others will have very little. We should be prepared on how to make best use of their time.

Some ideas:

• Guide for Service Managers - what to expect re: time commitments.
• A forum for Service Managers to post tasks for people to pick up & execute
• A way for volunteers to self-select areas / tasks they're interested in
• This may link to the Membership model (eg: should all members volunteer x days / year ?) -> #69

Like @agvbergin mentioned, use "The Cloud Resume Challenge" as inspiration.

• When first joining, new joiner agree to the rules first.
• Add wait of X (e.g., 10) minutes before being able to post anything
• The "red-carpet" treatment feels great.

Permanent link to join (ideally to join call directly, no hoops)
Update Meetup.com
Write Onboarding howto
Signpost on other channels (Slack, Wonder.me)

Setup email for foundation, and figure out: who should it go to? who should read it?

Reach out to @swardley: he's got domains registered for the Foundation.

Move proposed operating model from Miro

Get drafted Articles reviewed by lawyers

Splitting off this comment from @adrianco into a new issue.

Should we configure a CRM tool to manage incoming requests? There are a few
that are free for nonprofits. I didn’t look that hard at them.

https://www.springly.org/en-us/free-crm-nonprofit/

https://www.bitrix24.com/uses/free-crm-for-nonprofits.php

(CRM = Customer Relationship Management)

Pull in Adrian's draft, and flesh it out based on conversations / other work.

Create a Video intro of how the foundation is organised, and how people can get involved.
Link to this in Discord #start-here channel

Ben & Julius

Explore creating a Technical Standards & Tooling working group.

Goals:

1. How would the working group be structured & operate?
2. What user needs should the foundation focus on?

Once these questions are answered, we can set up a working group to focus on a set of user needs, which in turn could decide what projects, github repositories, etc. should be set up and/or funded.

As mentioned, some work was done earlier in the year on related needs & maps. see:

• cards tagged with "Tooling" here: https://miro.com/app/board/uXjVOcvEfQM=/?moveToWidget=3458764514679363581&cot=14
• this capital flow map: https://miro.com/app/board/uXjVOcvEfQM=/?moveToWidget=3458764518469414841&cot=10

Use this to inform / test: #6

What do we want to do in these scenarios and what should we do with the campaign?

• Scenario 1: enough money to start foundation but nothing else
• Scenario 2: not enough money. Do we continue with foundation?
• Scenario 3: enough money as investment to do more than initial legal setup

We have 5 mins at Map Camp, what are we going to say?

Map? Elevator pitch?

To cover topics like Email, Miro, etc.
Basic account management & such.

Goal: help new joiners catch up.

• Where is the group heading?
• What's been discussed previously?

Able to search for keywords in transcribed meeting.

Use tools to help. Summarise and write down themes.

Options:

• Discord bot: https://top.gg/bot/830626887779876884
• Discord Transcriber: https://github.com/dtinth/discord-transcriber

Evaluate https://opencollective.com/

Particularly: https://opencollective.com/fiscal-hosting

Mentioned by Simon Clifford, looks like a good way to manage funding transparently, and take on the legal & accounting side.

How about trying out (using ?) Discord for "real-time" collaboration for the Foundation's working group(s)?
A server for Wardley Maps that @cdaniel and I are on is already available.

Reasons:

• Slack's limit on history of chats - can access 10k most recent chats: https://slack.com/help/articles/115002422943-Message-file-and-app-limits-on-the-free-version-of-Slack
• Affects only those who'd be working on the working groups while the rest can continue to use Slack.

There needs to be a few people who can edit the repo to add workgroups, and commit to each workgroup, to enable async work and contributions.
From the miro board there are proposals for 6 working groups.

1. Operating model
2. Research
3. Education
4. Events
5. Tooling
6. Community

When #5 & #6 are done, reach out to list of potential Trustees created with Simon last year and invite them to join to encourage involvement from a diverse group of people.

For those who accept:

1. Add them to the WMF Trustees group in Github
2. Go through onboarding.md (& update as needed)
3. Ask them to review the proposed operating model
4. Invite them to join relevant WMF meetings

(Split from #3)

Github offers someting akin to forums, "Discussion" -> https://github.com/Wardley-Mapping-Foundation/wmf-operating-model/discussions/landing

Seems related to #14

This might (or might not) be better formed as contributing guidelines.

Create github project for standards, like https://github.com/orgs/Wardley-Mapping-Foundation/projects/6 to track work.

Shrink calls of weekly sessions to 30min, and organise another one for others in different timezones to attend

eg: Krzysztof can make: Tues 1hr earlier, or Wed same time

will do: UK Morning, UK afternoon

Considering Wed @ 11

Update agenda in Event Descriptions on Meetup: https://www.meetup.com/g/wardley-mapping-foundation

Forecasts, what's the bare minimum?

What can be funded from crowdsourcing? What can be funded from other organizations (i.e. corporate sponsorship, which would require commercial licensing)?

(Please split as needed.)

Once a sufficient number of Trustees have joined (#30), and the purpose + principles (#5) & proposed operating model (#6) are in place, review, adjust & ratify the operating model with a quorum of Trustees.

Create follow-up tasks to set up new groups depending on what is agreed. At time of writing, this may include:

• Steering group
• Admin group

And working groups for:

• Body of Knowledge
• Branding

(Split from #3)

Once the foundation is sufficiently a thing, we should add ourselves as a adopter of the Contributor Covenant by following these instructions.

Given the turn of the calendar year is approaching, I feel like it's worth running a poll to check the meeting time is convenient for folks.

As a non-profit open organisation, teams should be visible by the general public.

Consider adding a code of conduct, e.g. Contributor Covenant.

This would have dependencies on a reporting mechanism (e.g. email address) and an ability to enforce the CoC.

First step: configure publicly visible in Github

How about making the main branch protected such that only reviewed/looked over changes land in there?

Docs: https://docs.github.com/en/repositories/configuring-branches-and-merges-in-your-repository/defining-the-mergeability-of-pull-requests/about-protected-branches

It could also be "overkill" for the foundation :)

In #13, @adrianco recommended using Google Groups to simplify management of shared emails. There is a free non-profit tier we can investigate:

https://www.google.com/nonprofits/offerings/workspace/#!#workspace-pricing
https://support.google.com/nonprofits/answer/3215869?ref_topic=3247288

We'll need to setup the charity as a legal entity before applying as it's a pre-requisite, so let's split that into a future task.

Add @agvbergin to appropriate team in the GitHub org so that I can move issues around on the project board etc.

When done, we should name and add this procedure to onboarding.md under an appropriate heading so that we can refer to this process when we onboard to the project in future.

Should roles on github and discord mirror/match those of OSOM - https://github.com/Wardley-Mapping-Foundation/wmf-operating-model/blob/main/README.md?

Right now,

What about roles and permissions for Services (Service Managers and their teams) and the Executive?