-
Notifications
You must be signed in to change notification settings - Fork 128
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Optimization Algorithms #25
Comments
@manrajgrover I will claim this and work on implementing Viterbi algorithm. Let me know if anyone is working on this implementation. |
Hi. I want to work on this. Can I have more information regarding this issue.?? |
@manrajgrover @junhouse @ashutosh-b-b |
Also Manraj if you've found a maintainer do you mind @mentioning them here too? |
Hi @remes2000, are you maintaining this project? I've forked this repo and cloned from that for work on my local machine, and I now see that that means I'm pushing commits to my own repo. Granted I'm new to this, but it seems like merging pull requests from a forked repository would be more difficult than from a direct clone of this one. Any advice on the best way to set this up for making contributions? |
Hi. Yes, I currently take care of this project. First off all, You have to fork this repo and then clone it to your local machine. Then create a new branch by typing "git checkout -b [branch name]", then write some code and commit changes. After that push Your branch to your forked repository. Then You can create pull request. After that, I'll review your PR and decide if it's ready to be merged. Remember to run "npm run test" and "npm run lint" commands, and to pull current master to your branch before sending PR. If something is unclear for You, feel free to contact me. I'll explain everything :) |
Thanks for the explanation! |
Hi @remes2000 is anyone still working on the case? If no, could you please explain to me a little more about the project, I'm a newbie and would like to contribute... |
is this still open? |
The text was updated successfully, but these errors were encountered: