security:meetings:18022015
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
security:meetings:18022015 [2015/02/19 11:08] Luke Hinds |
security:meetings:18022015 [2015/02/25 15:49] (current) Luke Hinds |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== Security Group 11/02/2015 ====== | + | ====== Please help move this page ====== |
| + | * NOTE: Meeting info pages for each project should be moved to the ''[[/meetings/|https://wiki.opnfv.org/meetings/]]'' folder. | ||
| + | * Do not place meeting related pages under the ''/wiki'' or ''/project-name'' folders. | ||
| + | * To move your page you should create a new page and update this one with a note stating it has been moved. | ||
| + | * The IRC channel for meetings is #opnfv-meetings. Each project should still use their own IRC channel for daily project communications but during a meeting it's important to share the main channel. This helps ensure meetings stop and start on time. | ||
| + | |||
| + | |||
| + | ---- | ||
| + | ====== Security Group 18/02/2015 ====== | ||
| Line 23: | Line 31: | ||
| **Scope discussion** | **Scope discussion** | ||
| - | * For the **mailing linst** we agreed we will remain on opnfv-tech-discuss and use subject tag [opnfv-sec], until the mail volume is sufficient to justify the need for a dedicated list. | + | * For the **mailing list** we agreed we will remain on opnfv-tech-discuss and use subject tag [opnfv-sec], until the mail volume is sufficient to justify the need for a dedicated list. |
| * We agreed we will establish an **advisory / vulnerability handling** process | * We agreed we will establish an **advisory / vulnerability handling** process | ||
| * We agreed we need to **interwork with other security groups** - other members should ideally be present on all upstream groups | * We agreed we need to **interwork with other security groups** - other members should ideally be present on all upstream groups | ||
| Line 29: | Line 37: | ||
| * We agreed on **Internal OPNFV Security Best Practices**. This will cover two areas; Internal Security polices such as password complexity, encryption etc. The other area will be to establish secure coding guidelines for opnfv projects. | * We agreed on **Internal OPNFV Security Best Practices**. This will cover two areas; Internal Security polices such as password complexity, encryption etc. The other area will be to establish secure coding guidelines for opnfv projects. | ||
| * We agreed **Security Change Reviews (gerrit)** | * We agreed **Security Change Reviews (gerrit)** | ||
| - | * We agreed **Research and Development** and emphasis was made on insuring we support the spawning of sub-projects. | + | * We agreed **Research and Development** and emphasis was made on ensuring we support the spawning of sub-projects. |
| **Actions** | **Actions** | ||
security/meetings/18022015.1424344110.txt.gz · Last modified: 2015/02/19 11:08 by Luke Hinds
Page Tools
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
