Closed nedbat closed 1 year ago
Thanks! Following
@ProductRyan can you work with Sarina to take a look through the blog posts in the PROD space, and check that they are OK to make public?
@ProductRyan said to me already,
do you know if these posts were public pre-acquisition and confluence transition? I thought that they were. If yes, I don't see any issue re-opening them
I don't know how to check if they were public.
You have to look at it page by page, to see what the page permissions are. It looks like none of the pages over-wrote the space permissions. I don't know if the space was previously open. There aren't that many pages, it may make sense to just meet and go through them and unarchive any we're okay with making public and delete the rest.
Ryan says, "if it was public before, it is ok to make public"
@nedbat unfortunately I don't know if the space was public before, do you know about that?
I think our other option is to evaluate page-by-page, correct? I can do that as we encounter relevant pages referenced in various documentation, but won't be able to be comprehensive about it
Off the top of my head, I don't know if the space was public, or how to determine that.
Here's my assessment of the pages in the PROD blog:
I'm not sure of these, either because I don't know if the feature is available to the community, or because of business stats in the pages:
These discuss features that are available to the community, and have no business information:
These pages only apply to edx.org, or have too much business information to be public:
@ProductRyan Can you take a look at the 10 "Consider Further" pages?
Methodology: For the pages to make open, I'm moving them from the private PROD space to the public OEPM space (ex: https://openedx.atlassian.net/wiki/spaces/OEPM/blog/2022/02/23/3316875400/New+Discussions+Experience+-+edX+Global+Staff+Preview?moved=true)
I'm moving the ones to make public, then I'll review the maybes and see if there's anything that seems like we might particularly want
@jmakowski1123 do you think any of these product blog posts should be public? I've left my comments here:
I am not sure: Program & Degree level Zoom Integration
I don't think so; this is publicly available now Program & Degree level Discussion Integrations
This has a throwaway line that open edx people can configure this if they need. Perhaps that's enough for us to want the post? You could argue it could be scrubbed of references like "Braze" Bulk Email Tool Default Filter
Yes but remove support ticket data Course Authoring Import Messaging & Validation
I'm not sure if the community uses this Proctoring Improvements: Proctortrack is Live!
I think this is too much edX data to release A Mobile Year in Review: Mobile FY19 📱🌏📈😀
I don't think this is worth making public unless this is a feature that is rolled into the main platform (how many community members use Enterprise?) Enterprise: Recovery email for restoring account access
Same as above, how many use enterprise? Enterprise Admin Dashboard - Learner Data
Same as above, is just a bunch of edX data. edX Mobile Update 📱🌏📈😀 (July 2018 + FY18 Recap)
Sarina and I edited Course Authoring Import Messaging & Validation to remove edX-specific details, and made it public.
The rest of the Consider Further pages were left private.
As a specific instance of #104, the PROD space blog (https://openedx.atlassian.net/wiki/spaces/PROD/overview, then select Blog in the left-hand panel) has a lot of relevant content that would be useful for the community, and likely has no private information.
How do we make it public?