Thanks Adam for the reply. I'll make some time during the weekend to send a PR to add a note to the README
For now I'm only trying mesos out to see some personal use cases which then would move on to applying them with some clients, so at first I could just try the bleeding edge. Thanks Diego On Fri, Oct 24, 2014 at 3:43 AM, Adam Bordelon <[email protected]> wrote: > Good question. That is confusing. The one at > https://github.com/mesos/mesos-go should be the official repo, although > it looks like some of kdomanski's PRs only got merged into the mesosphere > repo. We should update the README and probably archive/close the fork at > mesosphere. Feel free to issue a PR to update the README to clarify. > (Niklas, please correct me if I'm wrong.) > > Now that that's settled, the next question is whether you want to use the > stable Go bindings in the master branch (requires a libmesos), or use the > (in-development) pure bindings at > https://github.com/mesos/mesos-go/tree/pure (pure Go + protobufs). I'd > advise the master branch, unless you like the bleeding edge and hate cgo. > > On Thu, Oct 23, 2014 at 8:02 PM, Diego Medina <[email protected]> wrote: > >> Hi, >> >> I just started using mesos and I'm trying to see which of the two Go >> bindings is the one I'm supposed to use. >> >> github.com/mesos/mesos-go or github.com/mesosphere/mesos-go ? >> >> Google searches point to github.com/mesos/mesos-go but the README there >> points to go get github.com/mesosphere/mesos-go >> >> if the one at mesosphere is the one I should be using, would it be ok to >> send a PR to the other repo to add a clear message on the README that the >> mesos/mesos-go isn't the one people should use? >> >> And lastly, the repo on mesosphere doesn't have github issues enabled, >> but I couldn't find a Jira replacement >> >> Thank you. >> >> >> -- >> Diego Medina >> Scala/Lift Consultant >> [email protected] >> http://www.fmpwizard.com >> > >
