Place to dicuss the formation of the Tech Admin Ops Team proposal.
Put up a proposal after a round of poll feedback to facilitate the formation the Tech Admin Ops team. Open to feedback and adjustments to proposal as needed.
https://www.loomio.org/p/ubS15AHl/formation-of-the-initial-interim-tech-admin-ops-team
Victor Matekole Thu 28 Jun 2018 4:02PM
I don't think we can easily just start over - we're not setting up a fresh new Mastodon instance any more, there are users and data to respect.
Strongly disagree, I came into this project where Mayel had a more conventional deployment and I decided to migrate it on fresh instance(s) into a Docker swarm cluster and decouple how user-generated content was stored and distributed... I did this by myself and it was a considerably more complex and longer process than you will most likely meet ...
Anyone with Postgres skills can easily restore the database, all user-generated content is decoupled from the instances as it stored at DreamObjects and delivered by Fastly... I would be very surprised if a fresh instance could not be deployed using Mastodon documentation and existing data being restored, without too many hoops to jump through.
Nick S Thu 28 Jun 2018 4:40PM
I think this is much easier for you to say with all the hindsight you have :) I would simply not have known this.
Victor Matekole Thu 28 Jun 2018 4:47PM
I wouldn't suggest one recommend anything unless the person thought it reasonable and viable — twice I have recommended this, with no caveat... On this occasion I have been more descriptive.
Robert Benjamin Thu 28 Jun 2018 11:00PM
Thank you @victormatekole and @wulee for engaging on this. One of most difficult things right now seems to get the kind of engagement required to move something forward as complex and critical as a transition from a legacy dev group to a hopefully sustainable team structure. All the while having that conversation continually buried under other a ton of other activity.
One of the reasons I have been pushing for a formalization of the process is so that volunteers contributing to the platforms operations will be empowered to do what needs to be done within a clearly laid scope of work and established level of group over-site and input.
Once the Coordinators officially take on their roles I'm hopefully the process produce less frustrations.
On a side note; From my vantage I don't believe that your (@victormatekole) or @mayel lengthy contributions have been properly recognized. No doubt the organization wasn't in a form to do so piror and I'm not exactly sure what should or could be done about it now but it is something that I do believe would be right to do so.
Poll Created Mon 2 Jul 2018 5:40PM
Tech Admin Ops Team Coordinators - Nominations and Voting (3 of 3) Closed Mon 16 Jul 2018 5:02PM
Congratulations and thank you to @wulee for stepping up and being voted in as Coordinator of the initial Social.Coop Tech Admin Ops Team.
You can support the volunteer team in their efforts by joining and engaging at the policy and proposal level on the Tech Working Group.
For those interested in potentially joining the Teach Ops Team look for future announcements to fill open positions.
A poll to both gather nominations and to vote to fill two (2) open Coordinator positions on the initial/interim Tech Admin Ops Teams as specified in the previously passed proposal.
To nominate yourself please add your name as an option and a short statement to pertinent skill set and availability. The window for nominations is open for four (4) days of this poll (may be extended if a minimum of (2) nominees are not received.)
To Vote choose one or two nominees. The main voting period is set for the last three (3) days of the poll.
The two (2) nominees with the most votes at the end of the poll will fill the open positions.
Position Title: Tech Admin Ops Team Coordinator
Position Description: Maintain and administer development and hosting access. Coordinate needed proposals inside Tech WG to kick off work not covered by an established policy or previous proposal. Coordinate, document, and report on team activities.
Time Commitment: Unknown
Initial Term: 6 Months
Qualifications: Organized. Good Communication. General knowledge of development or technology used.
Eligibility: A member of Social.Coop in good standing.
*Remuneration: * Volunteer position. Track hours to split limited monthly remuneration pool amongst team members (pending Remuneration Budget Proposal).
INCLUSION NOTE: Although Tech Admin Ops Team positions may require some degree of pre-existing specialized knowledge, for which individual members may use as their criteria when casting their vote, roles may also be considered "learning" opportunities, for which any member (regardless of skill level or background) with enthusiasm to take part is welcomed to apply.
Poll Note: 1st time using a poll this way. Will monitor for any issues that may arise.
Results
| Results | Option | % of points | Voters | |||
|---|---|---|---|---|---|---|
|
|
Nick S (@wulee) | 100.0% | 8 |
|
||
| Undecided | 0% | 28 |
|
8 of 36 people have participated (22%)
Poll Created Mon 2 Jul 2018 5:52PM
Critical Infrastructure Maintenance Developers - Nominations and Voting (2 of 3) Closed Mon 16 Jul 2018 5:02PM
A poll to both gather nominations and to vote to fill two (2) open Critical Infrastructure Maintenance Developer positions on the initial/interim Tech Admin Ops Teams as specified in the previously passed proposal.
To nominate yourself please add your name as an option and a short statement to pertinent skill set and availability. The window for nominations is open for four (4) days of this poll (may be extended if a minimum of (2) nominees are not received.)
To Vote choose one or two nominees. The main voting period is set for the last three (3) days of the poll.
The two (2) nominees with the most votes at the end of the poll will fill the open positions.
Position Title: Critical Infrastructure Maintenance Developer
Position Description: Maintain and keep up to date critical infrastructure.
Time Commitment: Unknown
Initial Term: 6 Months
Qualifications: Working knowledge of development or technology used.
Eligibility: A member of Social.Coop in good standing.
*Remuneration: * Volunteer position. Track hours to split limited monthly remuneration pool amongst team members (pending Remuneration Budget Proposal).
INCLUSION NOTE: Although Tech Admin Ops Team positions may require some degree of pre-existing specialized knowledge, for which individual members may use as their criteria when casting their vote, roles may also be considered "learning" opportunities, for which any member (regardless of skill level or background) with enthusiasm to take part is welcomed to apply.
Poll Note: 1st time using a poll this way. Will monitor for any issues that may arise.
Results
| Results | Option | % of points | Voters | |||
|---|---|---|---|---|---|---|
|
|
Nick S/WuLee | 50.0% | 6 |
|
||
|
|
Ed P (@elplatt) | 50.0% | 6 |
|
||
| Undecided | 0% | 30 |
|
6 of 36 people have participated (16%)
Poll Created Mon 2 Jul 2018 6:00PM
Project Developers - Nominations and Voting (1 of 3) Closed Wed 18 Jul 2018 5:02PM
A poll to both gather nominations and to vote to fill 1-10 open Project Developer positions on the initial/interim Tech Admin Ops Teams as specified in the previously passed proposal.
To nominate yourself please add your name as an option and a short statement to pertinent skill set and availability. The window for nominations is open for four (4) days of this poll (may be extended if a minimum of two (2) nominees is not received.)
To Vote choose 1-10 nominees. The main voting period is set for the last three (3) days of the poll.
The ten (10) nominees with the most votes at the end of the poll will fill the open positions.
Position Title: Project Developer
Position Description: Assist in Social.Coop development as determined by the Tech Admin Ops Team Coordinators.
Time Commitment: Unknown
Initial Term: 6 Months
Qualifications: Learning knowledge of development or technology used.
Eligibility: A member of Social.Coop in good standing.
*Remuneration: * Volunteer position. Track hours to split limited monthly remuneration pool amongst team members (pending Remuneration Budget Proposal).
INCLUSION NOTE: Although Tech Admin Ops Team positions may require some degree of pre-existing specialized knowledge, for which individual members may use as their criteria when casting their vote, roles may also be considered "learning" opportunities, for which any member (regardless of skill level or background) with enthusiasm to take part is welcomed to apply.
Poll Note: 1st time using a poll this way. Will monitor for any issues that may arise.
Results
| Results | Option | % of points | Voters | |||
|---|---|---|---|---|---|---|
|
|
Ed Summers | 31.6% | 6 |
|
||
|
|
Nathan Wittstock (@fardog) | 26.3% | 5 |
|
||
|
|
Jeremy Apthorp (@nornagon) | 26.3% | 5 |
|
||
|
|
GilScottFitzgerald (@gilscottfitzgerald) | 15.8% | 3 |
|
||
| Undecided | 0% | 28 |
|
7 of 35 people have participated (20%)
Ed Summers @edsu Thu 12 Jul 2018 12:32PM
I didn't vote for myself :-)
Nick S · Thu 28 Jun 2018 3:44PM
Victor, my apologies if I gave that impression, but by no means do I wish to belittle what you and Mayel have already put in, or to express any form of ingratitude!
I can't comment on that call you mention everyone was invited to - possibly that was before or early on in my readings of the Loomio group.
I hope you'd agree, we outsiders cannot infer the processes required easily (and just as importantly, safely) just by looking at the servers, there are too many unwritten assumptions to negotiate.
Firstly, I don't really want to have to discover the truth by poking around on the server and guessing. These are productions servers, and expecting me to do this is really as much a waste of my (also somewhat valuable) time as it would be to expect you to write large amounts of documentation.
It's not enough just to say everything is following "standard procedures" - you need to say which document you mean, and give indications where, if anywhere, our servers deviate from it.
I don't think we can easily just start over - we're not setting up a fresh new Mastodon instance any more, there are users and data to respect.
So we need some sort of a compromise.
Of course I don't expect you to write extensive docs (as nice as that would be). I hope that could be done by the incoming team. I will do some of it myself if I can gather the information and get some feedback on how correct I am.
To achieve this, during the hand-over period we will need to be able to ask questions, and get answers of some sort (perhaps this will be "don't know" or "ask so and so"), or at least know if or when we can't do this and have to guess. I think the problem with Loomio is that questions asked here get buried and don't get answered. For instance this and this are two of mine.
Perhaps we need a forum which is quieter and more discreet to ask in, so that we can avoid you needing to deal with long Loomio threads quite so much. GitLab might work for that, when I can get it procured (I'm blocked on this here).
I'm not sure if audio/video calls are very suitable since we are all in different time zones and have different commitments. I suggest something asynchronous is more likely to work out.
For now I'll probably use email as you suggest.