-
Notifications
You must be signed in to change notification settings - Fork 15
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
Discover collaborating orgs via contributor activity feeds #32
Comments
andrew
added a commit
that referenced
this issue
Jun 16, 2020
Here's the output of a similar query for libp2p, finding lots of the expected collabs and doing a good job of filtering out false positives:
|
One note here for both ipfs and libp2p: collabs that had already been imported into those dashboards where filtered out from suggestions, incase anyone was worried that those collabs had been missed. |
Filecoin didn't find many non-protocol orgs as potential collabs.
|
This is fantastic, thanks for pulling on this thread.
I'd like to have this running daily, tracking absolute number over time for
all three projects (including existing collabs), and pushing to Influx,
Grafana (or somewhere).
Additionally I'd like to have a daily digest email that covers all three
projects and shows additions and removals so that we can act within 24hrs
to onboard potential new users and also to know about *departures* (is
after the fact... but also might be the soonest possible for us to know).
Additionally additionally, I'd like this to run hourly and post
notifications to #collabs on Slack about additions/removals.
…On Tue, Jun 16, 2020 at 11:25 AM Andrew Nesbitt ***@***.***> wrote:
Filecoin didn't find many non-protocol orgs as potential collabs.
Organization GitHub code search for "filecoin" result count
ipld <https://github.com/ipld> 322
ipfs <https://github.com/ipfs> 135
ProtoSchool <https://github.com/ProtoSchool> 25
protocol <https://github.com/protocol> 8
ipfs-shipyard <https://github.com/ipfs-shipyard> 8
libp2p <https://github.com/libp2p> 7
drand <https://github.com/drand> 4
multiformats <https://github.com/multiformats> 1
rocicorp <https://github.com/rocicorp> 0
quarantenalive <https://github.com/quarantenalive> 0
ipfs-rust <https://github.com/ipfs-rust> 0
soramitsu <https://github.com/soramitsu> 0
celo-org <https://github.com/celo-org> 0
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#32 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAAMHN7YTIJN4DCWA35EIVTRW6FGLANCNFSM4N6O562A>
.
|
andrew
added a commit
that referenced
this issue
Jun 17, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For issues and pull requests that are opened by non-core non-collab folk, we can look in their personal activity feeds for
PushEvent
events to see which orgs that user has commit access to, and so is likely to be a core contributor of.We have the
contributors
table now so we can store the etag of the users latest activity poll to keep api requests to a minimum, we can also store the events in the existing events table.This can then be used to generate some kind of weekly report of suggested orgs as potential new collabs, perhaps even speculatively indexing some of their repositories to look for dependencies on internal packages.
The text was updated successfully, but these errors were encountered: