can't you just push to the scriptler repo?

This would be useful for us too. Because of company policy, all source code must be stored in our company's Git server.

If this plugin allowed access to use a different external repo, I believe that enterprise users of Jenkins would still contribute some scripts to github and scriptler, but the main body of scripts would be from an internal repo.

If scriptler is not updated to allow an internal catalog, then teams will just fork the code to build their own internal versions of the plugin

I have the same requirements as the users stated above. We would like for this plugin to have the ability to point to our own repo for groovy scripts.

just to be clear, you would like to have an inhouse catalog (1) - a list of scripts that can be imported into individual jenkins instances via scriptler?

(1) https://wiki.jenkins-ci.org/display/JENKINS/Scriptler+Plugin#ScriptlerPlugin-Catalogs

That is correct.

imod, can I launch this "Import" step through a groovy script as well?

That way, I could have a job that listens to my in-house git repository, and imports all new/changed scripts on every push. Which would be as good as specifiying an external GIT repo.

Of course, if I manage the scripts externally, a way to forbid direct changes through the Jenkins UI would be necessary, but this is the next step

hakan no sorry, that's not possible - but there is an extension point you can implement to add a new catalog: org.jenkinsci.plugins.scriptler.share.ScriptInfoCatalog