Dear @szopin, please keep the tone of this conversation non-personal. I would like to get the thread back on track, get replies from Jolla and clearly understand what is going on with the infrastructure. Unfortunately, your messages are filling several pages already and it is hard to get to something constructive in them.
Please, calm down and consider deleting the messages that are not contributing to the discussion on the topic.
What I said is āsignificant contributorā
Indeed, sorry about that, apparently g7 is a major contributor, Iām not sure what way of PNGing his contributions from github will be ānon-sidedā by you, but it seems like 10-15 lines of code in the last 3 months, not a main contributor to any of sfos packages, pls correct me if Iām wrong, he might be a cool guy and an awesome contributor, but neither a huge contributor for sfos, nor a BIG GUY FOR YOU. The guy ārunning away from Jollaās latest acknowledgementā is neither big, nor interesting.
@rinigus This is neither personal, or non-personal, kabouik is selling a lot of shit that is not personal while he pretends to be the āsellerā, heās not, if you think pretending like this is OK, cool, but I do not avow
Perhaps this could be some reasons why Jolla is moving away from OBS:
https://specs.openstack.org/openstack/fuel-specs/specs/7.0/replace-obs.html
As far as I understood, the reason for OBS removal is primarily legal. People are uploading whatever and Jolla may be held responsible for hosting illegal content or something along those lines. You canāt beat that sort of argument 
IMO it should stay around at least to allow outside developers to make reproducible builds of their Jolla Store apps. I donāt think my opinion weighs much, thoughā¦
@slava, I presume it is not an official reply and from your response it sounds like the reasoning was not fully discussed in house among Jolla developers.
I am not aware of anyone pushing something illegal at OBS. I presume we are talking about Android binary blobs here. Or anything else?
Again, if it is for legal reasons, those have to be stated and not plastered over by something irrelevant. When we get the reasons behind considering closure of OBS, we can start the discussion regarding it and how to find the solution that would work for the all parties involved.
Just conspiracy theory: Last year I saw increased amount of attacks to build environments and other internal systems in various technology companies. When such attack is successful, you have to shut down such environment and donāt release details until investigation ends.
Iāve created a separate topic of the OBS shut down and next steps Iāve tried to describe the rationale behind the decision. Please use that thread for ideas, questions and discussion related to this topic.
The mer wiki (https://wiki.merproject.org) also seems to be regularly down. Is this also because of this change? Parts of the merwiki contained useful information, such as the current community adaptations, information about how Spectacle works and such.
If this is related to this topic, are there plans to make the content of the wiki available once again, albeit on its original location or somewhere else?
wow, wiki with https://wiki.merproject.org/wiki/Adaptations/libhybris table was really shut down? Are youā¦? Canāt believe this.
Thereās just a problem with the disks on the machine hosting the wiki. Iāll try and get it back up ASAP.
aaaaand itās back up
Thereās a typo in your link - the word āprojectā should have an ārā in it. So donāt be surprised if the site seems to be down if you try to follow your link 
Is there some time plan for migration to https://github.com/sailfishos ? I would like to send some patches to connman, but I donāt have account at git.sailfishos.orgā¦
You can ask @lbt on IRC (#mer or #sailfishos on Freenode) if you would like to have one there.
I donāt think we have any time plan for the migration - please donāt wait for that to happen if you have patches to send.
please donāt wait for that to happen if you have patches to send.
Well, in the past that did not make any difference.
In hope that this may have changed (you tend to sound so authentically enthusiastic @vige), as one example, see GitHub - sailfishos/udisks2 with a few issues and MRs nobody ever reacted to (I would have to look up what else I filed where).
Have you pinged the developers? Itās quite possible that no one has noticed your MRs, that happens quite easily with gitlab.
@vige, no. How? Why?
Gitlab emits emails to the maintainers on every new MR or issue.
The way I usually do it: Look at the git logs, see who has been making most of the commits lately. Ask them to review.
I can think of at least two reasons why this does not work in practise: 1) When you get ~50 emails daily from various git repositories, itās quite easy to miss the actually important one. 2) There usually isnāt only one person who maintains a single repository. When there are several people doing it, itās quite easy to think that someone else will take care of this MR.
@vige, trying to express my point better:
Jolla obviously has or deliberately created a big structural issue here (since SailfishOSā beginnings):
As you point out, Jolla is apparently deaf for bugs reported over conventional channels, which exist for this very purpose: reporting bugs.
If somebody denotes that, Jollaās usual reaction is to single-out that person and issue, by requesting to jump to further hoops:
Jolla is systematically and consistently shrugging people off by this mindset and course of actions.
Still new people (like you) sailors are usually replicating this behaviour right from their start at Jolla, so it looks like they are internally primed to act so.
One only wonders, what the purpose of Jollaās public beta programme (āSailfish Xā) really is, if not testing and gathering feedback?
P.S.: I once modelled, that our testing and reporting is used by Jolla for enhancing SailfishOS to become more appealing for big licensees, but Jolla never seems to have utilised it this way.
Fact is, that Jolla deliberately leaves many resources and much energy untapped, due to this very non-integrative testing and development process.
P.P.S.: @vige, while rereading your reply for a third time, I realise, that your central statement is: āJolla has (developed) no working processes for bug reports and MRs, yet.ā
While this understanding may be the basis for designing a change for the better (after more than 7 years, but ābetter late than neverā), you really do not sound like this is ever going to happen (rather the opposite).