Richard Brown wrote:
On Thu, 6 Sep 2018 at 16:22, Per Jessen email@example.com wrote:
- Are we going to deal with all the other teams like this as
well? I.e. Are the forums team going 100% transparent? Can all the mod area discussions be anonimized and publised? Same for the other teams?
If those teams are elected or appointed by the community, in principle I think we ought to.
What does the election or appointment have to do with it? The other teams in the Project are also doing things on your behalf.
I think being elected or appointed makes a significant difference compared to having more or less accidentally joined a team. I (as an arbitrary community member) did not choose/elect/appoint e.g. the forums team nor do I, to my knowledge, have any influence on it's composition. A select do-ocracy. Much like the openSUSE Heroes.
Why should privacy of decision-making be afforded to those who undemocratically declare themselves a certain function in our Project? Why can you change any thing in this project without needing to proactively explain the thoughts and reasons that led you to make that change, but the Board not?
Permit me to reply with a question - you don't see the Board taking up a special position, the board is just a team, as any other?
If the Board isn't special, why is the Board elected? If the Board is special, why should the Board not be subject to different rules?
Why are all openSUSE infra tickets private by default?
I believe the reason is that they might contain sensitive information.
Why aren't the logs of every thing you type on every openSUSE server public record? Why can't I see the configuration of this mailinglist server?
Isn't it because that if all of that information was public, it would increase the risk we have to the servers that you are administering? That's a perfectly reasonable explanation to me.
Something like that. It's the usual Linux/Unix security model.
More people with that knowledge means more potential for malevolent individuals to make use of that information to disrupt the Project.
In theory. (in practice anyone is welcome to see the root command history logs as well as the mlmmj configuration).
Given the responsibility [the Heroes] have, and the nature of the internet if everything was public by default, I believe the Heroes decision to do things private by default, while opening as much information as they can, when they can (often after the incident is relevant), is a fair philosophy to follow.
Just so we are on the same page - this _only_ applies to the ticketing system. As we cannot dictate to a user what to share with us, it is a fail-safe in case a user decides to add passwords etc.
With that one exception, the Heroes did not decide "to do things private by default", that is simply how our systems, i.e. openSUSE, work.
If all of our votes were public, the elected members of the Board who are also SUSE employees could find themselves in a very awkward position, being required to publicly go on record against their employer.
I thought it was quite clear by now that no one is asking for _every_ vote or decision to be made public, automagically? Just enable more transparency by encouraging/enabling votes to be made public, in particular if asked for or if a board member feels it is right.