Security Policy: update technologies used

Update based on the use of the GitLab tracker instead of Bugzilla. Additional clarifications and explanations.

Signed-off-by: Marta Rybczynska marta.rybczynska@eclipse-foundation.org

requested review from @mbarbero

added 1 commit

• 1814cf4a - Security Policy: update technologies used

Compare with previous version

resolved all threads

Updated. @netomi another pair of eyes would be helpful :)

requested review from @netomi

requested review from @wbeaton

The security policy is a board approved document, so you'll need to get board approval before you can post any changes to the policy.

My recommendation is that you split these changes. Board approval is not required for the index page.

Here's the fun part... to get board approval, you'll be asked to provide a "redline" diff of the changes. I've had success with htmldiff. I can help. I usually provide a paragraph or two describing the changes as well.

Once you have the materials, contact Gesine and ask her to add it to the board agenda.

I'll take a harder look at the content later today.

The security policy is a board approved document, so you'll need to get board approval before you can post any changes to the policy.

That was not my understanding . The security policy is not mentioned anywhere in the bylaws. Am I missing something?

Mine neither.. @wbeaton I do have corresponding Handbook changes too. You might be interested to have a look at that too.

ok, actually @wbeaton already told me about it last Sept, but it seems that I keep forgetting about it . So we can freely change https://www.eclipse.org/security/ but https://www.eclipse.org/security/policy.php requires board approval.

@mrybczyn, would you mind splitting the changes for the the 2 files? IMO, the policy.php file actually contains only minor changes, so it's not too bad if it takes longer to have it approved by the board.

@mbarbero easy. What about the Handbook? This one we can change freely?

Split the commit. Now we have only index changes

@mbarbero easy. What about the Handbook? This one we can change freely?

Yes, handbook can be changed without board approval.

added 1 commit

• 61a6f787 - Security page: update technologies used

Compare with previous version

approved this merge request

mentioned in commit 7b052b32

merged