You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

xep-0002.xml 3.1KB

12345678910111213141516171819202122232425262728293031323334353637383940414243
  1. <?xml version='1.0' encoding='UTF-8'?>
  2. <!DOCTYPE xep SYSTEM 'xep.dtd' [
  3. <!ENTITY % ents SYSTEM 'xep.ent'>
  4. %ents;
  5. ]>
  6. <?xml-stylesheet type='text/xsl' href='xep.xsl'?>
  7. <xep>
  8. <header>
  9. <title>Special Interest Groups (SIGs)</title>
  10. <abstract>A definition of Special Interest Groups within the XMPP Standards Foundation.</abstract>
  11. &LEGALNOTICE;
  12. <number>0002</number>
  13. <status>Active</status>
  14. <type>Procedural</type>
  15. <sig>None</sig>
  16. <approver>Board</approver>
  17. <dependencies/>
  18. <supersedes/>
  19. <supersededby/>
  20. <shortname>N/A</shortname>
  21. &stpeter;
  22. <revision>
  23. <version>1.1</version>
  24. <date>2002-01-11</date>
  25. <initials>psa</initials>
  26. <remark>Clarified some details and added information about cut-offs for inactivity.</remark>
  27. </revision>
  28. <revision>
  29. <version>1.0</version>
  30. <date>2001-06-28</date>
  31. <initials>psa</initials>
  32. <remark>First release, modified from Rahul Dave's modification of my original post.</remark>
  33. </revision>
  34. </header>
  35. <section1 topic='Short Definition'>
  36. <p>A Special Interest Group (SIG) is a working group approved by the XMPP Council to address specific areas of growth or concern within the Jabber/XMPP developer community, usually by means of developing and publishing XMPP Extension Protocols (XEPs).</p>
  37. </section1>
  38. <section1 topic='Explanation'>
  39. <p>The main function of most SIGs is to produce acceptable XMPP extensions (delivered in the form of XMPP Extension Protocols or XEPs <note>For information about XMPP Extension Protocols, see <link url="http://www.xmpp.org/extensions/xep-0001.html">http://www.xmpp.org/extensions/xep-0001.html</link>.</note>) within a reasonably limited period of time. However, at the discretion of the XMPP Council, a handful of standing SIGs may be approved (e.g., to address security or standards compliance).</p>
  40. <p>Anyone (not limited to members of the XMPP Standards Foundation) may propose the formation of a SIG by completing a XMPP Extension Protocol outlining the need for the SIG and its proposed focus. However, SIG leaders must be members of the XMPP Standards Foundation. The number of leaders for a SIG is flexible, and shall be determined by each SIG, in consultation with the XMPP Council if necessary. The concept of "membership" with regard to SIGs is loose, and is essentially co-extensive with membership in the appropriate mailing list (each SIG has its own mailing list, which is archived for public review). SIG members do not need to be members of the XMPP Standards Foundation, and any member of the general public may subscribe to SIG mailing lists.</p>
  41. <p>It is expected that all SIGs (other than certain standing SIGs) will remain active for as long as necessary in order to produce one or more standards-track specifications for review by the XMPP Council in the SIG's area of focus. However, if a SIG does not show signs of activity for an extended period of time (usually six months of inactivity on the SIG's mailing list), the SIG may be disbanded at the discretion of the XMPP Council with appropriate warning to the SIG members (usually in the form of an email sent to the SIG's mailing list).</p>
  42. </section1>
  43. </xep>