The guy have wrong ideas about open-source developing. I've tried telling him why he should open it, but he was just rude... hope this other guy gets him to open it.
My opinions on what he said: Why does he need 2 versions of Mercury - one closed and one open? Just do it the open way, one single version. He should not fear a fork. He's the guy who knows Mercury inside-out, he's always gonna be requested, and a fork doesn't mean he can't work on the forked code too. That kind of fork he described i've never ever seen happen: a project that just "steals" code from another, giving nothing in return. That doesn't exist. Nobody will enjoy working on a project which does nothing but wait for code coming from the original project. About discussing in group how to implement stuff: well, i see he sees Mercury very much as a learning project... but when you get employed as a programmer, do you think you'll just sit on your chair, do code all day, go home and sleep? Don't you think working in group is a very good thing to learn? Because, you know, sooner or later you're gonna have to. Trust me, knowing how to work in group will get you more than your coding skills. And then his last comment about a company "stealing" Mercury finally shows he's innocent about open-source... you can just GPL it and nobody will close it. It's that simple. Cheers, J.V. 2005/12/11, Lz <[EMAIL PROTECTED]>: > I just read this: > > "the releasing it to a developer team has been one of my ideas at > first, but the downside of that is that it will slow me down, if I > want to rewrite the entire filetransfer handling, I would have to > check with everyone to see if they are ok with it, I would have to > sync every time I want to make a change to make sure the code doesn't > get out of sync, if we as a team assign a task to someone that could > be done in an hour and he waits a week to do it, the next beta release > would take it's time > in my reasoning about the dev team, I've looked a lot at aMSN, it's > been almost a year since 0.94, and they have an entire team... > an example for this: a jabber client named pandion has had problems > with a person stealing the code and making a client for himself (I'm > not sure I got this story 100% correct, if not, ignore this > tongue.gif)" > > He's right after all. :P > > http://forum.mercury.to/index.php?showtopic=10794 > > > -- > Lz ([EMAIL PROTECTED]). > http://elezeta.bounceme.net > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id865&opclick > _______________________________________________ > Amsn-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/amsn-devel > ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/amsn-devel
