#142 Add past FLOCK activities to D&I team docs
Closed: moved 7 months ago by orionstar25. Opened 9 months ago by bee2502.

We have compiled a list of previous FLOCK sessions by D&I team as well as FLOCK/ conference session ideas. As being discussed in ticket #124 , It would be good to have this in our team docs to showcase our work as well as make it easier in planning sessions for upcoming conferences.

Link to doc: https://docs.google.com/document/d/1IFsaPC09DZXaKrsWnxfb6im2rANmQGH1Wj0Fpeasym4/edit#heading=h.jg2ev5g9eziq


  1. It would be great to have this on a new page under Events section once @hirat is done with restructuring after #120. If you take up this task before, create a new page with the text and mention it in your PR and #120 about how it should be structured later.

  2. The new page can be titled 'Fedora FLOCK Sessions' and ideally 1-2 sentences of short description before the sessions from the google doc are listed. Example description:
    "FLOCK is the annual Fedora community conference. This page lists sessions from D&I team presented at previous FLOCK editions as well as some ideas" and a link to FLOCK page: https://flocktofedora.org/

  3. Once this page is created, add a link to this page to 'Event Organizer Resource Pack' (https://docs.fedoraproject.org/en-US/diversity-inclusion/fedora-womens-day/resource-pack/)
    with a short bridging description eg. "Ideas for organizing D&I related sessions at your event"

Metadata Update from @bee2502:
- Issue marked as depending on: #120
- Issue tagged with: good first issue, help wanted, improvement, type - docs

9 months ago

Metadata Update from @jflory7:
- Issue priority set to: waiting on assignee (was: awaiting triage)

9 months ago

Metadata Update from @jflory7:
- Issue unmarked as blocking: #120
- Issue priority set to: next meeting (was: waiting on assignee)

8 months ago

Metadata Update from @jflory7:
- Issue priority set to: waiting on assignee (was: next meeting)

8 months ago

Discussed in 2020-09-10 meeting.

A lot of hard work is already done in this ticket by collecting a historical archive of the things we have done over the years. We will need to think about how to structure and lay this out in our docs.

@orionstar25 is opening a new ticket to replace #122. I think the work in the forthcoming ticket is related to how we set up and write about things we have done in past events. Once the new ticket is open, I will update the metadata so there is a dependency on this ticket to the new ticket.

Once the organization work is done, I think we can work on copying content from Google Doc and migrating it into our own docs.

Metadata Update from @jflory7:
- Issue untagged with: good first issue, help wanted
- Issue priority set to: waiting on external (was: waiting on assignee)
- Issue tagged with: blocked

7 months ago

Closing this here as moved and tracking this further at #167

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

7 months ago

Login to comment on this ticket.