2022-02-14 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
• Google Summer of Code action items
• Frontend priorities
• Backend priorities
• Design priorities
• Product priorities
• Comms Assignee schedule
• Dominykas' check in
• Sean's check in
• Kriti's check in
• Ghislaine's check in
• Pavish's check in
• Brent's check in
• Mukesh'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

Nothing at the moment.

Complete

• Discussions:
  • Client-side vs server-side validation when saving records #1057
  • Shipping more quickly #1046
  • Dynamic Type selection & customization on the frontend #1035
    • We will renew discussion when we get to Store icon, labels, and input options for types on the backend #661
  • Design for List Data Type – Viewing & Editing List #1034
  • Code Styling guidelines for the backend #1007
    • Feel free to leave comments or thoughts, but we need a draft of Set up style guide and tooling for consistency in backend code #1008 before substantive discussion
• Wiki updates:
  • in preparation for our GSoC application, I filled out our Mentoring section, including:
    • Applicant Guide
    • Project Proposal Template for applicants
    • Mentee Guide
    • Mentor Guide
• Full stack and general work:
  • Introduce ui and db API namespaces #1041
  • Update README.md migrate+install instruction #1058
• Backend work:
  • Introduce function API #1022
  • Add Postgres Money type #1060
• Frontend work:
  • Fix spelling error in function name #1048
  • Enable TypeScript strict mode by ignoring lots of errors #1056

[kgodey]

Google Summer of Code action items

I plan to submit our Google Summer of Code organization applications this week. Some action items for everyone:

• Take some time to through our new Mentoring wiki section, especially:
  • Applicant Guide
  • Project Proposal Template for applicants
  • Mentee Guide
  • Mentor Guide
  • Action items:
    • Let me know (here or privately) if any of the documentation looks confusing.
    • Let me know (here or privately) if you have any questions about any of what you read.
• Read through the draft of our GSoC application (note: this is a private document, only accessible to the core team)
  • Action items:
    • Let me know (privately) if you have suggested improvements or questions.
• Look through our Project Ideas
  • Action items:
    • We need a primary and backup mentor for all ideas. Post here with the ones you're willing to mentor.
    • Let me know (here or privately) if anything looks confusing or needs more detail.
• Consider this the last call to add new Google Summer of Code ideas - please add them before end of day Thursday if you have more.

[dmos62]

I'm a primary mentor for the automatic hints reflection. I don't mind being a secondary on any of the others; I don't have preferences though.

[mathemancer]

My only confusion about the docs is where the entry point is for applicants. As for as willingness to mentor, I'm happy to mentor or co-mentor on any of the back end tasks, with a preference for data layer things.

[pavish]

I'm willing to mentor or co-mentor any project that involves frontend work.

[silentninja]

I would love to mentor the following ideas:

• Construct Dependency Graph for Database Objects
• Support More Data Import Sources
• Support Importing Data into Existing Tables

I'm happy to mentor or co-mentor on any other back end related ideas, with a preference for service layer things.

[kgodey]

@seancolsen and I talked via DM, I'll put him down as backup mentor or frontend support for any existing ideas that need it.

