Can I help getting hardinfo out for a new release with online benchmarking capabilities?

hwspeedy commented 10 months ago

Hey L. Pereira,

First - great tool - loved it for a decade!

I would like to help get the hardinfo to a new release with the benchmark submit and synchronization working.

STATE:

I have your GoLang web benchmark/blob server up and running at http://hardinfo.bigbear.dk, that has been lost&missed for many years. Anyone feel free to use it, thanx.

give it a go from updated repo https://github.com/hwspeedy/hardinfo - just build as normal

PLAN:

Only newer machines (Those running now from all architectures) - starting with empty database - not even the json.
Adjust algorithm to give the most accurate comparison possible. It is pretty darn open and vulnerable too. (WIP)
Use https://api.hardinfo.org as API interface - so it won't be broken again and can be moved around.
- guess you are giving the domain to the project, right?
Pullin the long overdue PR that every one wants to move forward - See https://github.com/hwspeedy/hardinfo (WIP)

NEEDS:

Access to/create a lets encrypt certificate for the domain.
DNS setup for the domain to get traffic to server.
Re-enable the synchronization as default build option in the repository - (DONE - just missed updates to readme)
Data from lots of machines - here the community will hopefully help and clone the git and benchmark their computer. Please boys and girls - who does not like a benchmark - Let's get it working.
Your help in releasing a new package for Debian/Redhat and all derivatives. We need to regain control over the synchronize API interface, that is currently lost to click advertising (SPAM) company. (WIP)

Let me know what you think, thanx.

Br

Hwspeedy, Denmark.

lpereira commented 10 months ago

The new API server is already running on api.hardinfo.org -- but thanks for setting it up elsewhere too, and being interested in releasing a new version and maintaining hardinfo. It's been a long time coming.

I took a look at your repo, and there are some interesting fixes. I can cherry-pick some of them, but not everything; for instance, the licensing change can't happen without the ack from the copyright holders (not everything in the project has been written by myself) and contributors, which isn't that trivial. It might be easier to port the old graph drawing code to a new GTK version rather than changing the license, unfortunately.

hwspeedy commented 10 months ago

Hi LPereira,

Yeah, I kind of see your strugle - so close for so many years - lets see if we can get it released.

Regarding license change from GPL2 to "GPL2 or later" is so small but so important - The application cannot be released with LGPL & GPL3 code and GPL2 by distributers.

This application and source code could potential vanish and no developer wants that.

It is a great program - but the code is pretty basic.

I therefor applied the minor license change to GPL2 or Later as you had agreed for the main part of source code and other parts are so small and old.

/hwspeedy

hwspeedy commented 10 months ago

It seams the hardinfo.org domain is not configured correctly.

https://hardinfo.org has self signed ssl.

http://hardinfo.org redirect to github - works.

If you go to https://hardinfo.bigbear.dk - you can see the results - just a very simple view. It could show so much more and a unique ID transfer to the benchmark page could give you informations like: your type vs world - are you in lower or upper for this type. Distro variation - which is faster - which is becoming faster etc.

The SQLite3 struggles so it needs a LAMP server instead with a mysql server. Fairly simple but first we need numbers to crunch and happy users to serve.

hwspeedy commented 10 months ago

I have put a notice in the readme.md file if any one has any problem with the license change - so that people can get the code removed from project, instead of the entire project goes to waste. That should be more than sufficient.

https://github.com/hwspeedy/hardinfo : The License has been changed in 2024 from GPL2 to GPL2 or later due to the existence of some LGPL & GPL3 code. If you have any code in this repository that you would like removed, just open an issue and we will remove it, thanx.

Is it possible to schedule a meeting with the following topics :

GPL2 or later
Maintainer
Domain
Status
Testing
Release for Distros

Br

hwspeedy, Denmark - skype: speedy19742

lpereira commented 10 months ago

Please don't change the license without the consent of the copyright holders, or people that wrote the code. That notice in the README file won't cut it. I understand you're eager to help, but this isn't the way to do it.

hwspeedy commented 10 months ago

We need to change the license for this to move forward - GPL2 is stopping this project now and will continue to do so. Big parts are already GPL2+ or LGPL, GPL3. You agreed to change your part to GPL2+. Burt P (The largest contributer) has already changed or is using GPL2+. @bp0 Christian Hergert already uses GPL2+ on his additions. Changes/fixes do not have influence on license, so they can be discarded. Left is very little code - if any.

Can you tell me which code is of concern to GPL2+?

hwspeedy commented 10 months ago

I have gone through the code once more to see if something is wrong for GPL2+ license.

I have used the following script: (minus the .txt ending) check_licenses.sh.txt

I got this file as output checked.txt

It clearly shows there are NO problems with GPL2+.

Can we all agree to move on and get this project released as GPL2+?

I know that you just want to be really nice to all the contributions, but look at all these beatifull contributions that are being put into the garbage bin...

Fedore, redhat has remove the program. debian is asking for help. People want it.

Is it okay for me to move on - then please agree to merge all the changes back into the repository and transfer the repository to me. I will maintain it until someone else wants to.

We are close to a release after more then 10 years... - Please help.

Here is the complete change: https://github.com/lpereira/hardinfo/pull/708/files

hwspeedy commented 10 months ago

The following email was sent out today - It is also possible to answer in this thread, thanx

Dear contributor for github project hardinfo

We want to change the source code license from GPL2 to GPL2+ for the hardinfo source code.

This is part of a reboot for the hardinfo project, which has not made a release in 10 years and is being pulled from distros.

I think that is a pity and has stepped forward to maintain and try to release "hardinfo".

Please reply "GPL2->GPL2+ OK" or "PLEASE REMOVE MY PART and describe it"

./hardinfo/hardinfo.c ./hardinfo/gg_key_file_parse_string_as_value.c Copyright (C) 1995-1997 Peter Mattis, Spencer Kimball and Josh MacDonald ->PLEASE HELP WITH EMAIL - JUST FORWARD, THANX Copyright: Jens Låås, SLU 2002 */

decode-dimms.pl by Philip Edelbrock phil@netroedge.com, Christian Zuckschwerdt zany@triq.net, and Burkart Lingner burkart@bollchen.de

x86cpucaps by Osamu Kayasono jacobi@jcom.home.ne.jp

PS: IF YOU KNOW ABOUT ANY OTHER WHO SHOULD SAY OK, PLEASE FORWARD THIS EMAIL, THANX.

Communication thread:

https://github.com/lpereira/hardinfo/issues/707

Thank you all very much,

Best Regards Søren B. Kristensen hwspeedy

zuckschwerdt commented 10 months ago

GPL2->GPL2+ OK

lpereira commented 10 months ago

It might be easier to port the graphing code from GTK2 to GTK3 than coordinating all the license changes, to be honest.

hwspeedy commented 10 months ago

Im not afraid of work and it is now or the project is gone.

Source code GPL2+ is future proof and safe - allows for use of GPL3/LGPL2.1+ for future developers.

I have sean this project die - It was the last program on my PC 10 years ago, that still used GTK2. I see no development nor anyone jumping in to help right now. We need new developers!!

So my opinion is that the source code must be changed to GPL2+ now for as much as possible to support the future developers.

Please spread some love - share the word and get as many as possible to write "GPL2->GPL2+ OK" for their copyrighted GPL2-ONLY source code submit, thanx.

zuckschwerdt commented 10 months ago

decode-dimms.pl was always GPL2+

hwspeedy commented 10 months ago

Thanks @zuckschwerdt - I did not consider that some of the remaining source files already were GPL2+ and LGPL. I have not heard from largest contributer @bp0

Most of his work is already GPL2+ and if he also agrees for some remaining files to become GPL2+ - we are down to four files from 2 persons:

hardinfo/usb_util.c: * Copyright (C) 2019 Ondrej Čerman - GPL-FIXME @ocerman
modules/devices/firmware.c: * Copyright (C) 2020 Ondrej Čerman GPL-FIXME @ocerman
includes/e2k/processor-platform.h: * Copyright (C) 2020 EntityFX GPL-FIXME @EntityFX
modules/devices/e2k/processor.c: * Copyright (C) 2020 EntityFX GPL-FIXME @EntityFX

bp0 commented 10 months ago

GPL2+ is fine, I think.

ocerman commented 10 months ago

GPL2->GPL2+ is fine

hwspeedy commented 10 months ago

Thank you all so much - We are now GPL2+ :)

I have removed E2K architecture support and submitted changes to PR.

@lpereira

Please check PR for submission, thanx.
What about the hardinfo.org domain - can the project get that? I can pay the yearly cost.

https://github.com/lpereira/hardinfo/pull/708/files

Release - here we come...

lpereira commented 10 months ago

I'll check the PR as soon as I have some time. As for the domain, I want to retain control of it; I don't mind paying the yearly cost.

hwspeedy commented 10 months ago

@lpereira Thanx,

Regarding the domain - just to clearify - I think we have the same considerations and wishes to be 110% sure that this project always has access to the domain - especially considering the past. As I understand you - you are giving the domain to this project and will do changes etc. to the domain for this project - Correct?

How do we ensure access to the domain? - shit happens - as berlios.

Wouldn't want to update all these distros just to loose access again.

My alternative plan was to buy a domain and let 3 people in the project have access to change it and transfer it.

