... | ... | @@ -56,7 +56,7 @@ |
|
|
- maybe teams that don't ship software need something other than the type of security policy used by the network team (e.g. what does a sec bug look like in network-health land)?
|
|
|
- nick explains the pain with the schleuder list bug intake (e.g. mostly encrypted spam)
|
|
|
- nick thinks we might want to use gitlab confidential issues more and make that flow nice
|
|
|
- there is a gitlab plugin for schleuder (BUT then we'd get the spam problem in gitlab)
|
|
|
- there is a [gitlab plugin for schleuder](https://0xacab.org/schleuder/schleuder-gitlab-ticketing/blob/master/README.md) (BUT then we'd get the spam problem in gitlab)
|
|
|
- could we require email submitted to schleuder list to be encrypted: no (although technically possible to enforce)
|
|
|
- many folks have a hard time to self-evaluate the severity of the issues they report
|
|
|
- there is sympathy for sunsetting schleuder list
|
... | ... | |