I have added screencast of how the GUI works on my blog:
http://blog.harshitjoshi.in/2018/07/invoicex-gui-google-summer-of-code.html
I had some problem related to UEFI and legacy boot option in my laptop
(took 3 days to fix it completely), hence work done was limited in week 9
This is what I did
> - each student creates a script to build your work product tarball. If
> you committed patches to an existing project you need to create a script
> that extracts all the patches committed by you. If you are the only
> committer in the repository or if all your contributions are under a
>
On 20/07/18 11:52, Dashamir Hoxha wrote:
> ...
> In the case of my students, it is easy to track all their work because they
> have worked on separate repositories (created just for GSoC), and 99%
> of the latest commits there are from them (with a few commits from the
> mentors).
same situation
On Mon, Jul 16, 2018 at 11:35 AM Daniel Pocock wrote:
> In August, every student needs to make an upload of code to Google.
> This is a mandatory requirement to pass GSoC.
>
In the case of my students, it is easy to track all their work because they
have worked on separate repositories (created
On 16/07/18 10:35, Daniel Pocock wrote:
>
> Hi everybody,
>
> In August, every student needs to make an upload of code to Google.
> This is a mandatory requirement to pass GSoC.
>
> I would propose that we do a trial run next week as described below. If
> anybody wants to propose an alternative
