Clarify purpose of the policy #8894
Conversation
Changed the sentence about the purpose of the policy to say, "not to impose arbitrary restrictions" (added "arbitrary") because the policy does impose restrictions, but those restrictions are intended to protect Sourcegraph's assets, so are not arbitrary. It's a bit of a nit perhaps. Perhaps the "restrictions" clause should not even be included, and the purpose statement should just be "to protect Sourcegraph's assets".
✅ Deploy Preview for sourcegraph-handbook ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Hey there! It looks like this pull request has been sitting for a long time. Keep in mind that when you make a pull request, the change doesn't actually go live until you merge the pull request. This needs to be done by you (the pull request author) as soon as you feel like you got the appropriate amount of review/approvals that make you confident with the change. For example: adding yourself to the team page doesn't require anyone's review and you can merge directly, while when proposing a change to your team's processes you'll probably want to get your team's review (and need to request review from your team explicitly, so they get notified). Please see whether you want to merge this pull request, close it and discard the change, or remind the people you would like review from. You can find more help on our Editing the handbook handbook page. Thank you! \(^-^)/ |
|
Since there were no updates in the past 7 days, this pull request is being automatically closed. Thank you! \(^-^)/ |
Changed the sentence about the purpose of the policy to say, "not to impose arbitrary restrictions" (added "arbitrary") because the policy does impose restrictions, but those restrictions are intended to protect Sourcegraph's assets, so are not arbitrary. It's a bit of a nit perhaps.
Perhaps the "restrictions" clause should not even be included, and the purpose statement should just be "to protect Sourcegraph's assets".