>Ok, good. I would create a master ticket for this project based on the
contents of the wiki page and your proposal. You can use the "Blocked By"
and "Blocking" fields of the ticket to create >dependencies.
>We should work on the documentation for the tracing right from the start.
The tracing is f
On 09/05/18 07:56, Vidushi Vashishth wrote:
Hi!
Updating the progress. I have updated my wiki page, created two
tickets and completed an introductory blog post. The next blog post
containing an analysis of live tracing vs kernel level tracing design
considerations might take about two days. L
Hello Vidushi,
please notify us when you cannot work on your GSoC project for a couple
of days. From the GSoC Students FAQ:
https://developers.google.com/open-source/gsoc/faq
"How much time does GSoC participation take?
You are expected to spend around 30+ hours a week working on your
proj
Hi!
Updating the progress. I have updated my wiki page, created two tickets and
completed an introductory blog post. The next blog post containing an
analysis of live tracing vs kernel level tracing design considerations
might take about two days. Let me know if you have any changes to suggest
for
Hello Sebastian!
I apologise for the apparent inactivity. I have been caught up with
preponed exams in college. I have a day off until my next exam so I will
update update both my blogs, wiki documentation and create relevant
tickets.
Meanwhile I have been reading up barectf documentation and hav
Hello Vidushi,
I hope you are doing well. The wiki page and your blog are still empty.
I didn't see any new tickets for this tracing GSoC project. I didn't see
much activity from your side in the last couple of days. From the GSoC FAQ:
https://developers.google.com/open-source/gsoc/2018/mento
