[standards-jig] JEPs and Jabber Adoption

Dave Smith dizzyd at jabber.org
Sun Jun 29 19:36:39 UTC 2003

Hash: SHA1

On Sunday, Jun 29, 2003, at 13:09 America/Denver, Matt Tucker wrote:

> Perhaps one way to address the problem would be to set certain time 
> limits/goals on each JEP. For example, a JEP would be proposed on a 
> certain date and then would have between 1 and 3 months to be 
> developed (with feedback from the community) before moving to the next 
> stage. The exact amount of time would be set by the JEP author. Then 
> there would be a last call process with a certain length of time, an 
> approval process, etc, etc. Having dates and deadlines is often a good 
> way to get people motivated. :) This would even help to guide 
> community members in where their feedback might be most effective -- 
> for example, there could be a time-based list of JEP's in development, 
> in last call, etc. The one thing we want to avoid is JEP's that 
> languish with no process for months and months. At the moment we're 
> archiving them in an ad-hoc basis, but having timelines for each JEP 
> would make that a more formal process and would hopefully avert more 
> abandoned JEP's.

Perhaps we should just say that all JEP submissions have 90 days (3 
months) to be motioned for a Last Call or be marked as "abandoned"..or 
something like that?

Regardless of the mechanism, I concur we need to put bounds on this 

Version: GnuPG v1.2.1 (Darwin)


More information about the Standards mailing list