Neutral Gas Dynamics in the Edge: EIRENE Licence and Developer Code of Conduct

Slide Note

Task 5 discusses the licensing and developer code of conduct for EIRENE related to neutral gas dynamics in the edge. It encompasses the history, motivations, and feedback received, focusing on licensing agreements, developer groups, and ethical considerations. Various stakeholders are involved in shaping the new license terms to ensure open-source accessibility while safeguarding against commercialization and misuse. Discussions are ongoing to establish consensus and address legal feedback before the deadline.

sien895 Follow

Uploaded on Nov 27, 2024 | 0 Views

Download Presentation

Please find below an Image/Link to download the presentation.

The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.

E N D

Presentation Transcript

TSVV Task 5 Neutral Gas Dynamics in the Edge EIRENE: Licence and developer Code of Conduct D. Borodin et al.

History and motivation The old UA was quite declarative and not very clear about further development Still it was signed by ITER and other parties. Similar to ERO and other code licences. Was never used in court, however has multiple time been very helpful the fact of an official UA already makes it morally meaningful . Particular often the cause of disagreement were publications. Multiple private fusion technology companies are recently created, which act aggressively. Moreover, the growth of EIRENE community and expected development make proper licencing of importance for future. New UA is infectious open source, really ensuring no commercialisation, non-military use etc. USERs and AD s (associated developers) are clearly separated. The question of licensing is undecided for now inside the E-TASC, however marked as important one. We should seek consensus with all our partners, however we do have certain leverage. First reaction from ITER was very friendly and positive. D.Borodin | TSVV-5 VC#9 | 09.07.2021 | Page 2

Preamble for the new license placeholder software and community description Suggestion: EIRENE code package, including all related data, collisional-radiative models (AMJuel, HydKin etc.), interfaces to other codes, code documentation, CI cases, catalogued I/O of the simulations, data handling and visualization tools. Anything and everything documented at www.eirene.de and contained in the central repository by the time of download. D.Borodin | TSVV-5 VC#9 | 09.07.2021 | Page 3

First feedback obtained: GS/YM: we should enforce good practice to publish the modified code (or additional routines) as metadata together with the results. DB: Should we introduce EIRENE-NGM-DEVELOPERS group author name? Should we introduce official EIRENE reference, mandatory for USERs ? Should we enforce the pin board rules? DB: Are USERs-AD s , EPL (EIRENE Public Licence) are acceptable to all? DB: Should developer code of conduct (DCoC) and role of PI be hardwired into the licences? D.Borodin | TSVV-5 VC#9 | 09.07.2021 | Page 4

Feedback for FZJ lawyers Remarks type A: Remarks type A: "This passage in licence concerns me, because "This passage in licence concerns me, because... ... Remarks type B: Remarks type B: "I suggest the following to be added/corrected in the licence "I suggest the following to be added/corrected in the licence... ... Remarks type C: Remarks type C: "I have concern, but no explicit idea for the solution" "I have concern, but no explicit idea for the solution" Dead line: 16.07 (agreed?..) D.Borodin | TSVV-5 VC#9 | 09.07.2021 | Page 5