-
Notifications
You must be signed in to change notification settings - Fork 22
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
Chapter D: Trust but Verify #21
Comments
Planning on discussing tool validation and needing to go beyond traditional commercial forensic tools. |
Ooh I like that. I'm sure I'll have some ideas for this too 👍 but it's your chapter so you steer the ship! Let us know how we can support. |
Are we thinking this will be generalized? Mobile? Computer? |
Right now leaning towards generalized, with hitting on mobile and computer. |
Ok cool. It'll only matter for placement in the order of chapters since we'll be having subsections. |
Hey there! I'm tentatively setting 7/31/2022 as a milestone for publishing v1.0 of this book. We'll have the title decided in the next couple weeks which will be the first of multiple administrative tasks we'll complete in July. At this point, please let me know if you intend to have at least a working, editable version of your chapter by 7/31/2022. If not, please know that's perfectly fine. It doesn't mean your chapter won't get published, it just won't get published in v1.0. It'll simply be added when it's ready to be published and I'll push out a new version of the book, (i.e., V1.3, v1.7, etc) with your new content. I hope we have about 10 ready to go by 7/31/2022 so we can push to publish v1.0 shortly thereafter, but I won't know that until I hear from you! So, please let me know! |
Hey there, it's been a few months. Just wanted to check in and see how progress is going on your chapter? Whenever your chapter is ready to go, submit it to the repo, and once its reviewed it'll get published without delay! Cheers and hope you are well! |
No description provided.
The text was updated successfully, but these errors were encountered: