Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Time-tracking MVP #31

Closed
10 of 11 tasks
nelsonic opened this issue Jun 10, 2022 · 1 comment
Closed
10 of 11 tasks

Time-tracking MVP #31

nelsonic opened this issue Jun 10, 2022 · 1 comment
Assignees
Labels
discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality priority-1 Highest priority issue. This is costing us money every minute that passes. T1d Time Estimate 1 Day technical A technical issue that requires understanding of the code, infrastructure or dependencies

Comments

@nelsonic
Copy link
Member

nelsonic commented Jun 10, 2022

We need a way of keeping track of who is working on what for our project.
This will become a core feature of our product.
It's there on the MVP feature roadmap: https://github.com/dwyl/product-roadmap#mvp-basic-workflow

todo-list-with-timer png

Essentially we are building a Todo List with a Stop Watch. ✅ +⏳
Hence the reason for us writing tutorials for these individual components ... 💭

Once you click/tap on Start it will insert a timer record associated with the item
see schema: https://github.com/dwyl/app-mvp-phoenix#create-schemas

Note: this "fits in" to our bigger picture road map: once you have captured and categorized your thoughts (items), some of them will become tasks.
When you are completing those tasks, you need to keep track of how much time you have spent on them. That's where Time-tracking comes in! Knowing how long something has taken is essential!
So in essence we are "building the bridge from both ends". The time-tracking aspect is 100% part of completing a task. We can build that part of it without having a fancy editor.

  • Capture: we want to build a beautiful and responsive "capture" interface that has markdown (and eventually Rich Text) support e.g. images, annotations etc. but we have to start with plaintext first.
    We have a sub-task to build the "capture" part in our gitea-demo (tutorial):
  • Tech Stack?
    • Thinking of using PETAL PETAL Stack technology-stack#87 for this MVP because Tailwind looks a lot easier to build Mobile-first Apps with (than Tachyons where it's still totally possible, but more difficult..._) and from listening to the
      There is a checklist in that issue we need to try and complete as quickly as possible.1
  • Exclusively Web-based and online-only. (will not work offline because LiveView ... 🙄 but that's "OK" for MVP!)

Features

  • Auth using https://auth.dwyl.com 🔒
  • Basic capture task to be done as plaintext. 📝
  • Start timer for the task ⏳
  • Stop timer ✅

1We don't have to have complete tutorials for everything, but we need to capture the basics so that both we (our current core team) and other people can find our "learn-..." tutorial/notes useful. But our main objective is learning the tech/tools ourselves as quickly as possible so that we can build our MVP!

@SimonLab let me know if this is clear or if I can clarify anything ... 🙏

@nelsonic nelsonic added enhancement New feature or enhancement of existing functionality T1d Time Estimate 1 Day discuss Share your constructive thoughts on how to make progress with this issue technical A technical issue that requires understanding of the code, infrastructure or dependencies priority-1 Highest priority issue. This is costing us money every minute that passes. labels Jun 10, 2022
@nelsonic
Copy link
Member Author

This functionality is now fully covered in the MVP: dwyl/mvp#89 (comment) 🎉
@SimonLab please test: mvp.fly.dev and provide feedback. 👍
(PR dwyl/mvp#90 will be assigned very shortly... 🧑‍💻 ⏳ )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discuss Share your constructive thoughts on how to make progress with this issue enhancement New feature or enhancement of existing functionality priority-1 Highest priority issue. This is costing us money every minute that passes. T1d Time Estimate 1 Day technical A technical issue that requires understanding of the code, infrastructure or dependencies
Projects
None yet
Development

No branches or pull requests

2 participants