SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Strategies for Sustaining the CS Framework Post-Workshop at GSI

lela avatar
lela
5 diapositives · 182 Views · Jul 19, 2014

This document outlines the key organizational details and future strategies discussed during the 2013 CS Framework Workshop held at GSI. Key points include dinner arrangements, potential transportation options to Khan, and thoughts on future maintenance of the CS Framework and its packages. The need for community engagement in documenting and maintaining resources is emphasized, as well as recommendations for using version control systems like Git for better collaboration and management. The aim is to ensure ongoing development and longevity of the CS Framework.

Strategies for Sustaining the CS Framework Post-Workshop at GSI - slide 1
01 / 5Strategies for Sustaining the CS Framework Post-Workshop at GSI
1 / 17

Télécharger la présentation

Strategies for Sustaining the CS Framework Post-Workshop at GSI
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. CS Framework Workshop 2013 Welcome! H.Brand@gsi.de

  2. Organisational • Attendee list • Dinner • Please note whether you join the dinner. • We made a reservation for 12 persons. • Transportation • We could use the GSI bus and S-Bahn to go to Khan. • We could buy group tickets. • We could go by car. • Workshop photo H.Brand@gsi.de

  3. ThoughtsaboutCS Future • Inventors of CS are busy with other projects for FAIR • Dennis Neidherr will maintain CS_Main Package and • Packages necessary for HITRAP & MATS • Who takes over the maintenance of other packages & classes? • Upgrade to new LabVIEW Version 2012? • Integration of LVOOP? • Native support by NI • CS Integration • CS base classes using LVOOP • Example: IMAQDevice using HGF_IMAQ • Independent NI Actor Framework application • Connected to CS via DIM • Long term perspectives? • Which is the driving project? • Software, which is not actively developed or maintained by the community, is dead! H.Brand@gsi.de

  4. Wiki & Sourceforge • CS@wiki.gsi.de • Central place for CS documentation • Most contribution stem from Dietrich! • Only very few other authors. • Outdated documentation is at least misleading or even worse: useless! • CS@sourceforge.net • Mailing list: Cs-framework-info is rarely used. • Do we really need it? • Forum & Tracker are rarely used. • Do we really need it? • Alternative: forum.gsi.de • Frequent SF changes • Maintenance of CS@Sourceforge.net? • (Un-)Packager? • Central place for download of released packages. • Alternative: Distribution using VI Package Manager?(VI Package Manager is pushed by NI.) H.Brand@gsi.de

  5. Source Code Control • No substitute for backup! • Subversion • Central repository • World wide accessible, but needs online connection. • Head revision contains most recent developments. • Individual classes or packages can be updated to specific revisions in order to match corresponding releases. • Branching is possible but seldom used. • Quality assurance • Commit permissions restricted to responsible (group of) developer • Observed behavior • Checkout once • Never update – risk to miss important updates or bug fixes! • Commit seldom or never – in contradiction to collaboration! • Alternative: Git – Distributed Version Control System • Can be used as subversion client. • Allows local offline commits. • More flexible, but needs more discipline. • Chance to get rid of history • Keeps a release repository slim! H.Brand@gsi.de