5 ms·
The documentation is not Enterprise Ready™; it still contains a description of what the product actually does in an accessible location. For proper compliance,
by _pmf_ 8y ago
The documentation is not Enterprise Ready™; it still contains a description of what the product actually does in an accessible location. For proper compliance, this description should be in a PDF whitepaper that will only be mailed to you after providing your e-mail address and phone number.
- dx034 8y agoIt should probably be sent via Fax to be sure.
- bencollier49 8y agoYeah, to be fair, just by being on GitHub there are issues. Ideally, it should be sat on Visual SourceSafe or something in a server on an industrial estate somewhere.
- Joeri 8y agoThat pdf whitepaper won’t actually explain how to use it. It will describe the synergy of the experience of using it, give three real world customer stories of how it is used (without actually explaining how), and then end with a link to a documentation site that redirects to a login screen that it will take two weeks to get past because your account rep can’t get the right team on the line to approve your account for access.
- detaro 8y agoAnd don't forget to fax a signed copy of the NDA!
- discreditable 8y agoThe PDF whitepaper should also be an image instead of text to prevent anyone from using find or selecting text.
- PascLeRasc 8y agoReal Enterprises would print out the PDF and scan it back in and then delete the original.