ossf
Draft Baseline Whitepaper
The Baseline Whitepaper should contain detailed descriptions, background information, and technical guides for each metric. It should draw on the findings of the Pilot, and will act as the primary reference material for the subsequent rollout initiatives.
@funnelfiasco I think we should consider this work in our tech writer funding proposal. This seems higher value than the style guide in terms of driving adoption and clarity.
The goal of the tech writer proposal as currently scoped is to reduce the un-adoption, which is different from driving adoption.
That said, it's something we can consider (although they might be separate efforts). I'm not convinced of the value of a white paper for driving adoption, though. It will be out of date the moment we change any control or when GitHub changes how a configuration option works. A better approach, I think, would be to have independent context documentation for controls. How that's stored and who manages it is an open question.
I can certainly start us off, collect the data, and get a draft for us if we still desire this.
I'm not convinced a white paper is the best format for this, but I agree there's a need to expand on "detailed descriptions, background information, and technical guides". I expect that we'll have enough to talk about on Tuesday, but I'll try to put together a rough skeleton prior to the following meeting (27 May).
Related - What would we think about 2 blogs, one focused on the value of OSPS to devs and the second focused on the value to downstream? This is something I can start in June if the group sees value in this.
Related - What would we think about 2 blogs, one focused on the value of OSPS to devs and the second focused on the value to downstream? This is something I can start in June if the group sees value in this.
We think this is a great idea. I just opened #318 and #319 for this and will assist in any way I can.