Hello there! I'm FG (short for François-Guillaume 🇫🇷), the founder of Quack AI.
tl;dr: We help large software companies run like the most efficient open-source projects. In the future, top-tier developers in those organizations will be able to contribute to pivotal projects, regardless of what teams they're from.
Successful OSS projects are well-organized communities where information is shared and valued. Recognizing this gold standard, corporate giants like Microsoft and IBM are shifting towards 'innersource' - a strategy that fosters ownership, augments communication, and bolsters productivity. However, like many cluttered OSS projects, the vast array of solicitations and varying expertise easily gets overwhelming.
Our Dual-Fold Approach:
While maintaining popular OSS projects and being an active contributor to PyTorch, I’ve often faced the frustration of seeing Pull Requests from newcomers and thinking “If only that person had the reflex to do XYZ.” Those unwritten norms, which often evade CI restrictions, only sink in after repeated code reviews and numerous trials and errors. This uneasy feeling that “it would be so easy if they were to do ABC” highlights the absence of a solid framework for collaborative development.
I tend to describe myself as a "Deep learning engineer by day, open source contributor by night 🦇" which is fairly accurate! On top of being among the top contributors of PyTorch, I’ve led the development of the open-source OCR library of devtool company Mindee (YC W21). I experienced first-hand how some open-source communities are structured to achieve high engagement & productivity, which now appeals to software behemoths.
Up to revolutionize developer collaboration? Let’s get quacking then!