We cannot be the only FOSS program to need a domain that is certain to be within the project - anyone know if there is any help for these problems from FOSS organisations?

mckaygerhard commented 10 months ago

@hwspeedy in your pull request #708 there are some things that must be considering, into README and also into packages, by example many many external tools not mentionen to able to work fully yhe hardinfo that are only runtime depends.. i only said that dont make a release yet until i trak all need to run fully all the hardinfo features in proper documentation.. i could made it next weekend or during the week

lpereira commented 10 months ago

The previous subdomain ceased to exist because I was using a free hosting service that stopped hosting open source things. That's one of the reasons I bought the domain. However, I've had this domain for many years and I've been using it for a lot of personal stuff (including email, which is used for some accounts I use regularly), so I hope you understand I can't just hand it over.

Also, the subdomain api.hardinfo.org should be configured correctly -- CNAME pointing to tia.mat.br, and that with an A and an AAAA record, all pointing to the same machine, running the server that's in the server branch. There's an automated Let's Encrypt bot refreshing the TLS certificates, and I receive notifications on email if anything stops working. The server runs a few other things, including my personal web page, so I don't mind paying for it; it's just a cheap VPS I've had for quite a while.

Since there was no web page for a while, I haven't really set up hardinfo.org or www.hardinfo.org properly, but it's just the matter of sitting down and doing it. We may even host it on GitHub so it's easier for more people to update the web page.

hwspeedy commented 10 months ago

@lpereira Fully understand that the domain is yours personal.

hardinfo.org - is just perfect for open source project hardinfo - I really like the www.hardinfo.org, hardinfo.org and api.hardinfo.org - if you can set these 3 up for the project and promise that hardinfo project can get the domain when you no longer needs it. That would be fine for me. Is that possible?

Anyone prefer I buy a domain and share codes to highest contributers?

The plan is to get more developers active in FOSS on hardinfo project - I think the server part can also inspire some people to join the project. So many possibilities and fun.

I have made a small demo page, that is meant to go on www.hardinfo.org and hardinfo.org. It is currently active on https://hardinfo.bigbear.dk

Serverparts won't run on github directly. API and WWW on same server easiest solution as we want open source development of both. Github pull from server every hour is my plan for opensource development on the server. Some scripts for database changes via github. - We will make it work.

Release will be with your GO server - after release and bugfixing is done, it will be upgraded to LAMP.

I will submit demo www, when you have accepted the change and transferred repo. So all can start changing and commenting on that part also.

PS: What do you think about my creativity - The refreshed LOGO? Enhancing information->looking glass, Report and Benchmark, check! - Please don't kill me :) https://github.com/lpereira/hardinfo/pull/708/commits/27358d65551f1fce73816cfd8f75fc575b24518d

DNS setup hardinfo.org IN A 94.237.111.86 hardinfo.org IN AAAA 2a04:3544:1000:1510:681a:4eff:feb6:3f2f www.hardinfo.org IN A 94.237.111.86 www.hardinfo.org IN AAAA 2a04:3544:1000:1510:681a:4eff:feb6:3f2f api.hardinfo.org IN A 94.237.111.86 api.hardinfo.org IN AAAA 2a04:3544:1000:1510:681a:4eff:feb6:3f2f

hwspeedy commented 10 months ago

@mckaygerhard Don't worry - we will get you up and running again. First we need to complete transfer - then a new prerelease. Then I will contact you for more information as I don't see nor understand the issue - but we will get it fixed.

Regarding the CMakeLists file, that will be changed during and after release - the goal is for all distributions to could use this file as much as possible. Then developers and distro maintainers have common ground.

hwspeedy commented 9 months ago

oldmaintainer: @lpereira dev: @zuckschwerdt @bp0 @ocerman @TotalCaesar659 reviewer: @mckaygerhard

How do we move forward?

I have made a lot of minor fixes, code upgrade and GTK3 is now working and the project documentation is being updated and a webpage and refresh of logos etc. I have made packaging and a test setup for the different distro flavours to actually test and verify the code. All in all - some 60% of the missing maintainance for the last 14 years. There is still a lot of errors and fixes and dokumentation updates needed.

@lpereira has not accepted the PR and transferred the repo and I am stuck in my maintainance process - getting ready for release - I want to submit a prerelease with status for the entire project (All branches).

@mckaygerhard wants to make a toplevel organisation hardinfo. Who will maintain that extra level? He votes for not submitting the maintainer change! - Which means he does not want to release - There is 10 years of issues/PR to handle and alot of work before and after release - with a maintainer that has openly and frankly said she don't have time and is moved on, but might be back if the project is released.

My way of moving forward is CI/CD inspired with test - we can always blame a change. Every active person is member of the project and can submit to the project - it is all about everyone feeling part of the FOSS project.

