Ben Cotton
Ben Cotton
@evankanderson can you please address Eddie's feedback?
I agree with the general direction, but we should resolve #403 first since that may obviate this discussion.
For context, I said in the Slack discussion: > we want to make it clear that people don't need to go back and retroactively fix archived projects The challenge that,...
I agree, which prompted #403. If we reject that, we should come back to this.
I don't think this is in scope for a security baseline, but we need to resolve #403 and then we can come back to this discussion.
> This is going to be true for nearly every project. For example, any contribution on GitHub requires this per https://docs.github.com/en/site-policy/github-terms/github-terms-of-service#6-contributions-under-repository-license and I expect other platforms to have similar language....
Is this still a thing, @eddie-knight?
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...
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...
> 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...