#5 update ambassadors conduct document, put in new docs site
Closed: Stale 2 years ago by riecatnor. Opened 6 years ago by mattdm.

https://fedoraproject.org/wiki/Ambassadors/Conduct

is an interested document -- looks like a never-approved doc. This should be updated and put on the new docs site


Metadata Update from @jflory7:
- Issue set to the milestone: Fedora 28 (to May 2018)
- Issue tagged with: ambassadors, needs feedback

6 years ago

@mattdm I believe this was in place for some time before you were the lead. This page is what I used to teach the incoming ambassadors on how to conduct themselves. A central place to have all of these types of instructions is a great idea. So how do we as ambassadors know that the page has been approved?

To be folded into ambassadors conversation.

Metadata Update from @bex:
- Issue priority set to: None (was: awaiting triage)

6 years ago

Metadata Update from @jflory7:
- Issue untagged with: needs feedback
- Issue priority set to: no deadline
- Issue set to the milestone: Future releases (was: Fedora 28 (to May 2018))
- Issue tagged with: blocked

6 years ago

I might like to see this addressed in wider messaging around the Code of Conduct. Some of this is specific to the work of Ambassadors/Advocates, but some things I find are a little strict or maybe not as relevant:

"and know the differences between [Fedora] and its cousin, Red Hat Enterprise Linux. You are not to insult any other project or product, just focus on the strengths of Fedora."

While I wouldn't consider it insulting, sometimes it makes sense to critique shortcomings of CentOS/RHEL for some use cases. If people are looking for fast and cutting-edge, and CentOS/RHEL come up, I'm going to be honest and lay out the differences depending on the specific context of the person I'm talking to. The language here somewhat implies that critiquing RHEL or Red Hat is forbidden, which I don't think is true. But there are respectful and disrespectful ways to handle any such kind of critique.

Please do not use a hat, whether it's a fedora or any other type of hat, in any presentation of Fedora or to represent the Fedora Project in any way.

Given that Red Hatters wear their literal and metaphorical red hats while representing Fedora at events and conferences, I think this one is a little dated too.

I guess what I am getting at is, I would like to see this ticket addressed at the Council level in Code of Conduct messaging instead of messaging at the Advocate level. I don't think this messaging needs to apply only to a narrow subset of the community.

I support @mattdm in this Objective, as all we know a lot of TEAM migrated their wiki page to the new standard fp.docs.org, Ambasador is not one of them, I thought this wiki can't be a place to capture new talent, because the following reason:

  1. Is completely obsolote.
  2. Don't reflect the new Role designed as -> advocate.
  3. A new complete revmap of the Ambassador Process, proposed and approved by FCAIC -> Revamp and #218 and is making it as a GOAL of Fedora.
  4. MindShare TTF @sumantrom and @marianab should consider this and add a card in their trello board to accomplish this task, to reflect somewhere in fp.docs.org under Fedora CommOps umbrella as was reflected in the revamp wiki page.
  5. and redirect to the new docs following this rule -> wiki redirect.

cc @riecatnor @siddharthvipul1

As additional note there is a complete clean up of the Ambasador Group -> #236

Regards.,

I wonder if it might make sense to convert the Ambassador wiki pages into docs hosted here in the Mindshare docs repo. This might be a way to enable us to start moving over the most important wiki pages to the docs site, and encourage people to work on them, sort of like quick docs.

This issue is being addressed in the Ambassadors Revamp. Updated documentation will be created in the form of a Role handbook for existing and new ambassadors.

Closing this issue.

Metadata Update from @riecatnor:
- Issue close_status updated to: Stale
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata