On 2/21/19 2:23 PM, Vincent Untz wrote:
This isn't the first time I've asked this question on a public stage, but in the hope that this time I get an answer; Who volunteers to tackle the problem with connect.o.o and drive forward a solution?
I would give this request a deadline of a week or two max, and then simply export the data and shut down connect.o.o.
Just a technical side note. The Travel Support Program application would need to be tweaked to stop getting some profile information from connect.o.o and start asking for that information directly (it's just a configuration value). https://connect.opensuse.org/travel-support On the other hand, it actually lives in the same server right now. Just take that into account if "shut down connect.o.o" means shutting down the server itself. In short, connect.o.o and TSP app are independent applications, but are hosted together and occasionally talk to each other (although that's optional). Just take that into account. Cheers. -- Ancor González Sosa YaST Team at SUSE Linux GmbH -- To unsubscribe, e-mail: opensuse-project+unsubscribe@opensuse.org To contact the owner, email: opensuse-project+owner@opensuse.org