• home
• mirrors
• search
• announcements
• mailing lists
• documentation
• books
• download
• donations

• contacts
• Samba Team
• development
• support
• gui interfaces
• thanks
• vendors
• survey
• t-shirts, etc

Development List of Projects

Samba is developed with the hard work of a world wide team of volunteers. We ask that patches submitted to Samba not infringe on any known patents. In order to avoid any potential licensing issues we also ask that any who have signed the Microsoft CIFS Royalty Free Agreement not submit patches to Samba, nor base patches on the referenced specification. Finally, as with all GPL work, the submitter should ensure that any patches that you submit do not conflict with any 3rd party copyright.

Documentation

• (Priority - CONTINUOUS, Status - ACTIVE) Consolidate the existing text HOWTO's and HTML FAQ's into a single admin guide document.
  All Manpages and a significant portion of the files in the textdocs/ directory have been converted to SGML/DocBook. We have also worked on better support for non-english documentation and translations on existing docs.
  
  The document docs-status in docs/ in the CVS tree contains information about the status on the docs and who is working on what.
  
  Contact Jerry or Jelmer if you would like to help out with the docs.
  

Testing

• Samba 3.0 is currently under development (see the Development Page for details on Samba CVS branches). The more testing it gets the better the release will be. Everyone counts. Be aware that this is prelease development code made available for testing purposes only (i.e. non production systems).

Coding Projects

All coding work needs to be coordinated with a Samba Team member at the very least on the samba-technical mailing list or on the #samba-technical IRC channel (irc.freenode.net). Don't just start coding and expect patches to automatically be integrated in. Obviously. projects by specific team members, winbind for example, need to be coordinated with those team members in charge.

For those without CVS write access (non-team members), patches should be incremental and in the form of context diffs ( attached diff -u output)

If you want to code, you should know how to get the source branches via anonymous CVS. See the Samba CVS instructions for details.

Anyone interested in actively participating in Samba development should also probably subscribe to the samba-cvs mailing list in order to follow CVS checkin log messages.

• (Priority - MEDIUM, Status - ACTIVE) Implement ACL support for currently unsupported platforms.
   
• (Priority MEDIUM, Status - ACTIVE) Rewriting Samba's current filesystem quota support as a VFS module. This would allow for the use of different quota mechanisms (e.g. UFS quotas and VXFS quotas) for different files shares on the same server. The general idea is something like:
  
  

       [foo]
            vfs = generic_quota_solaris5
  
       [bar]
            vfs = generic_quota_vxfs

• (Priority - MEDIUM, Status - ACTIVE) design, document, and fix the DEBUG levels in the Samba code. This is a large, tedious project. All proposals for stratifying the debug levels into bitmasks and documenting what should be done at what level should be carried out on samba-technical as we are currently undecided on whether this should actually be carried out.
   
• (Priority - MEDIUM, Status - PSEUDO-ACTIVE) Isolate client side RPCs into a portable libmsrpc library (need a portable SMB client type library first). How about a Perl module for this? Very interesting idea...
   
• (Priority - LOW, Status - ACTIVE) Decoding WINS replication protocol between NT servers.