[standards-jig] Development Standards II

Michael Bauer bauer at jabber.com
Tue Aug 14 16:25:42 UTC 2001


The Development Standards describe what software development practices
should be followed in order to effectively integrate software within the
Jabber infrastructure.  Effectively integrating open source software centers
around the delivering software that substantially conforms to relevant
protocols, behaves appropriately within the overall Jabber environment, and
is developed in a spirit of mutual cooperation.  Commercial software doesn't
need to be opened up to be integrated but it does need to behave
appropriately in the open environment.

Software should conform to a set of Jabber protocols.  Submissions should be
accompanied by a clear description of which draft, core, or alternative
protocols the software conforms to as defined by relevant namespaces.  

Whether included with a software submission or not, extensions to the Jabber
protocols should be described with a Jabber Enhancement Proposal (JEP -
http://foundation.jabber.org/jeps/) that's been submitted to the appropriate
Jabber Interest Group (JIG - http://foundation.jabber.org/jigs.html).  

Operational integrity of software is up to the individual developer or
company.  Effort should be made on the part of the developer to create
software that conforms across all relevant protocol categories and across
all operating environments.  Of course, if building a specialized
application that is integrated with an operating system this is less
important.  

Effort also should be made on the part of the users to provide effective and
constructive feedback to developers to help them accomplish this goal in
return for use of the software.  Software should fail gracefully whenever
possible.  Users should provide specific test cases to identify software
failures to assist developers in enhancing operational integrity.



More information about the Standards mailing list