2022-04-04 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

1. Last Week in Mathesar
2. Frontend priorities
3. Backend priorities
4. Design priorities
5. Product priorities
6. Comms Assignee schedule
7. Sean's check in
8. Pavish's check in
9. Kriti's check-in
10. Ghislaine's check-in
11. 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

• Data explorer specs mathesar-wiki#42
• Mathesar money display and db options #1243

Complete

• Milestones:
  • 2022-03 improvements with 28 issues completed
• Discussions:
  • Should we consider removing the import preview option? #1242
• Full stack and general work:
  • Add E2E test for toggling an indeterminate checkbox to true, false, true #1131
• Backend work:
  • Multiple tables with the same oid #876
• Frontend work:
  • Make TS TableRecord interface contain the record response instead of extending it #906
  • Refactor Select and SimpleSelect components, merging them into one #1099
  • NumberInput component improvements #970
  • Provide a clearer visual distinction between edit mode and select mode #927
  • Fix regressions from #1229: #1236
  • Display options groundwork & config for boolean, number #1239
• Closed without work:
  • Implement data modeling on the frontend #224
  • APIs for data model changes #223
  • "List of Columns" page implementation #401
  • Backend support for working with primary keys #440
  • Frontend support for tables without single-column primary keys #396
  • Backend support for tables without single-column primary keys #395
  • Frontend support for working with primary keys #441
  • Data type of ID #1245
  • Blank row cells were added before user click add new row #1234
  • Sorting bug #1246

[kgodey]

Frontend priorities

1. Get open PRs merged:
   1. Add E2E test for converting boolean type to text type #1182
   2. issue-1134 Insert newlines in TextAreaCell only via keyboard shortcut #1211
   3. Bump minimist from 1.2.5 to 1.2.6 in /mathesar_ui #1225
   4. Adds missing unit test for select component #1241
   5. [1189] - Number 0 should show in table cell #1254
   6. Added event dispatcher in columnStore to fetch rows on adding new column #1256
   7. Cursor position in FormattedInput #1257
2. Make progress on high-priority issues for Initial Data Types milestone:
   1. Decide on date/time formatting string syntax #1108
   2. Frontend implementation for Boolean Mathesar type #257
   3. Improve UX when adding new records to a table with a NOT NULL column #775
3. Continue working on other Initial Data Types frontend issues.

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

[seancolsen]

Looks good

[pavish]

Looks good to me

[kgodey]

Backend priorities

1. Get open PRs completed and merged:
   1. Accept display options for MathesarMoney type #1205
   2. Fix bugs that lead to empty display options objects begin created for required display option #1251
   3. replace empty column name with "column_X" #1255
2. Complete remaining backend work for Initial Data Types:
   1. @mathemancer
      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
   2. @silentninja:
      1. Implement display options for the custom Money type #1105
      2. Internal server error after column type is converted from text to boolean with display options  #1228
   3. Not assigned to core team members:
      1. API should validate input for number columns #1145 (unassigned)
      2. Batch updating column using /tables/ api should reference column using id instead of column_index #1167 (assigned to @ratika-12)
      3. Custom python class to represent "char" DB type #1214 (assigned to @Cronus1007)
3. Start work on backend work for Links between Tables, some ideas:
   1. Modify constraints API to list foreign key constraints #943
   2. API support for storing "record preview" and "record selector" settings #944
   3. Ensure integrity of columns with foreign key constraints applied #973
   4. API support for "Link Table" dialog #972
4. Set up style guide and tooling for consistency in backend code #1008
5. These issues are on hold until @dmos62 is back from vacation.
   1. Minor refactor recycled from closed PR #1174
   2. Type logic refactor #1222
   3. Resolve logic duplication in the db.types namespace #1100
   4. Add database type alias information to database type endpoint #1037

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

[kgodey]

Design priorities

1. Complete one round of review for Design for visual query builder ("Data Explorer") #1065
2. Submit first draft of spec for review for:
   1. Support for opening and interacting with a View #466
   2. Design for List data type #978

