Skip to content

Add pattern: Transparent Catalog of Privacy Controls and Posture - #931

Open
shrutibist wants to merge 3 commits into
InnerSourceCommons:mainfrom
shrutibist:add-privacy-controls-pattern-v2
Open

Add pattern: Transparent Catalog of Privacy Controls and Posture#931
shrutibist wants to merge 3 commits into
InnerSourceCommons:mainfrom
shrutibist:add-privacy-controls-pattern-v2

Conversation

@shrutibist

Copy link
Copy Markdown

A new InnerSource pattern addressing the lack of standardized privacy controls and lack of visibility into privacy compliance posture across engineering teams, solved via a two-repository model (open Controls Catalog plus access-tiered Posture Register.

@shrutibist

Copy link
Copy Markdown
Author

The failing Link Checker check appears unrelated to this PR, it's flagging a 403 from oreilly.com elsewhere in the repo, not from my new file.

@spier spier added the 📖 Type - Content Work Working on contents is the main focus of this issue / PR label Aug 21, 2026
@spier

spier commented Aug 21, 2026

Copy link
Copy Markdown
Member

Hi @shrutibist. Thank you for opening this (and the other) PRs to cotnribute your pattern content!

We are currently trying to train additional maintainers to help with the review of these PRs. Therefore it may be a little bit slower than usual but it is for the greater benefit of increasing the number of maintainers of our repo, so I hope it is ok for you to wait a bit longer :)

Some general questions from me, just out of curiosity:

  1. How did you discover this repo?
  2. How come that you directly contributed 4 patterns? Did you work in an InnerSource-setup for a while already and therefore just had these patterns "somewhere in a drawer"? ;)
  3. Did you use AI in generating these patterns? (We have seen this a lot lately, and are all for it! We always like to understand how AI can be used to make it easier to create pattern content for our repo)

We aim to provide specific feedback to your PR within the next week.

In the meantime if you have any questions, please ask!

@shrutibist

shrutibist commented Aug 21, 2026

Copy link
Copy Markdown
Author

Hello Sebastian,

  1. How did you discover this repo?
    I am an InnerSource Community member for some time now. I know about this repo based on my acquaintance and involvement with InnerSource Commons, and also during recent discussion with Clare Dillon.

  2. How come that you directly contributed 4 patterns? Did you work in an InnerSource-setup for a while already and therefore just had these patterns "somewhere in a drawer"? ;)
    I have led a very successful InnerSource program at my past company. Believe it or not they were indeed sitting in my drawer :). Clare encouraged me to share it with the broader community. Clare helped us during the InnerSource program foundation and operationalization at my past company. I was also a Speaker at the InnerSource Commons in 2022. 3 out of 4 patterns have been implemented and validated for its success. One was still in progress, hence I contributed under Initial patterns.
    Besides InnerSource, I was also leading Privacy Engineering efforts, giving me close, firsthand knowledge of the problem areas and how I used InnerSource principles to operationalize standardized privacy practices at my company. I believe this is a classic example of looking at InnerSource beyond source code contributions.

  3. Did you use AI in generating these patterns? (We have seen this a lot lately, and are all for it! We always like to understand how AI can be used to make it easier to create pattern content for our repo)
    Yes I used Claude to generate the final structure. I came across the AI usage guidance in the repo file, and provided a raw problem and solution we implemented. AI did the magic to put that in an approved structure. I reviewed the draft and made some more edits.

If you have more questions, I will be happy to help. Thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

📖 Type - Content Work Working on contents is the main focus of this issue / PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants