-
Notifications
You must be signed in to change notification settings - Fork 130
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
GPL2+ LICENSE change and MAINTAINER change #710
base: master
Are you sure you want to change the base?
Conversation
According to approval from copyright holders - see: lpereira#530 lpereira#707
Simple test for GTK3, LIPSOUP2.4 only build
My contact details for video call: skype:speedy19742 discord:hwspeedy#6613 Looking forward to talk to you, thanx. |
pretty ironically .. the less free software social networks in the world do you know it? 😆 |
@lpereira - Any timeframe for getting this small PR into the repo and get the repo transferred? I have made a lot of maintenance and would like to work on the repo and make a pre-release with known issues from test of 21 distros. |
Look, I'm going through some difficult things in my life right now, so things will take some time. I can't commit to any timeline, just promise that these changes will be looked at when things calm down. |
Version 2, June 1991 | ||
Valid-License-Identifier: GPL-2.0+ | ||
|
||
GNU General Public License v2.0 or later | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mckaygerhard - I am trying to keep the community together.
- so my repo was scratched to make this commit as small as possible. This PR is all that is needed to move forward - GTK3 with uber-graph with correct licensing and a maintainer change, so that we all can help on this project.
As soon as @lpereira has transferred the repo, I will recreate discussion for entire project.
I have around 20 commits lined up for you and others to provide feedback on. And we have a discussion about dependencies for packaging. It will be fun - we will get hardinfo released.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok got it.. lest wait until responds, lest have a bit of patiente
@lpereira - Hang in there - you will get through it. All love from here ❤️ Let me take this hardinfo maintenance of your shoulders - it will be good, I promise you. And you will come back to something positive as the hardinfo release. 3 tasks are required to keep the community together:
DNS setup |
@lpereira - Just wanted to say hi and give you a status I have with some guidance from @mckaygerhard created a community version of hardinfo and named it hardinfo2: https://github.com/hardinfo2/hardinfo2 Have a look - there is even a working pre-release with known issues. Everything is branded hardinfo2 - executable, domain, etc. This way it does not disturb your private domain, sorry about that. And the community can continue going for release. I also thought about the repo transfer (private maintainer switch) - That will probably be a bad idea - so many commits are pointing to your private repo. I want to ask you if you want to be a second maintainer on hardinfo2 organization? - I want to have 3 maintainers at all times and project developers will have direct access to committing CI/CD like scheme. It will keep the developers happy and thereby the users. The third maintainer - I was thinking about is you @bp0 - you have made so many commits and have your heart in this project. So I will be sending you an invite also. @mckaygerhard has developer access + issues access. I will start inviting - this is just a heads up. PS: You don't have to do any maintenance/development/etc. now. Br hwspeedy |
I tried adding you on Discord, but the username |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi. Why did you remove support for the e2k (Elbrus 2000) architecture?
The source code for the Linux kernel and other software is available on the organization's website.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi, could you please specify which license you requested to change to and mention that you haven't received a response? It seems that the current license is already "version 2 or later," as indicated in the commit: aeacb71
Found. No answer from @EntityFX here #707 (comment)
@EntityFX pls say yes for GPL2 -> GPL2+ :)
UPD: @EntityFX agreed #707 (comment)
- sudo apt install lm-sensors sysbench lsscsi mesa-utils dmidecode udisks2 xdg-utils | ||
- hardinfo | ||
|
||
**Fedore/Centos/RedHat/Rocky/Alma/Oracle** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fedora
HardInfo is now being maintained by @hwspeedy in a different repository -- https://github.com/hardinfo2/hardinfo2 -- I suggest sending a new PR there adding e2k support back. (This wasn't the intention, at least from my part, but I apologize for the inconvenience.) |
this seems replicated in newer repository i also stopped tocontribute becouse of the good intentions @hwspeedy seems being too fast and do not prepare so good the path of the things |
This is the smallest pull request needed to prep for fixes, refresh, update, testing, webpage, etc. and finally release of hardinfo.
FIX: GTK3 now working.
ADD: Package building via CPACK (WIP)
Updated Doc README.md