M
by Moult on 15 Jan 2022, edited 7 Apr 2022
#
+14 votes
Hey everyone! As mentioned in this thread, I think the time is ripe for OSArch to take its next step and grow into something larger.
The first step to make these larger steps is to agree on a number of individuals who can make serious decisions on behalf of the OSArch community. It is not physically possible to coordinate with absolutely everyone with a fluctuating community audience, so by nominating a number of key individuals, it makes it easier to make decisions. This is not a new concept, and has been floated around the OSArch community in various channels for a while now.
In this thread, this is a call for volunteers for people who would like to be part of the 2022 OSArch Steering Committee. Here are some self-imposed rules I've come up with based on a existing discussions from others in the community.
-
You must nominate yourself. You must want to be in this role :) Nobody will force you to do it.
-
The steering committee will only last a year, then the role expires, and we will re-nominate.
-
You must have already participated in contributions to Free Software somewhere.
-
We make a decision on the individuals in a month's time: Feb 15. The reasoning for this quick pace is that we expect all those taking this role to be already active on OSArch. At the same time, if we want to achieve other goals through the rest of this year we can't start too late.
-
No more than 10 people. I made up the number 10. But the intention is that too many people make it harder to coordinate. We're growing, but we're not that large yet :)
The responsibility of the role is:
-
The top priority is creating a legal entity. We're going to work out how, where, and when. We will achieve this within 2022.
-
We're going to make this whole leadership process a little less fuzzy than the 5 rules I made up. So next year, we've got a process that doesn't come as a surprise.
-
If an OSArch proposal comes through that will have an impact on OSArch earning money, spending money, or the OSArch branding, or enterprise affiliation (i.e. making partnerships with OSArch and corporations), then it is your responsibility to make sure that the proposal reflects OSArch values. If they do not, you have the responsibility to "prevent" a project being associated with OSArch. When a project goes ahead, you may also be responsible for being the legal or financial contact when letters are written, or transactions are being made.
-
It is your responsibility to ensure that OSArch decision making is never made in private. Decisions are made publicly with full participation and grace periods provided to allow community participation.
As you can see, the responsibilities are pretty restricted. Essentially nothing is changed, except that when legal association and money get involved, we now have people we can turn to who must all agree to get the final yes/no decision. Everything is still done 100% in the open.
I would like to volunteer myself to be part of this committee for the first year :)
Now it's your turn!
C
by CadGiru on 15 Jan 2022
#
+14 votes
Would like to nominate myself (peter Sande / cadgiru)
The responsibility of the role is:
The top priority is creating a legal entity. We're going to work out how, where, and when. We will achieve this within 2022.
Not my expertise, but might know someone who has
We're going to make this whole leadership process a little less fuzzy than the 5 rules I made up. So next year, we've got a process that doesn't come as a surprise.
Agree
If an OSArch proposal comes through that will have an impact on OSArch earning money, spending money, or the OSArch branding, or enterprise affiliation (i.e. making partnerships with OSArch and corporations), then it is your responsibility to make sure that the proposal reflects OSArch values. If they do not, you have the responsibility to "prevent" a project being associated with OSArch. When a project goes ahead, you may also be responsible for being the legal or financial contact when letters are written, or transactions are being made.
Agree
It is your responsibility to ensure that OSArch decision making is never made in private. Decisions are made publicly with full participation and grace periods provided to allow community participation.
Agree
B
by brunopostle on 15 Jan 2022
#
+12 votes
Ok I'll bite, I volunteer.
Free Software experience: user, documentation writing, support, bug reporting, drive-by contributions, bikeshedding, release manager, distribution packaging, library and application development.
T
by theoryshaw on 15 Jan 2022
#
+13 votes
Good initiative. As things evolve I'm interested in trying to off load the historically messy process of governance to 3rd party technical platforms-- in the evolving spaces of DAO's or similar.
I don't have all the answers, but think since OSArch is in it's early days, and generically we like hacking on things, that we are in an excellent position to test them out together.
D
by duncan on 16 Jan 2022
#
+7 votes
Okay, I'm in. It will mean I cut down on time spent on the wiki and social media. Social media is important for our growth and reaching new people all the time. So it concerns me a bit to drop the ball on that one. Hopefully someone else will pick it up, and that's worth a discussion in this thread.
M
by Moult on 4 Feb 2022
#
+2 votes
Hey all! Very excited to see who's up for the adventure so far! Just bumping this thread as it is now early February. On Feb 15, so far, we will confirm @Moult @CadGiru @brunopostle @theoryshaw and @duncan .
J
by Jesusbill on 14 Feb 2022
#
+6 votes
Hi all, I would like to volunteer for being part of the committee and help as I can to achieve the goals, especially setting up an organization that can bring as to the next stage, cheers.
N
by Nigel on 15 Feb 2022
#
with Jesusbill joining that makes six. I think that's a suitable quorum, minimum six, maximum ten. I am looking forward to seeing what happens next.
D
by duncan on 15 Feb 2022
#
I'm free all week @theoryshaw @Moult @Jesusbill @brunopostle @CadGiru so I'd love a first meeting. Maybe just a meeting about who we each are and our motivations for being here. I don't know you all equally well. I'm really flexible for time. What timezones are we all in? I'm in CET (UTC +1)
B
by brunopostle on 15 Feb 2022
#
I'm in the UK, WET (UTC+0). Evenings, Fridays or weekends are best, but I work part-time, so can rearrange to office hours with a bit of notice.
J
by Jesusbill on 15 Feb 2022
#
I am CET, too; pretty flexible in general.
Finding a suitable time across three continents will definitely be a challenge :)
T
by theoryshaw on 15 Feb 2022
#
UTC-6... i'm the bastard child. ;)
M
by Moult on 15 Feb 2022
#
+1 votes
Sydney timezone, but pretty flexible, any time or day that isn't 2am :)
How about the usual Monthly meetup time/day? Does that work for everyone?
D
by duncan on 16 Feb 2022
#
I think the suggestion is Saturday 20:00 UTC
M
by Moult on 16 Feb 2022
#
Indeed, can I tentatively propose 19th Feb, 20:00 UTC? If we don't get enough responses in time, how about 26th Feb, 20:00 UTC?
T
by theoryshaw on 16 Feb 2022
#
can't on the 19th, but can on the 26th.
B
by brunopostle on 16 Feb 2022
#
I can't on the 19th, though 26th should be ok
D
by duncan on 17 Feb 2022, edited 17 Feb 2022
#
OK with Saturday 26th 20.00 UTC.
Check your timezone: https://everytimezone.com/s/5fd3cf6a
At the top of this page https://wiki.osarch.org/index.php?title=Organization I've mentioned the steering committee and members, I would like to link to each persons wiki page where we can each write whatever we want (or nothing) about us with links etc. I can't find a wiki page for Bruno and Peter (CadGiru). I have also added two new fields to the forum profile page. It would be great if we all fill out one of them which is a link to our wiki user page. Personally I'd also like if people fill out the new field on the forum profile for 'real name' but people have different views on that.
Connecting these profiles together and saying at least a little about who we are is all about trust and transparency.
M
by Moult on 20 Feb 2022, edited 20 Feb 2022
#
Happy days! See you all on the Saturday 26th 20.00 UTC !
May I propose https://meet.jit.si/osarch :)
T
by theoryshaw on 22 Feb 2022, edited 22 Feb 2022
#
+2 votes
We finally got 100 stars on our Gitlab repo, https://gitlab.com/osarch/FreeMVD_WorkFlow!
I think we now satisfy all the criteria to be fiscally hosted by the https://opencollective.com/opensource, if we still want to pursue that angle.
related conversation: https://community.osarch.org/discussion/comment/3732/#Comment_3732
M
by Moult on 26 Feb 2022
#
+3 votes
Bump :) See you all soon!
T
by theoryshaw on 27 Feb 2022
#
+5 votes
meeting notes here: https://gitlab.com/osarch/OSArch/-/blob/main/Meeting%20Minutes/20220226.md