2024-07-16 RSAC Meeting notes

2024-07-16 RSAC Meeting notes

Date

Date

Date: Jul 16, 2024

Time:  6pm PDT | 9pm EDT |  03:00 CEST +1 |  09:00 UTC 08:00 +1

Join Zoom Meeting

Please subscribe to: https://lists.o-ran-sc.org/calendar (only there is the truth)

Goals

  • Define demo Details for O-RAN F2F in Montreal (Oct28 - Nov01)

  • Define requirements for O-RAN-SC

Discussion items

Time

Item

Who

Notes

Time

Item

Who

Notes

05min

admin

@Rittwik Jana 

  • @Martin Skorupski will be the new co-chair after @David Kinsey [AT&T] became co-chair of WG10 - in Martin's timezone it is now 3am, so he is not going to join the Tuesday meetings - but he sends "Greetings"

  • Next meetings

    • Tue 2024-07-16 9pm EDT by @Rittwik Jana 

    • Wed  2024-07-24 8am EDT by @Martin Skorupski    

    • Tue 2024-07-30 9pm EDT by @Rittwik Jana 

    • Wed  2024-08-07 8am EDT by @Martin Skorupski 

05min

O-RAN F2F demo

@Rittwik Jana 

Request to all PTLs

  • Please think about what are you going to demonstrate at the O-RAN F2F in Montreal Oct28 to Nov01.

  • We would like to understand how to structure the demo sessions.

  • Format does not matter much - content matters - live demo and/or recorded, with and with out slide set - you decide

  • Message to O-RAN: O-RAN-SC is alive and needs further support

SIM @Alex Stancu 

OAM @Martin Skorupski 

  • ...

  • Martin plans to be in Montreal, but it is not finally confirmed.

30min

Blockers - general discussion:

@Rittwik Jana 

  • SMO @Seshu Kumar Mudiganti 

    • Feature release is completed - is there a link?

  •  O-DU high @Ankit Barve 

10min

Software release procedure

@Martin Skorupski 

(maybe postponed to next week)

The importance of developer guides and software release processes:

  1. Clear structure process will reduce efforts in the code contribution process and will leads to world wide know and understood processes. This way, it is also easier to get contributions from developers any developer anywhere.

  2. Well defined process and pipelines will avoid adding problematic software artifacts into releases.

 

On the O-RAN-SC wiki we have some Developer guides, which the different teams should follow:


LF itself has nice pages and trainings:


Please have a look - and correct or make us aware of misleading or outdated statements. 

05min

gerrit clean up

@Martin Skorupski

 

https://gerrit.o-ran-sc.org/r/q/status:open,25

05min

Q/A

@all

  • if any

 

 

 

End of the meeting

 Action items

 Decisions

  • if any

References

  • if any