As pointed out to me by Daniel Robbins, the final line of our social contract (https://www.gentoo.org/main/en/contract.xml) adds an exception to the open-bugs policy for devrel and security issues. Here's the line: "Exceptions are made when we receive security-related or developer relations information with the request not to publicize before a certain deadline." The problem is that the date deadline should only apply to security issues, while devrel-type stuff should be able to stay closed. Secondarily, s/devrel/comrel/. Suggested fix: "Exceptions are made when we receive community-relations information or security-related information with the request not to publicize before a certain deadline."
Ideally, it would be good to delineate exactly what types of bugs will be hidden by comrel, and for what reason(s). This keeps things transparent. Such as: "Exceptions will be made for: 1) Security-related information, where there is a valid reason to not publicize the content of the bug. 2) Bugs that violate Community Relations standards, such as those that contain inappropriate or offensive content or copyright violations. An itemized list is best -- easier to read.
Added to the Jan 18 trustee meeting; https://wiki.gentoo.org/wiki/Foundation:Gentoo_Foundation_2015_Jan_Agenda
(In reply to Daniel Robbins from comment #1) > An itemized list is best -- easier to read. I'm not keen on an itemised list, we are bound to leave something off. Think of "What did the Romans ever do for us?" in the Life of Brian. I could go with closed bugs will be as approved by the trustees on a case by case basis but that means that all bugs need need to be able to be reviewed by the trustees, which is not the case at the moment. I could even go an itemised list with the above as a 'catch all' the ones we forgot about. Thu Trustees are after all the guardians of the Social Contract.
IMHO community relations bugs and any interactions should only be made private at the request of the involved party. I am not a fan of such matters being private. I have seen community relations given out information that support their actions. Which limits anyone's scope who is reviewing the matter. Rather than letting them form their own opinion based on all the facts. They are only able to see a subset. I think Daniel Robbins may feel differently about this based on his recent 7 day ban bug 652240. What if all that was made private? He would not be able to make his case in public. He would just be silenced by others, and that is it. Look at my bug, all information there is pretty defaming to my publicly.https://bugs.gentoo.org/135927 Why is this hidden? All others against me are open... https://bugs.gentoo.org/618254 Would be interesting to hear Daniels comments on the matter... What if his current 7 day ban bug was closed?
Not that people would like it, but this is my suggestion, it means that we'd have to approve the hiding of bugs, which is extra work, but like Roy said, we are the guardians of the social contract. :| New We will not hide problems We will keep our bug report database open for public view at all times; reports that users file online will immediately become visible to others. Exceptions may be made at the discretion of the Trustees. old We will not hide problems We will keep our bug report database open for public view at all times; reports that users file online will immediately become visible to others. Exceptions are made when we receive security-related or developer relations information with the request not to publicize before a certain deadline.
(In reply to Matthew Thode ( prometheanfire ) from comment #5) > Not that people would like it, but this is my suggestion, it means that we'd > have to approve the hiding of bugs, which is extra work, but like Roy said, > we are the guardians of the social contract. :| > > New > > > We will not hide problems > > We will keep our bug report database open for public view at all times; > reports that users file online will immediately become visible to others. > > Exceptions may be made at the discretion of the Trustees. We accepted this wording in the 201809 board meeting. > > > > > old > > > > > We will not hide problems > > We will keep our bug report database open for public view at all times; > reports that users file online will immediately become visible to others. > > Exceptions are made when we receive security-related or developer relations > information with the request not to publicize before a certain deadline.
b48c80802f82ed82878b19a924752b050d5f3330 updates the social contract. -A
