blob: 56c2de5b41d4fe6b0e4e2a7d84116d1b5a46ec43 (
plain) (
blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
|
Agenda for Security Team Meeting
Workflow
========
- Opening up the security process further to allow maintainers of packages with
frequent issues to release updates themselves
- Updates need to be reviewed/acked by sec team members
- Requires changes to dak to no longer require access to security-master, e.g.
by using a mechanism similar to allowing a DM to upload and sendingk error
messages to the signer of the upload (already requested by Thijs)
- Requires changes to debian-security-announce
- Is dsa-needed an improvement? What shall we do with embargoed issues?
- Ditch RT?
- Draft new people, possible candidates
Archive tools
=============
- Compile a list of issues we want to see fixed
- Do we really need the embargo queue? This would simplify dak/FTP situations immensely.
Tracker
=======
- Add a new status to differentiate between "no-dsa, if the maintainer wants
to fix in a point update go ahead" and "no-dsa, was ignored because it's
possible to backport".
- Automatic weekly status on open issues sent to maintainers (catches
issues which fell through the cracks, like CVE-2013-2236)
- Check open bugs in the BTS, check bugs against security-tracker pseudo package
- Migrate to git?
Documentation
=============
- Work on proper documentation how people can contribute
Others
======
- d-d-a mail for file collecting willing testers for exotic setups
- Compile a list of test instructions for key packages
LTS
===
- Setup and organisation
- Gather a specific list of people interested in contributing (e.g. credative already stepped forward)
|
