Christian Boltz wrote:

FYI: at the moment, we have exactly 300 open admin tickets, and the oldest open ticket is 3 years old :-( Needless to say that I don't like this state ;-)

Do those 300 include all the spam? Initially I closed some of those, but it was suggested I also delete the auto-created account, which my access doesn't permit.

Christian Boltz

[1] especially for people like me who refuse to create a facebook account ;-)

You've got my vote. -- Per Jessen, Zürich (1.0°C) http://www.cloudsuisse.com/ - your owncloud, hosted in Switzerland. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On 7 February 2017 at 19:24, Lars Vogdt wrote:

Hi Richard

On Mon, 6 Feb 2017 16:15:18 +0100 Richard Brown wrote:

...

issues with connect.opensuse.org that caused the cancellation of the openSUSE elections

Here we have a problem: the host and services are up and running from an "openSUSE Hero" perspective.

There is no - and there will never be a - way that "general" Admins, who take care about the operating system on those machines, will take over the application development/maintenance. This is the *job* of those people who volunteered to maintain this application [1].

Funny to say that the Heroes asked the board (again) during their first meeting[2] what to do with connect.o.o, as this service seems not to be actively maintained any more. I'm a bit sad to see that now the board tries to blame the Heroes for something they have no control over.

with kind regards, Lars

The Board chose its words carefully in the minutes, but allow me to say the following explicitly - we do not blame the openSUSE Heroes for the current situation. By 'openSUSE Heroes' I refer to both those volunteers who are not employees by SUSE, and those who are. We greatly appreciate all of the work they do, and do not feel the current situation reflects badly on the work they've been doing. But regardless of that excellent work, the status quo is not acceptable. In the case of connect.o.o, the Heroes threat of shutting down the Projects members database & voting platform is unacceptable given it is a key part of the Projects infrastructure - the Project as it is currently founded cannot function without it, just as it couldn't function without OBS. Who created the server in the past, who was responsible, is immaterial, the server exists, the project needs it, and we need to find a solution to it. And we need that solution by 3 weeks ago because we should have a new Board by now. It is from this position we are discussing the situation with SUSE Management, in the hope that they can provide help & resources to alter that status quo, regarding connect and all of the other infrastructure problems we are currently facing. with kind regards, Richard -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org

On 8 February 2017 at 16:40, Henne Vogelsang wrote:

Hey,

On 08.02.2017 15:54, Richard Brown wrote:

...

It is from this position we are discussing the situation with SUSE Management, in the hope that they can provide help & resources to alter that status quo, regarding connect and all of the other infrastructure problems we are currently facing.

So paid SUSE employees to the rescue. I must say I'm rather disappointed that this is the only solution that we as a community can come up with after ignoring this situation for years...

With the exception of connect.opensuse.org, the vast majority of the burning infrastructure issues are with infrastructure which community volunteers are in no position to help. It's also worth noting that connect was originally set up by SUSE employees, introduced to the Project as a key part of infrastructure, and then circumstances within SUSE changed leading to connect becoming somewhat of an orphan. I think I can be justified in saying that it's handover from a SUSE-administered service to a community-administered one was not handled correctly (or not handled at all, depending on your point of view). I do not think you can justifiably say that the community 'ignored' the situation, nor do I agree with your implication that the community needed to be the only one owning the problem. Regardless, we have more on our plate when it comes to openSUSE than just connect.o.o. The wiki problems from last year remain unresolved. news.opensuse.org was hacked at the weekend. Both remain fully in the Micro Focus sphere of control, despite a long time of lobbying to change that. This means currently SUSE employees are also near powerless to help, and involving community admins is even more unfeasible. The outstanding issues regarding download performance and mirrors might be something our community Heroes can deal with, but the training, access granting and onboarding for such systems cannot be expected to happen overnight. Tickets reporting these problems are many months old, long before the openSUSE Heroes team was even announced. Meanwhile SUSE employees have the knowledge, expertise, and access as they were the ones who set up such core services in the first place. The best way through this mess is one that involves contributions from both the community AND SUSE. That's what we work towards, but it requires enablement, effort and remedial work from those who currently control the reigns and who have held those responsibilities for years. If that disappoints you, too bad. -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org