@ghislaineguerin @ppii775 Please comment below with thoughts/concerns.

[ghislaineguerin]

@kgodey looks good

[kgodey]

Product priorities

1. Start research and documentation of Mathesar target use cases for alpha release.
2. Start figuring out goals for UI styling milestone.

[kgodey]

Comms Assignee schedule

Week	Person
2022-04-04 to 2022-04-08	Ghislaine
2022-04-11 to 2022-04-12	Kriti
2022-04-13 to 2022-04-15	Dominykas
2022-04-18 to 2022-04-22	Brent
2022-04-25 to 2022-04-29	Kriti
2022-05-02 to 2022-05-06	Pavish
2022-05-09 to 2022-05-13	Mukesh
2022-05-16 to 2022-05-20	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?

• Unfortunately I did zero coding last week. I was out for three days due to a horrendous stomach bug which made 3/4 of my family very sick. The two days I did work were entirely consumed by discussions, reviews, and comms.

What are you planning to work on soon?

• Improve UX when adding new records to a table with a NOT NULL column #775 is still my highest priority. It may require some more refactoring. I'm not sure. I need to get my head back into the problem before I have a good sense of how long I expect it to take. I'm really hoping I can make some headway on this, though I do have a number of smaller discussion/review/comms tasks queued at the moment.

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

• No

[pavish]

Pavish's check in

How did your most recent work go?

Much slower than planned. I was focused more on reviews, discussions and figuring out architecture during the week, and planned to get to focused coding during the weekend (when I'm not distracted by anything else), which did not work out due to personal issues.

What are you planning to work on soon?

My plan stays the same as last week, except that a lot of figuring out part is done. I'll have to do the grunt coding part.

• Lower-order selection list component and headless selection utilities #1250
• Frontend implementation for Boolean Mathesar type #257

I anticipate more discussions and PR reviews this week as well.

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

None

[kgodey]

How did your most recent work go?

I didn't do much last week other than meetings and keeping up with notifications because I was dealing with some personal issues. I have been reading books about design and copy, which have been helpful in thinking through future work.

What are you planning to work on soon?

1. Support GSoC as needed – proposal reviews, mentoring guidance, etc.
2. Write job descriptions for new roles and get the hiring process started
3. Start research and documentation of use cases and user personas for Mathesar's alpha releas. I'm prioritizing this to:
   1. help us create concrete goals for our launch preparation milestones (UI Styling, Deployment, etc.)
   2. get the team on the same page about product short-term and long-term goals, it should help with discussions like Mathesar money display and db options #1243
4. Think through how the team can collaborate better on the Working with Views milestone, since it will be big and highly interconnected.
5. Still on my plate, but not a priority this week:
   1. Set up style guide and tooling for consistency in backend code #1008
   2. Create pages for new engineering wiki structure mathesar-wiki#41

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

No.

[ghislaineguerin]

How did your most recent work go?

Really good. Design for views runs smoothly after initial data explorer definition

What are you planning to work on soon?

Data explorer spec round and spec updates
Design for #466

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?

Quite Slower than I expected as I got held up with some personal issues.

What are you planning to work on soon?

I have started working on issues in the Links between Tables milestone, planning to continue the progress with it.

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

None

Personal updates

I will be relocating in next few days, so I am anticipating some distractions and contributions will be slower than usual.

[mathemancer]

• How did your most recent work go?

Things are going well. I'm getting some programming done, but spending plenty of time fielding questions, going through PRs, and participating in discussions.

• What are you planning to work on soon?

I'm currently trying to figure out why my grouping PR broke seemingly unrelated e2e tests. I suppose that's why the tests are there, since I didn't expect the behaviors indicated to change. After that, I have one quick/easy case to finish up for numeric grouping (DB layer), and then I want to get character grouping done. I expect the character grouping to be easier than numeric, and be easier to reuse for multiple character-like types.

I'm going to wait until I have a few more grouping functions done before adding them to the "descriptive" part of the API, in the hopes that I'll be able to make the descriptions more useful with more of the grouping differences and commonalities in mind.

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

Not at the moment.