
On 4/4/24 12:39 PM, josef Reidinger wrote:
On Thu, 4 Apr 2024 09:01:08 +0100 Imobach González Sosa <igonzalezsosa@suse.com> wrote:
On Thu, Apr 04, 2024 at 09:30:36AM +0200, josef Reidinger wrote:
On Wed, 3 Apr 2024 11:51:21 +0200 Ancor Gonzalez Sosa <ancor@suse.de> wrote:
The call for papers closes in less than two weeks. Time to plan our presence there and submit all the abstracts.
Cheers.
Sounds good. I am thinking that we can have basically three talks there:
1. what is new in agama ( where we can say how project move from lat conference. Maybe we can do it together with two speakers and longer content ) 2. Agama in opensuse ( plan for using agama in opensuse, some introduction, some advantages and also possibly some discussion where we can show what agama can do and if opensuse users will find it useful ) 3. Agama and autoinstallation ( show what agama supports, show some use cases with examples and maybe mention also autoyast compatibility )
IMHO I think we could put all this content in a single presentation.
Regards, Imo
Well, for me advantage of having more presentations there is that
1. agama is more visible 2. if someone is interested in agama and has some presentation collision, he can see at least part of it 3. presentation can be shorter and more focused ( e.g. space for examples in autoinstallation one, or discussion in opensuse one ).
I'm not against having several sessions but I think I would do a different separation, asking the organization to respect the order between both sessions (not necessarily on the same day, just making sure session 1 happens first). Session 1. Demo. Little theoretical content. Focus on showing Agama in practice. Things we should explicitly show at the demo: - "Local interface" at Agama Live - Remote web interface relying on Avahi - Command line interface - HTTP interface - Capabilities to configure network - Capabilities to configure storage - Multi-product support, including a transactional one - Progress reporting through several interfaces (web, http, cmdline) Session 2. Agama vision and fit into openSUSE. Session to explain the status-quo and ask for feedback. Things we should cover - High level view. - A very quick recap for people who missed the demo (just screenshots and mentioning the features). - Explain the original goal is to be the installer for SLE-16 and SLE-for-SAP-16. Not sure if there will be a final decision regarding that by the time oSC'24 takes place. - Autoinstallation approach and AutoYaST compatibility. - Current Roadmap (not written in stone). - Agama in openSUSE. Intended to bootstrap a conversation. * What we are doing to support openSUSE. * Advantages if openSUSE adopts it. * Comparison to YaST. * What is missing for the openSUSE case. Including what we know is missing but also taking the opportunity to ask the audience. That's my proposal but, in any case, it would be more productive to discuss the options in a short video-call. Deadline for call for papers is in 5 days. Cheers. -- Ancor González Sosa YaST Team at SUSE Software Solutions