[Foundation] Draft JID list

Rahul Dave rahul at reno.cis.upenn.edu
Wed May 23 15:57:17 CDT 2001

Think you meant JIG :-)
I'd remove general, merge business and trademark, and add

Otherwise a very complete list without being too overly detailed, seems to
hit the right spot...

Regarding the notion of JEEP's, or Jabber EnhancEment Proposals, which we talked
briefly about on the conference today, see the following python links as
productive structures to model this after...
(dont laugh at the acronym, its the best I could do :-))

Python-SIGS <==> JIG's:

Python Enhancement Proposals (PEPS) <==> JEPS

See especially:

for a PEP about how to write PEPS. Save some additional fields for
status and pointers to reference implementations in CVS or elsewhere, this
would suffice to communicate work proposals and implementations in an open
 and informal but defined way..

 Comments? I'll volunteer to be overall JEEP co-ordinator, and go ahead and
 bootstrap the process if and when the community wants it/likes it. I also
 volunteer to co-ordinate the middleware JIG.

 We will need a mechanism for acceptance of JEEPS into the general codebase.
 Generally this wont matter for transports and such, so that mechanism can
 be devolved, but for core protocol changes and server extensions, this could
 be handled by a core Jabelin group, with veto power invested in a benevolent

I got this from you:
> Protocol Development
> 	Presents all proposals for protocol change to the membership
> 	for vote. Document protocol changes and maintain protocol docs.
> Client Interests
> 	Encourage standards between clients (settings formats, history formats,
> 	client support for new protocol bits, etc). Orchestrate client development
> 	docs, encourage good docs for clients, etc.
> Server Interests
> 	Same as for clients, but for servers.
> Business
> 	Manage trademark issues, brand + marketing management, etc.
> 	Manage legal issues, finance, etc. Issue press releases, etc.
> Standards Compliance
> 	Management of "Jabber Powered" labels and such... encourage standards
> 	compliance, etc.
> Security
> 	Look for security vulnerabilities, and ways to fix them. Propose new
> 	features/protocols to other JIGs
> General
> 	Try to manage co-operation between JIGs, keep things smooth. Mostly a
> 	political JIG. Keeps JIGs aware of what other JIGs are doing.
> Infrastructure
> 	Jabber.org website issues, keeping jabber.org up, etc.
> JIGs should have mailing lists, and sub mailing lists for more specific
> interests inside the JIGs. They could also have websites to keep people
> up to date. Maybe they can offload this JIG website stuff to the
> infrastructure JIG?
> Comments?
> Mathew Johnston
> _______________________________________________
> Members mailing list
> Members at jabber.org
> http://mailman.jabber.org/listinfo/members

More information about the Members mailing list