Code Contributor Role

Tasks

• Bring FeatureBrainstorming ideas
• Submit new FeatureEnhancementRequests and FeatureUnderConstructions
• If possible, provide patches following the PatchGuidelines

-- PeterThoeny - 19 Jul 2003

Feedback and Comments

• Make it clear that whether your work is in a state suitable for inclusion or not.
  • Uploading patches for discussion only isn't uncommon.
  • If it isn't for inclusion, provide a very explicit statement to this effect. Furthermore be prepared for your patch to be included in a modified form despite this if the existing functionality is valued.
• Make it clear what license your patches are provided under. If you provide patches back to the core team under any license other than the GPL do not be suprised if they do not make it into TWiki. If you do not state any license, GPL is assumed, but it is MUCH better to be accompanied by a statement to this effect.
• Producing a patch matching the guidelines does not guarantee inclusion - it does however stimulate discussion - sooner or later. (Corollary: If you use someone's patch, say something about it!)

-- MichaelSparks - 18 Aug 2003