2022-02-21 weekly planning

[kgodey]

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

• Last Week in Mathesar
• Frontend priorities
• Backend priorities
• Design priorities
• Product priorities
• Comms Assignee schedule
• Upcoming Core Team Events
• Dominykas check in
• Brent's check in
• Pavish's check in
• Ghislaine's check in
• Mukesh's check in
• Sean's check in
• Kriti's check in

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:

• How did your most recent work go?
• What are you planning to work on soon?
• Do you anticipate any dependencies or blockers that someone else on the team can help you with?

If you'd like to add anything else to your check-in that's not related to the prompts, feel free to do so.

[kgodey]

Last Week in Mathesar

Feedback Requested

• Discussions:
  • Which column identifier should we use for DDL operation #1081
• Specs:
  • Add initial spec for handling dates and times mathesar-wiki#35
  • [DRAFT] Update number type to support custom currency format mathesar-wiki#36

Complete

• We submitted our Google Summer of Code 2022 organization application!
• Major wiki updates:
  • The Product Spec for Views is getting a rewrite, but it's not complete yet.
• Full stack and general work:
  • Improve E2E test setup #1032
• Backend work:
  • Fix Not Null Violation to return detailed error response #1053
  • Interval type improvements #1067
  • Add new filtering API endpoint #1061
  • Replace filtering API; includes support for filtering numbers #1069
• Frontend work:
  • Fix form render regression #1075

[kgodey]

Frontend priorities

1. Complete front end changes to Mathesar 896 Change records api parameters to use column id instead of name #1047
2. Complete Improve UX when adding new records to a table with a NOT NULL column #775
3. Complete and merge basic E2E testing: Write integration tests for some important user scenarios #640. PRs:
   1. Finish adding E2E tests #1062
4. Make progress on issues from the Initial Data Types and 2022-02 improvements milestones. Some ideas:
   1. Implement setting a default value for a column #500
   2. Create Menu component #742
   3. NumberInput component improvements #970
   4. Wait until user is done editing a cell before saving #928
   5. Blur via keyboard after entering edit mode on a NULL cell should cancel edits #929
   6. Add keyboard shortcuts for setting a cell to NULL #936
   7. Add ability to minimize and expand groups in the frontend #475

@pavish @seancolsen Please comment below with thoughts/concerns.

[pavish]

Looks good to me.

There are currently two open frontend draft PRs, which isn't mentioned above. The goal for this week also includes getting them ready and possibly merged.

• Menu components #1076
• Text type & basic Boolean type frontend implementation #1080

[seancolsen]

Looks good.

As noted also in my check in, #1076 is on hold for a while. I don't expect to continue work on it for at least another week. #1047 and #775 are higher-priority and will take me a while.

[kgodey]

Backend priorities

The frontend is catching up fast to the backend, so we really need to get backend work for Initial Data Types completed and start on Links between Tables ASAP.

We divided up the issues as follows:

1. @dmos62:
   1. Filtering:
      1. Implement filtering options for Text types. #406
      2. Implement filtering options for the email type #410
      3. Implement filtering options for the URI type #413
      4. Implement filtering options for the money type #418
      5. Implement filtering options for date & time types #427
      6. Implement filtering options for duration type #431
      7. Reopen Implement filtering options for Boolean types #388 if needed to make sure it works with the new filtering setup.
   2. Data Type API updates::
      1. Split Date & Time data type into three Mathesar types  #960
      2. Inconsistent database type name casing in backend code #1036
      3. Add database type alias information to database type endpoint #1037
2. @mathemancer:
   1. Spec for human readable date and time parsing #845 + associated work
   2. Grouping:
      1. Implement grouping for Text types. #408
      2. Implement grouping options for the email type #411
      3. Implement grouping options for the URI type #414
      4. Implement range based grouping for numeric types. #384
      5. Implement grouping options for date & time types #429
      6. Implement grouping options for money types #419
      7. Implement grouping options for duration type #432 (currently blocked)
3. @silentninja:
   1. Replace column name usage with ID:
      1. Replace column index usage with attnums and Column model id #839
         1. Column selecting operations should use attnum #992
         2. Column dropping operation should use attnum #993
         3. Column alteration operations should use attnum #994
         4. Column creation and copying should use attnum #995
      2. Modify records API to use column id instead of column name #896
   2. Ensure that we can set, get, and delete default values for all types #1064
   3. Implement display options for Duration type #433
   4. Work coming out of Money type design updates #1063 (currently blocked)

I'll also work on #1008 if I have time this week.

@dmos62 @mathemancer @silentninja Please comment below with thoughts/concerns.

[dmos62]

No comment.

[kgodey]

@dmos62 Do we need to reopen #388 to make sure it works with the new filtering setup?

[dmos62]

