-
-
Notifications
You must be signed in to change notification settings - Fork 501
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
DietPi-General | Restructure of supported images #1281
Comments
I just created a single image so far, so have limited experience about how much work it does to support that much devices. But my impression is, that one special strength about DietPi is, that it does support so much different devices. The main developer of NextcloudPi already shared a thought about switching to DietPi as a grounding platform, because of that. Obviously it is not easy to provide software well working on different hardware, especially if it's about Linux, ARM etc. and involving sometimes many software working together. But we gathered now many experience here about that, and my impression is that it worked not too bad. The most issues occurred not because of different devices, but because of issues "outside" of DietPi, problems with PPAs, apt package issues, changed software commands etc. Those issues will occur also, if we support less devices and are solvable mostly for all together at one. Of course image creation is a topic. If we focus on that, trying to automate the process as much as possible, this would be great. Also it would be nice to find other people, owning a certain device, willing to regularly create an test the related image. But that's another topic again... Long story short, supporting many different devices is a strength and not a weakness, and we first should thing about how to reduce the workload, this produces (mainly image creation), before dropping it completely. |
👍 Maybe a solution would be to class these images as lower priority, and make user aware of?:
|
Do this for a VM is relatively fast, if you don't own ten years old hardware like me. Messing around with several SBC, SD card, old images versions be a mess, a very slow and time-consuming process.
Yea! 💯 👍
Yes. Und, damit das nicht falsch rüber kommt, ich persönlich bin mehr als froh, dass es im Moment so gut läuft, etwas Bewegung in die Sache kommt, ein Überdenkungsprozess begonnen hat und du Dich in dem Gesamtprojekt mit so großen persönlichen Einsatz einbringst. Danke dafür. |
The main problem in my eyes is, things have change over the time so many times:
... but by all changes, we never discontinue support for historical stuff and devices. At the beginning it was not a big problem, because @Fourdee has enough time and energy to keep hold all the balls rolling. So I have a long time reflected, how we can get a better situation for all of us, for user and the project. https://github.com/Fourdee/DietPi/issues/1257#issuecomment-347275265 The only solution I see at the moment, to get a better long-term situation, is to discontinue support for for historical stuff (software) and devices. To put it bluntly. And please keep an eye on, I'm not a coder or can help out to keep things rolling. It will be your arbitration. |
@Fourdee |
Yes we, I or you can do this by DietPi Survey. But, as always, it's very time consuming to get a statistic out of this. |
"Shall I do this, if I get some spare time?" Generally, I like the idea to mark certain devices and software as low priority/no active development and imform users about this (instead of completely remove it). That way we can also ask for maintainers, people who use the device/software and are willing to at least help maintaining it. If someone is found, we can unmark the device/software as long as maintainer is there. I e.g. will check in for Nextcloud+ownCloud, RPi (at the moment just testing, figuring out a way I can create image without disturbing production system) and VirtualBox Image creation+testing. |
I like as well to see this. And please as well a traffic statistic for the past 12 month But only @Fourdee can share this information with us. |
Device and Version statistic by
cute-of date: 10-12-2017 Installations:58,113 Debian ReleasesDebian 8 "Jessie": Debian 9 "Stretch": Other: DietPi Version:Used on devices:
DietPi v15x at detail:
All Devices:58,113 All "Raspberry Pi" Devices:36,191 Device: "RPi " Device: "RPi A " Device: "RPi A+ " Device: "RPi B " Device: "RPi B+ " Device: "RPi 2 " Device: "RPi 3 " Device: "RPi Zero W" Device: "RPi Zero " ALL "Odroid " Devices:4220 Device: "oDroid XU3/4 " Device: "oDroid C1 " Device: "oDroid C2 " Device: "oDroid U3 " All "OrangePi " Devices:9012 Device: "OPi PC2 " Device: "OPi Prime " Device: "OPi Win " Device: "OPi Zero 2 " Device: "OrangePi Plus " Device: "OrangePi Lite " Device: "OrangePi Zero " Device: "OrangePi One " Device: "OrangePi PC " All "BananaPi " Devices:579 Device: "BananaPi M2+ " Device: "BananaPi Pro " All "Pine A64" Devices:1234 Device: "Pine A64 512MB" Device: "Pine A64+ 1GB" Device: "Pine A64+ 2GB" All exotic or new devices:898 Device: "RoseapplePi " Device: "Asus Tinker Board " Device: "A20-OLinuXino-MICRO " Device: "Cubieboard 3 " Device: "Beagle Bone Black " Device: "Sparky SBC " Device: "Native PC " All different VM'sDevice: "Virtual Machine " unkown devices:2685 . . . |
wow ... 😳 Hmmm ... 😔
😃 😉 |
@k-plan |
|
yes, correct 21-03-2017. But online device will refresh their report from time to time.
no, 10-12-2017 18:31 , because I have to download them to get it seached ... no rights to do this on your server. And please let it as it is. It's okay. Thanks for the report! 👍 |
I changed
You have every right 👍 |
https://de.wikipedia.org/wiki/Wikipedia:Schreibweise_von_Zahlen#Dezimaltrennzeichen We don't live on a island, but is okay! 😄 Was only decimal point to get it more readable here. But for sure 🇬🇧 next time. Promised. |
Do I interpret this right? Average DietPi user is RPi owner, running Nextcloud? Hmm I am soo totally average it seems 😭 😆. Note to myself: Opt out survey with my testing VMs 😉. |
Marking as closed, in place of: https://github.com/Fourdee/DietPi/issues/1385 |
For discussion/consideration.
The text was updated successfully, but these errors were encountered: