Docs meeting agenda: 2022-03-30

Project Discussion
1

Here’s the agenda for the meeting 2022-03-30T18:30:00Z. No issues are tagged for the meeting.

  • Announcements
  • Previous action items
    • bcotton was to propose splitting user and WG docs to IoT
    • bcotton was to comment on #65 and #22
    • darknao was to find where the Modularity redirection is set up, and ask for removal
  • GitLab followup
    • darknao was to provide updates on permissions setup for GitLab space
  • Content plan Proof of Concept (PoC)
    • pboy was to start a PoC of the new content plan with the Installation Guide
  • Open floor

If you have anything else to add to the agenda, please reply to this thread!

2 Likes
2

PoC/POC? Do not assume everyone knows what the acronyms mean.

It is often better form to use the expanded of what will be the acronym and then have it in brackets i.e. Bill of Materials (BoM). At that point you can then use the acronym liberally. :grinning:

2 Likes
3

Good point. I’ll expand it

2 Likes
4

Minutes and full logs are available in Meetbot.

Highlights

  • Welcome, Outreachy applicants!
  • Fedora docs are branched for F36. pbokoc is writing a “how to do release notes” guide that he’ll post in the forum (and bcotton will pin)
  • pboy posted a plan for the content plan proof of concept. Please provide your feedback!
  • bcotton proposed retiring the Telegram group

Action items

  • @bcotton to start a Discussion thread welcoming Outreachy applicants and providing some additional information for them
  • @darknao to start discussion of GitLab migration plan for follow-up next week
2 Likes
5

4 posts were merged into an existing topic: A Proof of Concept (PoC) plan for new content proposal

6

@darknao Thanks for the info. I’ll start with the editing on Monday, according to my planning.