[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. Improve E2E test setup #1032
   2. 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.

[seancolsen]

Looks good 😁

[pavish]

Looks good to me

[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 won't be able to do that this week, but the closer we get, the better.

We met last week and divided up the issues as follows:

1. @dmos62:
   1. Filtering:
      1. Implement filtering options for Number types. #385
      2. Implement filtering options for Text types. #406
      3. Implement filtering options for the email type #410
      4. Implement filtering options for the URI type #413
      5. Implement filtering options for the money type #418
      6. Implement filtering options for date & time types #427
      7. Implement filtering options for duration type #431 (currently blocked)
   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. Handle INTERVAL type in the backend #430
   2. Spec for human readable date and time parsing #845 + associated work
   3. 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 (currently blocked)
   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]

Sounds good.

[mathemancer]

I think this makes sense

[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

[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-14 to 2022-02-18	Dominykas
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

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.

[seancolsen]

Sean's check in

How did your most recent work go?

• Going pretty well.
• All the work required to smooth out the E2E testing has been a little frustrating. I'm not really sure how to improve our process though.
• I'm excited to finally have TypeScript strict mode enabled.
• I'm still feeling like I ought to be spending a larger portion of my time on building features. Hopefully once the E2E dust is settled that ratio will come into balance.

What are you planning to work on soon?

• Add front end changes to Mathesar 896 Change records api parameters to use column id instead of name #1047, once the back-end changes are complete.
• Improve UX when adding new records to a table with a NOT NULL column #775 (after we have some discussion at this week's meeting)
• Write integration tests for some important user scenarios #640 (via Improve E2E test setup #1032 and Finish adding E2E tests #1062)
• That should probably take me most of the week. If I have time or I get blocked I'll move on to Create Menu component #742.

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

• Nope

Anything else?

• My kids are finally back in school starting this morning!! 🎉

[kgodey]

I'm glad the kids are back in school! E2E testing has always been a pain whenever I've worked on it, hopefully the infrastructure you're setting up will make things easier to write new tests.

[dmos62]

How did your most recent work go?

Pretty well. Filtering feels out of the woods.

Ever since we discussed shipping faster, the number of discussions and notifications I have to attend reduced drastically, and it's had a great effect on my focus and productivity. I'm very pleased with the low noise environment I'm enjoying right now. I didn't know I needed it. Also, I'm not sure where the discussions have gone: it's a bit like everyone became more focused. Good stuff!

What are you planning to work on soon?

Get foundational filtering PRs merged, then get the type-specific filters added. I'd love to have relevant PRs submitted by end of this week.

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

I have two filtering API PRs up for review.

[kgodey]

I'm glad to hear that the amount of noise has reduced for you and that it's helpful! :)

[kgodey]

How did your most recent work go?

Last week felt a little slow, I did get more Views work done, but not very much. I switched focus to Google Summer of Code and did get a lot done there, we're almost ready to apply.

I also have a lot more meetings now with the regular 1:1s and weekly meeting and that is hard on focused product work. I expect it will take me a couple of weeks to adjust fully.

What are you planning to work on soon?

Other than regular meetings, code review, discussions, etc.:

• Wrapping up the Google Summer of Code application
• Views product work
• If time permits, Set up style guide and tooling for consistency in backend code #1008

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

Yes, everyone should prioritize the Google Summer of Code action items since it is time-sensitive.

[ghislaineguerin]

How did your most recent work go?

My most recent work is still in progress. Last week was low on productivity due to taking some days off (I was sick). Had a meeting w/ Kriti at the start of last week that was very helpful in defining priorities for query builder work.

What are you planning to work on soon?

• Issue Money type design updates #1063
• Continue exploratory work for Views in the design prototype.

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

None

[pavish]

Pavish's check in

How did your most recent work go?

I was off for most of last week because I was sick. I didn't get any coding done, but did attend meetings, participated in discussions and reviewed some PRs.

What are you planning to work on soon?

• Frontend implementation for Text Mathesar type #254
• Frontend implementation for Boolean Mathesar type #257
• NumberInput component improvements #970
• Add frontend changes to Replace filtering API; includes support for filtering numbers #1069, when ready.

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

None

[mathemancer]

Brent's check in

How did your most recent work go?

Last week was less productive due to moving and a sick dog. However, the INTERVAL PR is in. At some point, we should assess our overall database type infrastructure to see if there are places where we can avoid repeating ourselves.

What are you planning to work on soon?

I'm speccing out date / time type information passing between the API and UI. I'll ticket and implement any needed changes. I'm also trying to squeeze in some of the GSoC tasks. After that, I'm planning to get into grouping.

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

Nope.

[kgodey]

we should assess our overall database type infrastructure to see if there are places where we can avoid repeating ourselves

Please create a ticket to track this. :)

[silentninja]

Mukesh's check in

How did your most recent work go?

Last week was quite productive, made a PR for Postgres Money data type and was able to add additional enhancement to error classes. Weekly check-in was also helpful in resolving a few issues.

What are you planning to work on soon?

I am planning to complete issues related to replacing column name usage with column id. Also, help Sean with E2E infrastructure.

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

Nope.