Goal: generate spreadsheet for simple coaching and invoicing

[georgeciubotaru]

SPECS Document

Live sheet

### Tasks
- [ ] https://github.com/holdex/autoinvoice/issues/199

[zolotokrylin]

@georgeciubotaru reverted in the doc.

[zolotokrylin]

@georgeciubotaru did we define the spreadsheet PoC before we do programming?

[georgeciubotaru]

@zolotokrylin Yes, feel free to iterate.

[zolotokrylin]

@georgeciubotaru we need the actual spreadsheet with events (simulated by hands sample) so we can build pivot tables and see if it is convenient. Otherwise, iterate over the event structure until we are happy with pivot tables.

[zolotokrylin]

@georgeciubotaru i left my comments in the doc

[georgeciubotaru]

@zolotokrylin I, also left comments from you, and connected a BigQuery DB for you to test

[zolotokrylin]

@georgeciubotaru I can't work with that sheet because of this:

[georgeciubotaru]

@zolotokrylin Check now.

[zolotokrylin]

@georgeciubotaru now this one

[georgeciubotaru]

@zolotokrylin Please check and let me know

[zolotokrylin]

@georgeciubotaru @markholdex the app is not working. Many blocking bugs making the app dead 😵

What's the reason? Why?

I just spent some time explaining why we need this tracker to Truflation stakeholders.

They also expect to see the table with the results.

Can we make the app reliable? What the reason it is not realisable? What's the plan?

[georgeciubotaru]

@zolotokrylin there were several issues generated somehow by the Github API library, so I changed the implementation, and now it should work.

[zolotokrylin]

Commits? PR links?

[zolotokrylin]

@georgeciubotaru I needed the report this week. Any success?

[markholdex]

@zolotokrylin check what I cooked ysterday: https://docs.google.com/spreadsheets/d/1BZSxH8vZ8-IdudTF7YxM789eWA1DDBxyA8p35QUyF1M/edit#gid=659288053

There are reports for April and May.

[zolotokrylin]

@markholdex Looks good! What are your observations based on this report? 3 observations (problems) and solutions?

[markholdex]

@zolotokrylin made updates. Check it out again. I will keep adding stuff as we go

[markholdex]

@georgeciubotaru I'm passing this Goal to you. I have updated the Specs document and you can use my examples from Live sheet to make sure we can answer the Specs questions for this month before we begin Salary review. You will have to apply some changes too after you made the latest fixes. If you have any questions in regards of some data or formuals, let me know. Appreciate it 🙏 🙏 🙏

[georgeciubotaru]

@markholdex, @zolotokrylin

Logs:

What was implemented:

• Currently, all the events from Bigquery are filtered (unique)
• All events come with 2 custom calculated fields
  • new_action - humanized text for each event action (can be customized)
  • Name - humanized text for each sender slug (can be customized)
• View the number of hours submitted (every day / per month)
• View the chart of hours submitted for (April and May)
• View the number of PRs got merged
• View the number of PRs opened
• View the number of PRs got closed (without merge)
• View the number of PRs that got rejected (better to call it the number of rejections received)
• View the number of Prs got approved (better to call it the number of approves received
• View the number of PR review comments received
• View the number of PR review comments left
• View the number of PR approves left
• View the number of PR rejections left
• View the percentage distribution between every PR action
• View the action count for each developer in each organization

What remaining:

• Sort the Cost submitted events in case there are multiple events (by taking the last event)

[georgeciubotaru]

@zolotokrylin, @markholdex

Today's log: What was implement

• sort the Cost submitted events in case there are multiple events (by taking the last emitted event)

Let me know if there is missing any information.

[zolotokrylin]

Sounds like we have everything (more then 20/80 for sure) to improve our operations and build coaching and retrospectives around these metrics! If it works well, then it is an awesome job, @georgeciubotaru !

I suggest to add the instructions in the README file as we don't have interface which can be used by ops people to understand what's available. Thus we need some notes for people who can't read it from the code, but can read the normal doc. README of the project would be the best place.

[markholdex]

@georgeciubotaru don't forget to kickstart the June data. Thx!

[georgeciubotaru]

@zolotokrylin I'm closing this goal as move the docs tasks in the newest goal