schaefera/utStudyBIble
Watch
1
0
Fork
You've already forked utStudyBIble
 0
Code Issues 62 Pull requests Projects Releases Packages Wiki Activity Actions

A proper design, a final name and a rebrand (after the v0.1 Shoulds) #95

New issue
Open
opened 2026-10-27 22:41:42 +00:00 by claude-bot · 10 comments
claude-bot commented 2026-10-27 22:41:42 +00:00
Collaborator

Owner's plan (PR #90 review): once the v0.1 Shoulds are done, do a design pass for the whole app, give it its final name ("utStudyBible" is a working name, CLAUDE.md), and rebrand.

Sequencing: after the other v0.1 Shoulds, before the polish Coulds that it would redo (#88, #93 and the icons issue), so those follow the design rather than getting done twice.

Likely parts (to be scoped together first, design before code):

  • Design language: colours, type scale, spacing, icon set (Lucide so far), how bars, menus, side sheets and dialogs look; written down (docs/) and built into the shared controls of #91 so pages pick it up in one place. Within the limits: QtQuick.Controls 2 only, Suru on the phone (#84: no colours that fight the system theme), docs/07 memory budgets.
  • Name: a final name, checked for clashes (OpenStore, other Bible apps, trademarks) and for how it reads in German.
  • Rebrand: the app id (utstudybible.schaefera, which affects the data path: migrate or keep), the manifest title, the icon and splash, the repo name, the po domain, and the docs and wiki.

Priority is a guess (Should, since the owner wants it before v0.1 is called done); relabel if it belongs to a later milestone.

Owner's plan (PR #90 review): once the v0.1 Shoulds are done, do a design pass for the whole app, give it its final name ("utStudyBible" is a working name, CLAUDE.md), and rebrand. Sequencing: after the other v0.1 Shoulds, before the polish Coulds that it would redo (#88, #93 and the icons issue), so those follow the design rather than getting done twice. Likely parts (to be scoped together first, design before code): - **Design language**: colours, type scale, spacing, icon set (Lucide so far), how bars, menus, side sheets and dialogs look; written down (docs/) and built into the shared controls of #91 so pages pick it up in one place. Within the limits: QtQuick.Controls 2 only, Suru on the phone (#84: no colours that fight the system theme), docs/07 memory budgets. - **Name**: a final name, checked for clashes (OpenStore, other Bible apps, trademarks) and for how it reads in German. - **Rebrand**: the app id (`utstudybible.schaefera`, which affects the data path: migrate or keep), the manifest title, the icon and splash, the repo name, the po domain, and the docs and wiki. Priority is a guess (Should, since the owner wants it before v0.1 is called done); relabel if it belongs to a later milestone.
claude-bot commented 2026-10-28 11:09:20 +00:00
Author
Collaborator

For the design document, from the F1 phone check (#10, comment 2134):

  • Destructive actions in red, starting with Remove in the module removal dialog.
  • Modules page notice: Refresh after an action (install, remove) should clear the previous notice, and the notice line looks crammed. Its place and spacing are part of the design.
For the design document, from the F1 phone check (#10, comment 2134): - Destructive actions in red, starting with Remove in the module removal dialog. - Modules page notice: Refresh after an action (install, remove) should clear the previous notice, and the notice line looks crammed. Its place and spacing are part of the design.
claude-bot commented 2026-10-30 15:40:11 +00:00
Author
Collaborator

Scoping proposal. The decisions here are yours; I'll start once they're made.

Proposed split (three PRs, in order)

  1. Design language. A docs/ page plus a mockup project covering the reading pane, footer, menu, side sheet, module manager and one dialog. I'd make 2–3 directions to choose from. After that I'd build it into the shared controls (#91 tokens in Theme.qml), so the pages pick it up in one place. This also covers comment 2141: destructive actions in red, and a Modules notice that clears on Refresh and has room to breathe.
  2. Name. 5–8 candidates, each checked against OpenStore, the other Bible apps on Linux, Android and iOS, a quick trademark search, and how it reads in German. You pick one.
  3. Rebrand. The app id, manifest title, icon and splash, po domain, docs and wiki. The repo rename is yours to do in Forgejo.

What I need from you

  • Design direction: any apps or looks you like or dislike? Should it stay close to Suru/system (the #84 constraint) or have its own accent colour?
  • Name: any ideas, words or a tone you want (plain/descriptive, Latin or Greek, a short word)? Does it need to work in English and German?
  • App id: changing utstudybible.schaefera moves the data path. My suggestion: change it now, before v0.1 has users. A one-time copy on first start from the old path would cover your own install, or you can just reinstall. The other option is to keep the id forever.
  • Order: should the name come first, so the mockups can use it?

Until you answer, I'm working on #124 and #125.

Scoping proposal. The decisions here are yours; I'll start once they're made. **Proposed split (three PRs, in order)** 1. **Design language.** A `docs/` page plus a mockup project covering the reading pane, footer, menu, side sheet, module manager and one dialog. I'd make 2–3 directions to choose from. After that I'd build it into the shared controls (#91 tokens in `Theme.qml`), so the pages pick it up in one place. This also covers comment 2141: destructive actions in red, and a Modules notice that clears on Refresh and has room to breathe. 2. **Name.** 5–8 candidates, each checked against OpenStore, the other Bible apps on Linux, Android and iOS, a quick trademark search, and how it reads in German. You pick one. 3. **Rebrand.** The app id, manifest title, icon and splash, po domain, docs and wiki. The repo rename is yours to do in Forgejo. **What I need from you** - **Design direction:** any apps or looks you like or dislike? Should it stay close to Suru/system (the #84 constraint) or have its own accent colour? - **Name:** any ideas, words or a tone you want (plain/descriptive, Latin or Greek, a short word)? Does it need to work in English and German? - **App id:** changing `utstudybible.schaefera` moves the data path. My suggestion: change it now, before v0.1 has users. A one-time copy on first start from the old path would cover your own install, or you can just reinstall. The other option is to keep the id forever. - **Order:** should the name come first, so the mockups can use it? Until you answer, I'm working on #124 and #125.
schaefera commented 2026-10-30 15:45:34 +00:00
Owner

Design direction: chess.com is an app whose interface I enjoy, but how well that translates to bible study apps, I don't know. I generally find more minimalistic designs more pleasant, reducing options on the main screens and preferring to organize them one or two levels lower, and also offering a "search everything (text, settings, app functions, etc)" feature in the app, much like Jetbrains does in IntelliJ.

Name: No need to prefer any one language, keep the name a bit more plain, as it should be very obvious what it's for just in the store listing without being the hyper generic "UT Study bible" or "uStudyBible" or what not.

App ID: yes, change it once a name is settled. use aps instead of schaefera for that segment in the future.

Order: Sure, name comes first.

Design direction: chess.com is an app whose interface I enjoy, but how well that translates to bible study apps, I don't know. I generally find more minimalistic designs more pleasant, reducing options on the main screens and preferring to organize them one or two levels lower, and also offering a "search everything (text, settings, app functions, etc)" feature in the app, much like Jetbrains does in IntelliJ. Name: No need to prefer any one language, keep the name a bit more plain, as it should be very obvious what it's for just in the store listing without being the hyper generic "UT Study bible" or "uStudyBible" or what not. App ID: yes, change it once a name is settled. use aps instead of schaefera for that segment in the future. Order: Sure, name comes first.
claude-bot commented 2026-10-30 15:46:50 +00:00
Author
Collaborator

Thanks. Here is what I'll do with your answers:

  • Order: the name first, then the design language, then the rebrand.
  • Design: minimalist, in the spirit of chess.com. The main screens keep only a few actions, and the rest goes one or two levels down.
  • Search everything: I'll file "search everything" (text, settings, app functions) as its own issue, because it is a feature and not only design. The design pass will leave a place for it in the main screen.
  • App id: it changes once the name is settled, to <name>.aps.

Name shortlist (a quick web search: app stores, F-Droid, linuxphoneapps, the UBports forum; not a trademark register yet)

The working name clashes outright: StudyBible is already on F-Droid as dev.studybible, an offline app with cross-references and Strong's.

Name Store listing reads as Clashes found
Bible Desk a desk you study the Bible at none found
Scripture Study exactly what it is "Ancient Path Scripture Study" (iOS); the phrase is common
Lamp Bible (Ps 119:105) a Bible reader Lamplight (a web Bible study workspace); a Fitbit "Lamp" verse watch face
Margin / Bible Margin study notes in the margin Wide Margin, an old Linux desktop Bible app (close)
Bible Workbench a study tool as far as I know, an existing commercial Windows Bible program (to verify)
Bible Explorer browse and study an existing Bible Explorer program (desktop, maybe mobile): avoid

Left out: PocketBible (Laridian), OpenBible (OpenBible.info, which also publishes cross-references), Berean (confused with the BSB translation), and Bible Notebook / Bible Notes (both taken on iOS).

My pick: Bible Desk. It is plain, and the store line "Bible Desk: offline Bible study" says what the app is for. I found no clash, it reads the same in German, and the id would be bibledesk.aps. Second choice: Scripture Study, which is clearer still but more generic.

Pick one, or name your own, and I'll run the full check on it before the rebrand: OpenStore directly, Google Play and the App Store, and a trademark search (EUIPO/USPTO).

Thanks. Here is what I'll do with your answers: - **Order:** the name first, then the design language, then the rebrand. - **Design:** minimalist, in the spirit of chess.com. The main screens keep only a few actions, and the rest goes one or two levels down. - **Search everything:** I'll file "search everything" (text, settings, app functions) as its own issue, because it is a feature and not only design. The design pass will leave a place for it in the main screen. - **App id:** it changes once the name is settled, to `<name>.aps`. **Name shortlist** (a quick web search: app stores, F-Droid, linuxphoneapps, the UBports forum; not a trademark register yet) The working name clashes outright: **StudyBible** is already on F-Droid as `dev.studybible`, an offline app with cross-references and Strong's. | Name | Store listing reads as | Clashes found | |---|---|---| | **Bible Desk** | a desk you study the Bible at | none found | | **Scripture Study** | exactly what it is | "Ancient Path Scripture Study" (iOS); the phrase is common | | **Lamp Bible** (Ps 119:105) | a Bible reader | Lamplight (a web Bible study workspace); a Fitbit "Lamp" verse watch face | | **Margin** / **Bible Margin** | study notes in the margin | Wide Margin, an old Linux desktop Bible app (close) | | **Bible Workbench** | a study tool | as far as I know, an existing commercial Windows Bible program (to verify) | | **Bible Explorer** | browse and study | an existing Bible Explorer program (desktop, maybe mobile): avoid | Left out: PocketBible (Laridian), OpenBible (OpenBible.info, which also publishes cross-references), Berean (confused with the BSB translation), and Bible Notebook / Bible Notes (both taken on iOS). **My pick: Bible Desk.** It is plain, and the store line "Bible Desk: offline Bible study" says what the app is for. I found no clash, it reads the same in German, and the id would be `bibledesk.aps`. Second choice: **Scripture Study**, which is clearer still but more generic. Pick one, or name your own, and I'll run the full check on it before the rebrand: OpenStore directly, Google Play and the App Store, and a trademark search (EUIPO/USPTO).
claude-bot commented 2026-10-30 15:49:57 +00:00
Author
Collaborator

I checked "Bible Desk" in full after you picked it. It turns up two clashes the first search missed:

  • BibleDesk on the iOS App Store: the same name, written as one word, also a Bible study app ($10, needs iOS 26, from Hardeep Kumar Sah). https://apps.apple.com/us/app/bibledesk/id6754764564
  • bibledesk.com: a Bible study book and web brand. Its copyright page mentions "the trademark" (the site didn't load for me, so I couldn't read more).
  • Close, in our own ecosystem: CrossWire's Bible Desktop (the JSword front end). SWORD users know that name.
  • OpenStore: no clash. The Bible apps there are Jubilee Bible, EveryBible and TheBookWurm.
  • Registers: no USPTO or EUIPO registration found for "Bible Desk" or "BibleDesk", but I searched through web results, not the registers themselves.

So we can use it, but it isn't clean: a store search for "Bible Desk" also shows the iOS app, and someone claims the name as a trademark. Your call:

  1. Keep Bible Desk. We are on different platforms, no registration was found, and it is plain. The risk is confusion with the iOS app, and a takedown if bibledesk.com holds a registered mark.
  2. Lectern. A lectern is the desk a Bible is read from. I found no Bible app with that name. The store line would be "Lectern: offline Bible study". It's less obvious on its own, which the subtitle makes up for. The id would be lectern.aps.
  3. Another name of yours. I'll run the same check on it.
I checked "Bible Desk" in full after you picked it. It turns up two clashes the first search missed: - **BibleDesk on the iOS App Store:** the same name, written as one word, also a Bible study app ($10, needs iOS 26, from Hardeep Kumar Sah). https://apps.apple.com/us/app/bibledesk/id6754764564 - **bibledesk.com:** a Bible study book and web brand. Its copyright page mentions "the trademark" (the site didn't load for me, so I couldn't read more). - **Close, in our own ecosystem:** CrossWire's **Bible Desktop** (the JSword front end). SWORD users know that name. - **OpenStore:** no clash. The Bible apps there are Jubilee Bible, EveryBible and TheBookWurm. - **Registers:** no USPTO or EUIPO registration found for "Bible Desk" or "BibleDesk", but I searched through web results, not the registers themselves. So we can use it, but it isn't clean: a store search for "Bible Desk" also shows the iOS app, and someone claims the name as a trademark. Your call: 1. **Keep Bible Desk.** We are on different platforms, no registration was found, and it is plain. The risk is confusion with the iOS app, and a takedown if bibledesk.com holds a registered mark. 2. **Lectern.** A lectern is the desk a Bible is read from. I found no Bible app with that name. The store line would be "Lectern: offline Bible study". It's less obvious on its own, which the subtitle makes up for. The id would be `lectern.aps`. 3. **Another name of yours.** I'll run the same check on it.
claude-bot commented 2026-10-30 15:52:40 +00:00
Author
Collaborator

Name decided: Lectern.

  • Store line: "Lectern: offline Bible study".
  • App id: lectern.aps.
  • OpenStore: a search for "lectern" returns no apps.

Next is the design language, with mockups for you to choose a direction from, and then the rebrand PR. The rebrand covers the app id with a one-time data copy from utstudybible.schaefera, the manifest title, the icon and splash, the po domain, and the docs and wiki. Renaming the Forgejo repo is yours to do when you want; links to the old name redirect.

**Name decided: Lectern.** - **Store line:** "Lectern: offline Bible study". - **App id:** `lectern.aps`. - **OpenStore:** a search for "lectern" returns no apps. Next is the design language, with mockups for you to choose a direction from, and then the rebrand PR. The rebrand covers the app id with a one-time data copy from `utstudybible.schaefera`, the manifest title, the icon and splash, the po domain, and the docs and wiki. Renaming the Forgejo repo is yours to do when you want; links to the old name redirect.
claude-bot commented 2026-10-30 15:54:10 +00:00
Author
Collaborator

Accent colour, from the owner: blue is the candidate, because it represents divinity.

In the design directions I'll try 2–3 blues, each in a light and a dark variant. Each must meet these checks:

  • Contrast: at least 4.5:1 against both backgrounds, for links, selected states and buttons.
  • Theme: it must not fight the Suru system theme (#84).
  • Distinct: it must stay apart from the red-letter text and from red for destructive actions.
**Accent colour, from the owner:** blue is the candidate, because it represents divinity. In the design directions I'll try 2–3 blues, each in a light and a dark variant. Each must meet these checks: - **Contrast:** at least 4.5:1 against both backgrounds, for links, selected states and buttons. - **Theme:** it must not fight the Suru system theme (#84). - **Distinct:** it must stay apart from the red-letter text and from red for destructive actions.
claude-bot commented 2026-10-30 17:49:53 +00:00
Author
Collaborator

Design directions are ready to compare: https://claude.ai/artifact/MwvxmpLR96sZkwbiCwAhp6 (private to the owner's account).

There are three directions. Each one shows the same four screens: reading, the verse sheet, the menu or search, and Modules with the Remove dialog. Each has a light and a dark variant. Every accent meets 4.5:1 or better. Destructive actions are red and kept apart from the red letters.

  • A · Quiet page: white paper and one deep blue (#1F5FBF / #7AA7FF). All controls sit in one thin footer; the rest is one tap down. "Search everything" opens a page that groups its results into verses, settings and actions (#138).
  • B · Board: closest to chess.com. It is dark first, with solid surfaces, a labelled bottom bar and a "More" page of tiles (#2563EB / #5B8CFF).
  • C · Ink and lapis: looks like a printed study Bible. Warm paper, lapis blue (#1E4FA8 / #8FB0F0), serif text, small-caps headings, hairline rules and one floating pill for the controls. Its verse sheet shows how a feature the module lacks is greyed out with a reason (Strong's).

All three cover comment 2141. The Modules notice gets its own block with room around it and is cleared on Refresh, and Remove is red.

Cost: directions A and C use a bundled text serif, Source Serif 4 or Crimson Pro. Each adds a few hundred kB to the click and no memory until it is shown. Liberation Serif is the fallback if we bundle no font.

Pick a direction, or mix them (for example A's footer with C's paper). I'll write the result into docs/ and the #91 tokens in Theme.qml.

**Design directions are ready to compare:** https://claude.ai/artifact/MwvxmpLR96sZkwbiCwAhp6 (private to the owner's account). There are three directions. Each one shows the same four screens: reading, the verse sheet, the menu or search, and Modules with the Remove dialog. Each has a light and a dark variant. Every accent meets 4.5:1 or better. Destructive actions are red and kept apart from the red letters. - **A · Quiet page:** white paper and one deep blue (#1F5FBF / #7AA7FF). All controls sit in one thin footer; the rest is one tap down. "Search everything" opens a page that groups its results into verses, settings and actions (#138). - **B · Board:** closest to chess.com. It is dark first, with solid surfaces, a labelled bottom bar and a "More" page of tiles (#2563EB / #5B8CFF). - **C · Ink and lapis:** looks like a printed study Bible. Warm paper, lapis blue (#1E4FA8 / #8FB0F0), serif text, small-caps headings, hairline rules and one floating pill for the controls. Its verse sheet shows how a feature the module lacks is greyed out with a reason (Strong's). All three cover comment 2141. The Modules notice gets its own block with room around it and is cleared on Refresh, and Remove is red. **Cost:** directions A and C use a bundled text serif, Source Serif 4 or Crimson Pro. Each adds a few hundred kB to the click and no memory until it is shown. Liberation Serif is the fallback if we bundle no font. Pick a direction, or mix them (for example A's footer with C's paper). I'll write the result into `docs/` and the #91 tokens in `Theme.qml`.
claude-bot commented 2026-10-30 18:11:44 +00:00
Author
Collaborator

Design language decided: C · Ink and lapis (owner, 2026-10-30, on the canvas https://claude.ai/artifact/MwvxmpLR96sZkwbiCwAhp6). A Bible app should feel calm and restful, so the directions that were too safe (A) or too loud (D, Ultramarine) are out. From B, every direction keeps the Menu pattern: 2×2 tiles plus a Continue card.

Mockup for the parts below: canvas board "C · Ink and lapis" (10 screens: paper, plain white and dark).

Planned PRs, one at a time:

  1. Palette and design doc (now): docs/10-design.md, and C's colour roles in SystemColours: paper in light mode, C's dark in dark mode, following the system switch live. The reading pane takes the new red letters, lapis verse numbers and note markers, and its verse highlight; the window, pages and sheets take the paper ground.
  2. Paper or White: a setting for the light ground, with Paper as the default.
  3. Type: bundle Crimson Pro for the text, with Liberation Serif as the fallback. Also the chapter heading (book name in small caps, lapis chapter number, hairline rule) and the floating footer pill. Memory effect stated in that PR.
  4. Menu one level down: tiles plus Continue, with only the tiles whose features exist.
  5. Rebrand to Lectern (lectern.aps, with a one-time copy of the data).

Search everything stays #138.

🤖 Generated with Claude Code

**Design language decided: C · Ink and lapis** (owner, 2026-10-30, on the canvas https://claude.ai/artifact/MwvxmpLR96sZkwbiCwAhp6). A Bible app should feel calm and restful, so the directions that were too safe (A) or too loud (D, Ultramarine) are out. From B, every direction keeps the Menu pattern: 2×2 tiles plus a Continue card. Mockup for the parts below: canvas board "C · Ink and lapis" (10 screens: paper, plain white and dark). Planned PRs, one at a time: 1. **Palette and design doc** (now): `docs/10-design.md`, and C's colour roles in `SystemColours`: paper in light mode, C's dark in dark mode, following the system switch live. The reading pane takes the new red letters, lapis verse numbers and note markers, and its verse highlight; the window, pages and sheets take the paper ground. 2. **Paper or White**: a setting for the light ground, with Paper as the default. 3. **Type**: bundle Crimson Pro for the text, with Liberation Serif as the fallback. Also the chapter heading (book name in small caps, lapis chapter number, hairline rule) and the floating footer pill. Memory effect stated in that PR. 4. **Menu one level down**: tiles plus Continue, with only the tiles whose features exist. 5. **Rebrand to Lectern** (`lectern.aps`, with a one-time copy of the data). Search everything stays #138. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
claude-bot commented 2026-10-31 09:15:17 +00:00
Author
Collaborator

Part 3 merged (#144). Part 4 (Menu page) is under way on feat/lectern-menu: tiles Modules and Settings only (History and Bookmarks wait for their features), plus the Continue card.

Part 5 decisions (owner, 2026-10-31):

  • Data: the app is AppArmor-confined, so lectern.aps can't read utstudybible.schaefera's folders, and the planned in-app one-time copy can't work. The app is unpublished and the owner's phone is the only install with data, so there's no migration code: after the first Lectern install, the old app's data, config and cache folders are copied into lectern.aps's once by adb, checked, and the old app is removed.
  • Rename depth: user-visible names and packaging only: app name Lectern, app id lectern.aps, the click/manifest/desktop/AppArmor files, window title, About, translation domain and docs. Internal names stay: the utsb-* crates, the utsb: log tag, UTSB_* env vars and the e2e tooling.

🤖 Generated with Claude Code

Part 3 merged (#144). Part 4 (Menu page) is under way on `feat/lectern-menu`: tiles Modules and Settings only (History and Bookmarks wait for their features), plus the Continue card. Part 5 decisions (owner, 2026-10-31): - **Data:** the app is AppArmor-confined, so `lectern.aps` can't read `utstudybible.schaefera`'s folders, and the planned in-app one-time copy can't work. The app is unpublished and the owner's phone is the only install with data, so there's **no migration code**: after the first Lectern install, the old app's data, config and cache folders are copied into `lectern.aps`'s once by adb, checked, and the old app is removed. - **Rename depth:** user-visible names and packaging only: app name Lectern, app id `lectern.aps`, the click/manifest/desktop/AppArmor files, window title, About, translation domain and docs. Internal names stay: the `utsb-*` crates, the `utsb:` log tag, `UTSB_*` env vars and the e2e tooling. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/e2e-pytest
feat/redesign-about
feat/redesign-first-start
feat/redesign-menus
feat/redesign-modules
feat/redesign-chooser
feat/redesign-settings
feat/lectern-rebrand
feat/lectern-menu
feat/lectern-type-footer
feat/lectern-light-ground
feat/lectern-palette
fix/sheet-theme
fix/unknown-v11n
i18n/part-2
fix/marker-colour
ci/module-cache
docs/mockup-check
fix/log-line-atomic
fix/sheet-scroll
feat/13-6d-tsk
feat/13-6c-markers
feat/13-6b-refs
feat/13-6a-notes-refs
fix/install-416-restart
fix/e2e-menu-retry
fix/back-one-transaction
feat/paragraph-starts
feat/verse-look
fix/empty-cipherkey
fix/mem-check-noise
chore/claude-config
ci/main-runs
refactor/shared-controls
feat/module-import
feat/offline-install-icons
feat/module-manager
tools/e2e-shots
fix/strongs-datapath
phase1/switch-bible
phase1/first-run
phase1/red-letters
phase1/e2e
phase1/quick-settings
ci/s3-sccache
phase1/picker-height
phase1/gettext
phase1/picker-history
phase1/build-info
phase1/core-layout
No results found.
Labels
Clear labels   
priority
Could
 MoSCoW: nice to have, done when time allows

  
priority
Must
 MoSCoW: the release isn't viable without it

  
priority
Should
 MoSCoW: important, but the release works without it

  
priority
Won't
 MoSCoW: not this release (kept for later)

  
type
Bug

No labels
priority
Could
priority
Must
priority
Should
priority
Won't
type
Bug
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
schaefera/utStudyBIble#95
No description provided.