[EMAIL PROTECTED] wrote: > [snip] >> So how do we go forward? This is important because a) we told the GUI >> team we'd have an API for them and if we want it being used by >> november, this needs to move quickly b) I thought this was a high >> priority item in terms making the code safe. >> > > You may have to go forward without consensus. You're the one doing the > work, ultimately the decision is up to you. You're an advocate of > Postion 2. I think you're correct. The more time you spend arguing > with people who won't change their mind, the less time you have to write > code. If they think they can do a better job than you can, let them > code up an alternate solution. > > Let me explain why I'm trying to get, if not consensus, at least grudging agreement on this. Having an API is only half the solution. Getting everyone to buy in and use/code to the API (and improve the API where it's deficient) is the other half. If there isn't agreement, then we're likely to have this argument on several code reviews going forward. The bytes_to_string issue which came up in the review of 3201 is really what spurred me to try and get this discussion moving more quickly towards a resolution. In short, yes, I'll go off and continue my current plan unless I get definitive direction to stop, but I'd rather have discussion once than spread across code reviews. Also, if the decision is different from my group, I'd like to know sooner rather than later so I can redirect my energies appropriately.
Brock > -j > _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
