You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mesos.apache.org by Tomek Janiszewski <ja...@gmail.com> on 2017/02/03 10:43:00 UTC
Mesos-go status
Hi
What is the status of https://github.com/mesos/mesos-go It looks like it's
abandoned. Useful pull requests are awaiting merge and issues need to be
fixed. Who is the owner of this repo? I can volunteer to continue this
project especially the executor module.
Thanks
Tomek
Re: Mesos-go status
Posted by Tomek Janiszewski <ja...@gmail.com>.
Thanks, glide will solve packaging problem. Nevertheless, if mesos-go is
dead we should bring it back to live or disable PRs and issues and add
comment that this repo is no longer maintained e.g.,
https://github.com/mesosphere/marathon-ui#project-status
pt., 3 lut 2017 o 16:00 użytkownik Jake Farrell <jf...@apache.org>
napisał:
> You do not necessarily have to repackage, if you are using glide [1] to
> build your application you can specify a package like
> github.com/mesos/mesos-go and then specify your fork as the repo to check
> out and glide will automatically place the fork into that package namespace
> for you.
>
> -Jake
>
>
> [1]: https://glide.readthedocs.io/en/latest/glide.yaml/
>
> On Fri, Feb 3, 2017 at 6:54 AM, Tomek Janiszewski <ja...@gmail.com>
> wrote:
>
> > I know but I'd prefer to avoid to double work that somebody have already
> > done. If I fork it and made custom changes (in Go this require
> repackaging)
> > I'll end up with my custom fork that only I'm interested in with no
> support
> > from community. See this comment[1] with one repo we have two nearly
> > identical pull requests. If I create custom fork I'll totally lose a
> track
> > with others. And it's possible I'll duplicate work somebody already did
> and
> > hit the bugs that already was resolved.
> >
> > [1]: https://github.com/mesos/mesos-go/pull/262#issuecomment-246865392
> >
> > pt., 3 lut 2017 o 12:31 użytkownik tommy xiao <xi...@gmail.com>
> napisał:
> >
> > > you can forked it>>>
> > >
> > > 2017-02-03 18:43 GMT+08:00 Tomek Janiszewski <ja...@gmail.com>:
> > >
> > > > Hi
> > > >
> > > > What is the status of https://github.com/mesos/mesos-go It looks
> like
> > > it's
> > > > abandoned. Useful pull requests are awaiting merge and issues need to
> > be
> > > > fixed. Who is the owner of this repo? I can volunteer to continue
> this
> > > > project especially the executor module.
> > > >
> > > > Thanks
> > > > Tomek
> > > >
> > >
> > >
> > >
> > > --
> > > Deshi Xiao
> > > Twitter: xds2000
> > > E-mail: xiaods(AT)gmail.com
> > >
> >
>
Re: Mesos-go status
Posted by Jake Farrell <jf...@apache.org>.
You do not necessarily have to repackage, if you are using glide [1] to
build your application you can specify a package like
github.com/mesos/mesos-go and then specify your fork as the repo to check
out and glide will automatically place the fork into that package namespace
for you.
-Jake
[1]: https://glide.readthedocs.io/en/latest/glide.yaml/
On Fri, Feb 3, 2017 at 6:54 AM, Tomek Janiszewski <ja...@gmail.com> wrote:
> I know but I'd prefer to avoid to double work that somebody have already
> done. If I fork it and made custom changes (in Go this require repackaging)
> I'll end up with my custom fork that only I'm interested in with no support
> from community. See this comment[1] with one repo we have two nearly
> identical pull requests. If I create custom fork I'll totally lose a track
> with others. And it's possible I'll duplicate work somebody already did and
> hit the bugs that already was resolved.
>
> [1]: https://github.com/mesos/mesos-go/pull/262#issuecomment-246865392
>
> pt., 3 lut 2017 o 12:31 użytkownik tommy xiao <xi...@gmail.com> napisał:
>
> > you can forked it>>>
> >
> > 2017-02-03 18:43 GMT+08:00 Tomek Janiszewski <ja...@gmail.com>:
> >
> > > Hi
> > >
> > > What is the status of https://github.com/mesos/mesos-go It looks like
> > it's
> > > abandoned. Useful pull requests are awaiting merge and issues need to
> be
> > > fixed. Who is the owner of this repo? I can volunteer to continue this
> > > project especially the executor module.
> > >
> > > Thanks
> > > Tomek
> > >
> >
> >
> >
> > --
> > Deshi Xiao
> > Twitter: xds2000
> > E-mail: xiaods(AT)gmail.com
> >
>
Re: Mesos-go status
Posted by Tomek Janiszewski <ja...@gmail.com>.
I know but I'd prefer to avoid to double work that somebody have already
done. If I fork it and made custom changes (in Go this require repackaging)
I'll end up with my custom fork that only I'm interested in with no support
from community. See this comment[1] with one repo we have two nearly
identical pull requests. If I create custom fork I'll totally lose a track
with others. And it's possible I'll duplicate work somebody already did and
hit the bugs that already was resolved.
[1]: https://github.com/mesos/mesos-go/pull/262#issuecomment-246865392
pt., 3 lut 2017 o 12:31 użytkownik tommy xiao <xi...@gmail.com> napisał:
> you can forked it>>>
>
> 2017-02-03 18:43 GMT+08:00 Tomek Janiszewski <ja...@gmail.com>:
>
> > Hi
> >
> > What is the status of https://github.com/mesos/mesos-go It looks like
> it's
> > abandoned. Useful pull requests are awaiting merge and issues need to be
> > fixed. Who is the owner of this repo? I can volunteer to continue this
> > project especially the executor module.
> >
> > Thanks
> > Tomek
> >
>
>
>
> --
> Deshi Xiao
> Twitter: xds2000
> E-mail: xiaods(AT)gmail.com
>
Re: Mesos-go status
Posted by tommy xiao <xi...@gmail.com>.
you can forked it>>>
2017-02-03 18:43 GMT+08:00 Tomek Janiszewski <ja...@gmail.com>:
> Hi
>
> What is the status of https://github.com/mesos/mesos-go It looks like it's
> abandoned. Useful pull requests are awaiting merge and issues need to be
> fixed. Who is the owner of this repo? I can volunteer to continue this
> project especially the executor module.
>
> Thanks
> Tomek
>
--
Deshi Xiao
Twitter: xds2000
E-mail: xiaods(AT)gmail.com