# Next CT meeting - decision process

**URL:** <https://community.humanetech.com/t/next-ct-meeting-decision-process/3958>\
**Category:** Feedback\
**Created:** [April 26, 2019, 10:11am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958 "2019-04-26T10:11:20Z")\
**Posts on this page:** 20\
**Page:** 1

<div class="post-metadata">

**Author:** ![micheleminno](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/micheleminno/32/3062_2.png) [@micheleminno](https://community.humanetech.com/u/micheleminno)\
**Post date:** [April 26, 2019, 10:11am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/1 "2019-04-26T10:11:20Z")

</div>

Hi,  
it should be good to have another [@CommunityTeam](https://community.humanetech.com/groups/communityteam) meeting (and maybe plan a recurring meeting each week/two weeks/…) to discuss about big and small issues about forum, website, relation to CHT after their event and so on. What do you think?

---

<div class="post-metadata">

**Author:** ![aschrijver](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/aschrijver/32/1498_2.png) [@aschrijver](https://community.humanetech.com/u/aschrijver)\
**Post date:** [April 26, 2019, 10:23am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/2 "2019-04-26T10:23:26Z")

</div>

Yes, we should do that. I suggest we follow @jonatoni’s advice and plan recurring bi-weekly meetings (so as not lay too much a burden on everyone). We hold the meetings with those that can be present at the time.

I suggest the following for the format of these meetings:

- We make them 40 min. Just the amount that Zoom allows us for free.
- Each meeting has a theme plus an agenda beforehand and we try to stick to it
  - Earlier meetings easily went way over time and we didn’t really adress the agenda points

- We put agenda up in a GH issue in `engagement-ideas` repo and add results afterwards as comments
- Then we post an update to a pinned wiki post in Announcements on the forum
  - It has one associated Discussion thread for the meetings itself
  - It provides links to discussion threads related to the agenda points that were discussed

---

<div class="post-metadata">

**Author:** ![micheleminno](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/micheleminno/32/3062_2.png) [@micheleminno](https://community.humanetech.com/u/micheleminno)\
**Post date:** [April 26, 2019, 12:18pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/3 "2019-04-26T12:18:10Z")

</div>



---

<div class="post-metadata">

**Author:** ![micheleminno](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/micheleminno/32/3062_2.png) [@micheleminno](https://community.humanetech.com/u/micheleminno)\
**Post date:** [April 26, 2019, 12:17pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/4 "2019-04-26T12:17:22Z")

</div>

Since we are _leaderless_ and we need to make the website/forum _evolve_, we need to agree on a decision process about _how_ we want the website/forum evolve, according to our vision and objectives.

So I propose for the [@CommunityTeam](https://community.humanetech.com/groups/communityteam) :

- a _regular_ video meeting, where they decide by majority the main issues to be done in the next period until the next meeting.

- All meeting activity and decisions will be _well-documented_ on the forum.

- _Feedbacks_ from other members taken into consideration

- Everything would evolve smoothly following the natural _pace_ of the community.

- Any technical advancements in any directions _beyond_ what agreed on the last meeting will be valued in the next meeting and accepted or discarded by the CT (Community Team).

---

<div class="post-metadata">

**Author:** ![patm](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/patm/32/3125_2.png) [@patm](https://community.humanetech.com/u/patm)\
**Post date:** [April 26, 2019, 5:52pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/5 "2019-04-26T17:52:49Z")

</div>

I agree about having regular meeting and want to suggest that a few others be invited to attend as well.

I have in mind @chris_davies_sanjose and perhaps @henryrowswell.

---

<div class="post-metadata">

**Author:** ![aschrijver](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/aschrijver/32/1498_2.png) [@aschrijver](https://community.humanetech.com/u/aschrijver)\
**Post date:** [April 26, 2019, 5:58pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/6 "2019-04-26T17:58:56Z")

</div>

We can completely open it up. We just hold meetings every 2 weeks, with some or all CT members present, and anyone else is free to join. We don’t do introductory rounds (too time-consuming then, or maybe do quick one sentence intro’s), and we go through the predefined agenda points.

Only thing I wonder is if this is too early. That we should have a bit more streamlined organization before we go this route.

---

<div class="post-metadata">

**Author:** ![patm](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/patm/32/3125_2.png) [@patm](https://community.humanetech.com/u/patm)\
**Post date:** [April 26, 2019, 6:01pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/7 "2019-04-26T18:01:01Z")

</div>

> [@aschrijver](#):
>
> Only thing I wonder is if this is too early. That we should have a bit more streamlined organization before we go this route.

Well this is a chicken-and-the-egg problem. Let’s do it now; with practice, we will become more efficient and better organized.

---

<div class="post-metadata">

**Author:** ![aschrijver](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/aschrijver/32/1498_2.png) [@aschrijver](https://community.humanetech.com/u/aschrijver)\
**Post date:** [April 26, 2019, 6:03pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/8 "2019-04-26T18:03:31Z")

</div>

Yea, I think you are right. Anyway, open meetups will be a great way to get more people active, I expect, and also face-to-face is so much better than all this typing.

---

<div class="post-metadata">

**Author:** ![healthyswimmer](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/healthyswimmer/32/229_2.png) [@healthyswimmer](https://community.humanetech.com/u/healthyswimmer)\
**Post date:** [April 27, 2019, 12:08am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/9 "2019-04-27T00:08:17Z")

</div>

> [@micheleminno](#):
>
> _Feedbacks_ from other members taken into consideration

> [@micheleminno](#):
>
> Everything would evolve smoothly following the natural _pace_ of the community.

These two points are well taken. If the community moves too fast with members that are online more than others- this will severely limit the amount of people that participate.

There should be a focus on posting topics and not just managing the forum. We are a forum not a company…

---

<div class="post-metadata">

**Author:** ![NSaikiwiki](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/nsaikiwiki/32/2467_2.png) [@NSaikiwiki](https://community.humanetech.com/u/NSaikiwiki)\
**Post date:** [May 1, 2019, 2:55am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/10 "2019-05-01T02:55:41Z")

</div>

Hi everyone. Sorry I’ve been slammed and away from the board for a bit. I think the team meetings are good, the last one, even though I wasnt able to attend for much of it, was extremely helpful.

@aschrijver I think that because things are not as streamlined it would be a good call to action for the meeting itself to get others involved.

---

<div class="post-metadata">

**Author:** ![patm](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/patm/32/3125_2.png) [@patm](https://community.humanetech.com/u/patm)\
**Post date:** [May 1, 2019, 2:59am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/11 "2019-05-01T02:59:43Z")

</div>

> [@NSaikiwiki](#):
>
> I think that because things are not as streamlined it would be a good call to action for the meeting itself to get others involved.

Yes, I agree. Now that @micheleminno and I have “graduated” from the MOL program, we can focus on planning. Happy to attend whatever anyone wants to set up.

---

<div class="post-metadata">

**Author:** ![patm](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/patm/32/3125_2.png) [@patm](https://community.humanetech.com/u/patm)\
**Post date:** [June 3, 2019, 7:34pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/12 "2019-06-03T19:34:48Z")

</div>

A post was split to a new topic: [Organizing the organizers](https://community.humanetech.com/t/organizing-the-organizers/4121)

---

<div class="post-metadata">

**Author:** ![patm](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/patm/32/3125_2.png) [@patm](https://community.humanetech.com/u/patm)\
**Post date:** [May 21, 2019, 1:27am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/13 "2019-05-21T01:27:02Z")

</div>

Dear all,

We did not set up a meeting, and now the Mozilla sprint event is upon us. It will be in five days!

Do we want to get together to talk about ways to make the event successful? Or would you like to discuss it here on the forum?

🐈

---

<div class="post-metadata">

**Author:** ![micheleminno](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/micheleminno/32/3062_2.png) [@micheleminno](https://community.humanetech.com/u/micheleminno)\
**Post date:** [May 21, 2019, 7:38am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/14 "2019-05-21T07:38:13Z")

</div>

Can we start a topic about what would they like to talk about?  
And maybe create an hashtag so people can talk about it on twitter?

---

<div class="post-metadata">

**Author:** ![patm](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/patm/32/3125_2.png) [@patm](https://community.humanetech.com/u/patm)\
**Post date:** [May 21, 2019, 6:07pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/15 "2019-05-21T18:07:46Z")

</div>

Mic, I’d like to post a general call for topics, thoughts, etc., on the forum, saying we are collecting these in order to help make the sprint event successful.

Also responded to @richard1 with an invitation to join the event. Realize I’m deviating a bit from the purpose of the event, which is to get new people to join the forum, but I hope it’s OK to invite current members as well.

---

<div class="post-metadata">

**Author:** ![richard1](https://avatars.discourse-cdn.com/v4/letter/r/50afbb/32.png) [@richard1](https://community.humanetech.com/u/richard1)\
**Post date:** [May 21, 2019, 11:03pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/16 "2019-05-21T23:03:22Z")

</div>

@patm thanks for the invitation. But I cannot be sure but I would like to help or share one way or another.

---

<div class="post-metadata">

**Author:** ![micheleminno](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/micheleminno/32/3062_2.png) [@micheleminno](https://community.humanetech.com/u/micheleminno)\
**Post date:** [May 22, 2019, 7:51am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/17 "2019-05-22T07:51:37Z")

</div>

I think the most useful thing to do before the event is to describe the status of all activities we do or we want to do in the future (I’m doing it [here](https://github.com/humanetech-community/community-hub/issues/74) for campaigns I started or contributed to), subdividing them into tasks and subtasks to encourage new people to join and contribute.

---

<div class="post-metadata">

**Author:** ![patm](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/patm/32/3125_2.png) [@patm](https://community.humanetech.com/u/patm)\
**Post date:** [May 22, 2019, 12:38pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/18 "2019-05-22T12:38:16Z")

</div>

That sounds awesome, Mic. 🐈

---

<div class="post-metadata">

**Author:** ![patm](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/patm/32/3125_2.png) [@patm](https://community.humanetech.com/u/patm)\
**Post date:** [May 25, 2019, 8:16pm UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/19 "2019-05-25T20:16:37Z")

</div>

For those who weren’t able to participate in today’s Mozilla sprint event, here are a few additions to the [transcript](http://community.humanetech.com/t/a-talk-with-htc-join-our-zoom-videochat-about-htc-tomorrow-25th-of-may-11am-pt-8pm-cet/4028/12):

1. People joining Siddhi, Mic, and me were @georgews, @cameron_t_adams, @jaedaemon, and [Jumana Abu-Ghazaleh](https://www.linkedin.com/in/jumanaabughazaleh/).
2. Mic summarized the relationship between CHT and HTC.
3. After short introductions and brief sharing, I asked people to indicate in the chat box how they heard about the event; seemed it was through HTC channels mainly.
4. Mic went over the [campaigns](https://humanetech.community/awareness-program/campaigns/) and tasks listed on the website and talked about using GitHub to modify and add to them.
5. Siddhi talked about the humanizing campaign she is running on our Instagram page and showed us a recent addition.
6. We agreed to have another video call in two weeks, adjusting for people’s schedules.
7. Cameron will give a short presentation on his [unzombie.me](http://unzombie.me) project, and others can present on their projects if they wish.
8. Overall tone of the meeting was very positive, infused with the kind of excitement and hopefulness you have when people meet for the first time.

The call went on for about an hour, so we might want to keep that in mind when scheduling future events.

It was a good, productive event. Grateful to the Mozilla Foundation for the opportunity to put it together 🥰

---

<div class="post-metadata">

**Author:** ![micheleminno](https://yyz2.discourse-cdn.com/flex036/user_avatar/community.humanetech.com/micheleminno/32/3062_2.png) [@micheleminno](https://community.humanetech.com/u/micheleminno)\
**Post date:** [June 10, 2019, 8:54am UTC](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958/20 "2019-06-10T08:54:33Z")

</div>

4 posts were split to a new topic: [Proposal: an HTC podcast](https://community.humanetech.com/t/proposal-an-htc-podcast/4132)

[Next page](https://community.humanetech.com/t/next-ct-meeting-decision-process/3958.md?page=2)
