MCWS - Document resource ownership -



3 years ago
2 years ago


(Reporter: Tad, Unassigned)


(Blocks: 1 bug)




3 years ago
We need your help in identifying who your community has given the authority to manage the services we provide you.

In the situation that a decision needs to be made or action needs to be taken in regards to your service (eg someone is requesting an email on your community domain) we need the name(s) of the person who can say yes or no, or initiate change requests.

Your community can identify more than one person who has the authority to make decisions regarding your services. We will reach out to every person listed as “owner” for your service. Please be aware though that if you identify more than one person, we will act based on the first response we get. The persons named *must* be responsive in a timely manner. These persons will also be able to request changes to the owners list moving forward.

You can use this bug to discuss who these names should be, or you can use whatever discussion channel your community prefers. We only ask that someone from your community responds within *30 days* to let us know a discussion is happening. If we don’t get any sort of response within 30 days we will assume your community is inactive and start the process to deactivate your services. 

You can take more than 30 days to give a final answer. Once we’ve received a response we will recognize the community is active and support you in coming to a decision that is right for your community.

Discussion and questions about this process should go on this Discourse thread -

If you need to reach out to us privately, you can send an email to

In short:

- Communities have 30 days to start the discussion
- It’s up to communities to appoint their resource owner(s)
- These owners must be responsive and will have the authority to request changes to the serivces owners list
- We will support communities in making their decision, including arranging conflict resolution if necessary.
- Please cc any active members of your community that we’ve missed

Comment 1

2 years ago
Hey All,

Thanks @Tom for filing this bug. 

On behalf of Mozilla Ghana Community I am proposing following Mozillian for the ownership of the community website:-
1. Mahendra Kumar Shrivas (
2. Michael E. E. Turkson (



Comment 2

2 years ago

Michael here.
I would like to acknowledge receipt of the request as being listed as "owner" of the services.
I am prepared to assist Mahendra in taking ownership and managing them.

Comment 3

2 years ago
Hey Tom,

Kindly process the request.

Flags: needinfo?(tom)
Thanks, as there have been no objections, we will list Mahendra and Michael as resource owners. We'll bee in touch with more info.
Last Resolved: 2 years ago
Flags: needinfo?(tom)
Resolution: --- → FIXED
@Michael - I can't find your Mozillians profile, do you have one? If not please make one. If there is a reason you don't want to have one, please email so we can discuss it. Currently it's our policy that you must have one, but we would want to take your objections into consideration.

Comment 6

2 years ago
Hello @Majken,

Yes plz he is contributing to Mozilla’s mission for more than 5 yrs. His profile is

I am wondering no one have vouched for him, Vouching rights are not activated in my Mozillian profile.
Anyhow if possible kindly vouch for him or let us know to whom we should contact regarding that.
We are having other members also who are contributing to Mozilla's mission but still not have vouched yet.

Kindly do process MCWS request.

You need 3 vouches to be able to vouch for someone else.

I am not comfortable vouching for people I don't directly work with, as that is the point of the vouching system.

If you need help finding people to vouch for you, email and we'll take it off bug.


2 years ago
Duplicate of this bug: 1208541

Comment 9

2 years ago
I'm not sure if ownership of was ever transferred to the community. There's also a second domain registered by one of the community members Reopening this to have that resolved
Resolution: FIXED → ---
You need to log in before you can comment on or make changes to this bug.