Bug 70682 - Highlight first time contributors in gerrit daily digest
Summary: Highlight first time contributors in gerrit daily digest
Status: RESOLVED FIXED
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: WWW (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: difficultyBeginner, easyHack, skillScript
Depends on:
Blocks:
 
Reported: 2013-10-20 17:18 UTC by Björn Michaelsen
Modified: 2016-02-18 16:37 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Björn Michaelsen 2013-10-20 17:18:12 UTC
We have a daily digest sending information about changes on gerrit. The current implementation can be found here:

 https://gerrit.libreoffice.org/gitweb?p=dev-tools.git;a=blob;f=gerritbot/send-daily-digest;h=ea3f9b5767e067147ba6a1fcc6a12448ce78d72f;hb=8ef490cebaf16778f18896448fa454c158368cef

This Easy Hack is to extend the script to:

- keep a local copy of the core repo
- do something like `git log --pretty=%aE master|sort|uniq` on that to find people, who already did commits
- then highlight those that are _NOT_ in that list in the output (e.g. a separate section in from of the others)

This is so that we core developers can make sure a first time contributor does not block too long on a patch waiting for review,
Comment 1 Mat M 2013-10-20 21:40:36 UTC
So basically, in the list returned by the query "Open changes on master for project core changed in the last 25 hours:", you want to have 2 parts, the first one with first-time contribs, the 2nd one with not-first-time ones ?
Comment 2 Björn Michaelsen 2013-10-21 09:08:56 UTC
(In reply to comment #1)
> So basically, in the list returned by the query "Open changes on master for
> project core changed in the last 25 hours:", you want to have 2 parts, the
> first one with first-time contribs, the 2nd one with not-first-time ones ?

That sounds nice to me, yes.
Comment 3 Mat M 2013-10-21 23:44:18 UTC
where should I put the repo ?
/tmp
/var/tmp
~/tmp
Another better location I do not know about ?
Comment 4 Robinson Tryon (qubit) 2015-12-15 23:19:32 UTC
Migrating Whiteboard tags to Keywords: (EasyHack DifficultyBeginner SkillScript SkillInfra)
[NinjaEdit]
Comment 5 Robinson Tryon (qubit) 2016-02-18 16:37:04 UTC
Remove LibreOffice Dev List from CC on EasyHacks
(curtailing excessive email to list)
[NinjaEdit]