We have a steering meeting planned for this Friday and i'd like to discuss the topics a bit beforehand. You can see the full list of topic ideas from our planning document. I'm going to pull out some of the things I feel most pressing:
there are a bunch of other things I'd love to talk about in that document, though, so take a look. I pulled out the Project Management question because I think getting a better handle on that side of things (our organizational side) would help us achieve all the other things.
Something that's been on my mind which intersects project management -- figuring out what (a) are the sets of conversations and tasks that we have need of, and (b) how we can make sure they are happening?
Some examples of things we have processes for:
Some examples of things we don't have a clear policies for:
Maybe this is a good thing? If so, I think I would want to start by doing some kind of survey where we try to gather the sorts of things we might be tracking.
I'll note that @mw won't be here this week (PTO), which is a bit of a downer. I'd like their input.
@pnkfelix any thoughts?
I still feel pretty torn :)
Basically the 3 options I listed above, in condensed form:
So I know I've used the term "Project Manager" in the past
I think I am leaning against the first, although I consider it important, in part because the 3rd seems like a useful .. precursor to it? It's a bit unclear what I even mean by that
but it might be good to tease out exactly what
you intend for that role to be
Yeah I was just thinking -- maybe just trying to make more precise what we think we might need
that is sort of the same as the 3rd thing but perhaps more narrow in focus
I don't have a very good definition yet, I can only explain a bit by analogy
I only now realized you were covering the same ground as I was working towards in my feedback
seems like we both had similar intutions, though I can't quite tell if you are asking me to try and enumerate now what I mean, or thinking that a meeting could be good for figuring that out
I guess I just didn't want you to say
I lean a bit towards the latter :)
"Hey we need a project manager, any volunteers"
without spelling it out more
on the topic of roadmap review, I don't know how general that would be either :)
I have some specific concerns I think we are not meeting
(and I kind of don't know what to do about it at the moment)
(specifically, I think we should be spending some effort working with people who use rustc to make sure we understand their scenarios, or profiling and identifying cases we think we should improve)
but I also feel like we've got more projects than we really have "bandwidth" for :) in some sense
and I'm loath to go about creating more
identifying potential projects
is still useful
as long as we collectively understand
that identification != commitment to follow through
yes. one thought I had is just talking about ideas of what we could do, and then worry a bit later about how to find people to be doing it
I also think that some of the pieces we need -- I'm thinking mostly of the self-profile stuff -- isn't there, so we could talk a bit about that.
It took me a little while to appreciate what you did at the start of this topic, spelling out all the things we already do
(i.e., look for technical hurdles)
or need to do
I don't consider that a complete list ;)
you may want to transcribe those two lists into some shared document
for further brainstorming
I'd like to try and get the list as granular as we can to start
I'll make a paper doc I guess
meaning as fine-grained as possible?
yeah, though maybe that's not so important
I guess I mean sort of "specific"
but I figured we can start with general
I'm mostly imagining things like this: we currently have a "WG lead" concept
but it's not very clear what that is
and I suspect it can be broken down into a number of roles
which might indeed be shared out, or rotated
e.g., reporting to the triage meeting
so i'd like it if we can say (to start) things like "a working needs to report to the triage meeting" -- and then maybe we say "often a lead does items 1, 3, and 6" but ..
anyway I created a paper doc, in the folder for @WG-meta, but I have to run to another meeting for a bit :)
I guess we'll wing it today :) I am thinking maybe we'll some announcements, then maybe a bit of discussion about the short-term stuff
I had a bunch of things I thought about announcing, though now of course I forget what they were :)
/me hopes they come back
I don't know about "wing it"
seems like there's plenty of meat on the agenda. Or at least seeds for conversations.
OK, this is my proposed format.
First, announcements (5-15min). People can make announcements of things they think are cool or interesting. We'll extend to 15min as needed.
In the meantime, I'll make a poll. People can vote and, at the end, we'll choose between:
We've got a lot of good projects planned, but I'm concerned that we need to also be sure we are understand the problems people face in everyday compiling. Among other things, I suspect there is still low-hanging fruit to be picked, but also I'm not convinced we have a good picture of what consumes the time when compiling (and it might not even be in the compiler). I'd like us to be able to say "not only are we working on RLS 2.0, but we've made serde 5% faster" (or whatever). Discuss.
Can we try to enumerate what are some of things the compiler team needs to be tracking? What communication is (or should) be happening? I'd like us to be able to come up with a good list of all the things we think should be happening, so that we can compare against our existing processes, and try to ensure they are covered (or adjust the processes as needed).
I guess I have to look into how to make a poll :)
whoops, had the format wrong >_>
wrong topic :)
yikes, had the format wrong
/poll to create a poll, and the args to the poll are its title
(and now i can't delete it :sweat:)
@nikomatsakis @QuietMisdreavus there is a topic in #genaral somewhere which has the full syntax out there, including the one that allows adding options with the command
right, that's the post i was trying to remember, but i remembered it wrong