Skip to content
This repository has been archived by the owner on Jun 8, 2023. It is now read-only.

📝 End Users neglecting documentation.. #21

Open
Rikj000 opened this issue May 2, 2021 · 10 comments
Open

📝 End Users neglecting documentation.. #21

Rikj000 opened this issue May 2, 2021 · 10 comments
Labels
Documentation Improvements or additions to documentation Won't Fix This will not be worked on

Comments

@Rikj000
Copy link
Owner

Rikj000 commented May 2, 2021

This has been the most re-occurring error I've seen since making MoniGoMani public!

First I spend tons of hours & hours of my precious time to write up some real good documentation.
Then these end-users just neglect all my hard work put into this documentation without reading it and start to waste even more of my time by bombarding me with questions..

Some of them even have the audacity of opening GitHub Issues for their ignorance towards reading documentations,
while these Issues are meant for well described bug reports that help me,
the developer in narrowing down the time needed to hunt for these bugs...

Please take your time to read all of the following documentation before asking questions:
👉 Official MoniGoMani Read the Docs Website

For questions you should not open GitHub Issues...
These can be posted in the #❔︱help channel of the Official MoniGoMani Discord Server
(But there goes the same rule, read before wasting other peoples time with noob questions).

  • No this strategy/framework is not an easy brainless copy/paste
    you should optimise your own version as described in the documentation.
  • ✔️ Yes this framework should lead towards a profitable strategy setup in a day or 2 without the need of programming knowledge, but while using your head/common sense..
    (We're still under Pre-Release as of writing this though, 0 promises..)
@Rikj000
Copy link
Owner Author

Rikj000 commented May 2, 2021

#20

@Rikj000
Copy link
Owner Author

Rikj000 commented May 2, 2021

#19

@Rikj000
Copy link
Owner Author

Rikj000 commented May 2, 2021

#18

@Rikj000 Rikj000 pinned this issue May 2, 2021
@Rikj000 Rikj000 unpinned this issue May 2, 2021
@Rikj000 Rikj000 pinned this issue May 2, 2021
@edebie
Copy link

edebie commented May 3, 2021

Hi there,

I did not like your comments above on my issues. Your way of response is a good evidence on your arrogance and very weak communication skills. You could simply direct me to the exact portion of your bad documentation that answers my question or leave it open for good people to answer if your "precious time" (haha) does not allow you to answer!!!

@Rikj000
Copy link
Owner Author

Rikj000 commented May 3, 2021

Hi there,

I did not like your comments above on my issues. Your way of response is a good evidence on your arrogance and very weak communication skills. You could simply direct me to the exact portion of your bad documentation that answers my question or leave it open for good people to answer if your "precious time" (haha) does not allow you to answer!!!

#20 (comment)
^ @edebie quote: "do we need to optimize the bot before every run? and how?"

The answer to your question is even in this GitHub Issue here (my 2nd last line with no in fat), so you did not even read that fully?
Following warning I have displayed on the home page, documentation page & every release version published:

WARNING: MoniGoMani should always be re-optimized after doing manual changes!
You need to optimize your own copy of MoniGoMani while thinking logically, don't follow your computer blindly!

Please elaborate how you missed this? Maybe I should reference it even more?...
You clearly show that you did not take the effort to read any / all documentation... I do not need to spoon feed you & I don't have time for that..
Now leave GitHub issues for actual software bugs, read first and then use the allocated Discord #moni-go-mani-help channel if you still have questions...

@mr-highball
Copy link

You could consider enabling github discussions? Sort of fills the gap of general question that might be bug scenario and keeps the communication close to the code (something discord misses out on in my opinion).
I enabled it for my algo trader and while I don't have the same amount of users, it seems to work well (and is easily searchable)
https://github.com/mr-highball/simplebot-support/discussions

@Rikj000
Copy link
Owner Author

Rikj000 commented Jun 1, 2021

You could consider enabling github discussions? Sort of fills the gap of general question that might be bug scenario and keeps the communication close to the code (something discord misses out on in my opinion).
I enabled it for my algo trader and while I don't have the same amount of users, it seems to work well (and is easily searchable)
https://github.com/mr-highball/simplebot-support/discussions

I will not do this on purpose.
It's too prone to re-attract leeches that will abuse it for already documented/asked/answered questions.
We'll stick with this place only being for actual bug reports & new issues, the Discord #moni-go-mani-help & #moni-go-mani-testing channels really suffices for these sorts of questions in my eyes.

Furthermore, there other users can take the load of my shoulders by replying towards other users questions + there the expectation isn't so high that I'll answer upon all questions.

@Rikj000 Rikj000 added Won't Fix This will not be worked on Documentation Improvements or additions to documentation labels Jun 5, 2021
@Rikj000
Copy link
Owner Author

Rikj000 commented Jun 7, 2021

#56

Repository owner deleted a comment Jul 2, 2021
Repository owner deleted a comment from ali-gen Jul 2, 2021
@Rikj000 Rikj000 changed the title End Users neglecting documentation.. 📝 End Users neglecting documentation.. Sep 5, 2021
@srsHitGub
Copy link

Documents in wiki link to 404

@Rikj000
Copy link
Owner Author

Rikj000 commented Oct 6, 2021

Documents in wiki link to 404

You currently need to be on the development branch documentation as mentioned in the warning at the main branch documentation in the wiki.
v0.12.0 is highly outdated & doesn't follow the new documentation format yet,
due to main currently being so outdated it's good that it's documentation can't be easily found, this will nudge more new people towards the development branch for now.
The wiki is already prepared for documentation format of the next release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Documentation Improvements or additions to documentation Won't Fix This will not be worked on
Projects
MoniGoMani - Global Development Progress
  
Permanent Documentation Pins
Development

No branches or pull requests

4 participants