# VDP-36 Stewardship Process Amendment #1

**URL:** <https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564>\
**Category:** Archived Proposals\
**Created:** [March 4, 2022, 6:19pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564 "2022-03-04T18:19:53Z")\
**Posts on this page:** 10\
**Page:** 2

<div class="post-metadata">

**Author:** ![alphazwest](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/alphazwest/32/151_2.png) [@alphazwest](https://gov.vitadao.com/u/alphazwest)\
**Post date:** [March 30, 2022, 8:56pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/21 "2022-03-30T20:56:08Z")

</div>

> [@theobtl](#):
>
> That is probably a legitimate concern. However, I wonder: Does it matter if we assume that the following steps of the process would prevent any of such malicious activities? If _neither_ VitaCore challenges the motivation _nor_ the working group members vote against the nomination, wouldn’t the nomination probably be rightful and reasonable then?

I think you are spot-on in assuming that other checkpoints would effectively supersede any issues this would cause. I think simple is definitely better.

---

<div class="post-metadata">

**Author:** ![longevion](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/longevion/32/675_2.png) [@longevion](https://gov.vitadao.com/u/longevion)\
**Post date:** [April 14, 2022, 4:44pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/22 "2022-04-14T16:44:13Z")

</div>

I’ve asked Token Engineering Commons for feedback on this since the original process was inspired from theirs.

Livia’s input:

> we don’t open this process for the whole community. We’ve had arguments for both, but the rationale to have this closed to the stewards group is that they have the most insight in the community and also on the role of steward to bring a new person in. Also it doesn’t open for bigger conflicts. It’s sensitive to have an open nomination where the community could vote someone down and affect this person sense of belonging.
> 
> also, we have community stewards that aren’t stewards of a working group - they are just stewarding the community in their particular way that is also valuable. We also have working group leads that are not community stewards. Separating this two roles was important for our organization and understanding of responsibilities

See more here: [Community Stewards Working Group Manifesto - Google Docs](https://docs.google.com/document/d/1cqdURiW7Qv50J_Ha9FLr9IvdqnZGuhlsffL6O1ivHnA/edit#)

I think it makes sense to discuss pros and cons around taking things “public” by default, instead of just allowing anyone to make a public proposal, like “appeal to a higher court if you disagree with the private group’s decision”.

But I think it’s definitely an improvement if there’s a dispute resolution process when there’s disagreement. With appropriate escalation as needed.

---

<div class="post-metadata">

**Author:** ![longevion](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/longevion/32/675_2.png) [@longevion](https://gov.vitadao.com/u/longevion)\
**Post date:** [April 18, 2022, 1:34pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/23 "2022-04-18T13:34:23Z")

</div>

Trying to summarize the various stewardship appointment mechanics proposed in the comments above, I notice it’d be useful to have a resolution on what the dispute resolution process is [VDP-37 VitaDAO Governance Amendment #2](https://gov.vitadao.com/t/vdp-37-vitadao-governance-amendment-2/565/)

---

<div class="post-metadata">

**Author:** ![theobtl](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/theobtl/32/13_2.png) [@theobtl](https://gov.vitadao.com/u/theobtl)\
**Post date:** [May 5, 2022, 3:25pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/24 "2022-05-05T15:25:20Z")

</div>

Thanks for reaching out again to TEC! Livia argues that the stewards group has the most insight in the community which is why they keep nominations to that circle. We’ve discussed the same initially but my impression was that we found that our working group members are usually sufficiently vetted and involved to be qualified to make nominations, especially if we require three working group members for one nomination. Also, VitaCore can still object (step 2) and vote against (step 3).

Rather than changing step 1 from “Any three working group members or any steward” back to just “Any steward”, we could also define steps 1-3 as being private to VitaCore, while steps 4-5 would be public. Meaning, three any working group members could nominate a new steward privately to VitaCore. If a majority of VitaCore supports the nomination (step 3), the nomination would be made public in #cross-wg-chat. Would that be an appropriate compromise?

> [@longevion](#):
>
> Trying to summarize the various stewardship appointment mechanics proposed in the comments above, I notice it’d be useful to have a resolution on what the dispute resolution process is [VDP-37 VitaDAO Governance Amendment #2](https://gov.vitadao.com/t/vdp-37-vitadao-governance-amendment-2/565/)

The latest (and significantly revised) Dispute Resolution Process proposal will be published here in the next hours. Is there anything else that requires this Stewardship Process proposal to be updated?

---

<div class="post-metadata">

**Author:** ![longevion](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/longevion/32/675_2.png) [@longevion](https://gov.vitadao.com/u/longevion)\
**Post date:** [May 5, 2022, 9:37pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/25 "2022-05-05T21:37:25Z")

</div>

Agree on keeping steps 1-3 private.

I think we should aim for consensus instead of majority rule. If VitaCore members have big reservations about a nominee, they can trigger a dispute resolution process (which seems worthwhile, to keep harmony in the group).

---

<div class="post-metadata">

**Author:** ![theobtl](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/theobtl/32/13_2.png) [@theobtl](https://gov.vitadao.com/u/theobtl)\
**Post date:** [May 6, 2022, 1:29pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/26 "2022-05-06T13:29:45Z")

</div>

> [@longevion](#):
>
> Agree on keeping steps 1-3 private.

I’m updating the proposal to include that. If that is the last change, we can move forward to the Snapshot vote in seven days.  
Edit: Of course this proposal is dependent on the Dispute Resolution Process (DRP) so we will move both proposals to Snapshot at the same time. The DRP has been substantially revised and will also be up for discussion on Discourse for at least seven more days once its up.

> [@longevion](#):
>
> I think we should aim for consensus instead of majority rule. If VitaCore members have big reservations about a nominee, they can trigger a dispute resolution process (which seems worthwhile, to keep harmony in the group).

This is certainly a valid perspective. We’ve discussed this a few times already and it seems controversial, so I’m not including it in the proposal right away but would put it up for discussion again. @Savva argued for a majority vote, I do too, @audieleon argued for a majority vote only for votes against the wg member’s vote (which is irrelevant in the current draft where the order was been changed and wg members vote after VitaCore).

You’re mentioning the Dispute Resolution Process and that any VitaCore member can trigger that through a challenge in step 2. This should ensure that we would ever only get to step 3 if there are no _significant and substantial_ doubts about the candidate. There may still be less significant reasons that someone would vote against a nominee - should this lead to a cancellation of the nomination? The whole point of step 2 is to filter out legitimate and substantial reasons from onboarding a new steward and distinguish them from other concerns that should not stop a nomination.

With the Dispute Resolution Process in place in step 2, shouldn’t step 3 therefore come with a majority vote?

---

<div class="post-metadata">

**Author:** ![theobtl](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/theobtl/32/13_2.png) [@theobtl](https://gov.vitadao.com/u/theobtl)\
**Post date:** [May 18, 2022, 5:54pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/27 "2022-05-18T17:54:52Z")

</div>

> [@theobtl](#):
>
> this proposal is dependent on the Dispute Resolution Process (DRP) so we will move both proposals to Snapshot at the same time.

The Dispute Resolution Process has just been published as VDP-44:

> [@VDP-44 Dispute Resolution Process](https://gov.vitadao.com/t/vdp-44-dispute-resolution-process/688):
>
> Summary This proposal introduces a Dispute Resolution Process to systematically prevent and resolve any tensions and conflicts. The process consists of escalating steps from Conciliation to Mediation to an internal VitaDAO Arbitral Tribunal and, finally, to online Third-Party Arbitration with enforceability of awards through VitaDAO. It is open to all members of VitaDAO to resolve disputes, including violations of VitaDAO’s Code of Conduct. In the event that a matter may be of a criminal nature…

This means that this proposal, VDP-36, may move on to phase 3 on Snapshot anytime from in seven days when VDP-44 has completed its seven-day phase 2 period without significant changes.

**Last call for feedback:** If anyone feels strongly about any further changes to this proposal, VDP-44, please voice your suggestion here as soon as possible so that we can move forward in a timely manner.

---

<div class="post-metadata">

**Author:** ![alexdobrin](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/alexdobrin/32/198_2.png) [@alexdobrin](https://gov.vitadao.com/u/alexdobrin)\
**Post date:** [June 29, 2022, 7:15am UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/28 "2022-06-29T07:15:21Z")

</div>

I suggest replacing working group members with VitaCORE in the following options

```auto
Option A
In a vote necessarily recurring every six months, members of all working groups vote on whether the steward should remain in place in an anonymous poll on Discord or Discourse.
If a majority of members of all working groups do not confirm the steward, the steward is offboarded.

Option B
In a vote optionally occurring at any time, members of all working groups vote on whether the steward should remain in place in an anonymous poll on Discord or Discourse.
If a majority of members of all working groups do not confirm the steward, the steward is offboarded.

```

---

<div class="post-metadata">

**Author:** ![theobtl](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/theobtl/32/13_2.png) [@theobtl](https://gov.vitadao.com/u/theobtl)\
**Post date:** [July 14, 2022, 3:10pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/29 "2022-07-14T15:10:32Z")

</div>

FYI, there’s now a counter proposal to this proposal: [VDP-52 stewards election proposal options](https://gov.vitadao.com/t/vdp-52-stewards-election-proposal-options/761)

---

<div class="post-metadata">

**Author:** ![theobtl](https://dub1.discourse-cdn.com/flex017/user_avatar/gov.vitadao.com/theobtl/32/13_2.png) [@theobtl](https://gov.vitadao.com/u/theobtl)\
**Post date:** [August 14, 2022, 9:25pm UTC](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564/30 "2022-08-14T21:25:44Z")

</div>

Cross-posting my comment from [VDP-51 Stewardship election [counter proposal] - #15 by theobtl](https://gov.vitadao.com/t/vdp-51-stewardship-election-counter-proposal/759/15) here for reference. I’d suggest to update this proposal accordingly:

Before:

> 1. If the nomination receives support from a majority of VitaCore members, the nomination is shared publicly in the Discord channel #cross-wg-chat where members of all working groups vote on the nomination.
> 2. If a majority of votes is in agreement, the nominated steward is offered the position.

After:

> 1. If the nomination receives support from a majority of VitaCore members, the nomination is shared publicly in the Discord channel #cross-wg-chat where members of all working groups participate in the voting process on the nomination.  
> – Anyone who has the corresponding working group’s “Member” Discord role has five votes.  
> – Anyone who has the corresponding working group’s “Guest” Discord role has a single vote.  
> – Anyone who has a “Member” or Guest" Discord role in any working group, but not in the corresponding working group, does not have a vote but has the right to receive a public response to questions and suggestions.
> 2. If a majority of votes is in agreement, the nominated steward is offered the position.

If there’s no objection until next week, I’ll update the proposal with this change.

[Previous page](https://gov.vitadao.com/t/vdp-36-stewardship-process-amendment-1/564.md?page=1)
