Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Decide on policy/guidelines for "Public Notifications" #625

Open
stpaultim opened this issue Jan 1, 2020 · 4 comments
Open

Decide on policy/guidelines for "Public Notifications" #625

stpaultim opened this issue Jan 1, 2020 · 4 comments

Comments

@stpaultim
Copy link
Contributor

stpaultim commented Jan 1, 2020

Due date: jan 15


We just added a content type for "Public Notifications" that will display on the Dashboard of any Backdrop CMS site with this block enabled (it will be enabled by default on any new installations with version 1.15 or later).

We need to discuss and settle on some guidelines for what is appropriate content to be displaying here. I suggest we put this on agenda for next Outreach meeting. In the meantime, we can gather comments here.

Currently, there are four Public Notifications published on BackdropCMS.org. The most recent 3 announcements are showing up on Backdrop sites. I think we should have a blog post about the new notifications system ready by January 15th and make sure that one of the notifications is a link to that post.

Audience

These messages will by definition reach a mix of the following people and we should keep them all in mind:

  • Developers
  • Site owners
  • Site builders
  • Content editors

Types of messages that MIGHT quality for public notifications

This list is still up for discussion

  • VUG - Virtual User Group announcements
  • Important releases of Backdrop CMS core
  • Special Backdrop CMS events (Mini camps, Birthday Parties, Etc)
  • Special blog posts worth highlighting
@stpaultim
Copy link
Contributor Author

In addition to some editorial guidelines, I think we should assign an individual or small group of people who are responsible for curating content in this feed.

@jenlampton
Copy link
Member

@stpaultim I think the list in the top post is perfect. :) I also like the idea for nominating a set of people who are responsible for creating these notices.

Anyone else want to weigh in on the types of messages?

@ghost
Copy link

ghost commented Jan 10, 2020

In my opinion/experience, I don't think these messages will really reach developers as much as the other audience listed. They might see them in passing while building a site, but I'm sure Backdrop developers already get their info elsewhere. So I think focus on the other 3 audiences.

As for content, I'm not sure about VUGs, but the others seem OK. But I'd suggest making sure they are only ever highly polished, set-in-stone announcements, posts, etc.

@klonos
Copy link
Member

klonos commented Jan 10, 2020

I also agree with @stpaultim's list, but I would also add announcements of PMC decisions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants