Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

1-click export MVP Tracking issue #39588

Closed
18 tasks done
sashaostrikov opened this issue Jul 28, 2022 · 6 comments
Closed
18 tasks done

1-click export MVP Tracking issue #39588

sashaostrikov opened this issue Jul 28, 2022 · 6 comments
Labels

Comments

@sashaostrikov
Copy link
Contributor

sashaostrikov commented Jul 28, 2022

Plan

This is a tracking issue for 1-click export project MVP. Related discussion can be found here: https://github.com/sourcegraph/sourcegraph/discussions/37930

This issue can be considered closed when the MVP version of the project is implemented and 1-click export can be successfully used in production.

Due to its nature, 1-click export feature is easy to extend (by adding new processors which fetch additional data about SG instance), that's why this tracking issue is not intended to be open until 100% of 1-click export functionality is developed and on the contrary tracks the progress of an MVP version implementation. Every future extension (GH issue) can be linked to this issue and implemented separately, out of the scope of this tracking issue.

Tracked issues

@unassigned

Completed

@jhchabran

Completed

@sashaostrikov

Completed

Legend

  • 👩 Customer issue
  • 🐛 Bug
  • 🧶 Technical debt
  • 🎩 Quality of life
  • 🛠️ Roadmap
  • 🕵️ Spike
  • 🔒 Security issue
  • 🙆 Stretch goal
@sourcegraph-bot-2
Copy link
Collaborator

Heads up @jplahn - the "team/repo-management" label was applied to this issue.

@sqs
Copy link
Member

sqs commented Jul 28, 2022

(cc @kstretch9 because this might relate to the OpenTelemetry export stuff, either actually or just from a customer's POV)

@sashaostrikov
Copy link
Contributor Author

One-click export weekly update

Week 2022/8/1 — 2022/8/5

What is done

  • Basic archiving functionality
  • Export of site config
  • Export of code host configs (all of them)
  • Export of external_services table rows
  • Export of external_service_repos table rows

Goals for the next week

  • Adding the endpoint to frontend REST API (in progress, expected by EOD Monday)
  • Creating the UI

Risks

  • Not a risk, but implementing UI from scratch within the team of backend developers is going to be fun.
    • However, this risk will be mitigated by working with @ryphil and demoing UI mock ups to CEs, AERs and interested customers

Notes

  • Basically, finishing with REST API + UI will let us test the feature internally on s2, which should give us valuable feedback on usability 🎉

cc @jplahn

@ryphil
Copy link
Contributor

ryphil commented Aug 7, 2022

@sashaostrikov - I just cleaned up our GitHub and these tracking issues may not be needed any longer! I tagged each ticket with the 1-click export Epic and created this view to show progress. Thoughts?

@sashaostrikov
Copy link
Contributor Author

@ryphil that's nice, thank you!

I think I want to keep this issue just to have a single place of project updates, so it will also be easier for me to track the progress after I am back from PTO (instead of jumping across Slack channels searching for updates).

But as soon as it is finished, we should close this ticket and continue working on post-MVP 1-click project in scope of your Epic :)

@sashaostrikov
Copy link
Contributor Author

@sourcegraph/delivery (which may be a legacy handle, but still)
Is this an active project?
If not, I want to close this issue.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants