mrimann / como Goto Github PK

Send a message to the winner itself for each award he has won.

Whilst having it added in the first run, the full frontend currently does not base on Bootstrap AFAIR -> so let's remove it.

If I look at a change like e.g. https://git.typo3.org/Packages/TYPO3.Flow.git/commit/da6b2c2ffb556ab00677b23f12c8163ed2ffc513 the author is a human being - and the committer is a Code-Review System which maybe rebased the change and thus is the committer of the change.

But the credits should definitely be for the author of the change.

Reload the status-screen e.g. every 5min or so to avoid displaying old data.

Maybe this can be shown as a sentence like: "In February we've seen X commits within Y of the Z monitored repositories."

Would be nice to show a randomly picket commit of the day, showing the following data:

• Project-Name
• commit-message
• Author details
  (but no code)

metadataextractor:processrepositories function sends 'Only variables can be passed by reference' in MetaDataExtractorCommandController.php at line 183
"exec ('git pull', NULL, $pullResult);"

Instead of the user focus, let's show the most active project

Repository::add(), Repository::update() and Repository::delete() don't persist changes. They are only written to the backend when PersistenceManagerInterface::persistAll() is called (which happens automatically after each request).

Because changes are not persisted explicitly during loops in the controllers - for example here https://github.com/mrimann/CoMo/blob/master/Classes/Mrimann/CoMo/Command/DataAggregatorCommandController.php#L50 the aggregated data can be incorrect.

The Code-Review-System for example shouldn't get any credits or even an award -> add an option to exclude certain users from getting an award (but still collect their data)

In case there's a very "old" repo being checked, we should avoid to extract every single commit from the last 10 years - and then just use the last 1 to 6 months for the aggregation + awards.

Longish names get cut off (last character(s) are not being shown, text does not break to second line.

Currently, also feature and maintenance branches (ok, every branch) are integrated into the aggregation of data

Not sure how these are counted and valued

When running::

./flow metadataextractor:processrepositories --quiet

The following error is shown::

fatal: bad default revision 'HEAD'

Currently they are detected but not activated by default.

For cronjob runs

Ideally we'd show the top 3 per category - with a trend indicator per person, showing the difference in ranking compared to the last (elected) month.

Depends on: #7

Showing e.g.

• a pie chart of the commits of the last vs. current month (split by type).
• a trend line of the number of commits from the last 6 or 12 months

Currently the sentence is something like::

Last month we've seen 323 commits within 42 of the 199 monitored repositories. 

It would be cool to also mention by how many different committers those commits were produced.

This should be short-reloading to show, who would be the next award winner, in case the election would be held now.

Idea is to show that in the right column of the page

On the base screen view, we have a sentences like "there were X commits within Y of the Z monitored repos last months".

This could be extended by "... made by n different commiters"