I'm Sheriff this week. During the weekend we received an email from the Prof that we were nearing the end of our term, and release 2.9 would be the last release for new features. The meeting on Tuesday was supposed to help people answer the following questions:
1. Which part of Telescope 3.0 do I own?
2. Which exsting Issues are part of this? Which new Issues do I need to file in order to properly describe the work? When will those issues be filed?
3. Who can I depend on for support in development, debugging, testing, and reviews? I can't do this alone.
4. What are the risks that I see, which could prevent me from getting this shipped?
5. How will I mitigate these risks?
Since it didn't really go as planned. As Sheriff, it is only right that I write this blog as an example, so I can encourage my fellow classmates to write a blog to answer these questions as well.
1. Which part of Telescope 3.0 do I own?
The Search Service. Most specifically ElasticSearch. For 2.9 I want to get some Autocomplete features in.
2. Which exsting Issues are part of this? Which new Issues do I need to file in order to properly describe the work? When will those issues be filed?
The Autocomplete will require many parts, including touching code within the legacy backend or the new Parser, the Search Service, and the front-end Search Bar. Tests will also need to be included, and the following issues will need to be involved.
- Backend - #1417-Add author suggestions to Elasticsearch indexer backend
- Backend tests - #3224-Tests for the ElasticSearch Indexer in the backend and Parser
- Search Service and tests - #3225-Updating Search Service and tests to implement Autocomplete for Authors
- Front-end - #3226.
- Meta issue - #1260- Add autocomplete to search for Authors, which seemingly has some front-end support for autocomplete.
3. Who can I depend on for support in development, debugging, testing, and reviews? I can't do this alone.
Besides the Prof, anyone who's worked on, written blogs about for, or have shown a keen interest in the Search service. Off the top of my head, but not limiting to Amasia, Jia, and Josue (alumni)
4. What are the risks that I see, which could prevent me from getting this shipped?
Besides a limiting time factor, the swap from legacy backend to the Parser service could greatly complicate things. It may also take a long time for ElasticSearch indexing to work as planned.
5. How will I mitigate these risks?
Keeping a close eye on the Parser service. Splitting things off in smaller issues (already done). As well as doing lots of tests and asking for reviews for the autocomplete implementation. As mentioned in my last blog, making use of the dev tools in Kibana could greatly help with testing indexing and search requests.
Top comments (0)