3 ms·
Best line in the article, re: Carrier forking from Pidgin: "A fork (initially called Funpidgin) was done of Pidgin 2.4.0 because there were disagreements about
by ivey 18y ago
Best line in the article, re: Carrier forking from Pidgin: "A fork (initially called Funpidgin) was done of Pidgin 2.4.0 because there were disagreements about the size of the text entry field."
- benbeltran 18y agoSometimes developers can be very childish and proud. Just make the damn thing resizable or write a plugin or something.
- Dobbs 18y agoI was listening to (I believe it was) Mark Shuttleworth the other week and he basically stated that: "All forks are generally a result of lack of good communication between developers." From what I have seen Pidgin developers are morose than normal. This clashed when they refused absolutely to listen to users who wanted at most an option to disable this effect from the options menu. In the end this isn't about a text entry field its about developers who will listen and act on user input.
- jwilliams 18y agoIndeed. I think this is a nice article - but it can be summed up by: why do (open source) project fork? For lots and lots of reasons. I guess the lesson is, if you're heavily invested in an open source project, you might want to think about how you'd deal with a (perhaps inevitable) fork.