# Open Source Design core maintainers
**URL:** https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888
**Category:** Open Source Design meta
**Created:** [February 6, 2019, 6:29pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888 "2019-02-06T18:29:43Z")
**Posts on this page:** 10
**Page:** 1
### Author:  [@jan](https://discourse.opensourcedesign.net/u/jan)
#### Post date: [February 6, 2019, 6:29pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/1 "2019-02-06T18:29:44Z")
**This thread is to write down the ways in which we are organized.** While we aim for as little hierarchical structure as possible, some core team is needed and this is to document it as transparent as possible. Feedback welcome 🙂
**This post is a wiki, you can edit it! Click on the ‘📝 Edit’ icon at the end of the post**
* * *
[Open Source Design](https://opensourcedesign.net) is a collective of designers and other design-minded people pushing to connect open source and design more.
Everyone is welcome and there is no formal membership. The core team acts as a sort of steering group.
Being in the core team is based on:
- Amount of time being active in the collective. At least a year of activity in whichever way: event organization, code, forum activity, advocacy, etc.
- Steady activity and engagement in the community.
- History of good decisions and commitment to openness.
- Other people of the core group having met them in person or having had a call with them and vouching for them.
The current people in this group are:
- [Amit Nambiar](https://amitnambiar.com) @amit.lzkpa
- [Anxhelo Lushka](https://lushka.al) @AnXh3L0
- [Belen Barros Pena](https://twitter.com/belenpena) @belenbarrospena
- [Bernard Tyers](http://www.ei8fdb.org/thoughts/) @ei8fdb
- [Dina Michl](https://dinamichl.com) @dmichl
- [Ecaterina Moraru](http://risherry.ro) @evalica
- [Eileen Wagner](https://bumble.blue) @bumbleblue
- [Elio Qoshi](https://elioqoshi.me) @elioqoshi
- [Eriol Fox](https://erioldoesdesign.com) @Erioldoesdesign
- [Georgia Bullen](https://georgiabullen.com) @georgiamoon
- [Jan-Christoph Borchardt](https://jancborchardt.net) @jan
- [Jan Dittrich](https://fordes.de) @jdittrich
- [Nimisha Vijay](https://mobile.twitter.com/nimishaavijay) @nim
- [Peace Ojemeh (Perrie)](https://bit.ly/perrieee) @Perrie
- [Saptak Sengupta](https://github.com/SaptakS) @SaptakS
- [Victoria Bondarchuk](http://www.victoriabondarchuk.com) @victoria-bondarchuk
- [Victory Brown](https://twitter.com/VictoryBrown_) @brownie @[https://twitter.com/VictoryBrown\_](https://twitter.com/VictoryBrown_)
Alumni:
- [Brennan Novak](https://github.com/bnvk) @bnvk
- [Sam Muirhead](https://www.cameralibre.cc) @cameralibre
- [Simon Vansintjan](https://github.com/simonv3) @simonv3
- [Charlie Kritschmar](https://en.wikipedia.org/wiki/User:Charlie_Kritschmar_(WMDE)) @Incabell
## Being in the core team means that these people are
### 💌 Core email address recipients
- core at opensourcedesign dot net – used for outside communication, and recipient of Code of Conduct mails
- We need to set up redirects for each person, firstname at opensourcedesign dot net so we can individually list people on the code of conduct page without leaking their email address.
- Additionally, for our application as affiliate of the Open Source Initiative, they are asking for one specific person of contact. We could define this representative and have an address representative at opensourcedesign dot net
### 👁 Internal Signal group members
- Used for private matters which don’t go in the forum
- If we would have the possibility to have more admins on Discourse, we could possibly get rid of this group and instead discuss in a private Staff category of Discourse. (The 5 admins restriction is because our Discourse instance is graciously hosted by Discourse cc @erlend_sh)
### 💬 [Discourse forum](https://discourse.opensourcedesign.net) admins
- Listed at [About - Open Source Design](https://discourse.opensourcedesign.net/about)
- Because we receive Discourse hosting for free, only 5 admins are possible: @Erioldoesdesign, @evalica, @elioqoshi, @jan, @jdittrich
- Everyone from the core group are in [@core-group](https://discourse.opensourcedesign.net/groups/core-group) [Core group - Open Source Design](https://discourse.opensourcedesign.net/groups/core-group)
- We should require Two-Factor Authentication being enabled for admins?
- Note: Discourse allows admins to read all content – including “private messages” – of this forum. This is for abuse prevention and legal reasons. See [this thread on the Discourse meta forum for more details](https://meta.discourse.org/t/impersonation-and-reading-private-messages/8485). We trust our admins, and they won’t do this unless they absolutely have to, but we thought you should know up front.
### 👩💻 [Github organization](https://github.com/opensourcedesign) owners
- Listed at [Members · People · opensourcedesign · GitHub](https://github.com/orgs/opensourcedesign/people?utf8=%E2%9C%93&query=+role%3Aowner)
- For historical reasons, we have some people set as owners who are not in the core team anymore (Brennan @bnvk, Simon @simonv3) or never were (Andreas @andreasn, Danila @danila.pellicani, Felix @eppfel, Garth @GarthDB, Gilli @gilli, Jon @jon, Kristina, Lewis, Una, Roy @Roy). What do we do here? To adjust to this structure, it’s probably best to remove them and then people can get nominated for the proper core team? Then: Who of you would like to be in the core team? 🙂
- We should require Two-Factor Authentication being enabled for admins?
- Admins should set their visibility to public 😉 (Dina @dmichl, Charlie @Incabell)
### 💸 [OpenCollective](https://opencollective.com/opensourcedesign) core contributors
- Listed at [Open Source Design - Open Collective](https://opencollective.com/opensourcedesign/#team)
- This does not require financial donation, but is of course welcome. 🙂
- It does give the power to approve (or deny) expenses which are submitted.
- (Expenses which are submitted should be discussed before actually ordering, which it also says in the description.)
---
### Author:  [@evalica](https://discourse.opensourcedesign.net/u/evalica)
#### Post date: [February 11, 2019, 1:40pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/2 "2019-02-11T13:40:11Z")
> [@jan](#):
>
> Then: Who of you would like to be in the core team?
Since in GitHub we don’t have any count restrictions, we could add everyone from the core group to owners.
---
### Author:  [@evalica](https://discourse.opensourcedesign.net/u/evalica)
#### Post date: [February 11, 2019, 1:42pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/3 "2019-02-11T13:42:10Z")
> [@jan](#):
>
> We should require Two-Factor Authentication being enabled for admins?
Not really sure how to activate this. It’s stated as ‘NO’ in Administration, but there is no ‘edit’ for the field.
---
### Author:  [@evalica](https://discourse.opensourcedesign.net/u/evalica)
#### Post date: [February 11, 2019, 1:43pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/4 "2019-02-11T13:43:52Z")
There are also:
- some **domain** admins responsibilities
- there were also some IRC channel owners, but we kind of stepped back in using it
---
### Author:  [@jan](https://discourse.opensourcedesign.net/u/jan)
#### Post date: [December 4, 2020, 1:39pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/5 "2020-12-04T13:39:31Z")
---
### Author:  [@Erioldoesdesign](https://discourse.opensourcedesign.net/u/Erioldoesdesign)
#### Post date: [July 16, 2024, 11:46am UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/6 "2024-07-16T11:46:28Z")
I added @Incabell to the Alumni list now as I believe they have left the core team for OSD.
---
### Author:  [@Erioldoesdesign](https://discourse.opensourcedesign.net/u/Erioldoesdesign)
#### Post date: [July 16, 2024, 11:47am UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/7 "2024-07-16T11:47:35Z")
Also added Victory Brown’s forum username to her listing as it was not there 🙂
---
### Author:  [@Erioldoesdesign](https://discourse.opensourcedesign.net/u/Erioldoesdesign)
#### Post date: [June 5, 2025, 5:53pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/8 "2025-06-05T17:53:11Z")
I’ve nominated Caroline Sinders to the core team group [https://carolinesinders.com/](https://carolinesinders.com/)
She helped hugely at FOSDEM 2025 hosting and helping organise the day and after FOSDEM she asked to be more involved. She has a fantastic wealth of experience in OSS and a few folks in the core team have seconded’ her nomination to core team 😃
---
### Author:  [@juhan](https://discourse.opensourcedesign.net/u/juhan)
#### Post date: [July 2, 2026, 10:21pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/9 "2026-07-02T22:21:56Z")
17 core members. ✔
What kind of decisions take a majority (ie 9/17) to pass?
To get onto the core, a member is nominated by one or some of the core. ✔
Does that denomination from member to core require a vote
or
is @jan’s checklist (in the 1st post) the formula (and no vote required)?
What’s the atrophy process, ie how do members move from core back to regular members? An inverse formula could also be used, ie “no regular activity in the past year” or there’s a yearly member ranked choice vote!
Are these the kind of questions being answered in the new governance structure?
---
### Author:  [@jdittrich](https://discourse.opensourcedesign.net/u/jdittrich)
#### Post date: [July 3, 2026, 3:49pm UTC](https://discourse.opensourcedesign.net/t/open-source-design-core-maintainers/888/10 "2026-07-03T15:49:11Z")
> [@juhan](#):
>
> Does that denomination from member to core require a vote
Afaic its that there is no ~~veto~~ vote.
> [@juhan](#):
>
> What’s the atrophy process
there is none atm
> [@juhan](#):
>
> Are these the kind of questions being answered in the new governance structure?
I hope so