Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Telescope Overview with Release 3.0 Information #3739

Open
2 tasks done
AmasiaNalbandian opened this issue Oct 26, 2022 · 5 comments
Open
2 tasks done

Update Telescope Overview with Release 3.0 Information #3739

AmasiaNalbandian opened this issue Oct 26, 2022 · 5 comments
Assignees
Labels
developer experience Helping the Developer Experience type: documentation (docs) Improvements or additions to documentation

Comments

@AmasiaNalbandian
Copy link
Contributor

Where is the problem?

  • Link comment/file/somewhere else
  • Screenshot

What exactly is wrong:
When you go to the document webpage you see the area for release 3.0, however, there is no information on what happened in release 3.0 - which has come and gone.

What should it be instead:
We need to update this section to include the changes made in release 3.0.

There's a few other places we need to add more information regarding release 3.0

@AmasiaNalbandian AmasiaNalbandian added the developer experience Helping the Developer Experience label Oct 26, 2022
@AmasiaNalbandian
Copy link
Contributor Author

image

@AmasiaNalbandian
Copy link
Contributor Author

And also change the timelines:
image

@AmasiaNalbandian AmasiaNalbandian added the type: documentation (docs) Improvements or additions to documentation label Oct 26, 2022
@AmasiaNalbandian
Copy link
Contributor Author

@sirinoks Hi Alex, I know you did a lot of the documentation and projects for release 3.0. Would there be a best resource to gather all of this to add into the documentation here?

@sirinoks
Copy link
Contributor

@sirinoks Hi Alex, I know you did a lot of the documentation and projects for release 3.0. Would there be a best resource to gather all of this to add into the documentation here?

@AmasiaNalbandian
Good question. Some would be in triage notes, like here. Would be cool to be able to rewatch the meetings we had, but I don't know if we have an ability to. There's also a priorities project used for organization. Another possible thing to check is people's blog posts. Usually final blog posts would be the best, as some people might summarise their progress.

There isn't a single place to look currently, which makes me want to solve this for the future generation.. If you want to meet in some call, or start a discussion to arrange all the topics and areas, I'm down. This will be needed anyway, since we need a "map of microservices" for docusaurus. Collecting such information would greatly help in this specific issue. I can give you an overview of the things I know myself, but it will not be complete.

PS: Perhaps for the next generation, after each week's triages, there should be a specific task to complete - in notes, or to add to notes - just update the docusaurus file with what was added. And after a release - review what was added and make it look nicer..?

@RC-Lee
Copy link
Contributor

RC-Lee commented Feb 10, 2023

At this point I think it'll be hard for just one person to summarize what we did since we had a rather large group.

I can list some of the things I remember, and obviously there's a lot of other stuff, but hopefully it'll help.

  • Improved indexing with Elasticsearch for implementation of search autocomplete features.
  • Combined Satellite into our monorepo
  • Launched our own Docker registry
  • Began initial work on a React Native mobile app
  • Removed legacy backend with Parser microservice.
  • Replaced Firebase with Supabase as a back-end data store
  • New docs site on Docusaurus with documentation updates and localization

(I'll add more if I remember some later on)

@RC-Lee RC-Lee self-assigned this Sep 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
developer experience Helping the Developer Experience type: documentation (docs) Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

3 participants