Dokieli is fantastic, but from what I know prose-document focused. A few projects are implementing linked data components, which allow choosing other pods or information sources, and that would be a basis of distributed project development. Original human text is important, of course, but can be a problem when it's overwhelming. There should be every opportunity and incentive to include dynamic well defined views. I'm doing this with components embedded in markdown (mdx), and smartdown has an implementation based on this approach as well. The embedded approach can help solve the polish issue, since people can embed components and focus on their own style.
One immediate outcome is the regular This Week in Solid bulletins could be largely automated, with curated queries from different sources. Embedding task tags across repos would allow a very fine overview of ongoing activities.
@csarven @csarven the context is "dogfooding," using our own tools to prove they work and practically develop them. In this case, to support the most people, start with the top level, the main project summary; This Week in Solid. Write simple importers for everything related to Solid news and development to the degree if it's not a query response it doesn't exist. That would require all sorts of different queries in the early days, from github organizations and repos, forums, chat, etc. But all those APIs exist.
Consolidate them to one linked data store, using a Curate component that allows an editor to filter them (of course saving the result in linked data, so other people can develop with that list). Not only does it become progressively easier for any person to get a live top-level view, useful APIs (github, etc) are getting linked-data-ified, with highly reusable curated data as another product. Aaaaand it's an excellent demonstration of decentralized social linked data that solves real-world problems.
https://solidproject.org/inbox/this-week-in-solid/2019-08-30/or whatever... indeed we can list all of the activities automagically. That's about as simple as it gets right now I think.
<> a as:Announce ; as:actor <the agent that's sending the notification> ; as:object <the thing that's of interest to the Solid community> ; ... and so on...