[12:45] <cjohnston> hey edrz
[13:21] <edrz> hi
[15:03] <cjohnston> edrz: how goes the work with summit?
[15:31] <cate> cjohnston: it goes well. Especially because vorlon did most of the work for last DebConf.  Now we are mostly improving things to DebConf ways
[15:34] <cate> One of the invasive change, would be to add a new summit.status = Done, to block editing a past conference
[15:35] <cate> But the most urgent change is to inhibit displayng the attendee list on ProposeMeeting (and other *Meeting forms), for privacy reasons.
[15:48] <cjohnston> mhall119, daker ^
[15:49] <cjohnston> cate: we use that because certain meetings require certain people to attend, so if I am creating a meeting and I know that mhall119 and daker need to be there, I'd add them... do you guys not have meetings like that?
[15:51] <cate> cjohnston: we don't use very much the "attend", and people are not so "dutiful" to complete it.
[15:51] <cjohnston> I see
[15:52] <cate> OTOH an other change [but probably could be made only in DebConf part] is to add multi-speakers
[15:53] <cjohnston> hmm.. I'm not sure how speaker was implemented, but it doesn't look to be like ours
[15:53] <cjohnston> (we don't have that notion)
[15:54] <cate> we interpreted someshing between drafter ans assignee
[15:54] <cjohnston> gotcha
[15:56] <mhall119> cate: can you use the "required to attend" for speaker?
[15:57] <mhall119> also, what is the privacy reason for not displaying attendees? Is the attendee list not public information?
[15:57] <cate> mhall119: it seems no. We had a lot of complain last year
[15:58] <mhall119> cate: that's going to be a much more difficult task then, we always considered info on who is attending to be public, so it's used in a lot of places
[15:58] <cate> but multi-speaker could be set only by content-team/track-leads
[15:59] <cate> mhall119: yes, we noticed that
[16:00] <mhall119> cate: is it an option for those people who don't want their name listed as attending to simply not register as attending?
[16:05] <cate> mhall119: I don't know yet. We use the registration system for many logistic parts [sponros, food, accommodation, t-shirts, ...], so maybe we can have something like attend = visible and really_attend
[16:05] <cate> But i should check the code, if it is feasible
[21:07] <edrz> we already hid the list of participants from meeting displays by making them only visible to organziers (in the templates)
[21:08] <edrz> now we're looking at the ProposeMeeting form.
[21:08] <edrz> and, we did use require_attendees for multiple "speakers" last year.
[21:10] <edrz> but, that doesn't allow 2 or more persons to own an event, i.e. 2 speakers each able to edit the talk they are giving together.
[21:10] <edrz> only drafter and organizer can do that.