Call with Andrew notes

[TkKonstantin]

Initial motivation:

• response time to issue 30 days
• ecosystem dashboard -> as a single source of tracking of all issues -> tracking stuff across the whole organization
• tracking the response rate and having additional metrics on issues created

Next functionality

1. Understanding how different projects work together
2. Packages linking and tracking libraries
3. Triaging issues of projects
4. Understanding how people are using all this open-source stuff (coz no tracking code in open source stuff)
5. Tracking the activity of projects using our libraries
6. Automatic crawler through GitHub
7. Tracking Hackathon submissions for quality of using our tech (tracking contributors as well)
8. General issue triaging

[TkKonstantin]

Similar resources:

• https://filecoin.ecosystem-dashboard.com/map
• https://ipfs.ecosystem-dashboard.com/map

Score calculator:

• https://filecoin.ecosystem-dashboard.com/repositories

Changes checking:

• https://ipfs.ecosystem-dashboard.com/discover <- check PL dependencies once a week

Further resources:

• https://ipfs.ecosystem-dashboard.com/search/highlights
• https://ipfs.ecosystem-dashboard.com/search
• https://timeline.ecosyste.ms/
• https://libp2p.ecosystem-dashboard.com/

[TkKonstantin]

Metadata and permissions of repos is a big challenge to maintain -> have separate metadata maintenance with some auth in PL

[TkKonstantin]

Kickstarting:

1. Exporting repos (e.g. Filecoin) and starting to track them and organize (pull on an hourly basis)
   • Query by Slap .json on the end of most URLs
2. Get a list then create a database for it
3. Add suitable metrics to data
4. Crawling by people? instead of adding repos manually
5. Potential orgs to add (as querying functionality) -> guess core contributors (outside PL as well)
6. Update interface for discoverability
7. Huge potential for suggesting possible contributors
8. Not published until validated functionality
9. Categories for contributors (e.g. PL natives, ecosystem, larger groups -> hackathons, etc.)
10. PL magic link for auth
11. Use dashboard as a feed to some other DB

[TkKonstantin]

Could be useful:

• Concept of dependencies event -> looking into dependencies changes (logic of what and why happened to add/remove dependencies)

[TkKonstantin]

Core reasoning:

• Better UI for understanding what is happening for all of the PL
• Discoverability of stuff within PL
• Highlight stuff that is already developed + identify main developers (talk to a human on slack button)

[TkKonstantin]

Asking for a site map