Sharing Omnis Libraries on GitHub
Hi everybody,
I was just looking at the recent Brainy Data’s contribution on GitHub and I noticed that his repositories have “topics” or tags/keywords associated with it.
That’s brilliant!
Can those that have already published to GitHub also please add the basic “omnis-studio” as a topic (tag/keyword) please.
This makes searching on GitHub easier and it also helps increase our overall visibility. Tag your individual repositories as “omni-studio” and then if it pertains to other areas of omnis, such as, lists, use “lists” and/or “notation” and/or “sql” …
To search for these topics there are two ways
1. Just type in the top search bar “omnis-studio” or its variance and GitHub will deliver its best guess results. OR
2. type in the search bar, topic:omnis-studio and hit return on your keyboard. You’ll instantly see (for now) Brainy Data’s repositories only.
To add a “topic”, head over to your individual repository and at the top, just under the “<> Code” tab lies the description and just below that is a link to “Add topic”. Hit that link and it will open up an edit box that has type-as-you-go lookups. Just start adding topics beginning with “omnis-studio”.
You can even save and come back later and hitting up the “Manage topics” link to continue adding more tags. There are chances that GitHub will automatically start to offer relevant suggestions based on your code in the repo. (I think for that you need to save and go away from that repo page and come back… if I am wrong someone here will correct me.)
Adding these topics will certainly affect the overall visibility of your repository and Omnis Studio itself.
I hope this catches on. 🙂
Kind regards,
Vik Shah
Director
Keys2Solutions
> On 29 Oct 2017, at 05:24, Alex Clay <aclay@mac.com> wrote:
>
> Hi All,
>
> At the Euromnis annual general meeting last week I volunteered to write a step-by-step guide for how to share Omnis libraries on GitHub. I’m pleased to announce that guide is available here:
>
> omnis.ci/guides/sharing-omnis-libraries-on-github.html <omnis.ci/guides/sharing-omnis-libraries-on-github.html>
>
> I wrote a blog post explaining why it’s important for us to share Omnis code on GitHub, but if you want the TL;DR: version, we need several hundred repositories that contain Omnis code in order to register Omnis as an official language with GitHub. Hence, I hope the above guide will be helpful to everyone in the pursuit of that goal.
>
> If you want to read more, here is the post:
>
> omnis.ci/github/tutorial/announcement/2017/10/27/a-call-to-arms.html <omnis.ci/github/tutorial/announcement/2017/10/27/a-call-to-arms.html>
>
> I’d also like to give a huge thank you to Henk Noppe for writing a second guide on how to contribute to an Omnis library that’s hosted on GitHub, and to Christoph Schwerdtner for beta-testing the guide. You can find Henk’s guide here:
>
> omnis.ci/guides/contribute-to-omnis-libraries.html <omnis.ci/guides/contribute-to-omnis-libraries.html>
>
> As a starting metric, there are 2,986 files with a .omh extension and a 1,338 with a .lbs extension on GitHub as of this writing. Not all of these are Omnis code, but I’ll report back periodically with how we’re doing in raising these numbers.
>
> If anyone needs help sharing their library on GitHub, I’m happy to provide it either on this list, or via direct email.
>
> Thank you in advance for sharing your code!
>
> Alex
> _____________________________________________________________
> Manage your list subscriptions at lists.omnis-dev.com
_____________________________________________________________
Manage your list subscriptions at lists.omnis-dev.com
Start a new message -> mailto:omnisdev-en@lists.omnis-dev.com
