Re: [ft-devel] [GSoC 2018] New font drivers

[Werner LEMBERG]

> 1. For the working of GSoC, I will have one branch `test` for
>    testing and random stuff and one `clean` branch with proper
>    commits which can eventually be merged.

OK.

>    I am not clear about the role of `freetype-commit` mailing list,
>    please help here.

Simply write all questions to the list instead of addressing the
mentors personally.  There might be reasons to address them
individually, but in most cases (i.e., technical issues and
discussions) this is not necessary.

>    I am not getting this "Please commit to `master' only after
>    discussing the intended changes in advance." (as mentioned by
>    Werner sir in the last mail) whether we have to commit changes
>    directly to master?

You might find bugs and/or unclear documentation in master that are
not related to your project, but which you would like to fix anyway.
Such commits should be discussed in advance.

> 2. I wanted to ask about status update method whether it should be
>    through e-mail or blog posts.  I am more inclined towards blog
>    posts as they will ensure all the progress at a single place and
>    can be accessed easily.

This is up to you as long as you send an e-mail to this list with a
link to a new blog entry.

> Currently I am having my university exams going on, so I will not be
> able to work full time and as mentioned in the proposal I will
> compensate this time after 3rd May i.e. after my exams.

Don't rush!  And good luck with your exams.

> Also I wanted to ask if I am missing out on any part in the work
> flow of FreeType please help me here.

No need to worry.  We will assist you in due course.


    Werner