Am 05.01.2014 um 03:31 schrieb Chris Morley <chrisinnana...@hotmail.com>:
> > > > We have no formal patch submission process. > Fairly often someone presents a patch to us and it > gets no response. > > I find this a bit of a tragedy and bad manners. > ... > - 1) Someone volunteers to follow up patch submissions. > - 2) patches are added to the linuxcnc-meeting so at least > there is a small discussion on the matter. > ... > I think our prime problem is that our push-capable developer > group is small so time and expertise become scarce. Actually I do not think this is the primary problem - nobody feels called, because there is no assigned responsibility. Part of the issue why nobody feels called is that 'developer' is an undefined term. The only realistic option I see is: - divy up the space into smaller blobs (say interpreter, HAL/RT, UI, doc, config, build..) - find persons which act as steward for that area - ideally a primary and a fallback person; for a term, say one or two years. - spell out clearly this person(s) have the final word whether a patch goes in or not. - no exceptions. The third point excludes the wobbliness of defining what is a 'developer' which includes all shades from 'has push permissions' to 'linuxcnc crew' (aka 'we'). The last point brings some homogenity to the 'developer' badge. The normal exchange channels will assure sanity prevails. --- Volunteers arent going anywhere, meetings arent going anywhere, 'patch submission systems' arent going anywhere. It's persons taking action, and that is - not at the very least - a question of control and reward. It does help to view an open source project as a primarily social venture, which includes the 'm word' (management). If such a scheme is agreed once the discussion converges, I would act as fallback for interpreter and primary for HAL/RT (post UBC merge, to be exact). - Michael ------------------------------------------------------------------------------ Rapidly troubleshoot problems before they affect your business. Most IT organizations don't have a clear picture of how application performance affects their revenue. With AppDynamics, you get 100% visibility into your Java,.NET, & PHP application. Start your 15-day FREE TRIAL of AppDynamics Pro! http://pubads.g.doubleclick.net/gampad/clk?id=84349831&iu=/4140/ostg.clktrk _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
