francishemingway opened a new pull request #8459: [WIP] User tutorial URL: https://github.com/apache/incubator-superset/pull/8459 ### CATEGORY Choose one - [ ] Bug Fix - [ ] Enhancement (new features, refinement) - [ ] Refactor - [ ] Add tests - [ ] Build / Development Environment - [x] Documentation ### SUMMARY A new tutorial that focusing more on how an end user might use Superset, rather than how an administrator might set it up and get it working for the first time. I have added this as a new rst file, and changed the hierarchy within the documents so that there's now a tutorials page, with links to the existing tutorial and the new one. ### ADDITIONAL INFORMATION This tutorial is based on a real dataset from [here](https://data.gov.uk/dataset/b2bc9c3f-c892-4bcf-b8c1-0d0efdace3fa/dft-flight-data) which is a set of flights taken by an organization in 2011. This data is licensed under the Open Government Licence v3.0, an ASF category A license. Then it was combined with data from [here](https://ourairports.com/data/), licensed under the public domain. Then I tidied it up by removing a single line (a flight with the same origin and destination). It's currently [on my github](https://github.com/francishemingway/unofficial-superset-tutorial/blob/master/tutorial_flights.csv). ### Questions I have: It would be great to get some guidance on the following: - What should the licence header be in the tutorials.rst and usertutorial.rst file be? - Is there somewhere within the project's repositories to host the data file. - Should I open a new issue? this addresses more #698. ### REVIEWERS
---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
