-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Skype/Google Hangout to discuss what we have so far, could focus on next? #27
Comments
I'm in depending on the time :) |
Great, Bjoern! Sure we'll find a time when at least a few of us are free. |
great! I am in. We might need doodle poll to decide on time. Also, I think multiple sessions might be good so people from different time zone can choose when to attend. |
Here's a Doodle poll for us to find a time - times as I put them in are for current German time i.e. CEST http://www.timeanddate.com/time/zones/cest http://doodle.com/kppufd3nme7vgtf7 We can chat via Google Hangout, but maybe first try out a video chatroom via appear.in? Malvika, think you've experience recording these things - would you be up for doing that and then sharing via YouTube? |
I have at times recorded the hangout chat by QuickTime Player. This I can do and send around the video or upload on YouTube/GitHub. Other option that I was suggesting is YouTube Livestream. This can be done by webcam. There is an option of Hangouts on Air to live stream a Hangout event using your webcam.This is automatically uploaded on YouTube for future reference. An alternative is livestream, here you can create an event and go live during the chat, I am not sure if its webcam friendly like youtube. It would be better if you do the livestream recording as a moderator. Let me know what do you think about it and which option sounds better. Cheers! |
I don't have (much) experience of this, Malviaka, you have more than me, I'm sure, so I'd follow your advice on this! |
If we are going to try appear.in then I can record the screen. But hangout on air is a very good option if we go for google hangout. How about we test it before the actual discussion/chat? |
Great - yes to all of that! |
Nice! I will learn a bit on how to handle hangout on air and we can test it beforehand. |
"re"-advertising plans for a chat here...: We'd like to discuss, together, what to do with what we've already collected on this repo about what makes a great open source bioinformatics community. We're keen that this develops as more than just one/a few people's vision - to make it, appropriately enough, as much as possible a "community" view. That's why we're so keen to talk about this with you. If you'd like to help out with this, please fill out this Doodle poll so we can find a time/date to meet online to discuss this: http://doodle.com/kppufd3nme7vgtf7 |
Hi guys, Online meetings sound good to me. I would suggest you to have a meeting via skype (like a group/conference call) or google hangout if you wish - whichever one takes quicker to arrange a meeting. Just a polite suggestion - I don't think it's necessary to have a recording of it, because there may be users who don't like the idea of their voice being recorded and/or users who don't feel comfortable appearing on a webcam. Also, video calls slow down the network speed...as far as my experience goes lol. The best (alternative) solution to recording/videoing is to keep a note of all the important points as we go along, and post them on Github. If any user is unable to attend the meeting, they can just quickly go through the notes. It would save their time from watching or listening to a recording. It would be less time-consuming for all, I think :) tbh I have had only skype, & face-to-face meetings so far. I understand and respect if others have different preferences. however I hope you take my suggestion into consideration. |
I too would prefer the meeting not to be recorded: we can be much more candid in a "private" discussion. |
When put like that, then, yes, certainly, let's not record it. I see value in keeping an (open) record of this kind of thing - BUT - encouraging relaxed participation in the activities is I think way more important than that, so for me, as I say, it's an easy call. |
Amazingly, with 8 respondents, we actually have a time that works for everyone!!! So let's meet, via GoogleHangout (I have the very original handle 'aidanbudd' if you need to link to me - I'll make a BOSC circle for this) on Thursday 20th August at 15.00 in Berlin time i.e. CEST http://www.timeanddate.com/time/zones/cest (which is GMT/UTC+2) Let us know if you strongly prefer an alternative to GoogleHangout e.g. appear.in For the format of the meeting - how about we try a virtual version of Lean Coffee as a way of us choosing and prioritising the topics we discuss (and how long we discuss them) together? http://leancoffee.org |
ahem - googlePlus name is aidan.budd not aidanbudd |
Plan for Hangout:
I'm going to (try) taking the role of neutral facilitator - plenty of my preferences and opinions have gone into current state of the project, I really want this to be shaped by other peoples ideas, so I'm happy to be neutral in this meeting - if I really feel the need to drop that role, I'll let you know I'm doing it.
|
Thanks to so many of you for joining the GoogleHangout today. I've created a directory in the repo for material related to this and possible future meetings - you'll find there the notes we made from todays discussion, and a summary of the key discussion topics, decisions, and action points: bosc2015/minutesOfMeetings/2015_08_20_googleHangout; summary is in 2015-08-20-BOSC-meetingSummary.md I've created an issue to discuss proposed/possible time plan for the project #30 |
Please add any constructive criticism/feedback about the hangout here - I'd be really interested in suggestions of how to make that kind of meeting more effective and inclusive |
Any of you up for meeting online to talk about this?
I'd be really interested to discuss like that to hear what you'd like to do with what we have so far.
The text was updated successfully, but these errors were encountered: