community gems draft april '20 #1155
Conversation
|
Hey @shcheklein, this is meant to publish sometime next week so no rush. There's a really detailed discussion (I think?) on discord here that I didn't include, but I wanted to get your opinion on: https://discordapp.com/channels/485586884165107732/563406153334128681/695408490956718170 I don't fully understand the discussion, so would like your opinion about if it would be a strong addition to this month's post and if so how to repackage it in a Q/A format |
|
@andronovhopf
that discussion is a dev related, probably pinned it to find it if needed. No need to include it in gems. Feels a bit less posts/discussions than usual? |
|
@shcheklein got it, i won't include that discussion as for length- yes, it's a bit shorter. I left some space because i thought we might want to include that Q&A about trees, and it looked like it would be quite long if we did. But since we're not, I'll add a few more questions in the next revision |
| look like hashes (because, well, they are). Luckily, DVC handles all the | ||
| conversions between the filenames in your local workspace and these hashes. To | ||
| get some more intuition about this, check out some of our | ||
| [docs](https://dvc.org/doc/command-reference/import#examples) about `dvc import` |
There was a problem hiding this comment.
can we find a better link that explains how data is stored? import/get is a bit strange choice for that.
There was a problem hiding this comment.
how about this one? I though you were not resolving it for a reason
There was a problem hiding this comment.
it should be changed. not sure why it isn't showing that code snippet as outdated
|
@shcheklein think this is ready- if you get time today, I'd love to publish |
| descriptionLong: | | ||
| A roundup of technical Q&A's from the DVC community. This month, we discuss | ||
| the DVC cache, cloud storage options and concurrency. | ||
| picture: ../../static/uploads/images/2020-04-16/DVC_Gems_April_20.png |
There was a problem hiding this comment.
please, merge the latest master - I think the way we do URL has changed (simplified)
There was a problem hiding this comment.
okay just did that
There was a problem hiding this comment.
take a look at some other blog posts, please - it's a minor simplification update
There was a problem hiding this comment.
oh, you mean with the picture URL. got it! changing now
There was a problem hiding this comment.
also updated author. although that seems to have thrown a "restyled" error in CI
There was a problem hiding this comment.
not that, restyled fixed an extra space in one of the lines that was introduced
❗ Please read the guidelines in the Contributing to the Documentation list if you make any substantial changes to the documentation or JS engine.
🐛 Please make sure to mention
Fix #issue(if applicable) in the description of the PR. This causes GitHub to close it automatically when the PR is merged.Please chose to allow us to edit your branch when creating the PR.
Thank you for the contribution - we'll try to review it as soon as possible. 🙏