Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make new release? #225

Open
v1993 opened this issue May 25, 2019 · 12 comments
Open

Make new release? #225

v1993 opened this issue May 25, 2019 · 12 comments
Assignees

Comments

@v1993
Copy link
Contributor

v1993 commented May 25, 2019

It's been a while since last release (about 1.5 years) and lgi got some improvements meanwhile.

Can you, please, consider making new release and uploading it to luarocks? Thank you!

@v1993
Copy link
Contributor Author

v1993 commented May 14, 2020

Bumping this. This is even more important than before considering further fixes and improvements, for me mostly but not limited to Lua 5.3 integers support.

@v1993
Copy link
Contributor Author

v1993 commented Dec 5, 2020

Another bump... It's been 3 years already. @pavouk?

@v1993
Copy link
Contributor Author

v1993 commented Jun 14, 2021

Okay, by this point we probably should make another lgi luarocks package if old one is no longer maintained or contact Luarocks staff to take over old one. It have been WAY too long without release.

@psychon
Copy link
Collaborator

psychon commented Jun 15, 2021

@v1993 I have no prior experience with luarocks, but I'd suggest to make a fork. No idea what a good name would be, but

  • I only have some access rights on this repo and @pavouk seems AWOL
  • I no longer use LGI myself

@ousia
Copy link
Contributor

ousia commented Feb 12, 2022

I don’t know whether I may be missing something (or even the whole thing 😅).

After #280 is merged (and since we may have GTK4 support [not sure about #278]), could we have a new release?

Many thanks for your help and your excellent work.

@psychon
Copy link
Collaborator

psychon commented Feb 13, 2022

could we have a new release?

Sure, feel free to do one. I guess you are in as good a situation to do a release as I am.

@Elv13 @Aire-One AFAIK you should have as much permissions here as I do. Any takers?

@ousia
Copy link
Contributor

ousia commented Feb 13, 2022

could we have a new release?

Sure, feel free to do one. I guess you are in as good a situation to do a release as I am.

@psychon,

many thanks for your generosity and the invitation.

I should have no permissions to make a new release (after all, I’m not even a collaborator [only a contributor]).

Besides, I have no proper programming knowledge (very basic Lua scripts with only very basic variables and functions).

All I know from that project is that it contains the Lua bindings for GTK+. It would be simply crazy that I released a new version.

Many thanks for your help.

@Aire-One
Copy link
Member

[...] @Aire-One AFAIK you should have as much permissions here as I do. Any takers?

I'm only member at the LGI organization. (I think even my PR's approvals doesn't weight that much (at least, they haven't this green background like yours 🤔))

I guess I can still update the README changelog section and push a new tag 🤷

@ousia
Copy link
Contributor

ousia commented Jun 17, 2023

@Aire-One, it seems that now you are the only member in LGI devs (https://github.com/orgs/lgi-devs/people).

I think that a new release would help a lot to have more current code as latest released version.

@Aire-One
Copy link
Member

Aire-One commented Jul 9, 2023

I'm only member at the LGI organization. (I think even my PR's approvals doesn't weight that much (at least, they haven't this green background like yours thinking))

I guess I can still update the README changelog section and push a new tag shrug

@psychon @pavouk, I can confirm I don't have the sufficient privilege elevation to push a new tag.

I have updated the README History in https://github.com/Aire-One/lgi/tree/prepare-0.10.0 based on the result of git log 0.9.2..master --reverse --merges --grep='Merge pull request #' ant cherry-pick of the “useful” commits.

it seems that now you are the only member in LGI devs (https://github.com/orgs/lgi-devs/people).

Nahh, don't worry... I'm the only public member, but there are other.

@ousia
Copy link
Contributor

ousia commented Jul 11, 2023

@Aire-One, from what I read in #225 (comment), @psychon wouldn’t have rights to release a new version either.

Only as an average user (not as a coder) and seeing things from the outside, I wonder whether it really makes sense to release a new version.

Please, bear with me. Forking the project (and asking @pavouk to transfer ownership of this repo in the meantime) , only makes sense when someone wants to assume the role as its maintainer.

The awesome WM depends on this project (as far as I can see). It might be a good reason not to abandon this project.

This is my personal opinion (as the rest of this comment), but if this project (LGI) has reached its end, it might be better to let it rest in peace.

Many thanks for your help and your contributions.

@Thomashighbaugh
Copy link

@ousia

Obviously I am not a contributor, nor have any membership in the LGI organization here or GitHub or otherwise but I thought it might be worthwhile to point out that while there has not been a new release in a while there is no reason to consider the project abandoned or even stalled, just the victim of people going AWOL without assigning to others a sufficient amount of permissions to actually create new releases (alternatively they could have assigned such permissions to no one else and forced the development to continue in the form of forks, which in some cases works well enough but in most cases leads to the project dying like "Way Cooler").

Some projects that are still used, such as the runit init system used by Void Linux and Artix Linux (among others), are dormant in terms of the underlying code as there is simply no reason for any changes to be made in its deliberately minimal code base. That's not a sign of project death but a pinnacle that some projects aim to reach, one where the code is at a place that it can continue to serve its intended functions into perpetuity without any more work from the developers. A sort of open-source development nirvana if you will.

But don't doubt yourself, if it is important to you to have it available via Luarocks, you are probably in the best place to maintain the package via releases and can pull any additional developments in this repo to your fork easily enough. You don't need an advanced degree in computer science to do that sort of thing, honestly with how scatter brained the people with those degrees are you might actually be in a better place without the thing.

What makes you a true coder or dev in the open source community is when no one else is doing something and you need the thing enough, through sheer force of irritation you just do it yourself. There is no government licenses issued for software developers (that I know of at least), so you are one if you consider yourself as much. Like the old Greeks said, "how many lies does it take before one becomes a liar? If he tells one less lie than that, is he still an honest man?" Reformulating that for our context here: how many lines of code does it take for one to be a coder? If he writes one less line than that is he still technically illiterate? This of course drives at the point, you are already sufficiently skilled to consider yourself a developer and quite capable of publishing releases from your own fork if you even know what Lua is, I believe in you.

As for a name for a potential fork, my advise would be to use lgi-ng for next generation, or something like that.

Hope This Finds You All Well

Thanks for the Hard Work on the Project to All Involved

gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Aug 18, 2024
luajit download server to tarballs stopped to work, which is expected,
since it was advised by the team in https://luajit.org/download.html:

"Please do not use obsolete versions from older tarballs or zip files.
Please remove any outdated links to these downloads — these links will
cease to work soon."

---

lua-lgi, on the other hand, is mostly abandonware right now, so it's
safe to use latest master. See: lgi-devs/lgi#225
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Aug 18, 2024
luajit download server to tarballs stopped to work, which is expected,
since it was advised by the team in https://luajit.org/download.html:

"Please do not use obsolete versions from older tarballs or zip files.
Please remove any outdated links to these downloads — these links will
cease to work soon."

---

lua-lgi, on the other hand, is mostly abandonware right now, so it's
safe to use latest master. See: lgi-devs/lgi#225
gnomesysadmins pushed a commit to GNOME/gimp that referenced this issue Aug 18, 2024
luajit download server to tarballs stopped to work, which is expected,
since it was advised by the team in https://luajit.org/download.html:

"Please do not use obsolete versions from older tarballs or zip files.
Please remove any outdated links to these downloads — these links will
cease to work soon."

---

lua-lgi, on the other hand, is mostly abandonware right now, so it's
safe to use latest master. See: lgi-devs/lgi#225
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants