-
Notifications
You must be signed in to change notification settings - Fork 13
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
Projects page adjustments #229
Comments
I see code review as part of software expertise since it's the same people who write and review? It's regular development process not a specific role. Proof read is part of technical writing similarly. For Meshstream flashing LibreRouter is necessary. It's not an intuitive thing to do for most people. |
It was required only because we where using a prototype of a device that has not yet been released. This is why flashing using uboot was necessary. I don't think we will be getting anymore device and librerouter would never expect their users to even know what u boot is. Therefore i don't think that having the skill to low-level flash routers is a requirement to work on mesh stream. Only time you should be using uboot is if you brick a device and need it unbricked. Unless you want to open meshstream to other devices beyond librerouter i don't think its a "skill" moving forward as general knowledge of how a website works. |
Okay we can drop that. The current instructions definitely need that though. |
From @darkdrgn2k:
For "skills": Add something like "documentation writing", "proof reader" and/or "code reviewer" to most of the tech stuff (prototype mesh orange etc)
"Flashing routers" is not really needed for mesh stream
The text was updated successfully, but these errors were encountered: