Open Stack

I fully understand the concern. Quality of presentations and depth of material is much better for project info for PTL and core members.
Unfortunately it creates a much higher bar for new members.
It discourage participation of new companies and new individual members and impact diversity.

Any ideas how to balance various concerns?

To be fair to the original thread, it is NOT tool specific.
Thanks,
Arkady

From: Ulas Kozat [mailto:Ulas.Kozat at huawei.com]
Sent: Thursday, August 25, 2016 11:18 AM
To: Kanevsky, Arkady <Arkady_Kanevsky at DELL.com>; yihleong at gmail.com; jimmy at openstack.org
Cc: openstack-track-chairs at lists.openstack.org
Subject: RE: [Openstack-track-chairs] Track Chair Feedback

If this was an academic full paper submission, I would say +1 (although many negative side effects will be still there). But in this type of submissions, it is not hard to generate a great abstract without actual deliverance. So, I would vote -2 for blind or double blind review.

From: Arkady_Kanevsky at DELL.com<mailto:Arkady_Kanevsky at DELL.com> [mailto:Arkady_Kanevsky at DELL.com]
Sent: Thursday, August 25, 2016 6:54 AM
To: yihleong at gmail.com<mailto:yihleong at gmail.com>; jimmy at openstack.org<mailto:jimmy at openstack.org>
Cc: openstack-track-chairs at lists.openstack.org<mailto:openstack-track-chairs at lists.openstack.org>
Subject: Re: [Openstack-track-chairs] Track Chair Feedback

For reviews and acceptance it would be better to have blind review.
No authors names, not affiliation. Just on the merit of submission.
Then when submission is accepted then post names and affiliation.

From: Yih Leong, Sun. [mailto:yihleong at gmail.com]
Sent: Thursday, August 25, 2016 7:28 AM
To: Jimmy McArthur <jimmy at openstack.org<mailto:jimmy at openstack.org>>
Cc: openstack-track-chairs at lists.openstack.org<mailto:openstack-track-chairs at lists.openstack.org>
Subject: Re: [Openstack-track-chairs] Track Chair Feedback

Very nice tool and 'evolving' over the past few summits.

Would be great if i can see a summary of affiliated companies of the proposals that I/we have selected at the Selection/Team list.
e.g.
Track A: A total of 20 companies are selected
Company X: 6 sessions are selected in Track A
Company Y: 6 sessions are selected in Track A
Company Z: 8 sessions are selected in Track A


On Wed, Aug 24, 2016 at 3:20 PM, Jimmy McArthur <jimmy at openstack.org<mailto:jimmy at openstack.org>> wrote:
All -

Thanks again for your hard (and quick!) work on the OpenStack Barcelona Summit Track selections. You all did an amazing job and we're really grateful to each of you.

I took notes of feedback, but please feel free to add to the list if you feel I've missed something:
•         Better ability for Track Chairs to merge
•         Option to email all speakers from one or more presentations
•         Ability for Speakers to submit/propose a new Title / Abstract as an attachment or within the thread
•         Track Chairs ability to deactivate merged talks, and save one with new abstract (or merge into a new record so we don't taint the originals)
•         Email issues
•         Track conversations with users within the Track Chair tool i/o just via email. Could also consider using ZenDesk API for this?
•         There was a problem with Sendgrid API this go round, so there were just generally problems. They were:
•         No CC of other track chairs
•         Reply address was noreply at openstack.org<mailto:noreply at openstack.org> i/o the ZenDesk ticket
•         Adding name of Presentation and other details automatically within the email "Track chair XYZ has a question about your presentation: ABCD"
•         Email all speakers i/o just one
•         Need the option back of being able to compare everyone's list side by side
•         The new method of using the dropdown makes it difficult for the team to compare selected talks
•         A way to auto-select common talks for placement in the team section would be cool, or at least a way to quickly view that list, along with the # of team members that selected each talk
•         An option for a Track to "Close" their selections
•         Send an email to track chairs list
•         Mark Track as "Closed" for non-admins
•         Another suggestion for the Boston CFP process might be to consider separate user and developer sub-tracks. For example. What might be considered a How To/Best Practice for developers might be completely irrelevant to users.
•         We at Dev Tools track found out that there are a lot of drafts related to the CI/CD and Testing processes. Seems reasonable to add such a track (Deployment and Testing) as an option for the next summit. What do you think?
Thank you again!
Jimmy

_______________________________________________
Openstack-track-chairs mailing list
Openstack-track-chairs at lists.openstack.org<mailto:Openstack-track-chairs at lists.openstack.org>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-track-chairs

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-track-chairs/attachments/20160825/6f2d42b0/attachment-0001.html>