ishcheklein

Please, find the full job description here - https://remoteok.io/remote-jobs/99244-remote-senior-software... ... and feel free to ask any questions.

To apply send a direct email to [email protected].

It reminded me this - https://www.bbc.com/news/technology-54423988. Sheets are not databases. Be prepared to hit one the issues like this.

1. Pick the project. Something that you like, but also something that is not huge or very mature (they tend to have longer turn around due to the volume of things they are getting). You can then check issue tracker for the project and see if there are tasks labeled "need help", "good first issue", etc. They are usually things that team would appreciate help with. On GH, it looks like this: https://github.com/iterative/dvc/labels/good%20first%20issue

If you don't know the project, try to search GH, may be here - https://github.com/explore ?

2. Check that project is "healthy" - check the recent history of PRs - that code is being reviewed and merged. It can be very demotivating to do stuff that won't be answered at all. Ask in the issue you like and see if there is a response.

3. Find the contributors guide. There should be a link in the project's README, something like https://github.com/iterative/dvc#contributing . The guide should help you understand how to do setup dev environment, how to create a PR, etc.

4. In a lot of cases these days, projects have chat or forum (or GH issue comments) to ask questions, ask help, etc. Check them our, see if they are "healthy" and don't hesitate to ping the team - usually people are responsive and are willing to help.

Good luck! and thank you for considering doing OSS contributions. That means a lot for them!

TL;DR: I think it should be compared with the upcoming DVC feature - https://github.com/iterative/dvc/wiki/Experiments . Stay tuned - it'll be released very soon but you can try it now in beta.

First of all, congrats on the launch! I do really like the aesthetics of the website, and the overall approach. It resonates with our vision and philosophy!

Good feedback on experiments feeling heavyweight! We've been focused on doing great foundation to manage data and pipelines in the previous DVC versions and were aware about this problem (https://github.com/iterative/dvc/issues/2799). As I mentioned - Experiments feature is already there in beta testing. It means that users don't have to do commits anymore until they are ready, still can share experiments (it's a long topic and we'll write a blog post at some point since I really excited about the way it'll be implemented using custom Git refs), support for DL workflow (auto-checkpoints), and more. Would love to discuss and share any details, it would be great to compare the approaches.