Re: libseed-list libseed is disappearing and what can we do about it

[Alan Knowles <alan akbkhome com>]

Have you done this already?

https://wiki.gnome.org/AccountsTeam/NewAccounts

Mention this conversation in the reasons.

Regards
Alan

On Friday, March 04, 2016 01:31 AM, Danilo Cesar Lemes de Paula wrote:
> Hi guys,
>
> So looks like we're all on board, right?
>
> May I suggest something here?
>
> My plan is to tag the current state as the latest stable version and
> bump the current version to 2.0.0 (maybe even calling it seed2).
>
> Next step, is it possible to get commit status on seed? That way I don't
> need to keep poking Alan regarding my patches. My main workflow at the
> moment is to push things to my personal github account and work there,
> and submit patches when I know they're ready. I would keep doing the
> same, but pushing them myself instead of poking Alan...
>
> There are other thing like tests that I want to improve... I did some
> changes regarding argument prediction and those things are just
> smoketested. I'm planning to enable the tests and adding a few more (as
> I want to make the GJS compatibility mode the default).
>
> I guess that's it.
>
> I'm waiting for the answer regarding the commit status.
>
> Thanks,
> Danilo
>
>
> On 02-03-2016 02:43, Robert Carr wrote:
> > Hey Danilo! Thanks for the thoughts. Comments inline.
> >
> > > > I want to start this email with an important consideration:
> > > > Seed is dead, long live Seed!
> > :)
> >
> >
> > > > I was looking for projects using seed, and looks like that at least in
> > > > Debian libseed is long gone. It's still being packaged on Fedora, but no
> > > > one is using it.
> > > > Looking for rdepends seed it's not required by anyone. Libpeas was using
> > > > it a while back, but they removed the dependency so we lost epiphany,
> > > > our last important user.
> > > > Considering that, I have a proposal:
> > > > Killing it the way it's now and making it a new tool.
> > > > At Collabora,  seed is an important component for a project and we are
> > > > willing to maintaining it. However, we would like to propose to drop
> > > > some parts of it and using the GJS compatibility mode as the default
> > > > mode. Since seems that there's no other project using it, it might be a
> > > > good idea.
> > Makes a lot of sense. When I was last working on Seed JavaScriptCore did
> > not have and actively
> > did not want 'let' support so we never took GJS compatibility too
> > seriously. I think it's definitely
> > a good idea and probably required if it's going to be useful in the
> > GNOME world.
> >
> > > > So, the plan would be:
> > > > We won't care about ABI break at this point. The API will probably
> > > > change considerably. Some components like SeedEngine shouldn't be a
> > > > global entity anymore and probably be a GObject.
> > > > Private header will be private, so no more header duplication...
> > > > Also, seed seems to care about some old behavior that I think we should
> > > > drop completely.
> > > >
> > > > That being said, I would like to think that the final goal would be to
> > > > make seed comparable to gjs, feature-wise. And, of course, allowing gjs
> > > > (which is the de facto javascript engine for gnome) code to run on seed.
> > No objections from me.
> >
> > > > I'm not seeing much movement in this mailing list, so I'm also inviting
> > > > Alan and some old Maintainers to the discussion.
> > > > I know you guys did a lot of work on it, and I'm sure you want to see it
> > > > being used again.
> > Again, thanks so much, I appreciate this a lot :). I am in a different
> > little corner of open source computing these days (working on the
> > Android frameworks) with lots of other interesting problems, so I don't
> > imagine myself spending time on Seed in the future :( I always felt in
> > the context of GNOME it could be a really useful tool though and I
> > definitely appreciate you taking some pragmatic steps to make it one again!
> >
> > Cheers,
> > Rob
> >
> > On Mon, Feb 29, 2016 at 5:55 AM Danilo Cesar Lemes de Paula
> > <danilo eu gmail com <mailto:danilo eu gmail com>> wrote:
> >
> >      Sorry guys, I've sent this from the wrong email and it got rejected by
> >      the libseed mailing list.
> >
> >      Sending it again from the correct one.
> >
> >      Hi folks,
> >
> >      I want to start this email with an important consideration:
> >      Seed is dead, long live Seed!
> >
> >      I was looking for projects using seed, and looks like that at least in
> >      Debian libseed is long gone. It's still being packaged on Fedora, but no
> >      one is using it.
> >      Looking for rdepends seed it's not required by anyone. Libpeas was using
> >      it a while back, but they removed the dependency so we lost epiphany,
> >      our last important user.
> >
> >      Considering that, I have a proposal:
> >
> >      Killing it the way it's now and making it a new tool.
> >      At Collabora,  seed is an important component for a project and we are
> >      willing to maintaining it. However, we would like to propose to drop
> >      some parts of it and using the GJS compatibility mode as the default
> >      mode. Since seems that there's no other project using it, it might be a
> >      good idea.
> >
> >      So, the plan would be:
> >      We won't care about ABI break at this point. The API will probably
> >      change considerably. Some components like SeedEngine shouldn't be a
> >      global entity anymore and probably be a GObject.
> >      Private header will be private, so no more header duplication...
> >      Also, seed seems to care about some old behavior that I think we should
> >      drop completely.
> >
> >      That being said, I would like to think that the final goal would be to
> >      make seed comparable to gjs, feature-wise. And, of course, allowing gjs
> >      (which is the de facto javascript engine for gnome) code to run on seed.
> >
> >      I'm not seeing much movement in this mailing list, so I'm also inviting
> >      Alan and some old Maintainers to the discussion.
> >
> >      I know you guys did a lot of work on it, and I'm sure you want to see it
> >      being used again.
> >
> >      That's it guys,
> >
> >      Cheers,
> >
> >      Danilo