Community
Participate
Working Groups
Denis, As you know, our submission system is really designed for the presenters to be responsible for their submission content, and subsequently their talk content as it appears on the website. Our keynote presenters are not typical submitters, and they are generally not going to do this themselves. So we have to figure out the best way to do this for them. (I think this is another thing that Gabe often hacked for us, so we need an alternative.) Here's an idea. For each keynote, I'll do this: 1) Create a submission system (bugzilla) account for the keynote speaker, using the contact email address we have for them 2) Using the keynote's account, create their submission, adding the title, abstract, bio info, etc. 3) Email the speaker to provide them the credentials for this account, and let them know that they can edit the information there at any time 4) Ask the speaker to review the submission information to make sure it's OK, and say that if they want to change something they can either ask me to change it, or do it themselves via the submission system 5) Let them know that they may receive some emails via the submission system, such as comments from the community, auto-emails, etc. 6) Add myself and Britta from MeetGreen as assistants on the keynote talks so that we get a copy of the emails that go to the keynote speakers (Britta is the speaker manager, and she communicates with the keynotes about various topics.) 7) Somehow "mark" the keynotes as having signed the online speaker agreements or "signing" them ourselves so they don't get our auto-nagging emails 8) After the conference, delete the bugzilla accounts we created for the keynotes Alternatively, we could use special Foundation email addresses for the bugzilla accounts so that the submission system emails never go to the speakers themselves -- e.g. Hendrik Speck's account would be "ese2010keynote1@eclipsecon.org" and those emails would go to Britta and me. This isn't very "open" because it doesn't allow a community member to send a comment directly to the speaker via the submission system, but realistically the keynotes are not very likely to want to edit their own submissions, respond to comments, etc. And doing it this way means avoids the issues mentioned in items 5 and 7 above. Comments?
Hi -- I talked with Britta (our MeetGreen speaker manager) and she and I both agree that Plan B is the preferred one -- using email aliases to set up the bugzilla accounts, with email to those accounts going to Britta and me. This is how it worked before, only I'm not sure how it was implemented. More of Gabe's magic, I believe. Of course you could do this without using email aliases, but I figured that might be the least amount of work for our IT guys -- once the aliases are set up, I can take care of the rest. Since we want the "real person" names associated with these accounts to be unique, I presume we'd need a unique email address for each keynote for each conference. So something like this: ese2010_keynote1@eclipse.org ese2010_keynote2@eclipse.org and both of those should go to anne.jacko@eclipse.org behnebuske@meetgreen.com Once that's done, we're all set. Will this bug serve as a request for creating those two aliases? Thanks.
To save on time, and to make this process repeatable for future conferences, I suggest we simply create one bugzilla account alias for the "keynotes" user. keynote@eclipsecon.org would be my choice.
Can we use the same bugzilla account and have the submission system display different "human names"? If so, then obviously having one account is ideal! I don't know why, but I was thinking you couldn't use the same bugzilla account for multiple names. I'm happy to be wrong about this. :-)
For all intents and purposes of the _submission system_, is it that important to display a unique name? Cannot the name be incorporated in the submission abstract?
Denis, could you or Matt please create an email account keynote@eclipsecon.org that goes to the following people anne.jacko@eclipse.org behnebuske@meetgreen.com I'm still not sure if this will work as a solution, but I'm going to try it in easy2010 and see. Thanks.
Aha! I just found out that I can add an author to a talk when they don't have a bugzilla account. So for keynotes, I can create an account with any email address, but the keynote's name. I did this in easy2010, putting my daughter's name in as the keynote author, but using my email address. (I then later deleted the entry with my daughter's name in the Foundation db.) So once we have a keynote email alias set up, we'll be good to go.
I've created keynote@ as requested. Just FYI -- there are also keynote1@ through keynote6@ which all redirect to emo @ eclipse org.
I'll close this as FIXED, assuming you have everything you need. Reopen if that's not the case.
Denis, one problem. I don't read the emo inbox anymore. In fact, nothing to do with conferences should go there, and when I've found that address being used in other places I've changed it. Could the email go to anne.jacko@eclipse.org? Thanks.
Ok, I've fixed those.
Thanks. Hoping the bugs stays fixed. I'll try adding the keynote submissions for ESE and see if I run into anything weird.
