* Restored docs page on roles in security, executed other touchups, and renamed docs readme.txt to readme.md
* missed a url anchor on the security page
* fixed licensing issue and limited char width to 80
* fixed licensing issue and limited char width to 80
* whitespace experiments
* removed 2 periods
* staging whitespace
* addressed Robs feedback
* implemented robs second round of feedback on public_role_like
* docs: typo
* docs: consistent two-line gap before sections in README
this is merely to touch something outside of docs/ to work around a CI
issue (comment in #11152), while not creating diff-noise only
The Slack community guidelines are kind of wordy and best belong as part
of our code of conduct.
Let's make `README.md` super streamlined, and link out to resources like
this one.
* Create INTHEWILD.md
Create INTHEWILD.md to: 1. collect all Superset users into a single document and shorten README to make it more usable; 2. Categorize users into broad industry categories, which makes the document more useful as a reference for new users looking for industry peers and best practices (e.g. healthcare industry has unique needs and use cases); 3. removed some companies, whose website is inaccessible or defunct.
* Update INTHEWILD.md
* Update INTHEWILD.md
* Update README.md
* Update INTHEWILD.md
* Update INTHEWILD.md
* Update README.md
Our README now points to a not-so-well-maintain, community-contributed
Docker image. The docker image we link to here is managed and
supported by actual committers under the Preset org.
I noticed two small typos in the README that I fixed:
1) "Acts" was wrong because it does not have the correct subject-verb agreement
2) "Who Have" is the wrong pronoun to use when referring to companies. "That have" is the grammatically correct option.
Additionally, my company, Let's Roam, uses superset to visualize people completing challenges all over the world.
The text in the README seemed overly Druid-centric at this time. While
originally (3-4 years ago) Superset was heavily focussed on druid, it's
just not accurate anymore. Druid is just one of the databases that we
support and docs should reflect that.
* Add refinements from 0.35.2 release
* Trim whitespace from voter name if voters entered with space after comma (e.g. 'Ville, Andy')
* Reinstate deterministic deps
* Bump copyright date in NOTICE
* Fix incorrect link in README
* Add Fanatics to companies that use Superset
We at Fanatics use Apache Superset to visualize data stored in Apache Druid. I wanted to add my firm's name to this list since we are very happy with the performance and visualization features provided by Apache Superset.
* Update README.md