Recent submissions

Comment · 2 years ago
Comment · 3 years ago
Not really funny. When I ask it to perform regular tasks, it does it with no sarcasm or dark shades in the way it is performed. Not really the evil twin of ChatGPT
Comment · 3 years ago
We've found some of the best engineers from the open source communities, but it's never been an easy task. Outbound on this has always been a lot of work, with low response rates.

Good to see a two sided solution for this. Keen to try out soon

Comment · 4 years ago
While their current focus is on badges and rewards using tokens, I see other possible directions for this product that could transform the opensource landscape. The founders seem to be looking at this direction in the mid-to-long term as per a comment on ProductHunt.

The early contributors to an Open source project often go unrewarded when it becomes a commercial hit.

Cases in point - Mongo, Hadoop (Hortonworks), Memsql, etc. started out with a good amount of community support, and later went on to becoming commercial successes. While they recognized a lot of the contributors through various programs, and sometimes hired them in, the others who didn't join their journey full time might not have benefited.

Many other companies start with a "Develop in the open" philosophy now, despite being VC backed from early stages - cases in point Meteor, Gitlab, Appsmith, etc. The community engagement is slightly on the lower side once the project is well staffed. The motivation seems to go down.

What if the contributors could have a pie of the company? A very small pie that is proportional to the importance of the feature or bug fix at that point in time. But, as the company grows, the value of the pie grows. Just like an ESOP, or any token. Could say a project set aside 20% of their enterprise value as tokens, and use them as rewards to drive their roadmap with the community? Higher the importance, higher the bounty. That could change the dynamics around OSS contributions, which are currently driven more by the interest of the contributor more than the importance of a feature or a fix to the project.

I see Aviyel could also potentially drive such a shift.

Saw them on Producthunt today - https://www.producthunt.com/posts/aviyel

The comment referred to at the top of this post - https://www.producthunt.com/posts/aviyel?comment=1785981

Comment · 6 years ago
Very helpful list. But it would be good to see a list that is organized around objectives than the current set of categories. Ultimately, one asks these questions to get a certain outcome or information. Starting from there would be better.
Comment · 6 years ago
We use a mix of confluence and slack groups. We have one slack group per type of learning (RCAs for failures, best practices in engineering / manufacturing / logistics, etc., Top of the mind thoughts, interesting reads). We use confluence to do detailed documentation or writing, and slack to share and drive visibility.
Comment · 13 years ago
Cant expect more transparency. Thanks for reasoning out.
Comment · 13 years ago
Another handy feature would be - ability to call teammates from within hipchat. When I read the title, that is the feature I expected. But even this is pretty neat.

Live from the official Hacker News API

A modern reader for Hacker News · SvelteKit + Skeleton