# Membership Model?

**URL:** <https://discourse.opensourcedesign.net/t/membership-model/1112>\
**Category:** Open Source Design meta\
**Created:** [June 9, 2019, 3:53pm UTC](https://discourse.opensourcedesign.net/t/membership-model/1112 "2019-06-09T15:53:25Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![jan](https://yyz1.discourse-cdn.com/flex029/user_avatar/discourse.opensourcedesign.net/jan/32/8_2.png) [@jan](https://discourse.opensourcedesign.net/u/jan)\
**Post date:** [August 7, 2019, 6:29pm UTC](https://discourse.opensourcedesign.net/t/membership-model/1112/6 "2019-08-07T18:29:33Z")

</div>

> [@elioqoshi](#):
>
> In a nutshell, I think it’s totally fine if we go on like we used to, expand the Core group with a lightweight set of rules to join and stay, have a few people within Core with Superadmin privileges for our services, and establish a process within Core on how we do decision-making. Would this be agreeable with?

Yes, I’d say this is good. The main thing I would change/add in [Open Source Design core team](https://discourse.opensourcedesign.net/t/open-source-design-core-team/888) is to have a set of tags / tasks which everyone can add to themselves about what they are interested in working on, e.g.:

- coordination
- event organization
- job board
- fundraising
- forum maintenance
- outreach
- etc…

---

_[View the full topic](https://discourse.opensourcedesign.net/t/membership-model/1112)._