Team Meetings

Registered by amjjawad 

No doubt, it is very important to have regular meetings every now and then. Obviously, we are going to need 'more' meetings at the beginning and then, the need will be less later one after releasing our first version of ToriOS 1 :)

= = = = = = = = = = =
Meetings Places
= = = = = = = = = = =
Option A: Goolge Hangout

Option B: IRC

===================
Google Hangout vs IRC
===================
No need to re-type everything, I shall add this link which should say it all:
https://wiki.ubuntu.com/UbuntuGNOME/Meetings#Ubuntu_GNOME_Meetings

It has also information about IRC and it should be helpful.

====================================
How To Edit The Whiteboard on Blueprints
====================================
The steps are very easy and simple:

1- While you are viewing the Blueprint you would like to edit, Click on the Yellow Icon which says "Edit Whiteboard" - please see: https://wiki.ubuntu.com/UbuntuGNOME/Brainstorming?action=AttachFile&do=get&target=step2.png

2- Add your name/username/launchpad name between two [YOUR_NAME_HERE].

3- Post your suggestion at the bottom of the Whiteboard.

4- Once done, click on the Green Icon to accept the changes. You are Done.

5- Thank you for editing the Whiteboard.

6- Please 'do not' edit the description of the blueprint.

Blueprint information

Status:
Not started
Approver:
amjjawad 
Priority:
High
Drafter:
amjjawad 
Direction:
Approved
Assignee:
ToriOS
Definition:
Review
Series goal:
None
Implementation:
Informational Informational
Milestone target:
None

Related branches

Sprints

Whiteboard

[amjjawad] For me, I'd highly recommend Google Hangout for the reasons listed on this link: https://wiki.ubuntu.com/UbuntuGNOME/Meetings#Ubuntu_GNOME_Meetings . It is very easy, very quick, very effective and a great way to spread the word of ToriOS and you don't really have to open your CAM if you are too shy ;) and for those who don't have the hardware for this, don't worry, you still can watch and be on IRC as we can do both at the same time. In short: +1 from me for Google Hangout.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[plimptm] +1 for Google Hangout
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[Mélodie] -1 for Google Hangout. It is messy and uncomfortable (tight window, when you open it large the messages are not one under the other). I can offer to put up an IRC chan on freenode for #torios, with chanserv keeping the chan and ask someone I know to configure a server to keep logs, such as the ones we have for #linuxvillage, which you can have a look at here:
http://irclog.perlgeek.de/linuxvillage

I can also give advice on xchat mail client for it's configuration, colors to be chosen for the background, for the fonts… and so on.

I'll end this discussion by saying that most FOSS projects have their channel at IRC, some at irc.freenode.net (which is quite a strong network of servers) or at OFTC (which I visit once a while but know much less well). And if in need of ANYTHING we can get help from the freenode staffers on their chan. :)

At Google Hangout this is not going to happen!

Let me know your decision.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[dbyentzen] Google Hangout may be the way to go for smaller group meetings such as sub-teams and the like. IRC may be more useful, at this time, for larger, more general meetings. @Melodie, I do agree with you that, whether we gravitate to Hangout or IRC, the project needs an IRC channel( I opt for irc.freenode.net). Perhaps, as an experiment, the general project meetings could simultaneously go on an IRC channel and Hangout( for those that wish to participate). We would quickly find out which worked better for the project.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[Geoffrey] +1 for IRC meetings at irc.freenode.net in #torios
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[amjjawad] For the time being, there is no need for weekly/monthly meetings as long as we are almost meeting everyday on IRC (informal meetings) after 8:00PM GMT TIME (before or after).

However, if there is an urgent stuff to be discussed, we will call for more organized meeting before we do a meeting :)

P.S.
I still do like the idea of Google Hangout and we're even less than 10 at the same time so don't worry about the limitation of the participants ;)
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

[gsilva] I don't know if this vote is still up, but since I'm here to help, I'd like to say that Hangouts or IRC works fine for me. I use both regularly, so it's okay. Hangouts it's better for this IMO since it can save records of our discussions.

Since I'm the newest member joining the group, I'd like to know if you do any regular meetings, aside from those informal meetings Amijawad mention after 8pm.

------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
[israeldahl]
Current status of team meetings:
http://torios.org/news/weekly-meetings/
1900GMT on Saturdays every week (MOL)
on freenode #torios
You can use any IRC client to join the meetings

(?)

Work Items

Work items:
1- Email has been sent to the list - https://lists.launchpad.net/torios/msg00216.html : DONE
2- To start the discussion about the team meetings ASAP and have a meeting this week : TODO

Dependency tree

* Blueprints in grey have been implemented.

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.