-
Notifications
You must be signed in to change notification settings - Fork 2k
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
README.md: add reference to FAQ #21061
README.md: add reference to FAQ #21061
Conversation
README.md
Outdated
[comparison][faq-riot-vs-others] of RIOT with other operating systems for | ||
embedded and IoT devices [in our FAQ][faq-riot-vs-others]. | ||
|
||
[faq-riot-vs-others]: https://www.riot-os.org/#faq-answer-12 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
somehow the riot-os.org "lazy-loader" / "don't make me click" thingy is not able to deal with the anchor (at least for me might be browser dependant)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh, it does indeed only work when the FAQ entry is already expanded. (I did so to search for the anchor and then tried out the link in the same window. Apparently Firefox does skip rendering the page new when the link is identical except for the anchor - which makes sense.)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not ideal the latest fixup. But probably better than a non-working link.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#faq-12
seems to work ( at lest goes to the question )
At the bottom the related projects section in the README.me, this adds a reference to the in-detail comparison between RIOT and related OSes in our FAQ.
00c205c
to
e152c39
Compare
Personally, I would like to get rid of the related projects (except for Ariel). The selection of projects seems quite arbitrary to me and the descriptions seem to be somewhat inconsistent. If there is consensus on keeping this section with all these OS' we should also define which projects should be mentioned here. Also, I would move this section down. At least after the Getting RIOT section. |
My first commit was as a small friendly note at the end of the intro - i also think it was quiet low key if looked at the README and not just the change in isolation.
I think the "related projects" selection is no more random than the FAQ comparison.
so right between Getting Riotand Getting Startedor between Getting Startedand Community |
And I liked that commit - except that I still think that the reference to Ariel is misplaced in the intro. The intro describes the key properties and attributes of RIOT - so it felt weird to suddenly have a link to something else (no matter how close or remote we consider the relationship with Ariel OS.
Agreed. We need some sort of a definition to what we want to list.
Hm. On a second thought I'm not sure. On the one hand I want the link to Ariel OS to be as visible as possible - on the other hand the most natural place for me seems to be rather towards the end of the document. |
Is the issue you have only the selection to be arbitrary and the inconsistency in wording or their description? If so, that seems to be a case for just refining this section. Or is the issue you have the addition of the related projects section as such, and you would like to see something like "Other Projects from the Same Crowd" instead? (It would be odd if the section header would be just "Related Projects" or "Other Projects", but only stuff from (parts) of our community would qualify.) If it is the latter, I'd convert this PR to a draft and revisit if this still makes sense when this discussion has concluded. |
honestly. whatever is about advertising other projects should go to the very end (if such text should be part of the README at all). it appears weird that the RIOT README starts with watering the focus on RIOT. in very former times, a readme file helped the user to quickly get an overview about the software project. the README file is not the web page of the project, even though it feeds the landing page on github. if you want to educate users that there are other projects that fits better the needs of the user, if you want to help the user to wisely choose their programming language or operating system, the README is not the best place. |
@waehlisch Please stay on point: This PR is about adding a reference to the FAQ. |
@maribu i tried to stay on point. sorry for misreading the comments. my understanding was different because Oleg wrote "except that I still think that the reference to Ariel is misplaced in the intro" and before that "Personally, I would like to get rid of the related projects (except for Ariel)". So, what is this PR about? |
I'm not sure how helpful it really is to add pointers to other references to the README at all. I tend to agree with @waehlisch here, that something likes this would be better suited for the web page instead. However, I'm probably a bit old-fashioned here (typically rather open the README in a pager application in my terminal emulator then looking at it on Github). However, in any case if the consensus is that we really want to list third-party projects here, we should have a good definition of the selection criteria first. Why do we list Nuttx but not FreeRTOS? Why RT-Thread but not Frosted or TockOS? |
Closing in favor of #21078 |
Contribution description
At the bottom the related projects section in the README.me, this adds a reference to the in-detail comparison between RIOT and related OSes in our FAQ.
Testing procedure
Proofreading and possible checking the output of the rendered version (easiest in the branch corresponding to this PR).
Issues/PRs references
Follow up to #21052