In fact, nothing of above about ^SYS is relevant. All is much simpler. If develop Interoperability solution as an IPM module source control works automatically because of git-source-control. No any additional settings needed.  Wrote an article about it, take a look:

https://community.intersystems.com/post/enabling-iris-interoperability-s...

Turned out, the following call should be executed to let source control start working:

do ##class(%Studio.SourceControl.Interface).SourceControlClassSet("SourceControl.Git.Extension")

Check Interoperability template to discover Git integration for Interoperability UI components. Production, Business Rules (old UI), Business Process and Data Transformations are supported.

Things to know:

1. Make sure the settings export changes in the folder you want, can be adjusted in the git-control UI.

2. Every Interoperability component should be first added to source control manually (in the git-control UI, add button).

3. Make sure you export the git-control settings too! They are in ^SYS global. @Timothy Leavitt , we also need source control for git-control settings ;) (Could be a ^git-control global name ?)

For now I use the following line to export it in a proper format and in a proper place, which I still call in a Terminal:

do $System.OBJ.Export("SYS*.GBL","/irisdev/app/src/gbl/SYS.xml",,.errors)

And I import it with the following setting in module.xml:

<Resource Name="SYS.GBL"/>,

a full module.xml example. 

4. @Timothy Leavitt , Would be great to have the UI to have the editable list of all the source-controlled elements. E.g. to easily transfer ^SYS global between projects. As the majority of settings for docker-enabled setups are the same, but the list of source-control elements is different.

@Guillaume Rongier , have a look! )

I think we are heading the NPM route. Quantity does not mean better. Quality does. We are all strong developers and individuals, and we all want to make a difference and contribute. We all also want that contest prize, to be honest. The contest prize I think pushes the people, which is good, but maybe contributes towards the single contributor packages. I am not saying the contests should stop, but maybe when doing something for a contest, try and do it and take part without making a new package. Chat with the Repo owner - I am sure the owner will not mind if you improve on their repo and get the prize.

Regarding it. First of all, thank you for the feedback. This is very important and we are looking for such a feedback all the time.

Yes, we have 700 apps, and 4 years ago we had zero and contests helped to have some variety.

Also, I hope every member of this developer community could participate in a contest with the new app, as it as we think gives a habit to stand-out from your own dev-bubble and consider docker, ipm, online demos, unit-testing and sometimes provide a feedback!

But on contrary we encourage very much re-applying with already created apps and we see several improved apps even in the current contest.

If nothing is in the list I encourage to submit an idea on ideas.intersystems.com

Stefan, for 1: have you tried DBeaver? It has IRIS driver and looks like the most popular SQL dev tool nowadays.

Also, there is actively supported for IRIS SQL add on to VSCode

If there is a step-by-step instruction how to setup python environment on Mac I’d appreciate very much

Also, we encourage participants of the contests to apply again with the existing apps and add new features into them. And developers do that.

On the team forming: we invite developers to participate as teams - and some of them do that. We have a team of 3 developers from Brazil who participate in a recent contest with iris-trippleslash. But of course it'd be great to see more teams like that.

Hi @Stefan Cronje !

Thanks for raising this topic! In fact we are aware of the problem and introduce different features and services that can increase the level of quality of the applications.

1. We give the bonus for the ObjectScript quality, and all the templates contain ObjectScript linter, that free of charge monitors ObjectScript public code upon a set of rules. 

And we introduced a special filter on OEX that shows only such apps.

2. We encourage developers to review applications. And to simplify the review, we encourage usage IPM (and we have a special filter) and applications with online demos, as this saves the time of reviewers greatly.

3. We'd love to see projects with multiple contributions and the first thing that could help contributors is to easily setup the dev environment - and here nothing is best than docker environment. That's why we encourage docker usage so much and dockerfile is presented in each and every template.

4. We have InterSystems supported samples and templates to show the set of trusted applications and establish the code guidelines.

Actually, you can see the focus of the enhancements if you look what bonuses we suggest for the applications in contests - they are all connected to what we think can increase the quality of applications and engage its usage.

Thanks to all the contributors! You make this community fantastically helpful!

What Python should I install on my laptop to make irissqlcli work?

I'm on mac. 

Sounds like a good enhancement request.

I'd place this as a embedded link (like debug and copy invocation) but above the classname, like "goto line" - you click it, place the copied debug string and it goes to the line. And opens "Other code" in neighbor window if needed.

Calling @Tani Frankel 

Great article, @Henry Pereira !

Could you please publish the github repo on Open Exchange?
 

Congrats to all the contributors! You make the community! Thank you!

Do you mean Debug in VSCode? It didn't work for me too

For your inspiration see also the ideas with the "Community Opportunity" status on the Ideas Portal. 

What a contest!

It'd be great if someone could implement the tool to export Interoperability components into a local folder with every changes saved in the interoperability UI?

Currently git-source-control can do the job, but it is not complete. Some Interoperability components (e.g. business rules) are not being exported. And lookup tables are exported in an not importable format.

I published and idea regarding it.