Mykola Krachkovsky composed on 2020-02-15 11:38 (UTC+0200):

I know that it's known bug about openSUSE bugzilla site unresponsiveness which AFAIK linked to servers where bugzilla is located. But can't we really do anything with this? Maybe with some help of community.

I've created bug report only now,

I don't see it. Where and when did you file it? What number is it?

though problem exists at least for 2 weeks, because when I try to do a search I don't get a result, but ERR_CONNECTION_RESET instead. I've made search today 3 times before error-free result, though I still not sure I haven't created duplicate,

https://bugzilla.opensuse.org/show_bug.cgi?id=1100506 is approaching 2 years old yet has had no activity from anyone but me and the screening team.

because I had issues with previous bug reports when I got empty search results while there were bugs with matching description and searching later showed them. -- Evolution as taught in public schools is religion, not science.

Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

This IT (web hosting) problem was mentioned here when we talked about what are the plans for 15.2 and opensuse.org website in general. If I remember correctly, opensuse.org is hosted by/at Microfocus datacent somewhere in Provo, UT. SuSE and openSuse has no access to it and IT tickets are not being answered. There was some talk of releasing that HW/SW access to SuSE at some point. It has probably been forgotten or .... While it was not said, based on my corporate experience, I would dare to guess that there is some unsurmountable obstacle in getting this done. Perhaps it is ownership problem or the fact that Microfocus does not see reason to do anything about it after SuSE spin off.... Tomas On Sat, 2020-02-15 at 16:25 +0000, Dave Howorth wrote:

On Sat, 15 Feb 2020 11:10:02 -0500 Felix Miata wrote:

...

Mykola Krachkovsky composed on 2020-02-15 11:38 (UTC+0200):

...

I know that it's known bug about openSUSE bugzilla site unresponsiveness which AFAIK linked to servers where bugzilla is located. But can't we really do anything with this? Maybe with some help of community. I've created bug report only now,

I don't see it. Where and when did you file it? What number is it?

...

though problem exists at least for 2 weeks, because when I try to do a search I don't get a result, but ERR_CONNECTION_RESET instead. I've made search today 3 times before error-free result, though I still not sure I haven't created duplicate,

https://bugzilla.opensuse.org/show_bug.cgi?id=1100506 is approaching 2 years old yet has had no activity from anyone but me and the screening team.

Well I just tested and confirmed the problem. Maybe that will result in some action? ...

...

...

because I had issues with previous bug reports when I got empty search results while there were bugs with matching description and searching later showed them.

-- To unsubscribe, e-mail: opensuse-support+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-support+owner@opensuse.org

неділя, 16 лютого 2020 р. 01:04:28 EET tomas.kuchta.lists@gmail.com написано:

This IT (web hosting) problem was mentioned here when we talked about what are the plans for 15.2 and opensuse.org website in general.

If I remember correctly, opensuse.org is hosted by/at Microfocus datacent somewhere in Provo, UT. SuSE and openSuse has no access to it and IT tickets are not being answered. There was some talk of releasing that HW/SW access to SuSE at some point. It has probably been forgotten or ....

While it was not said, based on my corporate experience, I would dare to guess that there is some unsurmountable obstacle in getting this done. Perhaps it is ownership problem or the fact that Microfocus does not see reason to do anything about it after SuSE spin off....

Tomas

Yes, but maybe something could be done? If server could be moved somewhere else, maybe do it with some help of community (fundraising or some other help). Or if server couldn't be moved (due to policy or other reasons) and problem is linked to heavy load of bugzilla server, create something like mirror(s) for searching. Just stupid ideas. But this problem persists for quite a time. -- Kind regards, Mykola Krachkovsky -- Найкращі побажання, Микола Крачковський

Hi All I meant to reply to this the other day, there are some changes happening. On 2/17/20 8:58 AM, tomas.kuchta.lists@gmail.com wrote:

On Sun, 2020-02-16 at 14:06 +0200, Mykola Krachkovsky wrote:

...

неділя, 16 лютого 2020 р. 01:04:28 EET tomas.kuchta.lists@gmail.com написано:

...

This IT (web hosting) problem was mentioned here when we talked about what are the plans for 15.2 and opensuse.org website in general.

If I remember correctly, opensuse.org is hosted by/at Microfocus datacent somewhere in Provo, UT. SuSE and openSuse has no access to it and IT tickets are not being answered. There was some talk of releasing that HW/SW access to SuSE at some point. It has probably been forgotten or ....

While it was not said, based on my corporate experience, I would dare to guess that there is some unsurmountable obstacle in getting this done. Perhaps it is ownership problem or the fact that Microfocus does not see reason to do anything about it after SuSE spin off....

Tomas

Yes, but maybe something could be done? If server could be moved somewhere else, maybe do it with some help of community (fundraising or some other help).

Or if server couldn't be moved (due to policy or other reasons) and problem is linked to heavy load of bugzilla server, create something like mirror(s) for searching.

Just stupid ideas. But this problem persists for quite a time.

I agree that it should be possible and relatively easy to do - fix/improve project's web presence - these days - with relatively small stable funding and core volunteers.

Under the surface of openSuSE open source project appearance - this maybe really, really, really difficult though.

----Disclaimer---- I have no affiliation with SuSE and no first hand knowledge of inner-workings of SuSE or openSuSE. I have been fan/user personal and corporate for over 20 years now - that is my only connection. So, please take my opinions with healthy measure of critical scrutiny. I do have practical experience with running corporate IT and a cultural charity in my past. ----End - Disclaimer----

It seems to me that openSuSE, for better or worse, is coupled with SuSE development and needs. That, in my opinion, is not necessarily bad, but over time this leaked out many external people from the general openSuSE community. Perhaps to this point where there is very weak community driven agenda/voice.

Yeah as someone who does work on both sides this is certainly true, Leap shares so much code with SUSE products and SUSE products use so much code from tumbleweed that having a joint bugtracker really makes sense.

On the openSuSE infrastructure side, again, for better or worse, the community cannot really participate with resources ($$/expertise). This is because from accounting, corporate and legal point of view openSuSE == SuSE. Corporations cannot freely take gifts without contracts, setup corporate backed community web/infrastructure without liability. All the corporate governance responsibilities makes any true community driven IT activities difficult and costly to SuSE. This is somewhat true, int hat legally openSUSE can't do anything there is ongoing work to setup a foundation which would somewhat change this. Having said that, there are some parts of openSUSE's IT infra that have been opened up to the community via the Heroes.

In my opinion, the biggest obstacle to the true community driven openSuSE, with or without SuSE's backing - is the projects name an ownership - if openSuSE, as a community, makes mistakes or just diverges too much from SuSE - it might affect SuSE brand. That is perhaps why RedHat --> Fedora/CentOS, Cannonical --> Ubuntu are separated by name and by their own legal entities - albeitsuccessfully sponsored/influenced by the need of their backer.

This is certainly one of the challenges the board is working through with SUSE in terms of setting up a foundation. Now onto the changes that are actually happening and will be visible soon. openSUSE's bugzilla instance along with being shared with SUSE is also shared with a number of other parts of what is now Microfocus (was Novell). This is the main reason why our current bugzilla instance is up over 1 million tickets. As SUSE is separating from Microfocus the bugzilla instance will be recreated inside SUSE's network (as opposed to where it currently is within Microfocus) as a part of that all the tickets from Microfocus / Novell products will be dropped and hopefully this will speed up things like the search. If there are still issues with speed of searches then it will also be easier for us to talk to SUSE about adding faster hardware. Cheers Simon -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B