For the case of Github, I think one file per one program/class would be the better approach.

You can use Atelier, like [@Amir Samary] mentioned. And in case you have no Atelier I can recommend also this very simple util: cache-udl

Setup the folder with:

d ##class(sc.code).workdir("your/workdir")

And export everything in a namespace with:

d ##class(sc.code).export()

For import use:

d ##class(sc.code).import()

to import all, or:

d ##class(sc.code).importUpdated()

for the recently updated files.

And yes, it exports in UDL. I think for Github UDL is more suitable. 

May I ask you, why do you need XML for your code files?

Just add *.INT into the list var:

s list="MyPackage*.INC,MyPackage*.CLS,Folder*.DFI,*.INT"

We can change the email in Global Masters to make it compatible with DC to let us count points in GM for your DC contributions. Would it work?

Sure. Also Caché Terminal doesn't work over SSH (AFAIK)

Caché Terminal is only for Windows.

At least you can have the benefits of Caché Web terminal itself: 

Code completion (methods, classes, properties, etc), code highlighting, nice SQL shell, endless history, etc.

Iterating over indexed value can be very helpful. 

We have IndexOpen and IndexExists autogenerated methods (article on autogenerated methods) for persistent classes. I'm using these very handy methods a lot.

It would be great if somebody introduce Next/Prev autogenerated methods too e.g. via some NavigationAdapter class to derive from.

Hi, Sean!

Check Cache-udl tool by [@Oleg Dmitrovich]. It does UDL import/export nicely in following manner:

path/cls/package/class

path/mac/package/routine

path/inc/package/include

path/DFI/Folder/dashboard

Hi, Ed! Thank you! We'll try to fix the problem.