GettingInvolved
2572
Comment: add link to SUP
|
3012
add information based on https://blueprints.launchpad.net/ubuntu/+spec/security-karmic-community-growth
|
Deletions are marked like this. | Additions are marked like this. |
Line 12: | Line 12: |
* hang out in #ubuntu-hardened on the Freenode IRC. | * hang out in #ubuntu-security (aka #ubuntu-hardened) on the Freenode IRC. * participate in IRC workshops on security during UbuntuDeveloperWeek |
Line 15: | Line 16: |
[[SecurityTeam/FAQ| FAQ]] items and [[SecurityTeam/KnowledgeBase| KnowledgeBase]] areas need to be written. See the [[SecurityTeam/Roadmap| Roadmap]] for details. | [[SecurityTeam/FAQ| FAQ]] items and [[SecurityTeam/KnowledgeBase|KnowledgeBase]] areas need to be written. See the [[SecurityTeam/Roadmap| Roadmap]] for details. |
Line 18: | Line 19: |
Testing the existing security features of Ubuntu can done to improve both documentation and to help find bugs. | Testing the existing security features of Ubuntu can done to improve both documentation and to help find bugs. You can also [[SecurityTeam/Specifications|test and participate in the development of new security features]] that are being developed. |
Line 27: | Line 28: |
Review open security bugs, find/write patches, build and test the fixes. Please see SecurityUpdateProcedures for details. | Review open security bugs, find/write patches, build and test the fixes. Providing patches for security vulnerabilities is an excellent way to learn about Ubuntu processes and develop the skills necessary to become an [[UbuntuDevelopment|Ubuntu developer]]. Please see [[SecurityTeam/UpdateProcedures|UpdateProcedures]] for details. |
Line 30: | Line 31: |
The Wishlist section of the [[SecurityTeam/Roadmap| Roadmap]] has many great ideas for new improvements to be made to Ubuntu's security. | The Wishlist section of the [[SecurityTeam/Roadmap|Roadmap]] has many great ideas for new improvements to be made to Ubuntu's security. |
What can I do to help ?
There are different areas where you can help the Ubuntu Security Team.
Help on the mailing list and the IRC channel
You can lend a hand with people's questions and problems on the mailing list and the IRC channel:
subscribe to ubuntu-hardened mailing list.
- hang out in #ubuntu-security (aka #ubuntu-hardened) on the Freenode IRC.
participate in IRC workshops on security during UbuntuDeveloperWeek
Write documentation
FAQ items and KnowledgeBase areas need to be written. See the Roadmap for details.
Test security features
Testing the existing security features of Ubuntu can done to improve both documentation and to help find bugs. You can also test and participate in the development of new security features that are being developed.
Find security bugs
Find new security issues in existing Ubuntu software.
Triage security bugs
Go through the list of security bugs in Ubuntu, and triage them.
Fix security bugs
Review open security bugs, find/write patches, build and test the fixes. Providing patches for security vulnerabilities is an excellent way to learn about Ubuntu processes and develop the skills necessary to become an Ubuntu developer. Please see UpdateProcedures for details.
Develop new security features
The Wishlist section of the Roadmap has many great ideas for new improvements to be made to Ubuntu's security.
How to become an member of the Ubuntu Security Team
The Ubuntu Security Team really consists of four sub-teams:
motu-swat: this team creates and tests security updates in Universe packages
- to become a member, help with Universe security updates for a while, and then get the approval of one of the team administrators.
ubuntu-hardened: this team develops and tests proactive security features in Ubuntu.
to become a member, just apply for membership
ubuntu-whitehat: this team is dedicated to "do not harm" while auditing and testing Ubuntu software and infrastructure, looking for new security issues
to become a member, see the UbuntuWhiteHat wiki pages.
ubuntu-security: this is a closed team responsible for performing security update publications
SecurityTeam/GettingInvolved (last edited 2022-01-05 18:30:02 by rodrigo-zaiden)