4 ms·

UI-wise, once I've clicked on a person in the graph, I don't see how to get back to the whole graph with that person not highlighted. More importantly, I don't

UI-wise, once I've clicked on a person in the graph, I don't see how to get back to the whole graph with that person not highlighted. More importantly, I don't understand what "collaboration" means. People who have ever touched the same file? I don't even see files, only "areas". And there don't seem to be any edge weights, i.e., if person A has collaborated with person B once, and is collaborating with person C every day, the A-B and A-C edges in the graph look the same, so I don't see if there really is a close collaboration or not. The latter point also means that your example from https://www.networkperspective.io/hr/ https://www.networkperspective.io/hr/ is very artificial, as a real graph will pretty much never have "brokers" or "peripheral" nodes. (These are first impressions without having read any docs, if there are any.) For whatever it's worth, I'm working on a big project with many collaborators, and I do use git annotate to figure out who knows what or who would be a good person to tag for a code review. But this also means that I know that not every change to a file should be weighted equally. For example, renaming something in one file might mean that I need to touch 50 others, and I will show up as a "collaborator" on those files even if they are outside my area of expertise. I really need to use some more complex judgement to see who is a "main" contributor to a file, especially to the parts relevant to my current work. So I think that very naively mining this data and dumping it on the screen as a big ball of string is not very useful. Deeper analysis would be needed IMHO.

n16e 7y ago
Thank you for your insights, that is very valuable. UI wise - I tried to make the browser back button work everywhere - so I assumed this as a standard ways of going back where you've been. But maybe that is not what people expect and it should be more obvious. Yeah the collaboration is calculated two step. First I make a dynamic interaction graph, with timestamped edges. When a person touches a file I mark it as an interaction with everyone else who touched the file before (timestamped directed edges). Then I transform this interaction graph into collaboration graph. I consider two people collaborate on a file when the interaction is bi-directional - i.e. they both touched the same file within given time period. That way we can limit collaboration to a given time window, like for instance last 30 days, or whole project lifetime like the demo shows. But you make a very good point about refactoring and renaming for instance class name that might imply changes across many files that outside your expertise. Yet still a person profile shows "Collaborators by areas" what is a proxy to one expertise - the more collaborators you have in a certain area the more experienced you should be in there. The example from https://www.networkperspective.io/hr/ https://www.networkperspective.io/hr/ refers not only to code collaboration, but becomes more valid if you plug in other data sources like formal structure, meetings / email metadata, like shown on the other demo https://bit.ly/2VRWdaB https://bit.ly/2VRWdaB We hand a long journey with this product starting with survey data collection as we were obsessed with privacy, then adding other data sources (as it turned out we shouldn't worry about mining data that is public or semi public anyway). Now I implemented this git integration and hence asking HN community for an opinion about how useful this might be. Anyways thank you for all the feedback, I'll spend more time going through it today, and I appreciate it very much.
- tom_mellior 7y ago
  > I tried to make the browser back button work everywhere Ha. That makes sense, but I admit that I didn't dare try it since so many web applications break when you use the back button. Congratulations on supporting it, I'm all for keeping it, but as things stand (and it's not your fault) users will expect an in-app back button as well. > I consider two people collaborate on a file when the interaction is bi-directional - i.e. they both touched the same file within given time period. I see, that's clever. Thanks for your answers, and all the best with this project!

n16e 7y ago

Thank you for your insights, that is very valuable. UI wise - I tried to make the browser back button work everywhere - so I assumed this as a standard ways of going back where you've been. But maybe that is not what people expect and it should be more obvious. Yeah the collaboration is calculated two step. First I make a dynamic interaction graph, with timestamped edges. When a person touches a file I mark it as an interaction with everyone else who touched the file before (timestamped directed edges). Then I transform this interaction graph into collaboration graph. I consider two people collaborate on a file when the interaction is bi-directional - i.e. they both touched the same file within given time period. That way we can limit collaboration to a given time window, like for instance last 30 days, or whole project lifetime like the demo shows. But you make a very good point about refactoring and renaming for instance class name that might imply changes across many files that outside your expertise. Yet still a person profile shows "Collaborators by areas" what is a proxy to one expertise - the more collaborators you have in a certain area the more experienced you should be in there. The example from https://www.networkperspective.io/hr/ https://www.networkperspective.io/hr/ refers not only to code collaboration, but becomes more valid if you plug in other data sources like formal structure, meetings / email metadata, like shown on the other demo https://bit.ly/2VRWdaB https://bit.ly/2VRWdaB We hand a long journey with this product starting with survey data collection as we were obsessed with privacy, then adding other data sources (as it turned out we shouldn't worry about mining data that is public or semi public anyway). Now I implemented this git integration and hence asking HN community for an opinion about how useful this might be. Anyways thank you for all the feedback, I'll spend more time going through it today, and I appreciate it very much.

tom_mellior 7y ago
> I tried to make the browser back button work everywhere Ha. That makes sense, but I admit that I didn't dare try it since so many web applications break when you use the back button. Congratulations on supporting it, I'm all for keeping it, but as things stand (and it's not your fault) users will expect an in-app back button as well. > I consider two people collaborate on a file when the interaction is bi-directional - i.e. they both touched the same file within given time period. I see, that's clever. Thanks for your answers, and all the best with this project!