4 ms·
Now this is how you pitch your product to an open source company
- jedberg 16y agoCongrats to the embed.ly team for doing it right and making our job easier.
- cookiecaper 16y agoAs a guy who runs a reddit install, I am pleased to hear that we'll be getting updates soon. : ) Is github going to be kept in sync with reddit's copy now? Is that the idea there?
- jedberg 16y agoWe are trying to be a lot better about keeping everything in sync. Our goal right now is to publish weekly, but we'll see how that actually works out.
- deleted 16y ago[deleted]
- CUViper 16y agoThe best way to keep in sync is to remove the need: just publish everything live and unfettered to a public repository.
- jedberg 16y agoWe used to do it that way, but we stopped because it was breaking people's installs. Sometimes we have to push half-baked code, and if you sync at that point, bad things may happen. Also, we stopped doing it because it meant revealing features before we were ready to reveal them, like sponsored links. That is when we split the public and live repos. Before that, the public repo was the live repo.
- CUViper 16y agoHi, thanks for responding. Obviously, I'm not involved in reddit development, since I didn't know you used to publish live. But still, I think it's ok to have half-baked code out there -- you just need to mark releases occasionally. Those can be as slow or frequent as you like, but it's still important for people to see what's going on in the interim. And in turn, those people can help you get it fully baked. As for controlled feature revelation, I think that's counter to the spirit of open source community -- the community is not really on equal footing with the company. It like you're saying "aren't we nice to share our code with you" rather than "let's all work on this together". Well that's my two cents. I understand that not every company feels they can work that way, but I think the really successful projects have figured this out.
- jedberg 16y ago> As for controlled feature revelation, I think that's counter to the spirit of open source community -- the community is not really on equal footing with the company. It like you're saying "aren't we nice to share our code with you" rather than "let's all work on this together". We very much embrace open source -- we use only open source software and we contribute back as much as we can. However, we are still a for profit company, and occasionally have to keep things secret (especially new features, for competitive reasons). So yeah, unfortunately the community really isn't on the same footing as us. The idea is that the code is modular enough that if someone wants to work on a new feature, they should be able to do so without having to worry about what we are doing, and for the most part that is the case.
- 16y ago
- Mongoose 16y agoLove the TLDR summary at the bottom. That should become more of a trend.
- apsurd 16y agoI never got why its standard practice to put it after the "too long" part? Shouldn't it be before? I guess semantically using "didn't" is past tense, implying some type of initial attempt to read it and then because it's too long, you didn't. But nevertheless it would more helpful at the top?
- howsta 16y agonice
- stingraycharles 16y agoJust curious, but what's the business model behind embed.ly? How does one generate revenue from such a service?
- codexon 16y agoI'd like to know that too. The only product I see here is an open standard which would be forked the moment they try to slap ads on it.
- Sthorpe 16y agoLove the idea. I did find a down page btw. http://api.embed.ly/about http://api.embed.ly/about