Security Interest Group - Activity in 2021
No matches.
GitHub
w3c/security-questionnaire
-
2 issues closed.
-
2.10 mis-spelled 'features' w3c/security-questionnaire#129.
-
Consider merging or retitling questions 2.1 and 2.8 w3c/security-questionnaire#97.
-
-
1 issue reopened.
-
Need a "How to Use This Questionnaire" section w3c/security-questionnaire#5, by @hober.
-
-
5 issues received 5 new comments.
-
Explain how groups should address issues raised by the questionnaire in their specs w3c/security-questionnaire#88 (1 comment by @pes10k)
-
Consider merging or retitling questions 2.1 and 2.8 w3c/security-questionnaire#97 (1 comment by @pes10k)
-
4 pull requests opened.
-
draft of clarity and concision pass on sections 2.1 through 2.5 w3c/security-questionnaire#136, by @pes10k.
-
revision pass of the abstract w3c/security-questionnaire#135, by @pes10k.
-
Add an acknowledgements section. w3c/security-questionnaire#134, by @hober.
-
Fix the build w3c/security-questionnaire#133, by @hober.
-
-
3 pull requests merged.
-
Fix the build w3c/security-questionnaire#133.
-
merge questions 2.1 and 2.8 w3c/security-questionnaire#100.
-
Rewrite intro w3c/security-questionnaire#131.
-
-
1 pull request closed.
-
revision pass of the abstract w3c/security-questionnaire#135.
-
-
3 pull requests received 8 new comments.
-
Add an acknowledgements section. w3c/security-questionnaire#134 (6 comments by @diracdeltas, @hober, @pes10k)
-
draft of clarity and concision pass on sections 2.1 through 2.5 w3c/security-questionnaire#136 (1 comment by @pes10k)
-
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
Contributors list? w3c/security-questionnaire#132, by @torgo.
-
GitHub
w3c/security-questionnaire
-
1 issue received 1 new comment.
-
1 pull request merged.
-
Add non-"fully active" document question w3c/security-questionnaire#128.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Rewrite intro w3c/security-questionnaire#131, by @samuelweiler.
-
-
1 pull request received 6 new comments.
-
Add non-"fully active" document question w3c/security-questionnaire#128 (6 comments by @ArthurSonzogni, @kenchris, @rakina)
-
GitHub
w3c/security-questionnaire
-
2 issues opened.
-
'Hidden' data question needed? w3c/security-questionnaire#130, by @dwsinger.
-
2.10 mis-spelled 'features' w3c/security-questionnaire#129, by @dwsinger.
-
-
2 issues closed.
-
Typo in "no known security impacts" boilerplate w3c/security-questionnaire#125.
-
2.9 (script loading) needs wrapper text w3c/security-questionnaire#104.
-
-
3 issues received 3 new comments.
-
Typo in "no known security impacts" boilerplate w3c/security-questionnaire#125 (1 comment by @hober)
-
1 pull request opened.
-
Add non-"fully active" document question w3c/security-questionnaire#128, by @rakina.
-
-
7 pull requests merged.
-
Bring questionnaire.markdown up to date w3c/security-questionnaire#121.
-
Update to Process 2020 w3c/security-questionnaire#120.
-
Correct a typographical error: feautures -> features. w3c/security-questionnaire#119.
-
Fix small typos w3c/security-questionnaire#118.
-
Revise question 2.7 for clarity. w3c/security-questionnaire#115.
-
First attempt at addressing #104. w3c/security-questionnaire#114.
-
Spelling: feautures w3c/security-questionnaire#127.
-
-
1 pull request reopened.
-
Bring questionnaire.markdown up to date w3c/security-questionnaire#121, by @hober.
-
-
4 pull requests received 6 new comments.
-
Add non-"fully active" document question w3c/security-questionnaire#128 (3 comments by @domenic, @hober, @rakina)
-
Correct a typographical error: feautures -> features. w3c/security-questionnaire#119 (1 comment by @tomayac)
-
GitHub
w3c/security-questionnaire
-
2 pull requests opened.
-
Spelling: feautures w3c/security-questionnaire#127, by @jyasskin.
-
Fixes typos of "features" w3c/security-questionnaire#126, by @Kangz.
-
-
1 pull request merged.
-
Fixes typos of "features" w3c/security-questionnaire#126.
-
-
1 pull request received 1 new comment.
GitHub
w3c/security-questionnaire
-
2 issues opened.
-
Typo in "no known security impacts" boilerplate w3c/security-questionnaire#125, by @scottaohara.
-
Mention (capability) negotiation? w3c/security-questionnaire#122, by @samuelweiler.
-
-
1 issue received 1 new comment.
-
Typo in "no known security impacts" boilerplate w3c/security-questionnaire#125 (1 comment by @scottaohara)
-
-
2 pull requests opened.
-
Minor fixes w3c/security-questionnaire#124, by @bialpio.
-
Minor changes to questionnaire.markdown w3c/security-questionnaire#123, by @bialpio.
-
-
1 pull request merged.
-
Minor fixes w3c/security-questionnaire#124.
-
-
1 pull request closed.
-
Minor changes to questionnaire.markdown w3c/security-questionnaire#123.
-
-
2 pull requests received 2 new comments.
GitHub
w3c/security-questionnaire
-
3 issues closed.
-
Rename master branch to main w3c/security-questionnaire#93.
-
2.16 (relaxed-sop) what are the bullet items? w3c/security-questionnaire#102.
-
Lessons from sharing URLs w3c/security-questionnaire#96.
-
-
3 issues received 3 new comments.
-
The current questionnaire is very browser-centric w3c/security-questionnaire#116 (1 comment by @dauwhe)
-
-
4 pull requests opened.
-
Bring questionnaire.markdown up to date w3c/security-questionnaire#121, by @alice.
-
Update to Process 2020 w3c/security-questionnaire#120, by @wseltzer.
-
Correct a typographical error: feautures -> features. w3c/security-questionnaire#119, by @jeremyroman.
-
Fix small typos w3c/security-questionnaire#118, by @chcunningham.
-
-
2 pull requests merged.
-
Revise 2.16 for clarity. Fixes #102. w3c/security-questionnaire#117.
-
New question: Does this specification allow an origin to send data to the underlying platform? Fixes #96. w3c/security-questionnaire#99.
-
-
2 pull requests received 6 new comments.
GitHub
w3c/security-questionnaire
-
1 issue opened.
-
The current questionnaire is very browser-centric w3c/security-questionnaire#116, by @atanassov.
-
-
1 issue received 3 new comments.
-
3 pull requests opened.
-
Revise 2.16 for clarity. Fixes #102. w3c/security-questionnaire#117, by @hober.
-
Revise question 2.7 for clarity. w3c/security-questionnaire#115, by @hober.
-
First attempt at addressing #104. w3c/security-questionnaire#114, by @cynthia.
-
-
3 pull requests received 9 new comments.
-
Revise 2.16 for clarity. Fixes #102. w3c/security-questionnaire#117 (4 comments by @atanassov, @pes10k)
-
New question: Does this specification allow an origin to send data to the underlying platform? Fixes #96. w3c/security-questionnaire#99 (4 comments by @hober, @martinthomson, @pes10k)
-