Releasing proprietary iOS SDK using github.

Question

We built a library (SDK) for iOS. The source code of the library is closed (proprietary). The output we want to release is iOS frameworks, API documentation, setup guide, license file but NO source code.

We are discussing differant ways to release it to public.

1) One way is to create a public git repository hosted in Github and push all the output in it.

2) Other way is to host these files in our own server.

Is there any benefit of hosting it on github over hosting it on our own servers? I know git is to manage source files but in this case there is no source file that we want to publish, it is just the output. Is there any general rule to release iOS close source SDKs?

I am inclined more towards hosting the SDK (as zips) in our own server. I believe it is always the latest SDK you market in your website and not the older SDK.

Answer 1

Is there any benefit of hosting it on github over hosting it on our own servers?

The main benefit is cooperation/feedback: on GitHub, people can fork your repo and send back pull request.

If you choose that publication option, I would maintain a parent repo with two submodules:

• one for the proprietary code
• one for the public code.

You can push the former on a dedicated private server.
You can push the latter on GitHub.

Using separate Git repos (here as submodules) minimizes the risk to push the wrong data to the wrong upstream repo.

---

That proposition is for text files only though.

Using Release (as in this question mentioned by the OP msk) isn't a good way to distribute deliveries, because the repo would be empty (no code, since it is proprietary), and would only contain deliveries (not necessarily executables).

Release in GitHub is done to associate deliveries to codes (through tags), and cannot accommodate any binary of any size.

In the Op's case, distributing deliveries should be done through another referential (typically a Nexus one, meaning an artifact repository, without size limit)