Consideration / Tutorial update for modules we may not want to be made public on GitHub

[JamesOHeaDLS]

Hello,

The current tutorial for creating a generic IOC starts with pushing the chosen module to GitHub. This makes sense, but I think we need to be careful of the (admittedly small) number of support modules which may contain proprietary code that we shouldn't be publishing.

Some suggested steps for this:

• Draw up a list of the modules which this applies to and make the list known within the group
• Add a notice to these modules to warn any developer not to publish it publicly
• Add a tutorial to these pages to describe what approach should be taken when creating a generic IOC for these types of modules

Thanks,

James

[gilesknap]

Thanks James.

Please could you note here any modules that you are aware of that fit this criteria.

[JamesOHeaDLS]

A survey on Slack returned:

• ADHamamatsu
• Potentially ADOdin as it may contain detector modules which fall under this
• xspress-detector but this is being actively looked at

[gilesknap]

Thanks James. That is not too onerous!

[JamesOHeaDLS]

An update regarding the xspress detector:

There are 3 repos to do with xspress:

• xspress-detector - currently being worked on to make it publishable
• xspress3 - not publishable and will probably remain as such
• da-xspress3 - same situation as xspress3

[gilesknap]

I believe @GDYendell is looking into publishing xpress with correct attention to licensing.