-
-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
Giveaway: Armbian & Khadas are rewarding contributors #7002
Comments
This comment was marked as spam.
This comment was marked as spam.
We are going to pull a random draft on upcoming meeting: Who got to the pool? (part 1, divided into two parts due to GitHub limitations) @adeepn |
Part2 @lanefu |
I don't want to participate in the giveaway as i don't care for proprietary hardware since it's useless brick to me. Thanks for remembering me though |
Writed from an iphone connected through a Huawei wifi router over a starlink connection using an AT&T Submarine Systems |
If you have to ask.. written by hardware engineer and hackerspace member from heavily modded OLIMEX Teres-1 managed via NiXium through Quactel EG25-G running an open-source firmware which is partially routed over pilsfree infrastructure.. :p If Khadas starts to make OSHW products then let me know i would be happy to help with kernel development and downstream maintenance.. Especially if it's decent RISC-V since the TH1520 i have is piece of vulnerable trash rn due to GhostWire and i am looking for better replacement as i can't yet make a better one through tinytapeout. |
If proprietary software, that came with Allwinner A64 SoC 10 years ago, and all other peripheral components, would not be reverse engineered and re-coded, mainly by Sunxi and Armbian community, Pine community was dealing mainly with modem, you would not be able to run (mainly) opensource software. The same goes for other hw. They are all proprietary by design, especially in ARM world.
Open source hardware is a concept. Like democracy, freedom, laziness, ... just a buzzword, sales label. You would only offer help to open source developers community when all the hard work is either done and/or hardware obsolete? ;)
Most of the peripherals around riscv64 cores are also pretty much proprietary. |
Rather critically important functionality that you need to adjust your business plan to be able to maintain economy e.g. what OLIMEX does as i can't easily fix the device e.g. OlinuXino-A20 that had multiple broken components as it was pulled from a heavily modded commercial 3D printer (Ultimaker <3) that experienced significant overvoltage due to failed experiment and i was able to fix it under 20 minutes through just looking on the kicad project vs. RockPro64 that PINE64 scammed me on by getting me a device that broke after 1 week of collective <10 min runtime that is not covered by any kind of warranty and i can't fix it without exposing myself to potential infringement lawsuit due to them releasing schematics under GPLv3 that does not cover hardware and indirectly threaten me with lawsuits if i were to use those and make gerbers for them which i intend to do anyway once i handle the legal part in more sane way. .. in addition to being unable to turn the product into actual projects like the OlinuXino-A64 i am constantly making new PCBs for these to have RP3-comparable device for <3 EUR in PCBs (that i can make in hackerspace) and including components. Releasing SBC without getting the schematics and gerbers just doesn't make sense for anything that i do to justify investing time to that and i consider working on those products as unethical as i am basically just enriching some evident bad actor that doesn't care for open-source and rather uses small investment to make themselves seem like they care in exchange to make ~€€€ €€€ EUR through getting the additional mainline support which i really hate that armbian does that in addition to keeping products alive that do not follow sane standards (SBBR, EBBR) or are painfully obvious engineering malpractice like some silicons are and would prefer them out of support by armbian as you are making money out of making the life for people who work on open-source more difficult. (Not implying that the TH1520 is engineering malpractice, i consider that a brave step towards riscv development including all of it's hardware bugs that are very fixable in next iterations that i will be getting to aid further development)
Sadly.. Though the BeagleDevs are trying to manage/fix the issue through BeagleV-Beyond for me to be happy to help with development. |
@Kreyren When you transcend the limits of being a simple participant in the technology industry and reach fulfillment in your achievements, you may notice that certain desires originally take shape within yourself. This moment may bring you an ambiguous feeling, where the original charm of pursuing a lofty goal mixes with other less clear motivations. I hope that, throughout this transformative journey, you will keep your essence intact and avoid being swallowed up by the flexibility of excessive ambition. Remember that many ventures, initially driven by purely altruistic and innovative purposes, end up being shaped by market pressure and financial demands. I am aware that this exchange may not be the most direct or transparent encounter you were looking for. Each chosen path has its unique nuances and specific complexities. May your efforts always be blessed by a higher power. |
I am happy!!! |
Shipping data here: https://www.armbian.com/update-data/ |
Hey, many thanks. Thats an awesome looking product! |
Congrats! |
🥳
|
congrats! |
Armbian’s developer community is the backbone of our success, dedicated to maintaining and updating a wide range of devices. To ensure our long-term sustainability, we need ongoing contributions that support our core infrastructure, including the build framework, OS components, and more.
Introducing the Armbian Contribution Reward Program:
We are thrilled to launch this initiative to recognize and reward the incredible contributors who help keep Armbian running smoothly. This program not only celebrates your hard work but also clarifies the roles of hardware manufacturers and the larger community in maintaining software support.
How to get to the pool? Who can participate?
Pull requests authors that will complete their work awarded with a special tag https://github.com/armbian/build/labels/Giveaway
Active community members that will be nominated by anyone and approved by at least one moderator
Regulars and first time contributors are both welcome!
You qualify by contributing to:
On October 15th, we’ll hold a random draft to select a winner from the pool.
Rewards:
One lucky winner will receive premium and one standard Khadas Mind portable workstation, both with dock, generously donated by Khadas.
How to Get Involved:
Dive into any of the eligible areas and make a significant impact on Armbian. Your contributions not only support our community but also give you a chance to win an amazing reward.
For more details about the reward, visit Khadas product page!
Let’s join forces to keep Armbian thriving and growing!
The text was updated successfully, but these errors were encountered: