I have a vague proposal I've been contemplating. I wanted to shop it around here for a bit of feedback. I've discussed this some with @mw and @pnkfelix, so all credit for good ideas goes to then, all blame for bad ones to me. =)
I like the idea. I think it would make sense (so much as is possible) for the topic of any given design meeting to be known in advance so that interested parties can make efforts to attend (as opposed to it being decided then-and-there what the topic is). I think you've more or less said as much in the proposal.
I think it would make sense (so much as is possible) for the topic of any given design meeting to be known in advance so that interested parties can make efforts to attend (as opposed to it being decided then-and-there what the topic is).
Yes I feel quite strongly about this. I have tried to bake this into the setup.
So @mw and I were talking about the design meeting ideas. We were thinking specifically that while it makes sense to have the design/steering meetings share a slot, we should be careful not to lose the role that the steering meeting has been playing -- in particular, it's been great for us to have a place to talk about non-technical things, and I'm wary they'll get overlooked if we're not careful.
We were thinking about moving from the 6-week cycle to a 4-week one, like this:
The idea being that we'll have a scheduling meeting where we either pick one topic to focus on (if it is lengthy and likely to require 2 meetings) or we pick two distinct topics. Then we'll have a steering meeting (we can also schedule its topic at the scheduling meeting).
I'm thinking about trying to write-up an RFC on this topic as well, to capture the sense we had in our last meeting.
cc @WG-meta :point_up:
I think that makes sense.
One thing we were thinking is that if the scheduling meeting winds up being shorter, that's ok too -- I could imagine that many weeks it won't be so hard to pick the topics.
Which reminsd me I have to check on the comments from the existing contributor RFC
@nikomatsakis :+1:, I think that's the best approach
So I wrote up an initial procedure for the design meeting:
I'd like some feedback. In particular, I proposed that people upload proposals as PRs to the compiler-team repository. @eddyb maybe take a look? I know you have a bunch of ideas =)
cc @WG-meta and @mw
I'm not sure when we should start this process -- we could start next week, or the week after next.
@nikomatsakis looks good in my opinion
unsure about proposals as PRs but don't have a strong opinion :)
I guess I didn't make it clear
I would expect to land the proposal
i.e., it's not that they would be lots of pending, open PRs
though that also wouldn't be the end of the world, I suppose
but I'd sort of like to keep it so that the total number of PRs open at any time is small
we can alwys change it