GSock weekly report of Harshit Joshi for Week 9 and 10

2018-07-20 Thread Harshit Joshi CIC 
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 in week 9:

   - Engaged in writing install file for the project
   - Integrated invoice2data with GUI

Here is work done in week 10

   - Rewrote spec files for Linux, Windows, MacOS
   - Wrote tests for GUI functions
   - Setup of Continuous Integration
   - Add Makefile
   - Restructure bin/
   - Added and corrected tests for Factur-X library

InvoiceX-GUI: https://github.com/invoice-x/invoicex-gui
Factur-x: https://github.com/invoice-x/factur-x
Project Description:
https://wiki.debian.org/SummerOfCode2018/Projects/ExtractingDataFromPDFInvoicesAndBillsDetails

Cheers
*Harshit Joshi*
*Freshman - B.Tech (Information Technology and Mathematical Innovations)*
Cluster Innovation Centre
University of Delh*i*
*Website: www.harshitjoshi.in *

Re: final upload to Google: trial run

2018-07-20 Thread 殷啟聰 | Kai-Chung Yan 
> - 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
> single directory you can just make a tarball of the whole repository or
> directory.

In our project students work on updating / creating multiple Debian packages, 
so we might not really need to upload the all those tarballs there. They can 
simply write down the links to the Salsa repositories, links to 
 pages, and maybe the upload notice like 

 which clearly states the names of the students.

A script for building the packages might not be needed as how to build a Debian 
package is quite conventional inside this community. Quoting the submission 
guide, "If your work is 100% complete, they should be able to use it." In our 
case building them won't be usable yet, not until it's uploaded to the Debian 
Archive.

Unfortunately not all packages managed to be uploaded by now because of some 
blockers in the NEW queue, they may need to also post a snippet of `git log 
--author=XXX` that shows all their commits. Salsa/GitLab does not support 
filtering commits based on authors yet, so we have to do this by hand (or by 
script).

> 
> - create a directory in a repository on Salsa somewhere in the Outreach
> space, maybe we can call it "intern-work-products" repository under here:
> 
> https://salsa.debian.org/outreach-team/
> 
> Maybe we use a subdirectory pattern such as this for each student:
> 
>   2018/gsoc/your_login-guest/work-product.zip
>   2018/outreachy/your_login-guest/work-product.zip
>> 
> - in the same directory you put the script for building your work
> product and a small text file with the following:
> 
> wiki: https://wiki.debian.org/Student
> work-product-script: zip-my-commits.sh
> work-product: work-product.tar.gz
> email: stud...@example.org
> IRCnick: student123
> repo: https://salsa.debian.org/foo
> repo: https://github.com/foo
> blog: https://student-blog.whatever
> report1: https://lists.debian.org/debian-outreach/.
> report2: ...

Is this just a drill? If so I will encourage our students post everything on 
their own Debian Wiki page and then submit the link to it to the final 
evaluation. Otherwise they can just make merge requests on the repository.

Cheers,
Kai-Chung Yan

Re: final upload to Google: trial run

2018-07-20 Thread Andrea Trentini 
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 for me

> ...
> For my students I would suggest that they just send a final detailed report 
> to this list,
> including the links above and any other relevant links (to blogs, weekly 
> reports,
> documentation etc.), including as well a general description on work done,
> problems that were solved, etc.

I agree

-- 

  /\___
 /--\ndrea |rentini  (http://atrent.it)
 .  Software Libero - Dipartimento di Informatica
..: Università degli Studi di Milano

Re: final upload to Google: trial run

2018-07-20 Thread Dashamir Hoxha 
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 just for GSoC), and 99%
of the latest commits there are from them (with a few commits from the
mentors).

For example, for the EasyGnuPG project, one can track all the commits
from this simple link:
 - https://github.com/EasyGnuPG/pgpg/commits?author=diveshuttam

Another link that is very useful for tracking the history of the work is
this
one:
 - https://github.com/EasyGnuPG/pgpg/issues?q=author:diveshuttam
Besides all the issues, it also shows all the pull requests from this
author (it turns out that pull requests in GitHub are just a special kind
of issues). Being able to track pull requests is very useful because they
also include comments and discussions about the code (between student
and mentors).

For my students I would suggest that they just send a final detailed report
to this list,
including the links above and any other relevant links (to blogs, weekly
reports,
documentation etc.), including as well a general description on work done,
problems that were solved, etc.

Then they can submit to GSoC the URL of this message (from the public
archive).
This is also considered acceptable and good practice by GSoC team
(see: https://developers.google.com/open-source/gsoc/help/work-product)

Regards,
Dashamir


>
> I would propose that we do a trial run next week as described below.  If
> anybody wants to propose an alternative way to do this or if you saw
> other communities doing this please comment.
>

Re: final upload to Google: trial run

2018-07-20 Thread Daniel Pocock 
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 way to do this or if you saw
> other communities doing this please comment.
>
> - 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
> single directory you can just make a tarball of the whole repository or
> directory.
>
> - create a directory in a repository on Salsa somewhere in the Outreach
> space, maybe we can call it "intern-work-products" repository under here:
>
> https://salsa.debian.org/outreach-team/
>
> Maybe we use a subdirectory pattern such as this for each student:
>
>   2018/gsoc/your_login-guest/work-product.zip
>   2018/outreachy/your_login-guest/work-product.zip



I tweaked the directory structure, it is

   gsoc/2018/your_login-guest

The repository is there now, existing admins can grant access to
students and mentors, please request access through Salsa or ask on IRC:


https://salsa.debian.org/outreach-team/intern-work-products/tree/master/gsoc/2018


>
> - in the same directory you put the script for building your work
> product and a small text file with the following:
>
> wiki: https://wiki.debian.org/Student
> work-product-script: zip-my-commits.sh
> work-product: work-product.tar.gz
> email: stud...@example.org
> IRCnick: student123
> repo: https://salsa.debian.org/foo
> repo: https://github.com/foo
> blog: https://student-blog.whatever
> report1: https://lists.debian.org/debian-outreach/.
> report2: ...
>
>
> Does anybody want to share examples of Git commands useful for
> extracting the commits?
>
>
> This trial run will serve two purposes:
>
> - help students focus on the final work product for Google
>
> - admins can make a sanity check and inform mentors in advance if any
> project is falling short of expectations
>
>
> Regards,
>
> Daniel
>
>