Am Mon, 15 Mar 2021 18:07:59 +0100
schrieb Sasi Olin <hellcp(a)opensuse.org>rg>:
* Are the
maintainers of Gitlab and Progress aware of this?
Progress yes, we only discussed Gitlab in passing, so there I'm not
Gitlab is mainly internal only because we were not sure in the beginning
if we might end up storing passwords in Salt (and therefor the git
repository of Salt).
Right now we use "pass" to store GPG encrypted passwords and Gitlab's
permissions only allow members of the right group to see them or check
I'm not 100% sure if we really want to provide another "code hosting"
platform without a real need - but (just in case) maybe we can also
consider to make Gitlab public?
Or is it already set in stone that openSUSE is using Pagure now?
In that case, I would love to see us getting rid of Gitlab. But I don't
know Pagure good enough to finally make this decision. Is there any
difference between Gitlab and Pagure?
* Is there a
If this means manual work/migration, this would be a blocker for
Gitlab -> Pagure might not be that problematic, but at least for
Redmine, this would be a no-go.
* Is there a
timeline that people can rely on?
Until we have CI, we can't migrate most things, while others are
already being migrated. Timeline would require us to have a solid
idea of when CI will be set up though.
Well: firing up a Jenkins installation is not really rocket science. ;-)
But: maintaining it and keeping it secure is a completely different
story, I agree.
Of course the problem being, we didn't really
create issues for
migration, so nobody knows what to actually do. Probably a mistake on
Not a big deal. Can I ask you to create some issues for the stuff on
your agenda? - Looks like at least I lost track of it.
other areas (just out of nowhere):
* Wiki.o.o upgrade
* integrating mlmmj archives in mailman 3
* upgrading Elections.o.o
* prepare failover setups (next NUE downtime... ;-)
* cleanup tickets on progress.o.o
I just want to avoid that we waste someones spare time to work on
things that are planned to get obsolete...
That's totally understandable
Jip, especially as I'm still waiting for:
* new FreeIPA (#64162 ?, #88433)
* new DNS, incl. easy management GUI (#88433)
* fixing tsp (#89647)
* 100% reliable Matrix (#63463, #88279, #88497, ...)
* forums migration to discourse (#88433)
* re-enabling nntp for forums (#47015)
* finalizing mailman 3 migration (#19900, #80900, ...)
* deprecation of community.o.o (#70264, #63466)
* replacement of account system (#64159)
* handling meet.o.o problems (#89575, #66173)
* adding a calendar for openSUSE events (#88457)
* setting up BigBlueButton (#75268)
* adjusting login.template (#68512)
* fixing susepaste (#56189)
* fixing survey.o.o (#80454)
* fixing osc-collab (#69568)
* fixing news.o.o (#67222)
* fixing Weblate auth (#89857, #73411, #69424)
* updating MediaWiki (#61104)
* updating ElasticSearch (#62672)
* migration of openSUSE domains (#88433, #88520)
* enabling DCIM and DNSSec (#88433 + boo#690867)
* Scripts to delete/disable users as requested by GDPR
* additional documentation and training material
* someone fixing the remaining *285* open Redmine issues
Sorry to sound a bit unfair, but I have to admit that I am surprised
that there are currently so many new (interesting) fields of action,
while we still lack the manpower to work on all the existing problems.
I know that working on that "old, rotten stuff" is not always so much
fun and often enough even nerve-wracking, but this is what makes people
think the openSUSE heroes are non-functional/not-productive, as they are
not even able to handle their (community/user) issues in a timely
Couldn't we agree to solve at least some of the problems listed above,
first, before you start turning the openSUSE infrastructure inside out?
With kind regards,