4 ms·
Hey, thanks for your reply; sorry for taking so long on mine. I understand why the Travis features you mention are good for open source, I'm not sure I underst
by lvh 14y ago
Hey, thanks for your reply; sorry for taking so long on mine.
I understand why the Travis features you mention are good for open source, I'm not sure I understand why they're not good for web apps. Notifications (email and IRC) sound great for in-house stuff too; and build statuses seem to make sense on some central web page that gets a lot of hits from your dev team (be it the Github front page, or whatever) as well.
The deployment part makes sense though, thanks!
- pbiggar 14y agoThey aren't bad, its just a question of where you put your focus. So while IRC could be used by businesses, its pretty rare (which surprised me, to be honest, but there you go). For notifications, my point was the way of implementation. For open source projects, there tends to be a fairly low-traffic mailing list where all notifications are sent. For businesses, there tend to be way more commits, and developers care a lot less about what happens in branches they aren't working on. So we personalized our emails so only the right people get the right emails. So its both a case of which features to prioritize, and the way the features are implemented, that make the difference for commercial web development teams :)