crategus / cl-cffi-gtk

cl-cffi-gtk is a Lisp binding to the GTK+ 3 library.

Home Page:http://www.crategus.com/books/cl-cffi-gtk

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

is the project still alive?

vityok opened this issue · comments

Commit logs show that the last commit has been submitted almost 2 years ago, in 2016. There is a backlog of open tickets and pull requests. Meanwhile @crategus seems to show no significant activity on Github.

If it is still possible, maybe moving the repository to a "project" and inviting new committers might unfreeze the progress?

With best regards

@vityok I'd like to invite you to my bit of a maintained branch at https://github.com/Ferada/cl-cffi-gtk - still "only" Gtk 3 and I can't promise anything, but I'm always happy to either merge things in and/or help out for specific issues. I also have a couple more additions in progress, in particular GStreamer for video playback and the OpenGL widget ... if that's something that you'd be interested in. Edit: Lastly you can ping me on IRC/freenode, #cl-cffi-gtk, if you like.

@Ferada thanks for the invitation. Though I think that as people come and go, some get interested in the project, some eventually loose interest, it might be better to setup a Github "project" to maintain the repository at a single location, with the documentation, and also update Quicklisp to use the maintained repository instead of the existing one.

P.S. in order to preserve all open tickets and the like it is preferable for the repository owners to move the repository.

@vityok absolutely right and I'd love to, unfortunately I had little success to move forward either of those points for the past two years.

I've created a GitHub organization to let great Common Lisp libraries that are no longer maintained find their new contributors: https://github.com/lisp-projects would be nice if this repository moved there...

by adding new members to the organization it would be possible to carry on the work without disruptions associated with a small number of developers losing interest

There is already an organization for that, @sharplispers

@PuercoPop oh, thank you very much for letting me know. This organization's name is a little bit counter-intuitive and I couldn't find it with simple searches on Github.

What is their policy for accepting new members and new repositories?

What is their policy for accepting new members and new repositories?

I'm not sure, I've seen them take new repos from requests to move them from their original sources, Ironclad. I'm guessing the best way to find out would be to contact Xach.

I'm wondering if we can do this via Github by mentioning their handles.

Hi @xach what is the current policy for admitting new projects to the @sharplispers?

Hi! Just to say that I would be interested in contributing to the collective maintenance of cl-cffi-gtk.

My primary interest would be to add support for some features introduced in recent versions of GTK in the 3.x series.

@svillemot , apparently to do this in a graceful manner maintainers of this repository should initiate its transfer to a community organization, like @sharplispers. Of course, it is still possible to just fork the repo and go on. But IIRC transfering it is preferable.

Also the community at, for example, @sharplispers, should be ready to accept it.

Given that @crategus has not been active in github for a long period of time, and did not jump into this discussion, I think it is unlikely that he will initiate the transfer (though I would be happy to be proven wrong). So a fork looks like the only practical option.

Concerning the receiving organization, this is less of a problem. It's always possible to create a new one if @sharplispers for some reason does not want cl-cffi-gtk.

So what has been decided? Do I do (ql:quickload :cl-cffi-gtk), clone this project, or something else?

I am an old Lisp hacker from the 70s and 80s that is just getting back into hacking Lisp again. I found this project, which seems to be the best free gui for Lisp development that works.

I want to build operational software. From that perspective I am not willing to fix defects that others find, but I am willing to fix defects that I find. I expect I would use most of GTK. I am using SBCL.

Nothing has been decided yet. We're going to contact @crategus again to get the permission to move this repository to an organization, and therefore keep the "cl-cffi-gtk" name. If that's not possible, we're going to fork it.

In the meantime, your best bet is to use the fork started by @Ferada, where current work happens.