> > 4. Finally, where is the best place for 3rd party plugins? This point was > raised in relation to the API client for C#. Any preferences for leaving 3rd > party material stay in the developer's repo, or the 'extras' repo? > > > > The term 3rd party confuses me. In your example, you were talking about > a .NET API wrapper, correct? Are you not the author? > [DL] By 3rd party, I mean any plugin or library that is useful for CloudStack, but has not met the IP clearance guidelines for inclusion in the project for a variety of reasons. Stuff the community does not think fits might also sit in this category.
It would be handy to be able to know which of the following two options apply: 1. Keep the code at arm's length in the developer's repo, but referenced by some sort of CloudStack market place. 2. Allow it into https://github.com/cloudstack-extras. > Generally though, we haven't decided if we want API bindings to be in the > project itself. For example, I know of python (not Marvin), ruby (which I > wrote), PHP, and other bindings that are outside of our CS repo. Are you > proposing that we start building up a set of canonical API wrappers within the > project itself? [DL] Canonical API wrappers? I hadn't that in mind, and I'd rather dodge the question for now :) > > > DL > >
