Sharing Omnis Libraries on GitHub
“Would anyone else like to see a list of Omnis-related resources we could
Great idea, I think we should get one going! Omnis could then simply update
the page direct to github etc.
On Sun, Oct 29, 2017 at 4:06 PM, Alex Clay <firstname.lastname@example.org> wrote:
> Hi Clifford,
> Yes, I agree we should organize a resource collecting these various
> projects together. Omnis Software recently added a page like this to their
> If there is community interest in hosted an awesome list on GitHub for our
> projects I’m happy to maintain that. Looking at some of the examples for
> existing Awesome Lists, we could include everything from useful libraries,
> to paid plugins like OWrite, to conferences like Euromnis. But I feel this
> is what Omnis is trying to do with their development portal. The programmer
> in me cries at the idea of duplicating this data source, but I understand
> the goal of spreading awareness by plastering Omnis in as many locations as
> If nothing else, we could include a link back to the developer portal from
> a community-maintained Omnis Awesome List.
> Would anyone else like to see a list of Omnis-related resources we could
> all maintain?
> > On Oct 28, 2017, at 18:42, Clifford Ilkay <email@example.com> wrote:
> > Hi Alex,
> > Someone, maybe you, should have a meta page kept in a GitHub repo that
> > lists the various repos that people have shared. Anyone who wants their
> > repos to be easily found can for that repo, make their changes, and then
> > submit a pull request to the maintainer of the meta repo. The owner of
> > meta repo can then merge the pull requests if appropriate.
> > Once you have something like that, submit it to the Awesome list < > > github.com/sindresorhus/awesome>, which itself is a meta list of
> > lists.
> > Regards,
> > Clifford Ilkay
> > +1 647-778-8696
> > On Sat, Oct 28, 2017 at 3:24 PM, Alex Clay <firstname.lastname@example.org> wrote:
> >> Hi All,
> >> At the Euromnis annual general meeting last week I volunteered to write
> >> step-by-step guide for how to share Omnis libraries on GitHub. I’m
> >> 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
> >> 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
> >> guide on how to contribute to an Omnis library that’s hosted on GitHub,
> >> 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
> >> are Omnis code, but I’ll report back periodically with how we’re doing
> >> raising these numbers.
> >> If anyone needs help sharing their library on GitHub, I’m happy to
> >> 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
> Manage your list subscriptions at lists.omnis-dev.com
Manage your list subscriptions at lists.omnis-dev.com