On Wed, Jan 25, 2012 at 09:07:14PM +0000, andy pugh wrote: > > I see your point, but that does leave a bit of a problem. > Currently I can have a great idea for a modification to LinuxCNC. I > can spend months working on it to get it to the point where it can be > demonstrated. Then somebody can say "Oh, we rejected that idea back in > 2005 because it's stupid". > > There surely has to be _some_ way of figuring out whether a feature or > change is likely to be accepted into the main branch prior to spending > a bunch of time coding it.
The way I see it, you just do this by discussing it with other developers and perhaps the whole community. People do this on irc and the mailing list all the time. You know that sticking points will be stuff like breaking existing configs, breaking existing gcode programs, changing existing behavior that a lot of people use, etc. You can use these metrics to figure out how much impact your change will have. Realistically, then, you as a developer will have some idea whether the idea will be controversial or will be a slam dunk. You use this judgement to determine how much buy-in/advocacy/discussion is needed before you spend too much time on it. ------------------------------------------------------------------------------ Keep Your Developer Skills Current with LearnDevNow! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-d2d _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
