Opened at 2021-08-02T14:41:07Z
Last modified at 2021-08-02T14:44:08Z
#3755 reopened task
GBS design discussion
| Reported by: | itamarst | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | unknown | Version: | n/a |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
Starting point for thinking about GBS refactor, as it pertains to Tahoe-LAFS internals. Will probably split this up a bunch.
Questions:
- Should implementation be in Python?
- What should internal API design look like to deal with transition?
Change History (2)
comment:1 Changed at 2021-08-02T14:42:23Z by itamarst
- Resolution set to invalid
- Status changed from new to closed
comment:2 Changed at 2021-08-02T14:44:08Z by itamarst
- Resolution invalid deleted
- Status changed from closed to reopened
Instead of discussing in ticket, going to create a design document in a branch so I can use an actual editor.
Note: See
TracTickets for help on using
tickets.
Actually ticket isn't good way to do this.