@kgodey we can. I'm currently going through those filtering issues and creating test suites for filtering those types. I'll do the same for boolean when I get to it.

[mathemancer]

These priorities make sense to me.

[silentninja]

I will be working on

• Implement display options for Duration type #433
• Ensure that we can set, get, and delete default values for all types #1064

as there are a few things to discuss before starting work on #839.

[kgodey]

Design priorities

1. Money type design updates #1063 is top priority since it's blocking backend work.
2. Continue exploratory work for Views in the design prototype.
3. Design specs for:
   1. Design for visual query builder ("Data Explorer") #1065
   2. Design for List data type #978

@ghislaineguerin @ppii775 Please comment below with thoughts/concerns

[ppii775]

@kgodey @ghislaineguerin apologies – i was under the weather for a few days. Hope to catch up in the coming days!

[ghislaineguerin]

@kgodey looks good

[kgodey]

Product priorities

1. Finalize definition of Views, which will result in updates to the GitHub issues for Views design and the product spec for Views.

[kgodey]

Comms Assignee schedule

Week	Person
2022-02-21 to 2022-02-25	Ghislaine
2022-02-28 to 2022-03-04	Brent
2022-03-07 to 2022-03-11	Kriti
2022-03-14 to 2022-03-18	Pavish
2022-03-21 to 2022-03-25	Mukesh
2022-03-28 to 2022-04-01	Sean
2022-04-04 to 2022-04-08	Dominykas

Instructions

You 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.

[kgodey]

Upcoming Core Team Events

We're going to be playing https://skribbl.io/ during our next team event on March 11. It would be great to get some ideas for team events for the following dates:

• March 25
• April 8
• April 22

If your idea involves prep ahead of time for a host, also mention whether you want to host the event.

[dmos62]

How did your most recent work go?

Well. Steady progress.

What are you planning to work on soon?

Continue submiting PRs that add new filters. Then move on to the data type API issues.

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

No.

[mathemancer]

Brent's Check in

How did your most recent work go?

Pretty well. I'm really happy to be finishing up the last type implementation work (for now). It was a bit more complicated than we originally thought (as usual), but the new implementation will be more robust and less reliant on python's parsing of both strings and postgres types into the same python type values.

What are you planning to work on soon?

Once my current Date/Time type implementation is merged, I'm into grouping. I'm also updating the date / time spec as I refine the implementation, and hope to get that merged into the wiki (though that's less urgent).

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

It seems like consensus is developing around the "human-readable dates and times" spec, but it still requires some coordination and participation to get that merged. I also suspect we're going to need to coordinate on the column ID discussion for @silentninja 's work.

[pavish]

Pavish's check in

How did your most recent work go?

It went well, progress is steady. I'm working on text and boolean mathesar type implementation which involves some groundwork.

What are you planning to work on soon?

I under-estimated the time when setting last week's goals, so the goals for this week remains mostly the same.

• Get PR Text type & basic Boolean type frontend implementation #1080 merged.
• Frontend implementation for Boolean Mathesar type #257
• NumberInput component improvements #970

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

None

[ghislaineguerin]

How did your most recent work go?

Went well. Proposed change to design process (lower fidelity wireframes) by Kriti is speeding up design exploration.

What are you planning to work on soon?

#1065

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

None

[silentninja]

Mukesh's Check in

How did your most recent work go?

Made good progress on issues I am working on. Synchronous weekly check meetings were quite helpful in resolving discussions.

What are you planning to work on soon?

I am planning to work on #1064 followed by #839

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

Discussion on replacing column index is blocking work on #839.

[seancolsen]

Sean's check in

How did your most recent work go?

• Going pretty well. I feel good about where we're at with the E2E testing now.

What are you planning to work on soon?

• The refactoring I'm doing to support column ids instead of names for Mathesar 896 Change records api parameters to use column id instead of name #1047 has become a bit more intensive than I originally thought. I'm hoping to finish it tomorrow.
• After that, Improve UX when adding new records to a table with a NOT NULL column #775 is my next priority, and I expect that work to carry into next week.
• Menu components #1076, though in draft state, is on hold for a while while I focus on higher-priority work.

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

• Nope

[kgodey]

Kriti's check in

How did your most recent work go?

Pretty well, got a lot of work done on the product spec for Views. I think it is close to another round of review, I just need to work on specifying formulas more.

What are you planning to work on soon?

• Complete work on formulas for the Views product spec
• Open a new discussion for Views product spec review
• Update design tickets for Views based on product spec
• Set up style guide and tooling for consistency in backend code #1008 if time permits

Do you anticipate any dependencies or blockers that someone else on the team can help you with?

I'll need the product team to look at the Views discussion once I have it up in the next couple of days. @mathemancer @pavish @dmos62 @silentninja.