>>>There is certainly an indirect effect of spec resolution -- as spec issues are resolved, hopefully we'll see an increase in users and more projects >>>interested in participating. This could happen pre or post graduation...
+1 I think that specification's non-stability situation must not affect the graduation process. Because that does not related with any graduation items.(http://incubator.apache.org/guides/graduation.html#community) I also think that we are ready to graduate. After we graduate, we can easily create our releases more efficiently and attract more community. --Gurkan ________________________________ From: Kevan Miller <[email protected]> To: [email protected] Sent: Wednesday, September 9, 2009 8:54:25 PM Subject: Re: Graduation? On Sep 9, 2009, at 12:26 PM, Mark Struberg wrote: > Sorry for repeating myself: I think we should wait for the 330 and 299 specs > to settle, and THEN we can decide what to do. I feel uncomfortable with being > promoted from incubator without having the API pretty stable. > > Once this point is reached, I look pretty confident that OWB will find a well > established place in the community. I understand that point. Personally, I think I've been guilty of allowing spec instabilities to affect my judgement on community readiness (or at least affecting how much I pushed the community to consider graduation). IMO, I think that was wrong. I should not be allowing external factors to be affecting my community evaluation. There is certainly an indirect effect of spec resolution -- as spec issues are resolved, hopefully we'll see an increase in users and more projects interested in participating. This could happen pre or post graduation... --kevan
