Let's make the email demo really good
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 15/100
Research direction
The issue identifies only the email demo and a desired search experience; no files, tests, or entry points are named. Start by locating the email demo and its current search flow, then clarify a bounded feature and acceptance criteria before implementation. Done is not defined beyond making personal email search better without creating a hosted service.
Written by the indexing model from the issue text.
Description
So good that I'll actually want to use it for searching my own email instead of GMail's own search (which is okay but not amazing, and recent tweaks just make it more chaotic).
But not so good that it becomes a service that everyone can just subscribe to -- I don't want to deal with running a service that might go down, etc.
- Dominant language
- Python
- Stars
- 889
- Forks
- 75
- Avg merge
- 3d 33m
- Merged PRs (30d)
- 12
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/typeagent-py
-
Memory and SQLite term indexes normalize terms differentlyPossibly taken @bmerkle claimed this 10 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 56/100
microsoft/typeagent-py#322 ·
Maintainers usually reply within 2 days
-
Draft: rename modules for clearer naming (interfaces_* split, _index family, import/ingest)May be free again @bmerkle claimed this 68 days ago, and no pull request is open. Open
microsoft/typeagent-py#307 · 6 comments · 1 assignee ·
Maintainers usually reply within 2 days
-
Difficulty 4/5 3-5 days Newbie friendliness 45/100
microsoft/typeagent-py#270 ·
Maintainers usually reply within 2 days
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/typeagent-py#171 · 1 comment ·
Maintainers usually reply within 2 days
-
Code Quality & Cleanup (from TODO.md)May be free again @shreejaykurhade claimed this 182 days ago, and no pull request is open. Open
Difficulty 5/5 Over a week Newbie friendliness 25/100
microsoft/typeagent-py#112 · 15 comments ·
Maintainers usually reply within 2 days
All issues in microsoft/typeagent-py
Similar issues
-
documentation
Difficulty 1/5 Under an hour Newbie friendliness 65/100
ansys/pydpf-core#3547 ·
Maintainers usually reply within 1 day
-
core
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
vectorize-io/hindsight#5457 ·
Maintainers usually reply within 1 day
-
[Bug]: LangChain drops OpenAI Responses text blocks from session recordingPossibly taken @ktz03 claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
volcengine/OpenViking#5806 ·
Maintainers usually reply within 1 day
-
HTML: <template> content is extracted as document textPossibly taken @ryanmeowy claimed this today. Openbug html
Difficulty 1/5 Under an hour Newbie friendliness 82/100
docling-project/docling#4714 · 2 comments ·
Maintainers usually reply within 1 day
-
APIv2 event data accepts a non-string reply and a NaN upper_boundPossibly taken @awss1i claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
freedomofpress/securedrop#7946 · 1 comment ·
Maintainers usually reply within 2 days