-
-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add some Q&A for the FAQ page chosen from answered questions already on the web. #1405
Comments
let's stuff the FAQ with general introductory questions... and maybe some harder ones. The Interlisp discord https://discord.com/channels/1129446509268697190/1141981846813540472 has some FAQs also |
The FAQ that is there now as https://interlisp.org/project/faqs/ are really questions and answers about running Medley. The FAQs suggested here are more about the context and history. So I propose moving project/faqs.md to software/faqs.md and linking it in (or integrate them into the software/using-medley/ and then taking the Q&A here as a history/faqs/ I still think a FAQ is mainly a place to put things that don't fit easily into the documentation and anything long deserves its own section. |
track Stackoverflow for questions about Interlisp? https://stackoverflow.com/questions/78645353/write-text-i-o-stream-to-file-with-interlisp-medley for example... |
I submitted PR 233 to link to our GitHub discussions board so that new users can easily access the communication channels we control and monitor. |
I know there was an issue "Want a FAQ page", but that kind of begs the question of "How should I ask questions?".
People ask questions in lots of places -- good or bad.
If we don't have a canonical place for people to ask questions or anyone gathering and responding to questions, we won't be able to add to this section. People ask questions on StackOverflow. Or on Libera Chat. or Lisp-romania Discord.
We're not ready for a FAQ and maybe just remove it. If we ever have enough people asking questions that we need one, we could just comment this one out.
The text was updated successfully, but these errors were encountered: