volatility3
volatility3 copied to clipboard
Documentation - Improvising with examples
I have planned to do it in the following manner:
- [x] Bring the vol3 tutorial similar to vol2.
- [x] Have examples for each plugin, which wasn't provided in vol3 wiki.
As of now the Linux page has been updated similar to vol2 wiki. Soon more updates will come
This PR is wrt issue #562
Please don't close the PR until I let you know guys, this PR was made in order to get reviews and do the needful fixes as I continue to work on.
Thanks
No problem, thanks for working on this! We'll leave this open, and keep an eye on it to see when it's done... 5:)
Thank you for your work @tejas15802, Awesome, I think documentation is one of the really good contributions! 😃
I don't fully knowing the PR policy of volatility 3 not yet, If continuous changes are needed for the goal, why don't you use Draft PR?
Of course, Draft PR can proceed with the review, and if it is changed to Open, it means that you are ready for the final review. 🙌
@ikelos I ll resolve them in further commits.
Thank you for your work @tejas15802, Awesome, I think documentation is one of the really good contributions! 😃
I don't fully knowing the PR policy of volatility 3 not yet, If continuous changes are needed for the goal, why don't you use Draft PR?
Of course, Draft PR can proceed with the review, and if it is changed to Open, it means that you are ready for the final review. 🙌
Sorry I wasn't aware of it. I'll change it to draft
Thank you for your work @tejas15802, Awesome, I think documentation is one of the really good contributions! 😃 I don't fully knowing the PR policy of volatility 3 not yet, If continuous changes are needed for the goal, why don't you use Draft PR? Of course, Draft PR can proceed with the review, and if it is changed to Open, it means that you are ready for the final review. 🙌
Sorry I wasn't aware of it. I change it to draft
Oh, it wasn't your fault or mistake, it was just a suggestion. 😅 Thank you for reflecting my opinion!
Please review the PR and let me know if there any improvisations needed @ikelos @digitalisx
Thanks
Just pinging to notify, if the last notification missed out. @ikelos
Hello @tejas15802,
If you haven't responded to Github's review request, it's a good idea to wait at least a month. (unless it's very urgent)
Perhaps your work completion and review request has already been recognized by him, If time permits he will be happy to look at it if it is available or reasonable to prioritize. It's his feedback on a similar request.
We all have to wait a little bit more broadly for a healthy open-source ecosystem. 🙂
okay noted, will wait then. I apologize ikelos.
How about now?
Thank you : )