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

What should we deliver for milestone 1? #7

Open
michielbdejong opened this issue Jan 19, 2023 · 9 comments
Open

What should we deliver for milestone 1? #7

michielbdejong opened this issue Jan 19, 2023 · 9 comments
Milestone

Comments

@michielbdejong
Copy link
Contributor

(continued from #4 (comment)):
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 michielbdejong added this to the Milestone 1 milestone Jan 19, 2023
@mcalligator
Copy link
Collaborator

Key outputs required for this milestone include:

  • a refined definition of federation, taking into account privacy, transparency, integrity, data sharing mode (ad hoc, scheduled, live, etc.); and
  • a protocol specification for federation.

@michielbdejong
Copy link
Contributor Author

  • different types of nodes
  • different use cases
  • different topologies

@mcalligator
Copy link
Collaborator

Yes, agreed! Regarding use cases, I was thinking of including some high-level example scenarios as context for them, and providing some more detailed use cases, expanded further into user stories with acceptance criteria for specific functional deliverables implemented in code.

As for types of node, I've captured those in draft in the current definition of Federation in the Wiki.

For topologies, we already described these in the Timesheets project, but it would be really good to build on that with the different real-world systems involved in this project, and depict these in a set up associated diagrams.

@michielbdejong
Copy link
Contributor Author

I think we can do a lot of research already using just the use case that we have already partially satisfied with the timesheets network. A central question could be "how can we make the timeld gateway support two-way sync of multi-homed data?"
See #16 (comment)

@michielbdejong
Copy link
Contributor Author

I'm preparing an RfP for the Ponder Source side of milestone 1, here: #23

@mcalligator @gsvarovsky are you still planning to claim milestone 1b (975 euros) and your part (3413 euros) of milestone 1a? If so, do you want to coordinate or is it fine if we work in separate processes?

@mcalligator
Copy link
Collaborator

@michielbdejong it's been a while since we've had a chance to focus on this - could we maybe have a call to discuss, say, early next week?

@michielbdejong
Copy link
Contributor Author

I'll email you

@michielbdejong
Copy link
Contributor Author

RfP's for 1a and 1c sent.

I asked @mcalligator in the matrix channel what the status of 1b is.

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

2 participants