Replies: 4 comments
-
E.g.: u-root minimum kernel requirements. For LinuxBoot and for u-root as its own thing. https://github.com/u-root/u-root/tree/master/configs says the configs are for tests. We should make that not so. |
Beta Was this translation helpful? Give feedback.
-
I wonder how many of us will be at the firmware workshop in june and if we should put part of our time into making this better. |
Beta Was this translation helpful? Give feedback.
-
Maybe some topics could be added to the OSF Hackathon: https://docs.google.com/document/d/1YsxFkX1CgHdRFf-updioOIO4BPH47Oz78invd6y9ryU/edit#heading=h.qbqupv1g13wg |
Beta Was this translation helpful? Give feedback.
-
I've taken the liberty to add two points to the agenda, I'll be there and as a newcomer I can express some of my frustrations... |
Beta Was this translation helpful? Give feedback.
-
Hey all,
I've made some observations I want to remark on in the last few months. Apologies for the rant-style... just on my mind today.
u-root isn't a Google project, but de facto those of us at Google provide >80% of the contributions - I would like that to change.
The four largest contributors to u-root and fiano are, naturally, the four of us working full time on LinuxBoot at Google. After that, the number of contributions and LoC or whatever drops off steeply. Most of the ones after us are our former interns. Yet, anecdotally, LinuxBoot is seeing pretty good adoption, from the stories people tell us.
At the same time, anecdotally, I've told many people that u-root might contain some good first projects for people who want to learn Go. A lot of the commands we have are very self-contained, very testable, and there's often work to be done on them. Yet - none of them ever do. (And I didn't expect a high conversion rate.) And external LinuxBoot users don't seem to be contributing back much. Are they just taking u-root as is and happy with it? I doubt it, we have lots of problems and bugs. And many contributors that do start often drop off after a few commits. Why is that?
There are probably some "all is good" reasons for that, everybody gets busy, but more than likely there are things we can do to improve. After all, the long-term vision of the project is for us all to collaborate and share knowledge and code.
A few things I've gathered:
Bad for adoption
Bad for newcomers
Some Ideas
Inspired by @bobcatfish's talk at the Open Source Summit (yes, months ago).
Github issues need more context.
Enforce godoc standards for code.
Enforce real commit messages w/ real context.
We need one unifying landing site for open source firmware.
???
Looking For Feedback
What can we do better for you to be excited to work on u-root?
Beta Was this translation helpful? Give feedback.
All reactions