Disclaimer, comments, observations, etc. - chuckablack/quokka GitHub Wiki
This software, "quokka", is named after the marsupial of the same name, which can be found on smaller islands off the coast of Western Australian. It is named thus for no specific reason, except perhaps for the fact that these creatures are small, cute, endearing, friendly, and not so full of themselves as to be annoying. My hope is that "quokka" the software ends up being something similar.
On to the disclaimers:
- Purpose: Quokka is primarily intended as a teaching vehicle, to help network folks (and others) to become legitimate programmers, in this world that is getting eaten up by software.
- Use: That said, you are free to use quokka for whatever purpose you choose. If it is desired to use this software to discover and monitor your environment, please feel free to do so.
- Testing: Since quokka is not a product per se, and it is just me writing software because I enjoy both software and networking, there isn't a rigorous back-end staff of test engineers hammering quokka day and night. It does run full time in my environment, and has been tested here and there; however, if there are issues, especially at the beginning, don't be too surprised. :-)
- Defects: If you encounter problems, feel free to let me know, in a civil, aka kind and gentle manner. I know that is out of vogue these days (especially here in the US, where I type this), but just do your best.
- Enhancements: I'm totally happy to accept suggestions for new features or enhancements to existing features. Just adhere to my comment on the bullet above (civility).
But most importantly, it bears repeating that I created this as an example, for people learning programming to be able to use to improve their skills in this area. Understand that perhaps as you compare quokka to other real products, whose intentions are different from those of quokka.
And finally: Quokka isn't done yet! By that I mean that I am having quite a bit of fun adding features to quokka, enhancing existing features in quokka, discovering issues and fixing them, etc. At this point, I have no intention of stopping. So, you can expect me to continue to enhance this thing - in fact, during the course of writing all this documentation, I've thought of a couple cool new things to add.
So, please take time to examine the capabilities of quokka, look at its tables, graphs, diagnostic capabilities, etc., and hopefully, investigate the code that makes it happen, and use it and other Python trainings (e.g. "52 weeks of Python") to become an accomplished programmer yourself!