Hacker News new | past | comments | ask | show | jobs | submit login

Just to clarify, I was never a developer of Passbolt. I think they based their repository off of CakePHP (which I do maintain) and inherited all the commit history that way.



Thank for the clarification. Sorry for the misunderstanding this caused.


I'm guessing GitHub's contribution insights sort of gave you this impression.

https://github.com/passbolt/passbolt_api/graphs/contributors

What I'm working on are developer insights and I've found the most intuitive way to look at contributions is to sort them by latest commits.

https://imgur.com/msfE9vS

With this type of display, you can quickly see who is contributing on an active basis, and for how long. A good example would be the vscode repository.

https://imgur.com/aX66Gj5

Here you can see a lot of developers have been contributing on a steady basis for quite some time.


Indeed GitHub's contributors graphs gave me the impression that https://github.com/markstory worked on passbolt. Isn't that is what they are supposed to?

Wish you all the best with your enhanced developer insights.


Yes the repository was forked from CakePHP v2, before the framework was moved as a composer dependency, so v2 contributors are shown as Passbolt contributors.


Here's some extra context.

https://imgur.com/mzdeA65

The last contribution was over 4 years ago (first contribution was 12 years ago), which would be the remnants of the fork.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: