Hi all, We have a regular community meetings today at 18:00 UTC. Cya later today! Meeting Details Date: Thursday, August 26 Time: Meeting at 18:00 UTC Location: https://meet.opensuse.org/meeting <https://meet.opensuse.org/meeting> Etherpad: https://etherpad.opensuse.org/p/weeklymeeting20210826 <https://etherpad.opensuse.org/p/weeklymeeting20210821> Moderator: Doug Leader: Doug Supporters: attendees Topic: (Default Topic is completely a social meeting) software.o.o code.o.o membership processes TSP, wiki and use code.o.o to process A copy of the meeting notes will be sent to opensuse-project@opensuse.org <mailto:opensuse-project@opensuse.org> after the end of the meeting. We now have two meetings a week; a meeting 1 and meeting 2 option for people to join: Meeting 1: Meeting is on Tuesdays at 11:00 UTC (time was shifted from 13:00 UTC) Meeting 2: Meeting is on Thursday at 18:00 UTC v/r Doug
Hi all, Here are the meeting notes and link to the regular community meeting we had yesterday - https://etherpad.opensuse.org/p/weeklymeeting20210826 v/r Doug Topics being tracked: * software.o.o. proposal * connect.o.o and membership procedures * Move meeting to Tuesday or a Thursday * TSP with wiki and use code.o.o to process ## Presenter: ddemaio ## Participants: bittin, simon, martin, jens, Onuralp, g ### topics * software.o.o. proposal (no update) * Meeting 1 on Tuesday at 11:00 UTC and Meeting 2 on Thursday 18:00 UTC. Reasoning for the times of the meetings are to give people opportunties to attend where ever they might be globally * connect.o.o. affected * Need a new TSP process and need to change the wiki Can use code.o.o Code for the program before on connect was at https://github.com/openSUSE/travel-support-program * Membership repository is set up at https://code.opensuse.org/project/membership * Membership officials have the repository writes (Recommendation is to list your contributions in your https://en.opensuse.org/User: profile on the openSUSE wiki.) * Survey * Is for packagers and maintainers * Fine tune the questions * Planned for Sept. 20. * Will run for three weeks? Add note to hemisphere question explaining a bit more Will add notification about results being anonymized
Hello, Am Freitag, 27. August 2021, 07:39:44 CEST schrieb ddemaio:
* connect.o.o. affected
* Need a new TSP process and need to change the wiki
Can use code.o.o
Code for the program before on connect was at https://github.com/openSUSE/travel-support-program
I'm a bit surprised to read this. Traditionally TSP lived on the connect.o.o VM, but it's independent of it - and about a year ago, Sasi moved it to tsp.o.o (on a separate VM). Since then, connect.o.o/travel-support redirected to tsp.o.o. Unfortunately tsp.o.o is currently down [1], but once this is fixed, it will continue to work as usual. Therefore I wonder if we really want to replace TSP with tickets on code.o.o, or if you just weren't aware of tsp.o.o. (That said - I'm quite sure that nobody would complain about "one system and software less to maintain" ;-) Regards, Christian Boltz [1] https://progress.opensuse.org/issues/95668 (fixing it hasn't been a priority because currently all conferences are online) -- "DOS=HIGH ...I knew it was on something!" (UNIX user, while reading C:\CONFIG.SYS)
Thank you Christian, On 8/28/21 9:16 PM, Christian Boltz wrote:
Hello,
Am Freitag, 27. August 2021, 07:39:44 CEST schrieb ddemaio:
* connect.o.o. affected
* Need a new TSP process and need to change the wiki
Can use code.o.o
Code for the program before on connect was at https://github.com/openSUSE/travel-support-program I'm a bit surprised to read this.
Traditionally TSP lived on the connect.o.o VM, but it's independent of it - and about a year ago, Sasi moved it to tsp.o.o (on a separate VM). Since then, connect.o.o/travel-support redirected to tsp.o.o.
Unfortunately tsp.o.o is currently down [1], but once this is fixed, it will continue to work as usual.
Therefore I wonder if we really want to replace TSP with tickets on code.o.o, or if you just weren't aware of tsp.o.o.
(That said - I'm quite sure that nobody would complain about "one system and software less to maintain" ;-) I'll take a look at it once it's up. If it is working like before, I'll just update the wiki to reflect the change. v/r Doug
participants (2)
-
Christian Boltz -
ddemaio