Please developers give your words: @zuckschwerdt @bp0 @ocerman @TotalCaesar659

Can we keep this project together or are everyone worn out and moved on? - In that case I will have to do hardinfo2 for release.

Br

Hwspeedy

zuckschwerdt commented 9 months ago

I can't really contribute to the discussion and effort, I only worked on part of a project later used by hardinfo.

mckaygerhard commented 9 months ago

Who will maintain that extra level? He votes for not submitting the maintainer change!

err nono! not per se!

maybe i means the people that are interested being honored into such organization..
noted that you @hwspeedy have done so much that now you are super involved without avoiding it :laughing: :smile:
maybe @lpereira not have much time anymore but as an honorary member and author he may casually make small contributions
i am so hater of any Windo-related, so not recommended to being a honored member but i can organized and take tags over the issues.. limited me to do not answered those, documented and contributed occasionally
maybe @bp0 its currently inactive but he contributed so much and must be a honored member of the future organization, in future maybe he wants to contribute again

We are aware that at some point we are all going to be busy, some with the devil and others with GNU, but in the end we are all here, helping the project, even if we don't have time, from time to time someone of us could give two or three minutes and do something... and if others see these, more contributors will emerge that we can guide and eventually pass the baton

hwspeedy commented 9 months ago

@mckaygerhard

"maybe i means the people that are interested being honored into such organization.." There is no honorable position for making FOSS - you do it because you love it and feel good about it. The reward is seeing users use it along with a bunch of bugreports :)

"and if others see these, more contributors will emerge that we can guide and eventually pass the baton" How is that working out? - The project is on the verge to be old electrons of no use. You all know that.

Any one can contribute to FOSS and the users decide which flavour they like.
There is no control or passing the baton after death - you give your work at every commit and hope it will be usefull.
I have seen a nice PR in this project not taken in eventhough a blind person tested it. humor but wtf!

All commits and alot of other projects have bought this app to what is now. Good job - but that does not make anyone entitled to be a controller as you describe. Nor should anyone want that - it will scare off developers and the project with branches will die.

PS: What is this fear that you are having? - If you really don't like one repo - just fork it and make your own flavour.

We develop together - All are welcome! ❤️

lpereira commented 9 months ago

* maybe @lpereira not have much time anymore but as an honorary member and author he may casually make small contributions

I'm not a man.

lpereira commented 9 months ago

There has been a lot of discussion here. I'll look at them whenever I'm less swamped and reply appropriately. This might take a while, but be assured it'll happen. The same goes for the open PR; I'll take a close look at it soon, but it'll take some time to go through that.

mckaygerhard commented 8 months ago

There has been a lot of discussion here. I'll look at them whenever I'm less swamped and reply appropriately. This might take a while, but be assured it'll happen. The same goes for the open PR; I'll take a close look at it soon, but it'll take some time to go through that.

@lpereira Watching the recent events, I have noticed that no matter how much I try to get things to get working for both projects, it seems that the forked project is not a good idea and you were right to be patient since @hwspeedy latest actions give a lot to talk about...

I stayed alert. margin in the new project trying to allow both to coexist, I suggested that he rename so as not to have problems..

*. it reaction was to remove me and deny me access... which is not very healthy for distros if a package maintainer did the same, only cos i requested to rename the project to another name.. cos he is trying to gains famous using the old name

mckaygerhard commented 7 months ago

hi @lpereira i see the notes in new hardinfo2.. i agree on the movement.. the only thing is that server page is made in ancient and deprecated tech (mysql+php)

github already provides containers and actions with auto builds.. so i guess is the only problem we have with @hwspeedy that seems is great with C/C++ but not the best with web tech..

also moves many parts of the project that let alone the contributors .. seems many are lost in credits

EntityFX commented 4 months ago

Hi, I agree to change license to GPL2+ of e2k source files:

includes/e2k/processor-platform.h modules/devices/e2k/processor.c

Toxblh commented 4 months ago

Thank you all so much - We are now GPL2+ :)

I have removed E2K architecture support and submitted changes to PR.

@hwspeedy Could you pls return E2K?

EntityFX agreed ^^^

mckaygerhard commented 4 months ago

"due missing answer" .. we as humans have busy time.. so inclusion is not relate to response.. fixed https://github.com/lpereira/hardinfo/pull/710#issuecomment-2221594193 @Toxblh

this is the reason why some people stoped to contribute.. too fast and discharting way of thinhgs.. one person wants to develo a new service for the remote part but we still see server side older techniques in hardinfo2 event use nextjs

lpereira / hardinfo

Can I help getting hardinfo out for a new release with online benchmarking capabilities? #707