You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It is likely the first link to a contributing guide a user see's when following the link specified in CONTRIBUTING.md.
This guide leads users down the likely painful path of trying to set up a developer environment without docker compose, as I have just experienced.
This link should be removed, moved to a less prominent position and/or a warning added with a link to the relevant up to date page which is available in the side bar menu.
The text was updated successfully, but these errors were encountered:
An easy fix would be to remove that link. I wonder if that content would have been better off as part of the official docs, where it would be easier to keep updated. I'm fine with removing that link, but will also ping @mistercrunch and @rusackas as people who have thoughts about developer docs and the Preset blog.
In a perfect world, we'd have the bandwidth to go back and change all our old blog posts to keep them fresh and current, but that's more than a full time job at this point, so we're probably better off treating them as time capsules, like so many blogs do. If anything, it's probably time for a NEW blog post on the topic!
There is a link to an outdated contributing guide here: https://github.com/apache/superset/blob/master/docs/docs/contributing/contributing.mdx?plain=1#L22
It is likely the first link to a contributing guide a user see's when following the link specified in CONTRIBUTING.md.
This guide leads users down the likely painful path of trying to set up a developer environment without docker compose, as I have just experienced.
This link should be removed, moved to a less prominent position and/or a warning added with a link to the relevant up to date page which is available in the side bar menu.
The text was updated successfully, but these errors were encountered: