Re: [Debconf-discuss] Summit discussion on Thursday, 11:00am (18:00 UTC)
Hello Vorlon, On 30.08.2014 09:47, Steve Langasek wrote: Hi Cate, On Wed, Aug 27, 2014 at 11:08:21AM +0200, Giacomo Catenazzi wrote: We have some problem on sso, people some are registering with both debian and alioth, which cause some confusion. Could we link debian and alioth accounts? Should we improve the login page? I had a hallway discussion with Enrico Zini about this here; he's interested in streamlining the SSO handling to address exactly this, normalizing so that Debian developers would always log in via Debian SSO and alioth would be used only for non-DDs. Implementing this thing we all agree on is left as an exercise for the relevant system maintainers. Nice! Maybe we should start again summit from upstream (and with some discussion with upstream), so to make think more generalized (for all debconf) and cleaner schema. I disagree. I think we should instead leverage django's top-notch schema migration support, to continue forward from our currently working deployment while normalizing for multiple DebConfs, and working with upstream to merge our schema extensions. This lets us carry forward our data intact in a retrievable fashion. Note: I don't propose to trash the changes, but only to start from zero, and correct the various patches (e.g. moving line, tables) (and than importing things to the database). Becuase it is the first dc on new database, it is easier to do it and thus to have a clean version, instead of taking care of special cases in future debconfs. [ - On deployment a reference from attendee_id to user_id was lost I'm not sure what you mean here. The reference between the two id is lost in the deployed version, so as I told you on IRC, one person had attendee_id and not user_id. - bursaries info are in different table need_food are never in the same table as need_accommodation Yes; they're part of the same django class, which means that the table joins are transparent if you're using the ORM. Upstreaming our model extensions would certainly let us make this simpler for those doing SQL queries. (And upstreaming our model extensions would also let us better tailor the code in various places which I've avoided touching because they would require extensive changes to cope with our current subclassing.) yeah, but doing again, we can put the three type of sponsorhip together, which in long run is a win. Not a big deal, but I find that summit as a lot of rough edges (e.g. also non so consisted naming), which IMHO could now be fixed easily (and maybe also upstream), simplify a lot the future development. Roles are still confusing (and not so much used). We need to improve this, so to delegate more. What other roles are you looking for here? Note: Now we have a notion problem with front desk so maybe we should rename the old front desk task. But now registration is admin, which is IMHO not so optimal. We had some discussion about how to add and track payments. IIRC I think scheduler and talk groups are not defined as previous DebConf usage. And IIRC video want to delegate again to talk team the talkmeister things. But also the procedure. Who and how to add people to groups was not clear to me. Note: I wrote many defects but anyway summit is much much more useable than penta (and apart of many non arrived people, we didn't have any disappeared persons/fields/statuses as we had regularly in penta) ciao cate ___ Debconf-discuss mailing list Debconf-discuss@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-discuss
Re: [Debconf-discuss] Summit discussion on Thursday, 11:00am (18:00 UTC)
Hi Cate, On Wed, Aug 27, 2014 at 11:08:21AM +0200, Giacomo Catenazzi wrote: On 27.08.2014 00:26, martin f krafft wrote: as you may know, DC14 uses a new conference management system (summit) and we are rather happy with it. But there are obviously aspects that need improvement. We will meet on Thursday at 11 in room 338 to discuss the future of Summit and DebConf. I've few comments. We have some problem on sso, people some are registering with both debian and alioth, which cause some confusion. Could we link debian and alioth accounts? Should we improve the login page? I had a hallway discussion with Enrico Zini about this here; he's interested in streamlining the SSO handling to address exactly this, normalizing so that Debian developers would always log in via Debian SSO and alioth would be used only for non-DDs. Implementing this thing we all agree on is left as an exercise for the relevant system maintainers. Maybe we should start again summit from upstream (and with some discussion with upstream), so to make think more generalized (for all debconf) and cleaner schema. I disagree. I think we should instead leverage django's top-notch schema migration support, to continue forward from our currently working deployment while normalizing for multiple DebConfs, and working with upstream to merge our schema extensions. This lets us carry forward our data intact in a retrievable fashion. [ - On deployment a reference from attendee_id to user_id was lost I'm not sure what you mean here. - bursaries info are in different table need_food are never in the same table as need_accommodation Yes; they're part of the same django class, which means that the table joins are transparent if you're using the ORM. Upstreaming our model extensions would certainly let us make this simpler for those doing SQL queries. (And upstreaming our model extensions would also let us better tailor the code in various places which I've avoided touching because they would require extensive changes to cope with our current subclassing.) Roles are still confusing (and not so much used). We need to improve this, so to delegate more. What other roles are you looking for here? And IMHO we disclose too much information in schedule. Fix in progress :) Cheers, -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developerhttp://www.debian.org/ slanga...@ubuntu.com vor...@debian.org signature.asc Description: Digital signature ___ Debconf-discuss mailing list Debconf-discuss@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-discuss
Re: [Debconf-discuss] Summit discussion on Thursday, 11:00am (18:00 UTC)
Hello, On 27.08.2014 00:26, martin f krafft wrote: as you may know, DC14 uses a new conference management system (summit) and we are rather happy with it. But there are obviously aspects that need improvement. We will meet on Thursday at 11 in room 338 to discuss the future of Summit and DebConf. I've few comments. We have some problem on sso, people some are registering with both debian and alioth, which cause some confusion. Could we link debian and alioth accounts? Should we improve the login page? Maybe we should start again summit from upstream (and with some discussion with upstream), so to make think more generalized (for all debconf) and cleaner schema. [ - On deployment a reference from attendee_id to user_id was lost - bursaries info are in different table need_food are never in the same table as need_accommodation - etc ] Also penta had similar issues, but I think if we can restart from zero (and using the positive experience and code of DC14) we could reduce the work porting summit and scripts from one DC to the next one, possibly coordinating with upstream. [and because the schema will be very similar, we can also easily port the data from DC14 to the generic version, if there is need, I can also port most of the info of penta to summit schema] Roles are still confusing (and not so much used). We need to improve this, so to delegate more. And IMHO we disclose too much information in schedule. Note: I think these points are design discussions, I put the technical bugs and missing parts in wiki ciao cate Whether you already know Django or not, if you are interested in helping out, we would love to see you there. Here are some of the issues we need to work on: https://wiki.debconf.org/wiki/Summit#TODO ___ Debconf-discuss mailing list Debconf-discuss@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-discuss
Re: [Debconf-discuss] Summit discussion on Thursday, 11:00am (18:00 UTC)
On Wed, Aug 27, 2014 at 2:08 AM, Giacomo Catenazzi wrote: And IMHO we disclose too much information in schedule. As an attendee and speaker I found that not enough information was available about the schedule and set of non-approved talks. I had to brute-force the talk ID space to decide if there would be enough interesting events and read about them. I could not report schedule conflicts between talks I needed to attend until the schedule had already been announced. I couldn't easily find out who the speaker for an event was. In my opinion the too much information issue was in leaking the registered attendee list to people loading the event registration page. Also the default for attendees should be to be able to mark their attendance but choose who sees it (admins, speakers, attendees or general public), with admins (or maybe speakers) being the default. The presented information was confusing in some instances; I had to inform people that bold means it is the speaker or that you can login to confirm that. I think it would be better to define a list of people and their relationship with the event (speaker, facilitator, panel member, other required, video team, likely to attend, might attend, etc) and present those roles on the event page. -- bye, pabs https://wiki.debian.org/PaulWise ___ Debconf-discuss mailing list Debconf-discuss@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-discuss
Re: [Debconf-discuss] Summit discussion on Thursday, 11:00am (18:00 UTC)
Thanks for the input! All good points that need to be addressed, just a current comment below on some work in progress. On Wed, Aug 27, 2014 at 07:08:25AM -0700, Paul Wise wrote: On Wed, Aug 27, 2014 at 2:08 AM, Giacomo Catenazzi wrote: And IMHO we disclose too much information in schedule. In my opinion the too much information issue was in leaking the registered attendee list to people loading the event registration page. Also the default for attendees should be to be able to mark their attendance but choose who sees it (admins, speakers, attendees or general public), with admins (or maybe speakers) being the default. I am in the process of adjusting things to address this. (at least partially) The presented information was confusing in some instances; I had to inform people that bold means it is the speaker or that you can login to confirm that. I think it would be better to define a list of people and their relationship with the event (speaker, facilitator, panel member, other required, video team, likely to attend, might attend, etc) and present those roles on the event page. Clearly separating the speaker(s) and hiding the attendees from non-organizers is what I am currently working on. With any luck I'll have that done tomorrow. It'll be an improvement, but there will surely be more concerns to discuss and address over time. For now, though, Daytrip! \o/ -edrz ___ Debconf-discuss mailing list Debconf-discuss@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-discuss
[Debconf-discuss] Summit discussion on Thursday, 11:00am (18:00 UTC)
Hello, as you may know, DC14 uses a new conference management system (summit) and we are rather happy with it. But there are obviously aspects that need improvement. We will meet on Thursday at 11 in room 338 to discuss the future of Summit and DebConf. Whether you already know Django or not, if you are interested in helping out, we would love to see you there. Here are some of the issues we need to work on: https://wiki.debconf.org/wiki/Summit#TODO See you there, -- .''`. martin f. krafft madd...@debconf.org @martinkrafft : :' : DebConf orga team `. `'` `- DebConf14: Portland, OR, USA: http://debconf14.debconf.org DebConf15: Heidelberg, Germany: http://debconf15.debconf.org digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) ___ Debconf-discuss mailing list Debconf-discuss@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-discuss
Re: [Debconf-discuss] Summit discussion on Thursday, 11:00am (18:00 UTC)
On Tue, Aug 26, 2014 at 03:26:35PM -0700, martin f krafft wrote: Hello, as you may know, DC14 uses a new conference management system (summit) and we are rather happy with it. But there are obviously aspects that need improvement. We will meet on Thursday at 11 in room 338 to discuss the future of Summit and DebConf. Whether you already know Django or not, if you are interested in helping out, we would love to see you there. Here are some of the issues we need to work on: https://wiki.debconf.org/wiki/Summit#TODO And also the session's summit page: https://summit.debconf.org/debconf14/meeting/143/summit-summit/ -edrz ___ Debconf-discuss mailing list Debconf-discuss@lists.debconf.org http://lists.debconf.org/mailman/listinfo/debconf-discuss
