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

Milestone 1 #4

Closed
michielbdejong opened this issue Jan 17, 2023 · 4 comments
Closed

Milestone 1 #4

michielbdejong opened this issue Jan 17, 2023 · 4 comments

Comments

@michielbdejong
Copy link
Contributor

michielbdejong commented Jan 17, 2023

Copied from the proposal:
The budget is primarily for human labour to realise the project's goals. The work will build on the foundations of the prior Federated Timesheets project, by establishing a federation involving several systems for issue-tracking (in addition to time-tracking), with the added capability of live data-sharing between a subset of those systems.

To underpin this, Milestone 1 will deliver the vital prerequisite work of thinking through the theoretical grounding of the federation, addressing the technical challenges captured below (including the implications for privacy and transparency), and specifying explicitly a follow-on iteration of the “federation protocol” described there. Estimated effort: 210 hours (MdeJ: 112,5h, AGM: 75h, GS: 22,5h).

@michielbdejong
Copy link
Contributor Author

Sub task: pondersource/CYB#34

@michielbdejong
Copy link
Contributor Author

michielbdejong commented Jan 17, 2023

What should be the deliverable?
I'm thinking maybe something like: pseudo code and elaborate and well-structured documentation (probably about 20 pages or so) for all the components involved in both timesheets and task tracking, with detailed lists of design choices and options.

@michielbdejong
Copy link
Contributor Author

As discussed in today's standup, one topic would be to document how edits are shown to the user.
Notes from @mlesmenio:

Two-way sync:

Maybe merge information as stated by different users in order to have 1 truth that supports multiples truths (e.g: Manuel said X, Michiel said Y);

Maybe expose a Github interface;

One-layer for state
One-layer for history of state changes
One layer for merge operations

@michielbdejong michielbdejong changed the title milestone 1 (Ponder Source part) milestone 1 Jan 19, 2023
@michielbdejong michielbdejong changed the title milestone 1 Milestone 1 Jan 19, 2023
@michielbdejong
Copy link
Contributor Author

Moved to Milestone 1.

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

No branches or pull requests

1 participant