Home

Tango-controls migration from Sourceforge SVN to Github status

Introduction

tango-cs and tango-ds Sourceforge projects are currently being moved to GitHub under the tango-controls GitHub organization. This page will present the current status of the migration.

Migration status

tango-cs

The following table will present the current status of the migration of the main tango kernel projects (from tango-cs Sourceforge project).

svn directory	source code migration status	tickets migration status	Commits on Sourceforge
distrib/source	migration in progress to https://github.com/tango-controls/TangoSourceDistribution	tickets not yet migrated	Allowed until next Tango release but all Sourceforge SVN commits shall be duplicated in Github.
api/cpp/log4tango	migrated to https://github.com/tango-controls/cppTango	tickets migrated	Allowed until next Tango release but all Sourceforge SVN commits shall be duplicated in Github.
api/cpp/cpp_test_suite	migrated to https://github.com/tango-controls/cppTango	tickets migrated	Allowed until next Tango release but all Sourceforge SVN commits shall be duplicated in Github.
api/cpp/cppapi	migrated to https://github.com/tango-controls/cppTango	tickets migrated until 27/10/2016	Allowed until next Tango release but all Sourceforge SVN commits shall be duplicated in Github.
api/cpp/cpp_test_ds	migrated to https://github.com/tango-controls/cppTango	tickets migrated	Allowed until next Tango release but all Sourceforge SVN commits shall be duplicated in Github.
classes/cpp/TangoTest	migrated to https://github.com/tango-controls/TangoTest	tickets not yet migrated	commits should probably be forbidden on svn (To be done)
api/java/client/tangorb	migrated to https://github.com/tango-controls/JTango	tickets not yet migrated	commits should probably be forbidden on svn (To be done)
classes/cpp/dbase	migrated to https://github.com/tango-controls/TangoDatabase	tickets not yet migrated	commits should probably be forbidden on svn (To be done)
classes/cpp/TangoAccessControl	migrated to https://github.com/tango-controls/TangoAccessControl	tickets not yet migrated	commits should probably be forbidden on svn (To be done)
classes/cpp/TangoAccessControl/AbstractClasses/AccessControl	migrated to https://github.com/tango-controls/TangoAccessControl	tickets not yet migrated	commits should probably be forbidden on svn (To be done)
idl	migrated to https://github.com/tango-controls/Tango-idl	tickets not yet migrated	commits should probably be forbidden on svn (To be done)
share/fandango	migrated to https://github.com/tango-controls/fandango	tickets not yet migrated	commits are forbidden on svn
bindings/PyTango	Github ownership transfer needed	tickets not yet migrated(Needed?)
gui/tgraphicsplot	Info needed	tickets not yet migrated
gui/qtango	Info needed	tickets not yet migrated
gui/qdddplot	Info needed	tickets not yet migrated
gui/tau	DO NOT MIGRATE	Obsolete.
gui/qgraphicsplot	Info needed	tickets not yet migrated
gui/taurus	DO NOT MIGRATE	Obsolete repo. Taurus is on a separate project now .
gui/atk	migrated to https://github.com/tango-controls/atk	tickets not yet migrated	commits are forbidden on svn
gui/qwt5-qt5	Info needed	tickets not yet migrated
distrib/debian	will not be migrated	Not applicable
api/java/client/web/client	Info needed	tickets not yet migrated
api/java/client/web/common	Info needed	tickets not yet migrated
api/java/client/web/server	Info needed	tickets not yet migrated
api/java/client/JTangoClientLang	Info needed	tickets not yet migrated
api/java/common/JTangoParent	Info needed	tickets not yet migrated
api/java/common/JTangoCommons	Info needed	tickets not yet migrated
api/java/common/IDL	Info needed	tickets not yet migrated
api/java/server/JTangoServer	Info needed	tickets not yet migrated
api/java/server/TestDevice	Info needed	tickets not yet migrated
api/java/server/JTangoServerLang	Info needed	tickets not yet migrated
doc/guidelines	Info needed	tickets not yet migrated
doc/manual	Info needed	tickets not yet migrated
archiving/tool/XmlReaderCDMA	Info needed	tickets not yet migrated
archiving/tool/snap/bensikinArchivingGUI	Info needed	tickets not yet migrated
archiving/tool/ArchivingPluginCDMA	Info needed	tickets not yet migrated
archiving/tool/AlarmArchivingGUI	Info needed	tickets not yet migrated
archiving/tool/common/sgadArchivingGUI	Info needed	tickets not yet migrated
archiving/tool/common/commonArchivingGUI	Info needed	tickets not yet migrated
archiving/tool/PyTangoArchiving		migrated to https://github.com/tango-controls	tickets migrated
archiving/tool/hdbtdb/mamboArchivingGUI	Info needed	tickets not yet migrated
archiving/api/AlarmArchivingApi	Info needed	tickets not yet migrated
archiving/api/hdbtdbArchivingApi	Info needed	tickets not yet migrated
archiving/api/snapArchivingApi	Info needed	tickets not yet migrated
archiving/api/commonArchivingApi	Info needed	tickets not yet migrated
archiving/hdb++/libhdb++	Info needed	no ticket to migrate
archiving/hdb++/gui/jhdbviewer	Info needed	no ticket to migrate
archiving/hdb++/gui/java-configurator	Info needed	no ticket to migrate
archiving/hdb++/hdbextractor/cpp	Info needed	no ticket to migrate
archiving/hdb++/hdbextractor/java	Info needed	no ticket to migrate
archiving/hdb++/doc/hdb++-design-guidelines	Info needed	no ticket to migrate
archiving/hdb++/doc/meetings/2014.09.19	Info needed	no ticket to migrate
archiving/hdb++/hdb++cm	Info needed	no ticket to migrate
archiving/hdb++/libhdbmysql	Info needed	no ticket to migrate
archiving/hdb++/libhdb++cassandra	Info needed	no ticket to migrate
archiving/hdb++/libhdb++mysql	Info needed	no ticket to migrate
archiving/hdb++/hdb++es	Info needed	no ticket to migrate
archiving/server/hdbtdbArchivingServers	Info needed	tickets not yet migrated
archiving/server/AutomaticLongTermTDB	Info needed	tickets not yet migrated
archiving/server/snapArchivingServers	Info needed	tickets not yet migrated
archiving/server/AlarmArchivingServers	Info needed	tickets not yet migrated
archiving/server/HDBTDBArchivingWatcher	Info needed	tickets not yet migrated
tools/test	Info needed	tickets not yet migrated
tools/notifd2db	will not be migrated	Not applicable
tools/vacca	migrated to https://github.com/tango-controls/vacca	tickets migrated
tools/astor	migrated to https://github.com/tango-controls/astor	tickets migrated	commits are forbidden on svn
tools/weblauncher	Info needed	tickets not yet migrated
tools/atktuning	migrated to https://github.com/tango-controls/atk-tuning	tickets not yet migrated	commits are forbidden on svn
tools/panels	Info needed	tickets not yet migrated
tools/tango_admin	Info needed	tickets not yet migrated
tools/classes2www	Info needed	tickets not yet migrated
tools/pysynoptictree	OBSOLETE, replaced by Vacca	tickets not yet migrated
tools/jive	migrated to https://github.com/tango-controls/jive	tickets migrated	commits are forbidden on svn
tools/atkpanel	migrated to https://github.com/tango-controls/atk-panel	tickets not yet migrated	commits are forbidden on svn
tools/tool_panels	deprecated	nothing to be done
tools/pogo	migrated to https://github.com/tango-controls/pogo	tickets migrated	commits are forbidden on svn
tools/pogo/pogo6	will not be migrated (deprecated)	No ticket to migrate
tools/logviewer	migrated to https://github.com/tango-controls/LogViewer	no ticket to be migrated?	commits are forbidden on svn
tools/devicetree	Info needed	tickets not yet migrated
classes/cpp/starter	migrated to https://github.com/tango-controls/starter	tickets migrated	commits are forbidden on svn
share/workbench	Info needed	tickets not yet migrated
share/yat	Info needed	tickets not yet migrated
share/nexuscpp	Info needed	tickets not yet migrated
share/weblauncher	Info needed	tickets not yet migrated
share/imagej	Info needed	tickets not yet migrated
share/synoptictree	OBSOLETE, replaced by VACCA	tickets not yet migrated
share/yat4tango	Info needed	tickets not yet migrated
share/nexus4tango	Info needed	tickets not yet migrated
bindings/igorpro	Info needed	tickets not yet migrated
bindings/c_binding	Info needed	tickets not yet migrated
bindings/matlab	Info needed	tickets not yet migrated
bindings/labview	Migrated to https://github.com/tango-controls/labview-binding	tickets not yet migrated	commits should probably be forbidden on svn (To be done)

tango-ds

The following table will present the current status of the migration of the tango device servers (from tango-ds Sourceforge project).

svn directory	source code migration status	tickets migration status	Commits on Sourceforge
Clients/python/Panic	migrated to https://github.com/tango-controls/PANIC	tickets not yet migrated	Commits are forbidden on svn Sourceforge
DeviceClasses/SoftwareSystem/PyAlarm	migrated to https://github.com/tango-controls/PANIC	tickets not yet migrated	Commits are forbidden on svn Sourceforge
DeviceClasses/Simulators/SimulatorDS	migrated to https://github.com/tango-controls/SimulatorDS	tickets not yet migrated	Commits are forbidden on svn Sourceforge
DeviceClasses/Simulators/PySignalSimulator	OBSOLETE, replaced by SimulatorDS	tickets not yet migrated	Commits are forbidden on svn Sourceforge

The other Tango device servers will be migrated in an automated way probably once all the tango-cs projects will have been migrated, unless device servers maintainers want to do the job themselves before like Sergi Rubio did for PANIC software.

Info needed

In the above table, there are many cells where it is written "Info needed". Here are the pieces of information needed to be able to achieve the migration of any tango-cs project:

• Project responsible name and e-mail
• New repository name on tango-controls GitHub organization
• GitHub accounts of the persons who should have admin permissions on the new repository. These persons will be responsible to manage the list of persons having write access (push permissions) on the repository. External contributors for the project should contribute via Fork + Pull Request mechanism in any case.
• Map of svn accounts <-> Github accounts for the users having already committed something for this project in svn (if relevant).
• List of Sourceforge tickets to be transferred (can be specified using expressions like: all the tickets from category _CCC _and having labels LLL, plus tickets having numbers n1,n2...nx, without the tickets assigned to John Doe).
• Map of svn accounts <-> Github accounts for the users having tickets assigned to them for this project
• Date from when the move can be done
• Date from when svn commits should be forbidden or if svn commits are still tolerated, there is the possibility to display a warning asking users to duplicate their commits using pull requests on the new GitHub repository.
• Specific requirements should be explicitly detailed. For instance, if several svn directories need to be merged into a single GitHub repository (as it was done for cppTango).

If you are a Tango kernel project maintainer, all the above pieces of info related to your projects should be sent via e-mail to Igor (Igor.Khokhriakov <at> hzg <dot> de) and Reynald (bourtemb <at> esrf <dot> fr), who are currently taking care of the move to GitHub.