Hello!
Thanks for your feedback! I really appreciate your taking time to answer me.
According to your notes and recommendations, I changed the timeline part of
my proposal. It actually looks like this:
___
# Timeline
Frankly speaking, I have exams at my University until the end of June. I
hope to pass most of them ahead of time; at best, I'll have only one exam
(or two, in a worse case), so I think I'll have enough free time to work on
the project. So, a timeline would be similar to something like this:
June - working with the Linux AppVM side:
-
May 30th - June 11th (one and a half weeks)
Reading more about systemd.
Determining fields of log entries which reasonably should be collected and
the exact way of getting them from log-collecting system.
Finding the proper way to extract the chosen fields from the log collecting
system and formatting them to form the desired output.
-
June 12th - June 25th (two weeks)
Applying the new knowledge and writing the log-exporter daemon for the
Linux AppVM side in the right way.
Rest part of June, July and the beginning of August - working with the
LogVM side:
-
June 26th - July 9th (two weeks)
Finding the proper way to prepend timestamps and writing the log-collector
program.
-
July 10th - July 23th (two weeks)
Writing the log-compressor daemon (or configuring already existed tools)
for the LogVM side (hope, I overestimate the complexity here and can start
working on the GUI earlier).
-
July 24th - August 6th (two weeks)
Learning toolkits like Qt or GTK and working on the GUI implementation.
Rest part of August - working with a documentation, unforeseen
circumstances (like I wouldn’t finish the GUI till this time) and final
evaluations:
-
August 7th - August 20th (two weeks)
Documenting the written project and dealing with unforeseen
circumstances.
-
August 21st - August 29th (one week)
Final code submission and final evaluations.
I plan to test the written components separately and the system in general
all the time during the work, that’s why I don’t allocate any special time
for testing.
I think a weekly formal posting to the qubes-devel mailing list is suitable
for me. It will include information about my current progress and
difficulties I will be facing.
I don’t plan any full or part-time time jobs during the summer. Maybe there
will be part-time jobs on weekends, but I’m not yet sure about it. In July
or August there can be a short (about a week) family trip. I’ll have access
to the Internet there in any case and will be available for communication
all the time.
Qubes is the only project I am submitting a proposal for.
___
> I think there should be sufficient time. Just sending & receiving logs
> is really not a multi-month task, and the GUI itself can be really
> quite simple.
I added the GUI point to the Project Goals part and to the Implementation
part of my proposal as:
___
# Project goals
[...]
-
Implement some convenient GUI designed specially for the log collecting
system.
___
# Implement
[...]
Also, there is the GUI for log collecting system on the LogVM side. It
allows to view a list of all collected logs sorted by their receiving time
and see some of log attributes (such as their origin, size, etc.). At the
same time it permits to open them with a suitable program in a DispVM. It
can be implemented in Python using toolkits like Qt or GTK.
As soon as this minimal functionality will be implemented, more capability
can be added. For example, it can be managing logs like sorting, deleting,
copying them or so on.
___
> Salt has a non-negligible learning curve though, so if you'd prefer to
> just work on the actual log handling and let someone else (most likely
> me) integrate it and do automatic creation of an actual LogVM by the
> installer, etc. I think that'd be fine.
Thank you, that would make it a lot easier. To be honest, it was the point
frightened and concerning me.
> The majority of the Qubes code base is in Python. We prefer Python
> over C for safety reasons, and Python over bash for portability
> reasons. I would recommend Python be used for this as well.
> How familiar are you with Python?
I had an experience with Python. There were mostly easy tasks for my
University courses, nothing the code quality of the OS depended on. :) I
understand that it isn’t the best recommendation for me, but I promise to
get more familiar with Python before the summer begins.
In this way, given the benefits of Python you mentioned (and because Python
has libraries for everything), I can work on project using Python.
> Your proposed timeline looks somewhat sparse to be honest. I encourage
> you to be more ambitious ;)
It looked this way because I tried to be pessimistic when I thought about
it. I believe it’s better than to overestimate myself and miss deadlines. I
hope it’s more ambitious now (but not entirely, I still want to be so
productive as I promise or more :) ).
> Does this mean you intend to write unit tests, etc. as you go? Or just
> manual testing?
Yes, I intend to write unit test for everything as I go.
> All of June potentially gone sounds like it would make it difficult to
> make sufficient progress by the first midterm evaluation. You need to
> have a clear plan for how you will make it work.
> To quote the GSoC FAQ: [5]
> [...]
> and the GSoC mentor manual: [6]
> [...]
> I'm not bringing this up to discourage you or to say it can't be done,
> but to be honest it is somewhat concerning. Some more information
> about how you plan to handle both would be most welcome.
I know other countries have a different appraisal system for students and
the last ones are absolutely free by June but by my country is not among
them. This is the reality I have to deal with.
I had read all of these documents before I decided to participate in the
GSoC. I am fully aware of the responsibility in relation to the GSoC too.
My situation is not as severe as the one in the mentor recommendation. At
best, I'll have only one exam (or two, in a worse case). In any case, I can
handle those and the GSoC at the same time and both of them won’t suffer
(or the GSoC will have to prevail).
So, you shouldn’t be concerned about it.
Here is my entire proposal in Google Docs <https://goo.gl/8ipaFP>. I
decided not to post it here again because this mail is already too long.
You are welcome to comment if it still has places that need to be edited.
Thank you again.
Best wishes,
Alisa.
--
You received this message because you are subscribed to the Google Groups
"qubes-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/qubes-devel/24d1943d-2551-4b15-86bb-fac8eaccc60e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
