|RE: [eclipse.org-architecture-council] Minutes from today's call|
I'm certainly not blaming anyone but myself for missing the meeting. The culture we have in the CDT is "I want feature X" and we say "great, where's the patch". I want to be reminded about the meetings and I'm sure I can patch outlook myself to do that.
At either rate, I'm just sad I missed the meeting. I didn't realize e4 was on the agenda. Rather than polling the arch council site for agenda updates, it would be nice to know before hand. For example, if you have a big topic to talk about, let us know on the list so we can prepare before the meeting. Which also sounds like a good process for architecture changes at Eclipse ;).
From: eclipse.org-architecture-council-bounces@xxxxxxxxxxx [mailto:eclipse.org-architecture-council-bounces@xxxxxxxxxxx] On Behalf Of Bjorn Freeman-Benson
Sent: Thursday, March 13, 2008 2:00 PM
Subject: Re: [eclipse.org-architecture-council] Minutes from today's call
Now, what we, the AC, can do is to help projects understand the roadblocks they are putting up against such greater involvement. Is there an architectural issue that is making more activity difficult? Is there a process issue? Is there a perception issue? ... That's where I think the AC can take an active role in encouraging more active participation by the larger community. Not just "lists of requested features", but actual code.
Anyway, that's my rant for the day...
[end of message]
Back to the top