Re: Guix Days and FOSDEM 2021?

[Julien Lepiller]

Le 13 décembre 2020 02:51:53 GMT-05:00, Pjotr Prins <pjotr.public12@thebird.nl> 
a écrit :
>I have access to BBB thanks to Julien. Yes, it looks like we can have
>open rooms. One thing we can consider is closing a room when running,
>i.e., if someone is a problem we can react to that. That way we can
>anticipate the worst scenario.

The reason we didn't do that is because in our tests, it was not possible to 
change the properties of the room while it was open, but only change those for 
next time it opens. So we would have needed to close the room and re-open it, 
making everyone join again, which was not deemed acceptable :)

>
>Pj.
>
>On Sat, Dec 12, 2020 at 04:45:23PM +0100, Pjotr Prins wrote:
>> Thanks Simon,
>> 
>> Can we test drive the rooms? Whoever can, just send Manolis and me a
>> private invite.
>> 
>> You have a good point with the TZs. I think we can do 3+4+3 hrs. 9
>> hours is more than I can handle ;).
>> 
>> A blog is a great idea. We can all help too once you have a draft.
>> 
>> Pj.
>> 
>> PS we have a great list of speakers for the real devroom. From near
>> and far :)
>> 
>> On Sat, Dec 12, 2020 at 02:57:30PM +0100, zimoun wrote:
>> > Hi Pjotr,
>> > 
>> > @Tobias: what about the meet.guix.gnu.org?  Is it doable for this
>event?
>> > 
>> > On Sat, 12 Dec 2020 at 11:44, Pjotr Prins
><pjotr.public12@thebird.nl> wrote:
>> > 
>> > > We would like to use the conferencing system as we did last time,
>if
>> > > possible. Can it handle open entry - we'd like to have an open
>door
>> > > policy. Can it handle working groups? If not, we'll just split
>out
>> > > with Jitsy and have IRC as a fallback.
>> > 
>> > You mean the FOSSHost Jitsi instance, right?
>> > 
>> > Tobias has the admin power.  Julien, probably too.
>> > 
>> > To have an account, you need an invitation.  Once you have an
>account,
>> > you can create rooms.  IIUC.
>> > 
>> > I am currently using the instance to our weekly Outreachy meeting
>with a
>> > dedicated room.  So yes, it is appears to me possible to open as
>many
>> > rooms as you want.
>> > 
>> > About the policy, last time, we did “admin of the room should
>accept”,
>> > so Julien, Tobias and me (maybe more I am not aware) were clicking
>on
>> > people to allow them to enter in the room.  It can also be totally
>open.
>> > I have no opinion.
>> > 
>> > From the past event, the schedule which seems maximizing dev
>attendees
>> > is 14:00-18:00 CET (more or less).  This slot is ok for American
>> > timezones (USA, Canada, Brazil, Argentina, etc.) and for European
>> > timezones (France, Germany, UK, Belgium, etc.).
>> > 
>> > Therefore, instead of the proposed morning unconference then
>afternoon
>> > hacking+newcomer, I would split:
>> > 
>> >    hacking+newcomer – unconference – hacking+newcomer.
>> > 
>> > Assuming unconference is what we want that most people attend.
>> > 
>> > Well, proposing a 12 hours event where people attend to what they
>want /
>> > can depending on their timezone.  For example, synchronising with
>> > Chinese Peng Mei Yu <pengmeiyu@riseup.net> for the early morning
>and
>> > with American folks for the late evening.
>> > 
>> > One point that fails at the previous event is “taking note”.  Each
>> > session should have one secretary and then report, even ugly notes.
> We
>> > are doing that at the IRL Guix Days–at least the 2 I attended–and
>it is
>> > a good and necessary practise.  We discussed it for the previous
>event
>> > but failed to implement it in the event.  It should be avoided this
>> > time. :-)
>> > 
>> > Last, I should prepare a blog post about the past event.  Boring
>and not
>> > fun task. :-) Since the initial motivation of this previous event
>was a
>> > repetition about the fringe FOSDEM Guix Days, it appears to me nice
>to
>> > end with the announce like “Schedule your Monday, Feb. 8th
>blablabla and
>> > stay tuned.”.  Well, since this task is blocking my agenda, I
>should
>> > send something about the previous event to review this week-end. 
>So,
>> > feel free to add anything which could be helpful for the next
>event.
>> > 
>> > 
>> > Cheers,
>> > simon
>> > 
>>