Skip to content

Conversation

j12y
Copy link
Member

@j12y j12y commented Jan 27, 2025

This is experimental branch to discuss ideas for #29

Events Feedback

I'm looking for feedback on the following:

  • the list of aggregators and use cases in events.md
  • the events.schema.json which is partially complete to be an example and test how validation would work
  • fosdem.org.json for an example of a more complete data file with proposed properties and nesting
  • design.md for notes about how it would all fit together

Tools Feedback

Extended to provide some examples of a similar approach to tools.

  • list of existing collections in tools.md for a justification of persona and task-based categorization
  • tools/data/*.json for some examples

@j12y j12y self-assigned this Jan 27, 2025
@j12y j12y requested a review from a team as a code owner January 27, 2025 15:55
@j12y j12y requested review from oleg-nenashev and robearlam and removed request for a team January 27, 2025 15:55
@j12y j12y linked an issue Jan 27, 2025 that may be closed by this pull request
6 tasks
@j12y j12y marked this pull request as draft January 27, 2025 15:56
@j12y j12y changed the title [WIP] proof of concept investigation for events aggregation [WIP] proof of concept investigation for events and tools aggregation Mar 2, 2025
@j12y j12y added the hold On hold for dependencies label Apr 7, 2025
@j12y
Copy link
Member Author

j12y commented Apr 7, 2025

This POC was useful for testing a concept. There is no intention to integrate it into this repository but putting it on hold so that it can continue to be used as a reference as the persona-library, tools-catalog, and events-directory are built out in separate repositories.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

hold On hold for dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Aggregation Proof of Concept

1 participant