Roadmap

[brayo-pip]

I have got the authentication working. I'm currently working on the d3 graph for the dashboard. Just starting out with a

bar chart. Interested in feedback or input on the project

[ErikBjare]

Here are some brief thoughts, let me know what you think!

Styling

I'd like to switch out Bootstrap (currently loaded via CDN) for Tailwind (possibly with shadcn components, or similar).

Reporting

Look at the working_hours_gspread.py script (that I'm using daily, as I explained here) for an example of how reporting could work.

We'd need to figure out how categories etc work.

Where should the category rules be stored?

• Server-side?
  • This is probably what you want for "team" categories, like for those working together on a project and want to see/compare individual time-contributions.
  • Perhaps only in cases where you join a "team" in the leaderboard, which opts you into reporting time matching the team regex to the team category.
• User-defined?
  • People have highly variable definitions of "work", so people need some way to have fine-grained control.
  • These might also be server-side, but configurable on a user-basis and not a "shared category" basis.

But to begin with, we will focus on all active time to keep things simple.

Charts

For charting, I would recommend using https://www.chartjs.org/.

We would ideally avoid making our own D3.js visualizations directly (can be quite a bit of work to make nice and maintain).

Previous attempt

Before I started this repo there was https://github.com/activitywatch/aw-leaderboard (now abandoned). But worth reading through the README!

[brayo-pip]

I'm 100% behind switching to tailwind. I haven't worked with bootstrap before and really avoided handling any UI CSS code because of it. I have minimal experience with tailwind but it's way better. I will learn! I have been experimenting with d3, finding it quite difficult to do right. Yeah I do think we should work with chartjs in the meantime but maybe switch later after we implement most of the functionality, or get more contributors. I was considering creating a leaderboard database, using cloud functions to update it hourly. Seems the only way to implement it. I'll think more about the categories. I honestly have to been thinking about how they will be implemented so far. But I'm guessing we just let the users define them in their client apps then we export them as is. On the clients we could have a hard-coded categories list that we update from time to time. Let me know what you think.

…

On Wed, 28 Feb 2024, 13:26 Erik Bjäreholt, ***@***.***> wrote: Here are some brief thoughts, let me know what you think! Styling I'd like to switch out Bootstrap (currently loaded via CDN) for Tailwind (possibly with shadcn components, or similar). Reporting Look at the working_hours_gspread.py <https://github.com/ActivityWatch/aw-client/blob/master/examples/working_hours_gspread.py> script (that I'm using daily) for an example of how reporting could work. We'd need to figure out how categories etc work. Where should the category rules be stored? - Server-side? - This is probably what you want for "team" categories, like for those working together on a project and want to see/compare individual time-contributions. - Perhaps only in cases where you join a "team" in the leaderboard, which opts you into reporting time matching the team regex to the team category. - User-defined? - People have highly variable definitions of "work", so people need some way to have fine-grained control. - These might also be server-side, but configurable on a user-basis and not a "shared category" basis. But to begin with, we will focus on all active time to keep things simple. Charts For charting, I would recommend using https://www.chartjs.org/. We would ideally avoid making our own D3.js visualizations directly (can be quite a bit of work to make nice and maintain). Previous attempt Before I started this repo there was https://github.com/activitywatch/aw-leaderboard (now abandoned). But worth reading through the README! — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AO6ENNMHYV5BGSIH4SVNHR3YV4A67AVCNFSM6AAAAABDX5LV6OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSNRYGY3TQOJTGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[0xFrama]

Hi @ErikBjare, @brayo-pip I would like to contribute. How can I help?

[brayo-pip]

Hi @0xFrama what are you most interested to work on?

[0xFrama]

I genuinely enjoy the process of learning new things; if there's something that can help me get familiar with the whole project, that would be great

[brayo-pip]

I suggest setting up the activityWatch tracker on your pc. That should familiarize you with the project. After that you can just peruse the repos at activityWatch. Don't let the numbers intimidate most are just duplicate implementations of the same thing in different languages. I also recommend joining the discord. I'll send you the invite link when I find it.

[brayo-pip]

https://discord.gg/Vktx4e4e here is the invite link

[0xFrama]

@brayo-pip thank you very much!
What about this specific repo? Is there something I can help you with?

[brayo-pip]

yes, let's connect on discord. Go over everything.