Add Fedora Planet doc, other misc. setup for on-boarding guide #2

Merged

jflory7 merged 2 commits from add/fedora-planet into master 2026-06-08 08:20:20 +00:00

Conversation 15 Commits 2 Files changed 5 +137 -19

jflory7 commented 2018-03-01 11:00:01 +00:00

Owner

Copy link

This PR adds a Fedora Planet doc to the On-boarding Guide. This is converted and modernized from the Fedora Planet wiki page. It also sets up other minor details for the on-boarding guide in the context of docs-fp-o.

This PR adds a Fedora Planet doc to the On-boarding Guide. This is converted and modernized from the [Fedora Planet wiki page](https://fedoraproject.org/wiki/Planet). It also sets up other minor details for the on-boarding guide in the context of docs-fp-o. [](/fedora-commops/onboarding-guide/issue/raw/f352b4268ad4cc1e8fa44875982c5d6d919a975d97a8600fb130759e2b3e3063-8OLoSNa.png)

jflory7 commented 2018-03-01 11:02:47 +00:00

Author

Owner

Copy link

rebased onto 7cc771c5d46f414c33542261e1b2ad00a39ab406

rebased onto 7cc771c5d46f414c33542261e1b2ad00a39ab406

jflory7 commented 2018-03-01 11:43:59 +00:00

Author

Owner

Copy link

Metadata Update from @jflory7:

• Pull-request tagged with: add doc, needs feedback

**Metadata Update from @jflory7**: - Pull-request tagged with: add doc, needs feedback

ssitani commented 2018-03-01 13:06:58 +00:00

First-time contributor

Copy link

Nitpick:
Please consider using a full link macro here.
link:http://fedoraplanet.org/[Fedora Planet]

Not a big problem, though, as URLs beginning with https:// (and other standard prefixes) are automatically parsed by AsciiDoctor.
Please feel free to ignore this nitpick:)

Nitpick: Please consider using a full link macro here. link:http://fedoraplanet.org/[Fedora Planet] Not a big problem, though, as URLs beginning with `https://` (and other standard prefixes) are automatically parsed by AsciiDoctor. Please feel free to ignore this nitpick:)

ssitani commented 2018-03-01 13:12:49 +00:00

First-time contributor

Copy link

I'd personally avoid contractions (Ln#8) and Saxon possessives (Ln#9).

I'd personally avoid contractions (Ln#8) and Saxon possessives (Ln#9).

ssitani commented 2018-03-01 13:29:51 +00:00

First-time contributor

Copy link

What would this be referring to on line 24?
Filtering your content? Setting up a feed of your content to Fedora Planet? The wording seems slightly ambiguous in this paragraph .
Please use pronouns with caution:)

What would `this` be referring to on line 24? Filtering your content? Setting up a feed of your content to Fedora Planet? The wording seems slightly ambiguous in this paragraph . Please use pronouns with caution:)

ssitani commented 2018-03-01 13:36:00 +00:00

First-time contributor

Copy link

I'd be inclined to use 2 words: plain text as opposed to plaintext, because:

1. plain text appears to be used considerably more often in technical writing.
2. plaintexthas connotations related to cryptography, which do not apply to this context

I'd be inclined to use 2 words: `plain text` as opposed to `plaintext`, because: 1. `plain text` appears to be used considerably more often in technical writing. 2. `plaintext`has connotations related to cryptography, which do not apply to this context

jflory7 commented 2018-03-02 09:34:26 +00:00

Author

Owner

Copy link

@ssitani Thanks for the feedback. The latest commit addresses all of your feedback. Thanks for the nitpicks. 👍

@ssitani Thanks for the feedback. The latest commit addresses all of your feedback. Thanks for the nitpicks. :thumbsup:

jflory7 commented 2018-03-02 09:34:29 +00:00

Author

Owner

Copy link

rebased onto 3e9d1aebfd

rebased onto 3e9d1aebfd7eeab4b511d5c69875203cda89017c

jflory7 commented 2018-03-02 09:36:27 +00:00

Author

Owner

Copy link

Metadata Update from @jflory7:

• Pull-request untagged with: needs feedback
• Request assigned

**Metadata Update from @jflory7**: - Pull-request **un**tagged with: needs feedback - Request assigned

bex commented 2018-03-02 09:42:36 +00:00

First-time contributor

Copy link

I could easily see this turning into a bullet list htat just lists the content i.e.

• sexual images ...
• copyright violations ...
• other material which violates the CoC

no need to explain why.

WDYT? CC: @mattdm

I could easily see this turning into a bullet list htat just lists the content i.e. * sexual images ... * copyright violations ... * other material which violates the CoC no need to explain why. WDYT? CC: @mattdm

mattdm commented 2018-03-02 10:55:40 +00:00

First-time contributor

Copy link

I don't know if we even need a list. Actually, I'd just remove the == Inappropriate material and put "Inappropriate material may be removed from Fedora Planet without prior notice." as the last sentence of == Appropriate material — that section already references the CoC.

