#12 Explain the two mailing lists (mindshare and mindshare-announce) in the Docs
Closed: Complete 5 years ago Opened 6 years ago by bex.

Who should subscribe? What do we want to which one? i.e. Meeting Minutes

Writing goes here: https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/mindshare.html#contact-info


From my POV the use of these list should be:

mindshare:

  • Ticket tracking
  • Internal discussions and communications (too long for the telegram gruop or IRC channel)

mindshare-announce:

  • Public Announcements (Like the monthly report, new strategies, etc). This will serve as an extension of the CommBlog publications.
  • Public Discussions (Like the Ambassadors' war that is coming the winter is coming )
  • Receiving contributors feedback and issues.

In general, lists named -announce should not have discussion. They should be low traffic and point to discussion elsewhere if needed.

Metadata Update from @bex:
- Issue assigned to x3mboy

6 years ago

+1 to what @mattdm said. We should work up a "release announcement" about these lists and get them into our docs/repo readme

This ticket is focusing on the docs page for Mindshare, specifically on the "Contact info" section.

https://docs.fedoraproject.org/fedora-project/subprojects/mindshare/mindshare.html#contact-info

The source for the above document is here.

Metadata Update from @bex:
- Issue priority set to: normal (1-2 weeks) (was: awaiting triage)

6 years ago

Metadata Update from @jflory7:
- Issue assigned to jflory7 (was: x3mboy)
- Issue priority set to: critical (next week) (was: normal (1-2 weeks))
- Issue set to the milestone: Fedora 29 (to Oct. 2018)
- Issue tagged with: docs, mindshare

5 years ago

I went ahead and opened a PR on council-docs#30 to add this into our official docs page. I thought it's better to put something there for people today. We can nitpick on details later if desired.

I also mirrored these changes to the wiki page.

@jflory7 thank you for the PR on this. We are going with lazy consensus. Assuming 3 +1s and no -1s by Friday, the PR will be merged and this ticket closed.

I dropped a follow-up ping in the Council PR.

merged and queued for publish

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

5 years ago

Login to comment on this ticket.

Metadata