Agreeing on/writing CCRP international RSE group protocols

[polly64]

Please do add any recommendations for protocols for the new CCRP international RSE group here. Also would be v useful if reps from countries' RSE teams could confirm agreement next to the protocols plus any suggestions for additions adjustments.

• what should protocols be for access to adding/ editing core repository be? Specific group of initial countries already leading and helping in this area? UK, Canada, Sweden, Germany, Australia ? also to co-write technical papers. Would it be good to decide before jan technical meeting?

• what should be procedure for agreeing what code is included in core and what country specific?

• Can we separate this into a) process for technical optimisation of platform and ease of reproduction of code, b) new content and features developed by individual countries that could be relevant to some or all international platforms?

• Is it easier to co-work on this discussion on a new page on the CCRP open manual, or, initially on this GitHub issue?

• Could Canada or Sweden possibly host or cohost monthly CCRP international engineering meetings? Would it be possible to send out recurring invite for next six months and then we can reassess hosting and whether should rotate?

• UK to forward RSE info for all countries by email so everyone can be invited to next meeting.

• What is the best way to encourage countries not to make quick fixes to code and to think of benefits for network as whole?

• Should we require attendance at technical meetings of CCRP platform engineers as part of CCRP main protocols? For PI meetings this is essential to drive collaborative, innovative work where platforms are in synch, as well as efficient, sustainable working methods.

• How can we make integrating new updates much easier and quicker for all countries and especially academic partners with small budgets.

• Where do we document that New Country specific subcategories categories (not core) must be added subject to protocols and CCRP open code licence terms? And how do we make this code easier for PIs from other countries to scan through to see if any additional features are relevant to them?

How can we best ensure that countries are following similar core format and branding ie not changing 12 category grid names for example other than translating? Essential for the same 100 plus datasets to be collected across countries and in same format to support transnational analysis (anyone can use CCRP open-source qcode and set up their own platforms including any academic depts.participation in the CCRP group involves those committed to v specific. agreed public goals, protocols and data sharing methods as well as an understanding of importance of us all Working to help all members of the group as well as our own countries. And the many great advantages of working as a group.

[matkoniecz]

I want to note that issues like #1284 by @Ruben1729 are very useful and helpful (and #1281 #1285)

[matkoniecz]

What is the best way to encourage countries not to make quick fixes to code and to think of benefits for network as whole?

necessary part of that would be setting aside some time for review and processing pull requests (ideally) and issues submitted by other teams, to avoid situation where someone spend time on making upstream pull request that was then ignored

[polly64]

Include protocol encouraging reporting of any problems and where to document so that makes easier for next person (as noted by @matkoniecz )

Would be good to move to next stage of protocol drafting at next meeting