I don't know if we even need a list. Actually, I'd just remove the `== Inappropriate material` and put "Inappropriate material may be removed from Fedora Planet without prior notice." as the last sentence of `== Appropriate material` — that section already references the CoC.

jflory7 commented 2018-03-02 11:22:57 +00:00

Author

Owner

Copy link

1 new commit added

• Revise content guidelines based on feedback in PR#2

**1 new commit added** * Revise content guidelines based on feedback in PR#2

jflory7 commented 2018-03-02 11:24:02 +00:00

Author

Owner

Copy link

@bex @mattdm I made a new commit based on your feedback. I opted to remove the Inappropriate content section, moved the disclaimer about inappropriate content, and renamed Appropriate content to Content guidelines.

@bex @mattdm I made a new commit based on your feedback. I opted to remove the `Inappropriate content` section, moved the disclaimer about inappropriate content, and renamed `Appropriate content` to `Content guidelines`.

ssitani commented 2018-03-02 18:03:28 +00:00

First-time contributor

Copy link

Unless you're referring to the Your Name placeholder itself, I'd use a regular font as opposed to bold. If you'd like to designate a placeholder inside the code block, you might prepend the [subs=+quotes] attribute

Unless you're referring to the `Your Name` placeholder itself, I'd use a regular font as opposed to bold. If you'd like to designate a placeholder inside the code block, you might prepend the `[subs=+quotes]` attribute

jflory7 commented 2018-03-16 20:21:46 +00:00

Author

Owner

Copy link

Pull-Request has been merged by jflory7

Pull-Request has been merged by jflory7

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

add doc

Adds a new document

  

blocked

Cannot move forward: blocked by feedback, other tickets, etc.

  

change doc

Changes an existing document

  

Closed As

Complete

Closed with the reason of Complete

  

Closed As

Duplicate

Closed with the reason of Duplicate

  

Closed As

Insufficient data

Closed with the reason of Insufficient data

  

Closed As

Moved

Closed with the reason of Moved

  

Closed As

Not possible

Closed with the reason of Not possible

  

good first issue

Good tickets to begin with (if you want to get involved, try working on one of these!)

  

help wanted

Tickets where we need help or need feedback from the wider Fedora community

  

meeting

Tickets marked for discussion at next meeting

  

needs feedback

Tickets needing feedback before moving forward

  

Priority

awaiting triage

Priority of awaiting triage

  

Priority

critical (next week)

Priority of critical (next week)

  

Priority

minor (3-4 weeks)

Priority of minor (3-4 weeks)

  

Priority

no deadline

Priority of no deadline

  

Priority

normal (1-2 weeks)

Priority of normal (1-2 weeks)

  

function

analytics

Community Social Analytics. One of the two main functions of the Community Operations Team. All issues/tasks should identify a function as different team members are responsible for different function

  

function

communications

Community Blog, newsletters, outreach content, Magazine coordination, and community messaging

  

function

docs

Documentation site, playbooks, guides, knowledge base, and contributor reference materials

  

function

events

Event production, release parties, conferences, streaming, video processing, and community event logistics

  

function

onboarding

Newcomer experience, mentoring, intern programs, team growth, and contributor onboarding

  

function

operations

Team governance, repo management, meeting logistics, infrastructure, and internal process

  

good first issue

Good tickets to begin with (if you want to get involved, try working on one of these!)

  

help wanted

Tickets where we need help or need feedback from the wider Fedora community

  

needs

changes

Needs changes or fixes before closing

  

needs

reporter feedback

Additional feedback or information from the reporter is needed to advance

  

needs

team vote

A vote is required from Fedora Community Operations Team members in order to advance

  

needs

triage

A repository maintainer is needed to triage this further

  

scope

bug

Something isn't working

  

scope

improvement

Requests for something we are either repeating or improving

  

scope

new

Requests for a new task or project for the team

  

state

approved

Tickets that received approval by the Fedora Community Operations Team

  

state

blocked

Cannot move forward: blocked by feedback, other tickets, etc.

  

state

duplicate

This issue or merge request already exists

  

state

invalid

This doesn't seem right

  

state

wontfix

This will not be worked on

No labels

add doc

blocked

change doc

Closed As

Complete

Closed As

Duplicate

Closed As

Insufficient data

Closed As

Moved

Closed As

Not possible

good first issue

help wanted

meeting

needs feedback

Priority

awaiting triage

Priority

critical (next week)

Priority

minor (3-4 weeks)

Priority

no deadline

Priority

normal (1-2 weeks)

function

analytics

function

communications

function

docs

function

events

function

onboarding

function

operations

good first issue

help wanted

needs

changes

needs

reporter feedback

needs

team vote

needs

triage

scope

bug

scope

improvement

scope

new

state

approved

state

blocked

state

duplicate

state

invalid

state

wontfix

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

4 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

commops/onboarding-guide!2

No description provided.