PCM Development/Palladio Concall/Minutes 20230711

Aus SDQ-Wiki

Participants

  • Martina Rapp-Sieger
  • Nicolas Boltz
  • Maximilian Walter
  • Steffen Becker
  • Floriment Klinaku
  • Sebastian Weber
  • Sebastian Hahner
  • Larissa Schmid
  • Snigdha Singh
  • Yves Kirschner
  • Frederik Reiche


Standup

  • Nicolas, Larissa
    • Built, supported by research assistance, new version of pipeline etc.
    • Preparation SSP and Palladio Dev Meeting
  • Maximilian: Not much done, writing thesis, written tool paper for Dataflow analysis
  • Freddy: nothing done
  • Yves: did nothing palladio community related, but diss palladio stuff
  • Snigdha: Not mutch done
  • Sebastian W.: fixed the palladio editor bug
  • Floriment: Working on Slingshot, targeting MODELS tool and demo track. Busy getting tool to state which can be used.
  • Steffen: Helped Sarah at mentor project for discussing cost models. Helped in creating new measurement points for various events in slingshop
  • Martina: Integrating DSL for Self-Adaptation Strategies, here for updates w.r.t. palladio release

Palladio Developer Meeting

  • @ SSP
  • Look in Wiki - Who will attend?
  • @Floriment: possible to have a little demo of slingshot?
    • Floriment agrees.
    • Nicolas gets in contact
  • Release of new version
    • Sebastian W. fixed bug -> version available
    • Use Dev Meeting for Testing Day
    • Do release at Dev Meeting
  • When to start? Lunch is self payed -> Start before lunch or at 1 p.m.? preferences in general?
    • Floriment: after 10 is ok
    • Steffen: no issue
  • Orga-Team will provide email with agenda later this week.

Release

  • Release of newer version of eclipse, currently 12-2022, Jörg wants newer Version of Eclipse.
  • New sustainable palladio build, see nightly build
    • Currently setup only build regarding the dependencies. Only repos directly build on a changed dependency is build
    • Once a week all is build
  • Palladio Website (Yves)
    • Maybe get rid of typo3 system and maybe build and deploy the github standard markdown -> html integration.
    • Should we stay with typo3 website?
    • Current website outdated/dead, last change was "new release"
    • Markdown easier to modify webseite.
    • However, need to transfer current website.
    • Steffen: Current state, not much stakes in the website.
    • Steffen: Maybe nowerdays markdown is more common, how to migrate?
    • Steffen: Use student for migration? -> where to get a student from?
    • Yves: Maybe write some Tutoriumsstudent if one wants to do?
    • Nicolas: Maybe use assistent researcher of nicolas and larissa
    • Larissa: Considers waste of talent because student can do stuff.
    • Maximilian: first list of what to migrate necessary
    • Yves: Migrate everything, throw away later is better.
    • Nicolas: Because of capability -> really done finished with task
    • @Nicolas: Ask Lukas!
    • Sebastian H.: There are more difficult stuff to do (select best design...). Search someone which is capable for the initial stuff for more than copy paste.

Handling Research Projects

  • Maximilian: Seperate github repos, maximilians stuff, stephans stuff. How to handle these projects? Easily migrated to github organisation, but more projects then there?
    • Maximilian: Migrate them? Keep them where they are? Outsite: - worse visibility, + do not fill in organisation.
    • Nicolas: Maybe with new website, stuff can be consolidated.
    • Nicolas: Past Approaches in GitHub orga, but then archived because they are not mainained or work.
    • Nicolas: More to deside by Steffen, Ralf and Anne
    • Sebastian W: Discuss this thing in person.
    • Nicolas: Maximilian not there anymore.
    • Martina: Question that comesup every once in a while. Work is lost if not in organisation. Better question to ask: why difficult to integrate into the palladio ecosystem.
    • Nicolas: Not that hard, but decide how finished work ist.
    • Talk about this in SSP in person.