2022-01-10 weekly planning #962
Replies: 12 comments 14 replies
-
Frontend updateCompleted
Current Priorities
@pavish @seancolsen Please comment below with thoughts/concerns. |
Beta Was this translation helpful? Give feedback.
-
Backend updateCompleted
Current priorities
@dmos62 @mathemancer @silentninja Please comment below with thoughts/concerns. |
Beta Was this translation helpful? Give feedback.
-
Design updateCompleted
Current priorities
@ghislaineguerin @ppii775 Please comment below with thoughts/concerns |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
Comms Assignee schedule
InstructionsYou can also find the schedule and instructions for the Comms Assignee on the wiki page. Please feel free to update the wiki page if you think of anything useful during your shift. |
Beta Was this translation helpful? Give feedback.
-
I think it's a good idea. Seeing what we've done during last week gives me a sense of pace.
I spent last week mostly rethinking the filtering refactor. I'm pretty happy with where it's at, though it's still in draft. I also participated in some architectural discussions, which was interesting because everyone had different ideas.
I'm currently in the feedback-iteration loop with the filtering refactor. I expect it to be my principal task next week.
No, except that prompt feedback on the filtering refactor would be useful. |
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
I think it's nice to see what we've been accomplishing, but I don't want to spend time on it if it's useless.
It was nice to finally get some product work done, and to get @seancolsen's help with the tickets. I'm happy with where we've ended up with Mathesar Data Types especially.
Nothing in particular. |
Beta Was this translation helpful? Give feedback.
-
Pavish's check in
I usually take a look at all newly created issues, discussions and PRs that are merged. I don't see much value in including this, but I still think it'll be good to use this as a weekly record to track progress.
Last week was a bit slow but I was more focused on analyzing and writing code, which felt good. Form builder is ready and type config PR needs a few more tweaks. I also started working on CellInput component.
None. |
Beta Was this translation helpful? Give feedback.
-
I guess for design, and it doesn't change much as work is more long-lived. I still think it's helpful to keep a log.
I think it went well. Specs are becoming more precise and easier to write. The prototype has many pieces I need to build the designs.
|
Beta Was this translation helpful? Give feedback.
-
I find it motivating, personally.
It went well; I'm trying to focus on smaller, higher-volume tasks, and I think it's going alright. As such, I got a few small PRs submitted and merged.
My top priority is supporting @dmos62 's work on filtering if there's anything I can do there (reviewing PRs / ideas, taking up menial implementations of various details, etc.). In particular, I had an idea for wrapping operators and setting up a function to reflect all needed info that might help, but will involve lots of ugly SQL (for the reflection, at least). If @dmos62 thinks that would be useful, I could throw together a quick, independent PR that would add some examples of such wrapper functions to the DB, and the reflection function. (If you don't think it'll help, @dmos62, just let me know.) I'm also on comms. Finally, I want to look through https://github.com/centerofci/mathesar/milestone/11 for any small(ish) issues to pick up and knock out.
The grouping and filtering work will probably modify many of the same parts of the code base, so we'll need to pay attention if we want to do those in parallel. |
Beta Was this translation helpful? Give feedback.
-
I find it to be useful. Looking back on what we have accomplished is quite motivating and great to know the pace we have been moving on. But I would cut it short if it takes too much time.
Error handling PR took longer than expected as I spent time looking at an alternate solution that didn't seem to work out, but I feel good about the outcome.
Currently looking to make any review changes that might come up with regards to the Error handling issue. Also looking to knock off issues related to date-time and column index -> id. Might get my hands on the filtering and grouping issues if I get time.
None, but would be helpful to get some quick reviews on the error handling PR as it has been blocking the frontend work for a long time |
Beta Was this translation helpful? Give feedback.
-
About
At the start of each week, we start a discussion covering Mathesar's progress, team member check ins, and general updates. Everyone is welcome to add a new topic to discuss or to comment on existing topics.
Discussion topics
Weekly check-in
@centerofci/mathesar-core please post your weekly check-in as a top-level response and edit the discussion topics above to add your check in as a topic. Others are also welcome to respond.
Prompts:
If you'd like to add anything else to your check-in that's not related to the prompts, feel free to do so.
Beta Was this translation helpful? Give feedback.
All reactions