Re: weekly reports: this list, into Git, or elsewhere?
On 31/05/2018 00:14, Daniel Pocock wrote: > Do people feel good about receiving 25 report emails each week on this list? I like seeing the reports on the list. It is low volume enough that having those extra messages is it not causing any inconvenience. However, it is not always obvious to me which project each student is reporting on as I am unable to associate 25 student names to 25 project titles. I would like to suggest that students add a reference to their project in their emails. Ideally that could be done in the subject and a link to the main project web resource (wiki, code repository, other) could be added at the bottom of the reports. For that to work, it would be helpful if projects could choose an acronym [1] to make the subject lines reasonably short. Maybe the requirement for an acronym should be added to the Debian guidelines. Cheers, Dan [1] When writing research proposals there is often the requirement to choose an acronym for the project. At first the requirement seems silly, but after having to deal with all the paperwork and communication involved in those, you are quickly grateful that you don't always have to spell the project title in its entirety :-)
Re: weekly reports: this list, into Git, or elsewhere?
Hi all, I am not one of the selected interns but I am having a lot of fun going through the emails from selected candidates and their projects, so I wish that the emails be continued so that it's easier for anyone going through the projects. That said it's quite cluttered and receiving lots of emails certainly make it an annoyance for someone looking for some important emails, so how about having git as mentioned and then send only one email every week which has the compilation of all the candidates progress, I think it would look elegant and would also make it easier for admins to go through it at the end. Anyway I don't have any experience with grading or review so I may be wrong but I just felt that I had to give my opinion here. Regards, Kartik Kulkarni
Re: weekly reports: this list, into Git, or elsewhere?
On 31/05/18 08:29, Bruno Magalhães wrote: > Hi, > > The wiki sounds like a sensible solution to have everything > centralised in one place, and for future reference. The emails work > better, IMO, because they are very visible and a student knows that if > they miss the report it will be noticed. > If we use a pattern for the wiki URLs or filenames in Git then we can build an automated report to show how many reports each student submitted and when they made their last report. For 26 interns this type of report may be easier for admins to follow A summary aggregated from all of them could also be sent to Planet Debian each week Regards, Daniel
Re: weekly reports: this list, into Git, or elsewhere?
Hi, The wiki sounds like a sensible solution to have everything centralised in one place, and for future reference. The emails work better, IMO, because they are very visible and a student knows that if they miss the report it will be noticed. Regards, Bruno On Thu, 31 May 2018 at 08:02, Andrea Trentini wrote: > On 31/05/18 08:14, Daniel Pocock wrote: > > Hi all, > > Do people feel good about receiving 25 report emails each week on this > list? > > no problem for me (I have filters that move messages in folders > automatically) > > > Would anybody prefer to see any of the following alternatives: > > - we create a new list, just for reports? > > no, not another list, please! > > > - students put the reports in a shared Git repository, maybe using > > Markdown so it can be rendered with Jekyll? > > that is a good solution, better RST than Markdown > > I suggested my mentored students to create a journal.rst in their repo > (under a GSoC-2018 dir) > > > -- > > /\___ > /--\ndrea |rentini (http://atrent.it) > . Software Libero - Dipartimento di Informatica > ..: Università degli Studi di Milano > > [il file "signature.asc" (firma gpg) potrebbe non essere compreso dal > vostro sistema] > >
