Skip to content
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.

Sign up for GitHub

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

start collecting feedback from OE/Yocto users #281

Merged
merged 2 commits into from
Feb 28, 2020
Merged

start collecting feedback from OE/Yocto users #281

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f5d5f39
configure prettier to wrap markdown blocks of text
cbrake Feb 27, 2020
cb5376d
start collecting feedback
cbrake Feb 27, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .prettierrc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1 @@
proseWrap: always
12 changes: 12 additions & 0 deletions docs/oe-yocto-feedback.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,12 @@
It is no secret that OpenEmbedded/Yocto has a steep learning curve. Many people
who try to use it get discouraged and write it off as porely done and impossible
to understand. This is one of the problems the motivated us to create Yoe.

Below is some of the feedback we've collected and links to various discussions.

- If a build breaks, it is not always obvious what went wrong. If there weren't
Google, I'd be dead in the water!
- If I modify some code in a package, how do I know that a bitbake will properly
pull in my changes and rebuild what I want it to? I'd expect that a simple
bitbake would do what I'd think it should do, but in some cases, it does not.
- https://news.ycombinator.com/item?id=21677639