People propose sessions from among the pool of ones that no one’s either strongly for or strongly against. Now we need three other cases (two definite accepts, one if the provisional accept falls through). In one, we decide that we’ll provisionally accept if the proposer adds some particular improvement. In two cases, the negative votes agree to accept. There are also five interesting disagreements. The structure of the conference depends on the submissions and how they match up with our available space. More likely, we’ll need to make some choices. It’s possible that the number of clear accepts fits exactly within the space boundaries we have. The interesting cases are those where you get one A and four C’s (or A’s and D’s). Most submissions will have a near consensus. I think this submission should be rejected, but I could live with it being accepted.ĭ.
The purpose of the website is to help the submitter hone the submission into its best possible form.Īfter submissions are closed, I’m planning to have something similar to what’s done at many software conferences:Įveryone votes on the submissions she’s read, using a four point scale:Ī: I will champion this submission (argue vigorously for its inclusion).ī: I support this submission, but it wouldn’t break my heart were it not included.Ĭ.
The first stage reviews will be public, on the submission website. How will the submissions be reviewed? What constitutes a good submission? That’s why the answers below should be considered specific to our stage. The “stage producers” have a lot of leeway in how they organize their own particular stage. Or you might decide to hang out at a particular stage with people who share your particular obsession. (Plug here for Karen Carroll.) Buy a pass to the music festival and you can wander among the stages, seeing what you like. I am thinking of a stage as a “conference within a conference.” It’s like a stage at a large music festival, where there’s a particular physical location where you might go to hear blues. Some questions on the submission process for Agile 2008, passed along by an Example stage committee member. Mainly on Agile software development, with a special
0 kommentar(er)
