Re: [E-devel] RFC unforgettable weekly meetings
On Tue, 15 May 2018 19:21:55 +0200 Marcel Hollerbach said: > Do what you like, call the time here. I give this up. I deleted the > calendar item and removed the wiki content regarding the proposed solution. > > I proposed this now 7 days ago, no one was opposed you even wrote > "I'm in on this. Already added it to my own personal calendar with > notifications etc." Now it seems that the wind has change 180° degrees > and we are from "I'm on this" to "I am against this". Both Okra and you convinced me with: "I'm well aware the other time slot allows for North Americans but it will then cut out anyone else. That's the point I was making - there is going to be little crossover. between the two groups of people meeting - and I don't think that is a good thing." "Just reminding you, UTC + 20 means that there will likely be noone else part of the meeting beside US people." People of late have been pointing fingers at me saying I don't listen, and I never change my mind and that it's impossible to do so etc. (despite me pointing at examples othrwise), and here these points seem really important and creating basically 2 groups sounds pretty bad to me and devalues the meetings significantly and will create friction etc. > Greetings, > bu5hm4n > > On 05/15/2018 04:48 PM, Carsten Haitzler wrote: > > On Tue, 15 May 2018 08:57:50 +0200 Marcel Hollerbach said: > > > >> We tried that last time, and you where the only one from the KR Timezone > >> while there are many committers from that part of the world, thats why i > >> say, try it this week with the other time, and see if it changes :) > > > > hermet was there for one, Christophe too. believe me when i say they wold > > have no issues staying up late (they do it often enough at the office). it > > has nothing to do with timezone, and more to do with "they wouldn't turn up > > regardless of time". in fact night times re technically far better as irc is > > blocked in their office environment unless you jump through hoops. > > > >> Also i dont see a problem with doing 2 meetings close to each other, > >> where one group is then just "reworking" the items from the last > >> meetings, giving theire decisions to it. In our case there is also a > >> overlapping group of people which is not too small, so its not really > >> seperated with the URC + 8 UTC + 16 time proposal. > > > > then that's just email with 2 entities passing back and forth. not really a > > meeting. :(. > > > >> Greetings, > >> bu5hm4n > >> > >> On 05/15/2018 07:35 AM, Carsten Haitzler (The Rasterman) wrote: > >>> On Mon, 14 May 2018 18:38:38 +0200 Marcel Hollerbach > >>> said: > >>> > I dont have strong feelings if its either shifted by 12h or by something > else. Just reminding you, UTC + 20 means that there will likely be noone > else part of the meeting beside US people. I dont want to propose that > some timezone needs to be active in both meethings, but it could > definitly help to have a few voices in both meetings, so things dont go > that orthogonal. > >>> > >>> i have to agree that doing it so that you end up with basically 2 > >>> disparate groups is bad. it's not a meeting then. we may as well just do > >>> things by mail if people have to "read the minutes later and then > >>> respond". you end up with an email-like back and forth between meeting > >>> groups. > >>> > >>> i say 1 time, and you make it, or you don't. if you care you make the time > >>> (stay up very late or get up early and sacrifice sleep). of course people > >>> have other things too in their lives, but this will just be dysfunctional > >>> if we end up dividing meeting groups up. and this was a good point. pick > >>> one time when most can make it with some effort. > >>> > >>> the previous 15:00 UTC slot seems to be about as good as it gets i think. > >>> > Greetings, > bu5hm4n > > On 05/14/2018 06:12 PM, Stephen Houston wrote: > > As Mike suggested and I've been saying... the meetings need to be > > exactly 12 hours apart, not 8 hours. So if Tuesday was UTC+8, Thursday > > would be UTC+20... then the next Tuesday UTC+20 and the next Thursday > > UTC+8, etc... > > > > On Mon, May 14, 2018, 9:42 AM Marcel Hollerbach wrote: > > > >> Okay, then lets say that we meet at the first full week and every third > >> full week, always on Tuesday and Thursday. > >> On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. > >> In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. > >> (This month however is a exception and we start this scheudule first > >> fully in June.) > >> > >> Meetings are captured with a IRC logger. > >> A few people can write the meeting minutes into http://collabedit.com. > >> > >> After the meetings the log is uploaded to the wiki same as the contents > >> that have been captured in collabedit document. > >> After that the
Re: [E-devel] RFC unforgettable weekly meetings
On Tue, 15 May 2018 21:48:05 +0200 Stefan Schmidt said: > Hello. > > > On 05/15/2018 07:21 PM, Marcel Hollerbach wrote: > > Do what you like, call the time here. I give this up. I deleted the > > calendar item and removed the wiki content regarding the proposed solution. > > > > I proposed this now 7 days ago, no one was opposed you even wrote > > "I'm in on this. Already added it to my own personal calendar with > > notifications etc." Now it seems that the wind has change 180° degrees > > and we are from "I'm on this" to "I am against this". > > > I am for one happy that you took the initiative to get some things started > (calendar entry, wiki page for minutes, etc) > > Going through this thread makes me wonder why we need to have like 30 mails > discussion about the perfect time for the meeting. I really think this can be > fine-tuned over time (echoing Mike here) as the need comes up. Right no we > should just go with a time that fits the people _we know_ attending. That is why i suggested the time we already used. for the prior IRC meetings. we could shuffle by one hour 1. a single time and see how it goes. see my other mails in this thread. > We should focus on having an agenda to talk about to actually achieve > something with this meetings and have an irc log and minutes later on. > Without having this and some actual meetings happened the whole discussion on > a complicated schedule is really mood. If we do not meeting content which is > worthwhile nobody will show up no matter how convenient the time is for them. > > Marcel took the step to setup time, agenda, etc for this meeting. Let's honor > this and see during the meeting if the time needs to change for the people > actually attending. > > regards > Stefan Schmidt > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On Tue, 15 May 2018 13:49:46 -0400 "William L. Thomson Jr." said: > On Tue, 15 May 2018 19:21:55 +0200 > Marcel Hollerbach wrote: > > > Do what you like, call the time here. I give this up. I deleted the > > calendar item and removed the wiki content regarding the proposed > > solution. > > > > I proposed this now 7 days ago, no one was opposed you even wrote > > "I'm in on this. Already added it to my own personal calendar with > > notifications etc." Now it seems that the wind has change 180° > > degrees and we are from "I'm on this" to "I am against this". > > The change is likely due to conceptual vs reality. At first likely > sounded like the best approach conceptually. Then in reality once > applied, it was deemed to not work out well. Thus the change in > support. Nothing to get discouraged over. This is right. it's not the whole meeting thing that I am against. it's 2 time slots that lead to 2 disparate groups. i don't want 2 groups. i don't want to encourage things to divide up like that. after this has been discussed i changed my mind on 2 slots because of exactly this point and i think 1 slot is better and people just have to make it. 7/8am pacific us time and about midnight jp/kr and 1am aus eastern time (and people in between have it easier) is doable for most people. nothing at 2, 3, 4, or 5 in the morning (well unless you re in hawaii or nz etc. ... but that's the least of the population). i'm just saying that i see a slot there that can work for everyone if they make a bit of effort and we don't divide people up. > If anything may consider a rotating time. One meeting at a given time, > then the next in a couple weeks at a different time. That way people can > make both, and each is having to make equal sacrifices. Late/early, > which flips for the next meeting. > > This is not to cater to time zones, as previously suggested and > attempted. But to make the suffering equal. Ideally at least one of > those all should attend, if not both. > > -- > William L. Thomson Jr. -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
Hello. On 05/15/2018 07:21 PM, Marcel Hollerbach wrote: > Do what you like, call the time here. I give this up. I deleted the > calendar item and removed the wiki content regarding the proposed solution. > > I proposed this now 7 days ago, no one was opposed you even wrote > "I'm in on this. Already added it to my own personal calendar with > notifications etc." Now it seems that the wind has change 180° degrees > and we are from "I'm on this" to "I am against this". > I am for one happy that you took the initiative to get some things started (calendar entry, wiki page for minutes, etc) Going through this thread makes me wonder why we need to have like 30 mails discussion about the perfect time for the meeting. I really think this can be fine-tuned over time (echoing Mike here) as the need comes up. Right no we should just go with a time that fits the people _we know_ attending. We should focus on having an agenda to talk about to actually achieve something with this meetings and have an irc log and minutes later on. Without having this and some actual meetings happened the whole discussion on a complicated schedule is really mood. If we do not meeting content which is worthwhile nobody will show up no matter how convenient the time is for them. Marcel took the step to setup time, agenda, etc for this meeting. Let's honor this and see during the meeting if the time needs to change for the people actually attending. regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
I uncancelled the event. Have this meeting since it was already scheduled, discussion and fine-tuning of schedule can continue independently. If a change is decided on, the schedule can be altered later. On Tue, May 15, 2018 at 1:50 PM William L. Thomson Jr. < wlt...@obsidian-studios.com> wrote: > On Tue, 15 May 2018 19:21:55 +0200 > Marcel Hollerbach wrote: > > > Do what you like, call the time here. I give this up. I deleted the > > calendar item and removed the wiki content regarding the proposed > > solution. > > > > I proposed this now 7 days ago, no one was opposed you even wrote > > "I'm in on this. Already added it to my own personal calendar with > > notifications etc." Now it seems that the wind has change 180° > > degrees and we are from "I'm on this" to "I am against this". > > The change is likely due to conceptual vs reality. At first likely > sounded like the best approach conceptually. Then in reality once > applied, it was deemed to not work out well. Thus the change in > support. Nothing to get discouraged over. > > If anything may consider a rotating time. One meeting at a given time, > then the next in a couple weeks at a different time. That way people can > make both, and each is having to make equal sacrifices. Late/early, > which flips for the next meeting. > > This is not to cater to time zones, as previously suggested and > attempted. But to make the suffering equal. Ideally at least one of > those all should attend, if not both. > > -- > William L. Thomson Jr. > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On Tue, 15 May 2018 19:21:55 +0200 Marcel Hollerbach wrote: > Do what you like, call the time here. I give this up. I deleted the > calendar item and removed the wiki content regarding the proposed > solution. > > I proposed this now 7 days ago, no one was opposed you even wrote > "I'm in on this. Already added it to my own personal calendar with > notifications etc." Now it seems that the wind has change 180° > degrees and we are from "I'm on this" to "I am against this". The change is likely due to conceptual vs reality. At first likely sounded like the best approach conceptually. Then in reality once applied, it was deemed to not work out well. Thus the change in support. Nothing to get discouraged over. If anything may consider a rotating time. One meeting at a given time, then the next in a couple weeks at a different time. That way people can make both, and each is having to make equal sacrifices. Late/early, which flips for the next meeting. This is not to cater to time zones, as previously suggested and attempted. But to make the suffering equal. Ideally at least one of those all should attend, if not both. -- William L. Thomson Jr. pgpH2yr0nW54l.pgp Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
Do what you like, call the time here. I give this up. I deleted the calendar item and removed the wiki content regarding the proposed solution. I proposed this now 7 days ago, no one was opposed you even wrote "I'm in on this. Already added it to my own personal calendar with notifications etc." Now it seems that the wind has change 180° degrees and we are from "I'm on this" to "I am against this". Greetings, bu5hm4n On 05/15/2018 04:48 PM, Carsten Haitzler wrote: On Tue, 15 May 2018 08:57:50 +0200 Marcel Hollerbach said: We tried that last time, and you where the only one from the KR Timezone while there are many committers from that part of the world, thats why i say, try it this week with the other time, and see if it changes :) hermet was there for one, Christophe too. believe me when i say they wold have no issues staying up late (they do it often enough at the office). it has nothing to do with timezone, and more to do with "they wouldn't turn up regardless of time". in fact night times re technically far better as irc is blocked in their office environment unless you jump through hoops. Also i dont see a problem with doing 2 meetings close to each other, where one group is then just "reworking" the items from the last meetings, giving theire decisions to it. In our case there is also a overlapping group of people which is not too small, so its not really seperated with the URC + 8 UTC + 16 time proposal. then that's just email with 2 entities passing back and forth. not really a meeting. :(. Greetings, bu5hm4n On 05/15/2018 07:35 AM, Carsten Haitzler (The Rasterman) wrote: On Mon, 14 May 2018 18:38:38 +0200 Marcel Hollerbach said: I dont have strong feelings if its either shifted by 12h or by something else. Just reminding you, UTC + 20 means that there will likely be noone else part of the meeting beside US people. I dont want to propose that some timezone needs to be active in both meethings, but it could definitly help to have a few voices in both meetings, so things dont go that orthogonal. i have to agree that doing it so that you end up with basically 2 disparate groups is bad. it's not a meeting then. we may as well just do things by mail if people have to "read the minutes later and then respond". you end up with an email-like back and forth between meeting groups. i say 1 time, and you make it, or you don't. if you care you make the time (stay up very late or get up early and sacrifice sleep). of course people have other things too in their lives, but this will just be dysfunctional if we end up dividing meeting groups up. and this was a good point. pick one time when most can make it with some effort. the previous 15:00 UTC slot seems to be about as good as it gets i think. Greetings, bu5hm4n On 05/14/2018 06:12 PM, Stephen Houston wrote: As Mike suggested and I've been saying... the meetings need to be exactly 12 hours apart, not 8 hours. So if Tuesday was UTC+8, Thursday would be UTC+20... then the next Tuesday UTC+20 and the next Thursday UTC+8, etc... On Mon, May 14, 2018, 9:42 AM Marcel Hollerbach wrote: Okay, then lets say that we meet at the first full week and every third full week, always on Tuesday and Thursday. On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. (This month however is a exception and we start this scheudule first fully in June.) Meetings are captured with a IRC logger. A few people can write the meeting minutes into http://collabedit.com. After the meetings the log is uploaded to the wiki same as the contents that have been captured in collabedit document. After that the wiki link can be sent to the mailinglists as reminder of what happened. How does that sound to you? Greetings, bu5hm4n On 05/11/2018 03:39 PM, Mike Blumenkrantz wrote: This is actually similar to how many projects organize their meetings. Having two separate meetings at "opposite" times allows everyone to have a choice of meetings to attend with at least one of the times being optimal for any given location. Using proper recording methods, everyone is then able to see what happened at each meeting. In the meeting procedures page (which should exist if it doesn't already), it should be documented that the meeting notes should be sent to all related channels/lists after each meeting to promote community involvement. I think that if everyone is okay with at least one of these times then this is fine, though it should be noted that this time schedule makes it awkward for any particular region to attend both meetings; traditionally the time rotates exactly 12 hours so that at least one timezone is capable of attending every meeting. The only adjustment I would make is that the meetings should be moved to weekly in this case. If the meeting times rotate and are set for every two weeks, this means that each group meets only once a month--hardly as
Re: [E-devel] RFC unforgettable weekly meetings
We tried that last time, and you where the only one from the KR Timezone while there are many committers from that part of the world, thats why i say, try it this week with the other time, and see if it changes :) Also i dont see a problem with doing 2 meetings close to each other, where one group is then just "reworking" the items from the last meetings, giving theire decisions to it. In our case there is also a overlapping group of people which is not too small, so its not really seperated with the URC + 8 UTC + 16 time proposal. Greetings, bu5hm4n On 05/15/2018 07:35 AM, Carsten Haitzler (The Rasterman) wrote: On Mon, 14 May 2018 18:38:38 +0200 Marcel Hollerbach said: I dont have strong feelings if its either shifted by 12h or by something else. Just reminding you, UTC + 20 means that there will likely be noone else part of the meeting beside US people. I dont want to propose that some timezone needs to be active in both meethings, but it could definitly help to have a few voices in both meetings, so things dont go that orthogonal. i have to agree that doing it so that you end up with basically 2 disparate groups is bad. it's not a meeting then. we may as well just do things by mail if people have to "read the minutes later and then respond". you end up with an email-like back and forth between meeting groups. i say 1 time, and you make it, or you don't. if you care you make the time (stay up very late or get up early and sacrifice sleep). of course people have other things too in their lives, but this will just be dysfunctional if we end up dividing meeting groups up. and this was a good point. pick one time when most can make it with some effort. the previous 15:00 UTC slot seems to be about as good as it gets i think. Greetings, bu5hm4n On 05/14/2018 06:12 PM, Stephen Houston wrote: As Mike suggested and I've been saying... the meetings need to be exactly 12 hours apart, not 8 hours. So if Tuesday was UTC+8, Thursday would be UTC+20... then the next Tuesday UTC+20 and the next Thursday UTC+8, etc... On Mon, May 14, 2018, 9:42 AM Marcel Hollerbach wrote: Okay, then lets say that we meet at the first full week and every third full week, always on Tuesday and Thursday. On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. (This month however is a exception and we start this scheudule first fully in June.) Meetings are captured with a IRC logger. A few people can write the meeting minutes into http://collabedit.com. After the meetings the log is uploaded to the wiki same as the contents that have been captured in collabedit document. After that the wiki link can be sent to the mailinglists as reminder of what happened. How does that sound to you? Greetings, bu5hm4n On 05/11/2018 03:39 PM, Mike Blumenkrantz wrote: This is actually similar to how many projects organize their meetings. Having two separate meetings at "opposite" times allows everyone to have a choice of meetings to attend with at least one of the times being optimal for any given location. Using proper recording methods, everyone is then able to see what happened at each meeting. In the meeting procedures page (which should exist if it doesn't already), it should be documented that the meeting notes should be sent to all related channels/lists after each meeting to promote community involvement. I think that if everyone is okay with at least one of these times then this is fine, though it should be noted that this time schedule makes it awkward for any particular region to attend both meetings; traditionally the time rotates exactly 12 hours so that at least one timezone is capable of attending every meeting. The only adjustment I would make is that the meetings should be moved to weekly in this case. If the meeting times rotate and are set for every two weeks, this means that each group meets only once a month--hardly as useful. On Thu, May 10, 2018 at 3:08 PM Stephen Houston wrote: I'm well aware the other time slot allows for North Americans but it will then cut out anyone else. That's the point I was making - there is going to be little crossover. between the two groups of people meeting - and I don't think that is a good thing. On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler wrote: On Thu, 10 May 2018 14:55:07 + Stephen Houston < smhousto...@gmail.com> said: This was the best time you could come up with for the meetings? 4-6AM EST, 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no North Americans are going to be present at all... at least with the time we were using for the meetings previously, it is reasonable enough for North Americans, Europeans, and Asians to all attend whether it be 8AM on the west coast of US or 11PM for like indefini in Japan... sure that is easier for US... but then you just flip that time for the second meeting and its st
Re: [E-devel] RFC unforgettable weekly meetings
On 15/05/18 15:05, Carsten Haitzler (The Rasterman) wrote: > On Mon, 14 May 2018 18:38:38 +0200 Marcel Hollerbach said: > >> I dont have strong feelings if its either shifted by 12h or by something >> else. Just reminding you, UTC + 20 means that there will likely be noone >> else part of the meeting beside US people. I dont want to propose that >> some timezone needs to be active in both meethings, but it could >> definitly help to have a few voices in both meetings, so things dont go >> that orthogonal. > > i have to agree that doing it so that you end up with basically 2 disparate > groups is bad. it's not a meeting then. we may as well just do things by mail > if people have to "read the minutes later and then respond". you end up with > an > email-like back and forth between meeting groups. > > i say 1 time, and you make it, or you don't. if you care you make the time > (stay up very late or get up early and sacrifice sleep). of course people have > other things too in their lives, but this will just be dysfunctional if we end > up dividing meeting groups up. and this was a good point. pick one time when > most can make it with some effort. > > the previous 15:00 UTC slot seems to be about as good as it gets i think. > I think 12 hrs apart is likely the wrong option, if you divide the world into approximately 3 time areas based loosely on working hours: Europe, US and Asia. 2 of the 3 will be able to make 1 meeting easily while the other would make the second. If the meetings had an 8 hr offset like I think the 2 most suggested times were, then it would be easy for 2 out of 3 timezones to get to one meeting and another 2 out of 3 to go to the second and there would be plenty of ovarlap between the 2 meetings >> Greetings, >> bu5hm4n >> >> On 05/14/2018 06:12 PM, Stephen Houston wrote: >>> As Mike suggested and I've been saying... the meetings need to be exactly >>> 12 hours apart, not 8 hours. So if Tuesday was UTC+8, Thursday would be >>> UTC+20... then the next Tuesday UTC+20 and the next Thursday UTC+8, etc... >>> >>> On Mon, May 14, 2018, 9:42 AM Marcel Hollerbach wrote: >>> Okay, then lets say that we meet at the first full week and every third full week, always on Tuesday and Thursday. On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. (This month however is a exception and we start this scheudule first fully in June.) Meetings are captured with a IRC logger. A few people can write the meeting minutes into http://collabedit.com. After the meetings the log is uploaded to the wiki same as the contents that have been captured in collabedit document. After that the wiki link can be sent to the mailinglists as reminder of what happened. How does that sound to you? Greetings, bu5hm4n On 05/11/2018 03:39 PM, Mike Blumenkrantz wrote: > This is actually similar to how many projects organize their meetings. > Having two separate meetings at "opposite" times allows everyone to have a > choice of meetings to attend with at least one of the times being optimal > for any given location. Using proper recording methods, everyone is then > able to see what happened at each meeting. In the meeting procedures page > (which should exist if it doesn't already), it should be documented that > the meeting notes should be sent to all related channels/lists after each > meeting to promote community involvement. > > I think that if everyone is okay with at least one of these times then this > is fine, though it should be noted that this time schedule makes it awkward > for any particular region to attend both meetings; traditionally the time > rotates exactly 12 hours so that at least one timezone is capable of > attending every meeting. > > The only adjustment I would make is that the meetings should be moved to > weekly in this case. If the meeting times rotate and are set for every two > weeks, this means that each group meets only once a month--hardly as useful. > > On Thu, May 10, 2018 at 3:08 PM Stephen Houston > wrote: > >> I'm well aware the other time slot allows for North Americans but it will >> then cut out anyone else. That's the point I was making - there is going >> to be little crossover. between the two groups of people meeting - and I >> don't think that is a good thing. >> >> On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler >> wrote: >> >>> On Thu, 10 May 2018 14:55:07 + Stephen Houston < >> smhousto...@gmail.com> >>> said: >>> This was the best time you could come up with for the meetings? 4-6AM >>> EST, 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no >>> North >>>
Re: [E-devel] RFC unforgettable weekly meetings
On Mon, 14 May 2018 18:38:38 +0200 Marcel Hollerbach said: > I dont have strong feelings if its either shifted by 12h or by something > else. Just reminding you, UTC + 20 means that there will likely be noone > else part of the meeting beside US people. I dont want to propose that > some timezone needs to be active in both meethings, but it could > definitly help to have a few voices in both meetings, so things dont go > that orthogonal. i have to agree that doing it so that you end up with basically 2 disparate groups is bad. it's not a meeting then. we may as well just do things by mail if people have to "read the minutes later and then respond". you end up with an email-like back and forth between meeting groups. i say 1 time, and you make it, or you don't. if you care you make the time (stay up very late or get up early and sacrifice sleep). of course people have other things too in their lives, but this will just be dysfunctional if we end up dividing meeting groups up. and this was a good point. pick one time when most can make it with some effort. the previous 15:00 UTC slot seems to be about as good as it gets i think. > Greetings, > bu5hm4n > > On 05/14/2018 06:12 PM, Stephen Houston wrote: > > As Mike suggested and I've been saying... the meetings need to be exactly > > 12 hours apart, not 8 hours. So if Tuesday was UTC+8, Thursday would be > > UTC+20... then the next Tuesday UTC+20 and the next Thursday UTC+8, etc... > > > > On Mon, May 14, 2018, 9:42 AM Marcel Hollerbach wrote: > > > >> Okay, then lets say that we meet at the first full week and every third > >> full week, always on Tuesday and Thursday. > >> On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. > >> In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. > >> (This month however is a exception and we start this scheudule first > >> fully in June.) > >> > >> Meetings are captured with a IRC logger. > >> A few people can write the meeting minutes into http://collabedit.com. > >> > >> After the meetings the log is uploaded to the wiki same as the contents > >> that have been captured in collabedit document. > >> After that the wiki link can be sent to the mailinglists as reminder of > >> what happened. > >> > >> How does that sound to you? > >> > >> Greetings, > >> bu5hm4n > >> > >> > >> On 05/11/2018 03:39 PM, Mike Blumenkrantz wrote: > >>> This is actually similar to how many projects organize their meetings. > >>> Having two separate meetings at "opposite" times allows everyone to have > >> a > >>> choice of meetings to attend with at least one of the times being optimal > >>> for any given location. Using proper recording methods, everyone is then > >>> able to see what happened at each meeting. In the meeting procedures page > >>> (which should exist if it doesn't already), it should be documented that > >>> the meeting notes should be sent to all related channels/lists after each > >>> meeting to promote community involvement. > >>> > >>> I think that if everyone is okay with at least one of these times then > >> this > >>> is fine, though it should be noted that this time schedule makes it > >> awkward > >>> for any particular region to attend both meetings; traditionally the time > >>> rotates exactly 12 hours so that at least one timezone is capable of > >>> attending every meeting. > >>> > >>> The only adjustment I would make is that the meetings should be moved to > >>> weekly in this case. If the meeting times rotate and are set for every > >> two > >>> weeks, this means that each group meets only once a month--hardly as > >> useful. > >>> > >>> On Thu, May 10, 2018 at 3:08 PM Stephen Houston > >>> wrote: > >>> > I'm well aware the other time slot allows for North Americans but it > >> will > then cut out anyone else. That's the point I was making - there is > >> going > to be little crossover. between the two groups of people meeting - and I > don't think that is a good thing. > > On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler > wrote: > > > On Thu, 10 May 2018 14:55:07 + Stephen Houston < > smhousto...@gmail.com> > > said: > > > >> This was the best time you could come up with for the meetings? 4-6AM > > EST, > >> 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no > > North > >> Americans are going to be present at all... at least with the time we > > were > >> using for the meetings previously, it is reasonable enough for North > >> Americans, Europeans, and Asians to all attend whether it be 8AM on > >> the > >> west coast of US or 11PM for like indefini in Japan... sure that is > > easier > >> for US... but then you just flip that time for the second meeting and > its > >> still reasonable enough for all to attend but easier for indefini in > >> Japan. This is what I was expecting. Not a time that is basically > going >
Re: [E-devel] RFC unforgettable weekly meetings
To be clear, my original point regarding a 12 hour difference between the meetings assumes that the selected times are viable for everyone and that it engages the maximum number of contributors: it's easier to remember a meeting time if it's always at the same numerical hour. In the case where a 12 hour flip is not ideal for this then there is no sense in forcing it. On Mon, May 14, 2018 at 12:39 PM Marcel Hollerbach wrote: > I dont have strong feelings if its either shifted by 12h or by something > else. Just reminding you, UTC + 20 means that there will likely be noone > else part of the meeting beside US people. I dont want to propose that > some timezone needs to be active in both meethings, but it could > definitly help to have a few voices in both meetings, so things dont go > that orthogonal. > > Greetings, > bu5hm4n > > On 05/14/2018 06:12 PM, Stephen Houston wrote: > > As Mike suggested and I've been saying... the meetings need to be exactly > > 12 hours apart, not 8 hours. So if Tuesday was UTC+8, Thursday would be > > UTC+20... then the next Tuesday UTC+20 and the next Thursday UTC+8, > etc... > > > > On Mon, May 14, 2018, 9:42 AM Marcel Hollerbach wrote: > > > >> Okay, then lets say that we meet at the first full week and every third > >> full week, always on Tuesday and Thursday. > >> On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. > >> In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. > >> (This month however is a exception and we start this scheudule first > >> fully in June.) > >> > >> Meetings are captured with a IRC logger. > >> A few people can write the meeting minutes into http://collabedit.com. > >> > >> After the meetings the log is uploaded to the wiki same as the contents > >> that have been captured in collabedit document. > >> After that the wiki link can be sent to the mailinglists as reminder of > >> what happened. > >> > >> How does that sound to you? > >> > >> Greetings, > >> bu5hm4n > >> > >> > >> On 05/11/2018 03:39 PM, Mike Blumenkrantz wrote: > >>> This is actually similar to how many projects organize their meetings. > >>> Having two separate meetings at "opposite" times allows everyone to > have > >> a > >>> choice of meetings to attend with at least one of the times being > optimal > >>> for any given location. Using proper recording methods, everyone is > then > >>> able to see what happened at each meeting. In the meeting procedures > page > >>> (which should exist if it doesn't already), it should be documented > that > >>> the meeting notes should be sent to all related channels/lists after > each > >>> meeting to promote community involvement. > >>> > >>> I think that if everyone is okay with at least one of these times then > >> this > >>> is fine, though it should be noted that this time schedule makes it > >> awkward > >>> for any particular region to attend both meetings; traditionally the > time > >>> rotates exactly 12 hours so that at least one timezone is capable of > >>> attending every meeting. > >>> > >>> The only adjustment I would make is that the meetings should be moved > to > >>> weekly in this case. If the meeting times rotate and are set for every > >> two > >>> weeks, this means that each group meets only once a month--hardly as > >> useful. > >>> > >>> On Thu, May 10, 2018 at 3:08 PM Stephen Houston > > >>> wrote: > >>> > I'm well aware the other time slot allows for North Americans but it > >> will > then cut out anyone else. That's the point I was making - there is > >> going > to be little crossover. between the two groups of people meeting - > and I > don't think that is a good thing. > > On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler < > ras...@rasterman.com> > wrote: > > > On Thu, 10 May 2018 14:55:07 + Stephen Houston < > smhousto...@gmail.com> > > said: > > > >> This was the best time you could come up with for the meetings? > 4-6AM > > EST, > >> 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no > > North > >> Americans are going to be present at all... at least with the time > we > > were > >> using for the meetings previously, it is reasonable enough for North > >> Americans, Europeans, and Asians to all attend whether it be 8AM on > >> the > >> west coast of US or 11PM for like indefini in Japan... sure that is > > easier > >> for US... but then you just flip that time for the second meeting > and > its > >> still reasonable enough for all to attend but easier for indefini in > >> Japan. This is what I was expecting. Not a time that is basically > going > >> to mean: US gets to meet the first meeting of the month with > eachother > > and > >> then Eastern European/Asians get to meet with eachother the second > > meeting > >> of the month and there is no crossover (minus Western Europeans that > can > >> make both
Re: [E-devel] RFC unforgettable weekly meetings
I dont have strong feelings if its either shifted by 12h or by something else. Just reminding you, UTC + 20 means that there will likely be noone else part of the meeting beside US people. I dont want to propose that some timezone needs to be active in both meethings, but it could definitly help to have a few voices in both meetings, so things dont go that orthogonal. Greetings, bu5hm4n On 05/14/2018 06:12 PM, Stephen Houston wrote: As Mike suggested and I've been saying... the meetings need to be exactly 12 hours apart, not 8 hours. So if Tuesday was UTC+8, Thursday would be UTC+20... then the next Tuesday UTC+20 and the next Thursday UTC+8, etc... On Mon, May 14, 2018, 9:42 AM Marcel Hollerbach wrote: Okay, then lets say that we meet at the first full week and every third full week, always on Tuesday and Thursday. On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. (This month however is a exception and we start this scheudule first fully in June.) Meetings are captured with a IRC logger. A few people can write the meeting minutes into http://collabedit.com. After the meetings the log is uploaded to the wiki same as the contents that have been captured in collabedit document. After that the wiki link can be sent to the mailinglists as reminder of what happened. How does that sound to you? Greetings, bu5hm4n On 05/11/2018 03:39 PM, Mike Blumenkrantz wrote: This is actually similar to how many projects organize their meetings. Having two separate meetings at "opposite" times allows everyone to have a choice of meetings to attend with at least one of the times being optimal for any given location. Using proper recording methods, everyone is then able to see what happened at each meeting. In the meeting procedures page (which should exist if it doesn't already), it should be documented that the meeting notes should be sent to all related channels/lists after each meeting to promote community involvement. I think that if everyone is okay with at least one of these times then this is fine, though it should be noted that this time schedule makes it awkward for any particular region to attend both meetings; traditionally the time rotates exactly 12 hours so that at least one timezone is capable of attending every meeting. The only adjustment I would make is that the meetings should be moved to weekly in this case. If the meeting times rotate and are set for every two weeks, this means that each group meets only once a month--hardly as useful. On Thu, May 10, 2018 at 3:08 PM Stephen Houston wrote: I'm well aware the other time slot allows for North Americans but it will then cut out anyone else. That's the point I was making - there is going to be little crossover. between the two groups of people meeting - and I don't think that is a good thing. On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler wrote: On Thu, 10 May 2018 14:55:07 + Stephen Houston < smhousto...@gmail.com> said: This was the best time you could come up with for the meetings? 4-6AM EST, 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no North Americans are going to be present at all... at least with the time we were using for the meetings previously, it is reasonable enough for North Americans, Europeans, and Asians to all attend whether it be 8AM on the west coast of US or 11PM for like indefini in Japan... sure that is easier for US... but then you just flip that time for the second meeting and its still reasonable enough for all to attend but easier for indefini in Japan. This is what I was expecting. Not a time that is basically going to mean: US gets to meet the first meeting of the month with eachother and then Eastern European/Asians get to meet with eachother the second meeting of the month and there is no crossover (minus Western Europeans that can make both). I foresee that as being bad and not really working out. ummm you need to look at the other time slot too. i don't think we're going to do 2hrs each... https://www.worldtimebuddy.com/?pl=1&lid=100,8,5,1850147&h=100 so one is 1am/4am PDT/EDT an the other is 9am/12pm PDT/EDT. (CDT being in between). and note on the other end with Japan (and Korea etc.) time. :) so they keep flipping between 2 times to try and let everyone attend at least once a month. On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach wrote: On 05/10/2018 09:22 AM, Simon Lees wrote: On 10/05/18 13:20, Carsten Haitzler wrote: On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz said: While I can see some summarization of meeting items on the relatively obscure https://phab.enlightenment.org/V33, which is inaccessible to anyone who has not been avidly following the mailing list archives--ie. will never be visible to any new community members--this is not quite the same as recording the minutes of a meeting.
Re: [E-devel] RFC unforgettable weekly meetings
As Mike suggested and I've been saying... the meetings need to be exactly 12 hours apart, not 8 hours. So if Tuesday was UTC+8, Thursday would be UTC+20... then the next Tuesday UTC+20 and the next Thursday UTC+8, etc... On Mon, May 14, 2018, 9:42 AM Marcel Hollerbach wrote: > Okay, then lets say that we meet at the first full week and every third > full week, always on Tuesday and Thursday. > On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. > In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. > (This month however is a exception and we start this scheudule first > fully in June.) > > Meetings are captured with a IRC logger. > A few people can write the meeting minutes into http://collabedit.com. > > After the meetings the log is uploaded to the wiki same as the contents > that have been captured in collabedit document. > After that the wiki link can be sent to the mailinglists as reminder of > what happened. > > How does that sound to you? > > Greetings, > bu5hm4n > > > On 05/11/2018 03:39 PM, Mike Blumenkrantz wrote: > > This is actually similar to how many projects organize their meetings. > > Having two separate meetings at "opposite" times allows everyone to have > a > > choice of meetings to attend with at least one of the times being optimal > > for any given location. Using proper recording methods, everyone is then > > able to see what happened at each meeting. In the meeting procedures page > > (which should exist if it doesn't already), it should be documented that > > the meeting notes should be sent to all related channels/lists after each > > meeting to promote community involvement. > > > > I think that if everyone is okay with at least one of these times then > this > > is fine, though it should be noted that this time schedule makes it > awkward > > for any particular region to attend both meetings; traditionally the time > > rotates exactly 12 hours so that at least one timezone is capable of > > attending every meeting. > > > > The only adjustment I would make is that the meetings should be moved to > > weekly in this case. If the meeting times rotate and are set for every > two > > weeks, this means that each group meets only once a month--hardly as > useful. > > > > On Thu, May 10, 2018 at 3:08 PM Stephen Houston > > wrote: > > > >> I'm well aware the other time slot allows for North Americans but it > will > >> then cut out anyone else. That's the point I was making - there is > going > >> to be little crossover. between the two groups of people meeting - and I > >> don't think that is a good thing. > >> > >> On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler > >> wrote: > >> > >>> On Thu, 10 May 2018 14:55:07 + Stephen Houston < > >> smhousto...@gmail.com> > >>> said: > >>> > This was the best time you could come up with for the meetings? 4-6AM > >>> EST, > 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no > >>> North > Americans are going to be present at all... at least with the time we > >>> were > using for the meetings previously, it is reasonable enough for North > Americans, Europeans, and Asians to all attend whether it be 8AM on > the > west coast of US or 11PM for like indefini in Japan... sure that is > >>> easier > for US... but then you just flip that time for the second meeting and > >> its > still reasonable enough for all to attend but easier for indefini in > Japan. This is what I was expecting. Not a time that is basically > >> going > to mean: US gets to meet the first meeting of the month with eachother > >>> and > then Eastern European/Asians get to meet with eachother the second > >>> meeting > of the month and there is no crossover (minus Western Europeans that > >> can > make both). I foresee that as being bad and not really working out. > >>> > >>> ummm you need to look at the other time slot too. i don't think we're > >>> going to > >>> do 2hrs each... > >>> > >>> https://www.worldtimebuddy.com/?pl=1&lid=100,8,5,1850147&h=100 > >>> > >>> so one is 1am/4am PDT/EDT an the other is 9am/12pm PDT/EDT. (CDT being > in > >>> between). and note on the other end with Japan (and Korea etc.) time. > >>> > >>> :) so they keep flipping between 2 times to try and let everyone attend > >> at > >>> least once a month. > >>> > On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach > >>> wrote: > > > > > > > On 05/10/2018 09:22 AM, Simon Lees wrote: > >> > >> > >> On 10/05/18 13:20, Carsten Haitzler wrote: > >>> On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz > >>> said: > >>> > While I can see some summarization of meeting items on the > >>> relatively > obscure https://phab.enlightenment.org/V33, which is > >> inaccessible > >>> to > > anyone > who has not been avidly following the mailing list archives--ie. > >>> will > > never > be visible to any new c
Re: [E-devel] RFC unforgettable weekly meetings
Okay, then lets say that we meet at the first full week and every third full week, always on Tuesday and Thursday. On the first week Tuesday is at UTC + 8 and Thursday at UTC + 16. In the third week Tuesday is at UTC + 16 and Thursday at UTC + 8. (This month however is a exception and we start this scheudule first fully in June.) Meetings are captured with a IRC logger. A few people can write the meeting minutes into http://collabedit.com. After the meetings the log is uploaded to the wiki same as the contents that have been captured in collabedit document. After that the wiki link can be sent to the mailinglists as reminder of what happened. How does that sound to you? Greetings, bu5hm4n On 05/11/2018 03:39 PM, Mike Blumenkrantz wrote: This is actually similar to how many projects organize their meetings. Having two separate meetings at "opposite" times allows everyone to have a choice of meetings to attend with at least one of the times being optimal for any given location. Using proper recording methods, everyone is then able to see what happened at each meeting. In the meeting procedures page (which should exist if it doesn't already), it should be documented that the meeting notes should be sent to all related channels/lists after each meeting to promote community involvement. I think that if everyone is okay with at least one of these times then this is fine, though it should be noted that this time schedule makes it awkward for any particular region to attend both meetings; traditionally the time rotates exactly 12 hours so that at least one timezone is capable of attending every meeting. The only adjustment I would make is that the meetings should be moved to weekly in this case. If the meeting times rotate and are set for every two weeks, this means that each group meets only once a month--hardly as useful. On Thu, May 10, 2018 at 3:08 PM Stephen Houston wrote: I'm well aware the other time slot allows for North Americans but it will then cut out anyone else. That's the point I was making - there is going to be little crossover. between the two groups of people meeting - and I don't think that is a good thing. On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler wrote: On Thu, 10 May 2018 14:55:07 + Stephen Houston < smhousto...@gmail.com> said: This was the best time you could come up with for the meetings? 4-6AM EST, 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no North Americans are going to be present at all... at least with the time we were using for the meetings previously, it is reasonable enough for North Americans, Europeans, and Asians to all attend whether it be 8AM on the west coast of US or 11PM for like indefini in Japan... sure that is easier for US... but then you just flip that time for the second meeting and its still reasonable enough for all to attend but easier for indefini in Japan. This is what I was expecting. Not a time that is basically going to mean: US gets to meet the first meeting of the month with eachother and then Eastern European/Asians get to meet with eachother the second meeting of the month and there is no crossover (minus Western Europeans that can make both). I foresee that as being bad and not really working out. ummm you need to look at the other time slot too. i don't think we're going to do 2hrs each... https://www.worldtimebuddy.com/?pl=1&lid=100,8,5,1850147&h=100 so one is 1am/4am PDT/EDT an the other is 9am/12pm PDT/EDT. (CDT being in between). and note on the other end with Japan (and Korea etc.) time. :) so they keep flipping between 2 times to try and let everyone attend at least once a month. On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach wrote: On 05/10/2018 09:22 AM, Simon Lees wrote: On 10/05/18 13:20, Carsten Haitzler wrote: On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz said: While I can see some summarization of meeting items on the relatively obscure https://phab.enlightenment.org/V33, which is inaccessible to anyone who has not been avidly following the mailing list archives--ie. will never be visible to any new community members--this is not quite the same as recording the minutes of a meeting. see the ticket that this was all about. it's there in the ticket itself in the body. that is where the conversation was happening so it's summarized there. https://phab.enlightenment.org/T6740 i don't see why etherpad is needed. we have plenty of tools on phab for this. no one disagreed with a wiki page. you were talking as if people need to have it explained to them what minutes are: "Typically for meetings where items of substance are discussed, the minutes will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes"; marcel already said: "But i agree in general that there should be a wiki page for monitoring contents of the meetings and some them up." ... so again. i see no reason why minute
Re: [E-devel] RFC unforgettable weekly meetings
This is actually similar to how many projects organize their meetings. Having two separate meetings at "opposite" times allows everyone to have a choice of meetings to attend with at least one of the times being optimal for any given location. Using proper recording methods, everyone is then able to see what happened at each meeting. In the meeting procedures page (which should exist if it doesn't already), it should be documented that the meeting notes should be sent to all related channels/lists after each meeting to promote community involvement. I think that if everyone is okay with at least one of these times then this is fine, though it should be noted that this time schedule makes it awkward for any particular region to attend both meetings; traditionally the time rotates exactly 12 hours so that at least one timezone is capable of attending every meeting. The only adjustment I would make is that the meetings should be moved to weekly in this case. If the meeting times rotate and are set for every two weeks, this means that each group meets only once a month--hardly as useful. On Thu, May 10, 2018 at 3:08 PM Stephen Houston wrote: > I'm well aware the other time slot allows for North Americans but it will > then cut out anyone else. That's the point I was making - there is going > to be little crossover. between the two groups of people meeting - and I > don't think that is a good thing. > > On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler > wrote: > > > On Thu, 10 May 2018 14:55:07 + Stephen Houston < > smhousto...@gmail.com> > > said: > > > > > This was the best time you could come up with for the meetings? 4-6AM > > EST, > > > 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no > > North > > > Americans are going to be present at all... at least with the time we > > were > > > using for the meetings previously, it is reasonable enough for North > > > Americans, Europeans, and Asians to all attend whether it be 8AM on the > > > west coast of US or 11PM for like indefini in Japan... sure that is > > easier > > > for US... but then you just flip that time for the second meeting and > its > > > still reasonable enough for all to attend but easier for indefini in > > > Japan. This is what I was expecting. Not a time that is basically > going > > > to mean: US gets to meet the first meeting of the month with eachother > > and > > > then Eastern European/Asians get to meet with eachother the second > > meeting > > > of the month and there is no crossover (minus Western Europeans that > can > > > make both). I foresee that as being bad and not really working out. > > > > ummm you need to look at the other time slot too. i don't think we're > > going to > > do 2hrs each... > > > > https://www.worldtimebuddy.com/?pl=1&lid=100,8,5,1850147&h=100 > > > > so one is 1am/4am PDT/EDT an the other is 9am/12pm PDT/EDT. (CDT being in > > between). and note on the other end with Japan (and Korea etc.) time. > > > > :) so they keep flipping between 2 times to try and let everyone attend > at > > least once a month. > > > > > On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach > > wrote: > > > > > > > > > > > > > > > On 05/10/2018 09:22 AM, Simon Lees wrote: > > > > > > > > > > > > > > > On 10/05/18 13:20, Carsten Haitzler wrote: > > > > >> On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz > > > > >> said: > > > > >> > > > > >>> While I can see some summarization of meeting items on the > > relatively > > > > >>> obscure https://phab.enlightenment.org/V33, which is > inaccessible > > to > > > > anyone > > > > >>> who has not been avidly following the mailing list archives--ie. > > will > > > > never > > > > >>> be visible to any new community members--this is not quite the > > same as > > > > >>> recording the minutes of a meeting. > > > > >> > > > > >> see the ticket that this was all about. it's there in the ticket > > itself > > > > in the > > > > >> body. that is where the conversation was happening so it's > > summarized > > > > there. > > > > >> > > > > >> https://phab.enlightenment.org/T6740 > > > > >> > > > > >> i don't see why etherpad is needed. we have plenty of tools on > phab > > for > > > > this. > > > > >> no one disagreed with a wiki page. > > > > >> > > > > >> you were talking as if people need to have it explained to them > what > > > > minutes > > > > >> are: > > > > >> > > > > >> "Typically for meetings where items of substance are discussed, > the > > > > minutes > > > > >> will be recorded for posterity: > > https://en.wikipedia.org/wiki/Minutes"; > > > > >> > > > > >> marcel already said: > > > > >> > > > > >> "But i agree in general that there should be a wiki page for > > monitoring > > > > >> contents of the meetings and some them up." > > > > >> > > > > >> ... so again. i see no reason why minutes will not be taken and > > > > recorded. > > > > >> > > > > > > > > > > What I would like to see and I think what Mike is getting at is a > > wiki > > > > > page ei
Re: [E-devel] RFC unforgettable weekly meetings
Perhaps we should -- otherwise I see people voting and making decisions in one group that the other group would not agree to at all, as well as the fact that the North American group is pretty heavily E devs and the European/Asian group is pretty heavily interfaces/EFL ... without crossover there I just foresee that being a problem. We can still have two meetings, but just make the time slot a little more reasonable for each so there is at least the opportunity for crossover, or we can go back to one, or we can just leave it as is and see what happens. On Fri, May 11, 2018, 4:27 AM Carsten Haitzler wrote: > On Thu, 10 May 2018 19:07:56 + Stephen Houston > said: > > > I'm well aware the other time slot allows for North Americans but it will > > then cut out anyone else. That's the point I was making - there is going > > to be little crossover. between the two groups of people meeting - and I > > don't think that is a good thing. > > in that case we should only have 1 time slot and "deal with it" because if > you > have 2, people will attend the one that easier for them and skip the > other. you > force people who want to participate to adapt to a single slot so there is > no > "lack of crossover". > > > On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler > > wrote: > > > > > On Thu, 10 May 2018 14:55:07 + Stephen Houston < > smhousto...@gmail.com> > > > said: > > > > > > > This was the best time you could come up with for the meetings? > 4-6AM > > > EST, > > > > 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no > > > North > > > > Americans are going to be present at all... at least with the time we > > > were > > > > using for the meetings previously, it is reasonable enough for North > > > > Americans, Europeans, and Asians to all attend whether it be 8AM on > the > > > > west coast of US or 11PM for like indefini in Japan... sure that is > > > easier > > > > for US... but then you just flip that time for the second meeting > and its > > > > still reasonable enough for all to attend but easier for indefini in > > > > Japan. This is what I was expecting. Not a time that is basically > going > > > > to mean: US gets to meet the first meeting of the month with > eachother > > > and > > > > then Eastern European/Asians get to meet with eachother the second > > > meeting > > > > of the month and there is no crossover (minus Western Europeans that > can > > > > make both). I foresee that as being bad and not really working out. > > > > > > ummm you need to look at the other time slot too. i don't think we're > > > going to > > > do 2hrs each... > > > > > > https://www.worldtimebuddy.com/?pl=1&lid=100,8,5,1850147&h=100 > > > > > > so one is 1am/4am PDT/EDT an the other is 9am/12pm PDT/EDT. (CDT being > in > > > between). and note on the other end with Japan (and Korea etc.) time. > > > > > > :) so they keep flipping between 2 times to try and let everyone > attend at > > > least once a month. > > > > > > > On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach > > > wrote: > > > > > > > > > > > > > > > > > > > On 05/10/2018 09:22 AM, Simon Lees wrote: > > > > > > > > > > > > > > > > > > On 10/05/18 13:20, Carsten Haitzler wrote: > > > > > >> On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz > > > > > >> said: > > > > > >> > > > > > >>> While I can see some summarization of meeting items on the > > > relatively > > > > > >>> obscure https://phab.enlightenment.org/V33, which is > inaccessible > > > to > > > > > anyone > > > > > >>> who has not been avidly following the mailing list > archives--ie. > > > will > > > > > never > > > > > >>> be visible to any new community members--this is not quite the > > > same as > > > > > >>> recording the minutes of a meeting. > > > > > >> > > > > > >> see the ticket that this was all about. it's there in the ticket > > > itself > > > > > in the > > > > > >> body. that is where the conversation was happening so it's > > > summarized > > > > > there. > > > > > >> > > > > > >> https://phab.enlightenment.org/T6740 > > > > > >> > > > > > >> i don't see why etherpad is needed. we have plenty of tools on > phab > > > for > > > > > this. > > > > > >> no one disagreed with a wiki page. > > > > > >> > > > > > >> you were talking as if people need to have it explained to them > what > > > > > minutes > > > > > >> are: > > > > > >> > > > > > >> "Typically for meetings where items of substance are discussed, > the > > > > > minutes > > > > > >> will be recorded for posterity: > > > https://en.wikipedia.org/wiki/Minutes"; > > > > > >> > > > > > >> marcel already said: > > > > > >> > > > > > >> "But i agree in general that there should be a wiki page for > > > monitoring > > > > > >> contents of the meetings and some them up." > > > > > >> > > > > > >> ... so again. i see no reason why minutes will not be taken and > > > > > recorded. > > > > > >> > > > > > > > > > > > > What I would like to see and I think what Mike is getting at is a > > > wiki > > > > > > p
Re: [E-devel] RFC unforgettable weekly meetings
On Thu, 10 May 2018 19:07:56 + Stephen Houston said: > I'm well aware the other time slot allows for North Americans but it will > then cut out anyone else. That's the point I was making - there is going > to be little crossover. between the two groups of people meeting - and I > don't think that is a good thing. in that case we should only have 1 time slot and "deal with it" because if you have 2, people will attend the one that easier for them and skip the other. you force people who want to participate to adapt to a single slot so there is no "lack of crossover". > On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler > wrote: > > > On Thu, 10 May 2018 14:55:07 + Stephen Houston > > said: > > > > > This was the best time you could come up with for the meetings? 4-6AM > > EST, > > > 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no > > North > > > Americans are going to be present at all... at least with the time we > > were > > > using for the meetings previously, it is reasonable enough for North > > > Americans, Europeans, and Asians to all attend whether it be 8AM on the > > > west coast of US or 11PM for like indefini in Japan... sure that is > > easier > > > for US... but then you just flip that time for the second meeting and its > > > still reasonable enough for all to attend but easier for indefini in > > > Japan. This is what I was expecting. Not a time that is basically going > > > to mean: US gets to meet the first meeting of the month with eachother > > and > > > then Eastern European/Asians get to meet with eachother the second > > meeting > > > of the month and there is no crossover (minus Western Europeans that can > > > make both). I foresee that as being bad and not really working out. > > > > ummm you need to look at the other time slot too. i don't think we're > > going to > > do 2hrs each... > > > > https://www.worldtimebuddy.com/?pl=1&lid=100,8,5,1850147&h=100 > > > > so one is 1am/4am PDT/EDT an the other is 9am/12pm PDT/EDT. (CDT being in > > between). and note on the other end with Japan (and Korea etc.) time. > > > > :) so they keep flipping between 2 times to try and let everyone attend at > > least once a month. > > > > > On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach > > wrote: > > > > > > > > > > > > > > > On 05/10/2018 09:22 AM, Simon Lees wrote: > > > > > > > > > > > > > > > On 10/05/18 13:20, Carsten Haitzler wrote: > > > > >> On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz > > > > >> said: > > > > >> > > > > >>> While I can see some summarization of meeting items on the > > relatively > > > > >>> obscure https://phab.enlightenment.org/V33, which is inaccessible > > to > > > > anyone > > > > >>> who has not been avidly following the mailing list archives--ie. > > will > > > > never > > > > >>> be visible to any new community members--this is not quite the > > same as > > > > >>> recording the minutes of a meeting. > > > > >> > > > > >> see the ticket that this was all about. it's there in the ticket > > itself > > > > in the > > > > >> body. that is where the conversation was happening so it's > > summarized > > > > there. > > > > >> > > > > >> https://phab.enlightenment.org/T6740 > > > > >> > > > > >> i don't see why etherpad is needed. we have plenty of tools on phab > > for > > > > this. > > > > >> no one disagreed with a wiki page. > > > > >> > > > > >> you were talking as if people need to have it explained to them what > > > > minutes > > > > >> are: > > > > >> > > > > >> "Typically for meetings where items of substance are discussed, the > > > > minutes > > > > >> will be recorded for posterity: > > https://en.wikipedia.org/wiki/Minutes"; > > > > >> > > > > >> marcel already said: > > > > >> > > > > >> "But i agree in general that there should be a wiki page for > > monitoring > > > > >> contents of the meetings and some them up." > > > > >> > > > > >> ... so again. i see no reason why minutes will not be taken and > > > > recorded. > > > > >> > > > > > > > > > > What I would like to see and I think what Mike is getting at is a > > wiki > > > > > page either on the main wiki or somewhere on phab, which atleast > > lists > > > > > all the links to the meeting summaries rather then just having > > obscure > > > > > phab links to them. Even better would be if all the summaries were > > also > > > > > just in one page so you didn't have to click links to follow the > > > > > previous meetings. > > > > > > > > > > > > > Yep, thats what i want to do on this page and the linked pages > > > > https://phab.enlightenment.org/w/meetings/ :). > > > > > > > > > Cheers > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > Check out the vibrant tech community on one of the world's most > > > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > > > > > > > > > > > > > > > > > ___ > > > > >
Re: [E-devel] RFC unforgettable weekly meetings
I'm well aware the other time slot allows for North Americans but it will then cut out anyone else. That's the point I was making - there is going to be little crossover. between the two groups of people meeting - and I don't think that is a good thing. On Thu, May 10, 2018 at 2:06 PM Carsten Haitzler wrote: > On Thu, 10 May 2018 14:55:07 + Stephen Houston > said: > > > This was the best time you could come up with for the meetings? 4-6AM > EST, > > 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no > North > > Americans are going to be present at all... at least with the time we > were > > using for the meetings previously, it is reasonable enough for North > > Americans, Europeans, and Asians to all attend whether it be 8AM on the > > west coast of US or 11PM for like indefini in Japan... sure that is > easier > > for US... but then you just flip that time for the second meeting and its > > still reasonable enough for all to attend but easier for indefini in > > Japan. This is what I was expecting. Not a time that is basically going > > to mean: US gets to meet the first meeting of the month with eachother > and > > then Eastern European/Asians get to meet with eachother the second > meeting > > of the month and there is no crossover (minus Western Europeans that can > > make both). I foresee that as being bad and not really working out. > > ummm you need to look at the other time slot too. i don't think we're > going to > do 2hrs each... > > https://www.worldtimebuddy.com/?pl=1&lid=100,8,5,1850147&h=100 > > so one is 1am/4am PDT/EDT an the other is 9am/12pm PDT/EDT. (CDT being in > between). and note on the other end with Japan (and Korea etc.) time. > > :) so they keep flipping between 2 times to try and let everyone attend at > least once a month. > > > On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach > wrote: > > > > > > > > > > > On 05/10/2018 09:22 AM, Simon Lees wrote: > > > > > > > > > > > > On 10/05/18 13:20, Carsten Haitzler wrote: > > > >> On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz > > > >> said: > > > >> > > > >>> While I can see some summarization of meeting items on the > relatively > > > >>> obscure https://phab.enlightenment.org/V33, which is inaccessible > to > > > anyone > > > >>> who has not been avidly following the mailing list archives--ie. > will > > > never > > > >>> be visible to any new community members--this is not quite the > same as > > > >>> recording the minutes of a meeting. > > > >> > > > >> see the ticket that this was all about. it's there in the ticket > itself > > > in the > > > >> body. that is where the conversation was happening so it's > summarized > > > there. > > > >> > > > >> https://phab.enlightenment.org/T6740 > > > >> > > > >> i don't see why etherpad is needed. we have plenty of tools on phab > for > > > this. > > > >> no one disagreed with a wiki page. > > > >> > > > >> you were talking as if people need to have it explained to them what > > > minutes > > > >> are: > > > >> > > > >> "Typically for meetings where items of substance are discussed, the > > > minutes > > > >> will be recorded for posterity: > https://en.wikipedia.org/wiki/Minutes"; > > > >> > > > >> marcel already said: > > > >> > > > >> "But i agree in general that there should be a wiki page for > monitoring > > > >> contents of the meetings and some them up." > > > >> > > > >> ... so again. i see no reason why minutes will not be taken and > > > recorded. > > > >> > > > > > > > > What I would like to see and I think what Mike is getting at is a > wiki > > > > page either on the main wiki or somewhere on phab, which atleast > lists > > > > all the links to the meeting summaries rather then just having > obscure > > > > phab links to them. Even better would be if all the summaries were > also > > > > just in one page so you didn't have to click links to follow the > > > > previous meetings. > > > > > > > > > > Yep, thats what i want to do on this page and the linked pages > > > https://phab.enlightenment.org/w/meetings/ :). > > > > > > > Cheers > > > > > > > > > > > > > > > > > > > > -- > > > > Check out the vibrant tech community on one of the world's most > > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > > > > > > > > > > > > > ___ > > > > enlightenment-devel mailing list > > > > enlightenment-devel@lists.sourceforge.net > > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > > > > > > > > -- > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > ___ > > > enlightenment-devel mailing list > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.ne
Re: [E-devel] RFC unforgettable weekly meetings
On Thu, 10 May 2018 14:55:07 + Stephen Houston said: > This was the best time you could come up with for the meetings? 4-6AM EST, > 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no North > Americans are going to be present at all... at least with the time we were > using for the meetings previously, it is reasonable enough for North > Americans, Europeans, and Asians to all attend whether it be 8AM on the > west coast of US or 11PM for like indefini in Japan... sure that is easier > for US... but then you just flip that time for the second meeting and its > still reasonable enough for all to attend but easier for indefini in > Japan. This is what I was expecting. Not a time that is basically going > to mean: US gets to meet the first meeting of the month with eachother and > then Eastern European/Asians get to meet with eachother the second meeting > of the month and there is no crossover (minus Western Europeans that can > make both). I foresee that as being bad and not really working out. ummm you need to look at the other time slot too. i don't think we're going to do 2hrs each... https://www.worldtimebuddy.com/?pl=1&lid=100,8,5,1850147&h=100 so one is 1am/4am PDT/EDT an the other is 9am/12pm PDT/EDT. (CDT being in between). and note on the other end with Japan (and Korea etc.) time. :) so they keep flipping between 2 times to try and let everyone attend at least once a month. > On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach wrote: > > > > > > > On 05/10/2018 09:22 AM, Simon Lees wrote: > > > > > > > > > On 10/05/18 13:20, Carsten Haitzler wrote: > > >> On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz > > >> said: > > >> > > >>> While I can see some summarization of meeting items on the relatively > > >>> obscure https://phab.enlightenment.org/V33, which is inaccessible to > > anyone > > >>> who has not been avidly following the mailing list archives--ie. will > > never > > >>> be visible to any new community members--this is not quite the same as > > >>> recording the minutes of a meeting. > > >> > > >> see the ticket that this was all about. it's there in the ticket itself > > in the > > >> body. that is where the conversation was happening so it's summarized > > there. > > >> > > >> https://phab.enlightenment.org/T6740 > > >> > > >> i don't see why etherpad is needed. we have plenty of tools on phab for > > this. > > >> no one disagreed with a wiki page. > > >> > > >> you were talking as if people need to have it explained to them what > > minutes > > >> are: > > >> > > >> "Typically for meetings where items of substance are discussed, the > > minutes > > >> will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes"; > > >> > > >> marcel already said: > > >> > > >> "But i agree in general that there should be a wiki page for monitoring > > >> contents of the meetings and some them up." > > >> > > >> ... so again. i see no reason why minutes will not be taken and > > recorded. > > >> > > > > > > What I would like to see and I think what Mike is getting at is a wiki > > > page either on the main wiki or somewhere on phab, which atleast lists > > > all the links to the meeting summaries rather then just having obscure > > > phab links to them. Even better would be if all the summaries were also > > > just in one page so you didn't have to click links to follow the > > > previous meetings. > > > > > > > Yep, thats what i want to do on this page and the linked pages > > https://phab.enlightenment.org/w/meetings/ :). > > > > > Cheers > > > > > > > > > > > > > > -- > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > > > > > > > > > ___ > > > enlightenment-devel mailing list > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -
Re: [E-devel] RFC unforgettable weekly meetings
From the original email: "(Times can be discussed, they are copied from https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx Christophe Sadoine)" So yes *for now* its the best i had as an example, feel free to propose something else :) Greetings, bu5hm4n On 05/10/2018 04:55 PM, Stephen Houston wrote: This was the best time you could come up with for the meetings? 4-6AM EST, 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no North Americans are going to be present at all... at least with the time we were using for the meetings previously, it is reasonable enough for North Americans, Europeans, and Asians to all attend whether it be 8AM on the west coast of US or 11PM for like indefini in Japan... sure that is easier for US... but then you just flip that time for the second meeting and its still reasonable enough for all to attend but easier for indefini in Japan. This is what I was expecting. Not a time that is basically going to mean: US gets to meet the first meeting of the month with eachother and then Eastern European/Asians get to meet with eachother the second meeting of the month and there is no crossover (minus Western Europeans that can make both). I foresee that as being bad and not really working out. On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach wrote: On 05/10/2018 09:22 AM, Simon Lees wrote: On 10/05/18 13:20, Carsten Haitzler wrote: On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz said: While I can see some summarization of meeting items on the relatively obscure https://phab.enlightenment.org/V33, which is inaccessible to anyone who has not been avidly following the mailing list archives--ie. will never be visible to any new community members--this is not quite the same as recording the minutes of a meeting. see the ticket that this was all about. it's there in the ticket itself in the body. that is where the conversation was happening so it's summarized there. https://phab.enlightenment.org/T6740 i don't see why etherpad is needed. we have plenty of tools on phab for this. no one disagreed with a wiki page. you were talking as if people need to have it explained to them what minutes are: "Typically for meetings where items of substance are discussed, the minutes will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes"; marcel already said: "But i agree in general that there should be a wiki page for monitoring contents of the meetings and some them up." ... so again. i see no reason why minutes will not be taken and recorded. What I would like to see and I think what Mike is getting at is a wiki page either on the main wiki or somewhere on phab, which atleast lists all the links to the meeting summaries rather then just having obscure phab links to them. Even better would be if all the summaries were also just in one page so you didn't have to click links to follow the previous meetings. Yep, thats what i want to do on this page and the linked pages https://phab.enlightenment.org/w/meetings/ :). Cheers -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
This was the best time you could come up with for the meetings? 4-6AM EST, 3-5AM CDT, 2-4AM MST, and 1-3AM PDT? That pretty much means that no North Americans are going to be present at all... at least with the time we were using for the meetings previously, it is reasonable enough for North Americans, Europeans, and Asians to all attend whether it be 8AM on the west coast of US or 11PM for like indefini in Japan... sure that is easier for US... but then you just flip that time for the second meeting and its still reasonable enough for all to attend but easier for indefini in Japan. This is what I was expecting. Not a time that is basically going to mean: US gets to meet the first meeting of the month with eachother and then Eastern European/Asians get to meet with eachother the second meeting of the month and there is no crossover (minus Western Europeans that can make both). I foresee that as being bad and not really working out. On Thu, May 10, 2018 at 3:58 AM Marcel Hollerbach wrote: > > > On 05/10/2018 09:22 AM, Simon Lees wrote: > > > > > > On 10/05/18 13:20, Carsten Haitzler wrote: > >> On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz > >> said: > >> > >>> While I can see some summarization of meeting items on the relatively > >>> obscure https://phab.enlightenment.org/V33, which is inaccessible to > anyone > >>> who has not been avidly following the mailing list archives--ie. will > never > >>> be visible to any new community members--this is not quite the same as > >>> recording the minutes of a meeting. > >> > >> see the ticket that this was all about. it's there in the ticket itself > in the > >> body. that is where the conversation was happening so it's summarized > there. > >> > >> https://phab.enlightenment.org/T6740 > >> > >> i don't see why etherpad is needed. we have plenty of tools on phab for > this. > >> no one disagreed with a wiki page. > >> > >> you were talking as if people need to have it explained to them what > minutes > >> are: > >> > >> "Typically for meetings where items of substance are discussed, the > minutes > >> will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes"; > >> > >> marcel already said: > >> > >> "But i agree in general that there should be a wiki page for monitoring > >> contents of the meetings and some them up." > >> > >> ... so again. i see no reason why minutes will not be taken and > recorded. > >> > > > > What I would like to see and I think what Mike is getting at is a wiki > > page either on the main wiki or somewhere on phab, which atleast lists > > all the links to the meeting summaries rather then just having obscure > > phab links to them. Even better would be if all the summaries were also > > just in one page so you didn't have to click links to follow the > > previous meetings. > > > > Yep, thats what i want to do on this page and the linked pages > https://phab.enlightenment.org/w/meetings/ :). > > > Cheers > > > > > > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > > > > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On 05/10/2018 09:22 AM, Simon Lees wrote: On 10/05/18 13:20, Carsten Haitzler wrote: On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz said: While I can see some summarization of meeting items on the relatively obscure https://phab.enlightenment.org/V33, which is inaccessible to anyone who has not been avidly following the mailing list archives--ie. will never be visible to any new community members--this is not quite the same as recording the minutes of a meeting. see the ticket that this was all about. it's there in the ticket itself in the body. that is where the conversation was happening so it's summarized there. https://phab.enlightenment.org/T6740 i don't see why etherpad is needed. we have plenty of tools on phab for this. no one disagreed with a wiki page. you were talking as if people need to have it explained to them what minutes are: "Typically for meetings where items of substance are discussed, the minutes will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes"; marcel already said: "But i agree in general that there should be a wiki page for monitoring contents of the meetings and some them up." ... so again. i see no reason why minutes will not be taken and recorded. What I would like to see and I think what Mike is getting at is a wiki page either on the main wiki or somewhere on phab, which atleast lists all the links to the meeting summaries rather then just having obscure phab links to them. Even better would be if all the summaries were also just in one page so you didn't have to click links to follow the previous meetings. Yep, thats what i want to do on this page and the linked pages https://phab.enlightenment.org/w/meetings/ :). Cheers -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
Come on, relax :) On 05/10/2018 05:50 AM, Carsten Haitzler wrote: On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz said: While I can see some summarization of meeting items on the relatively obscure https://phab.enlightenment.org/V33, which is inaccessible to anyone who has not been avidly following the mailing list archives--ie. will never be visible to any new community members--this is not quite the same as recording the minutes of a meeting. see the ticket that this was all about. it's there in the ticket itself in the body. that is where the conversation was happening so it's summarized there. https://phab.enlightenment.org/T6740 i don't see why etherpad is needed. we have plenty of tools on phab for this. no one disagreed with a wiki page. People can collaborative write that together, as a few might want to have other things noted down as others. At the end of the meeting things just end up in the wiki page :) (As Mike said :)) you were talking as if people need to have it explained to them what minutes are: "Typically for meetings where items of substance are discussed, the minutes will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes"; Yeah which is ok, as i have never ever heared from that before :) marcel already said: "But i agree in general that there should be a wiki page for monitoring contents of the meetings and some them up." ... so again. i see no reason why minutes will not be taken and recorded. Aside from the visibility issue (there should be a defined and documented page on the wiki/site where all of the minutes/logs from meetings can be found), here is an example of "good" minute-taking from a meeting that I was present in: https://github.com/servo/servo/wiki/Meeting-2015-05-18 . Note that this was a phone conference meeting, so someone was required to more or less sit out of the meeting to transcribe its contents onto an etherpad which everyone on the call was viewing during the call; since our meetings are in text form, it should be far simpler to either cut+paste notable statements or summarize them onto e.g., a http://collabedit.com/ document such as was previously suggested. i don't think we should just copy & paste the entire thing. i think there should be a summary of it like the ticket above has. if members of the meeting disagree with the summary then it can be altered etc. having to wade through an hour of irc log to know what a meeting was about is not a brilliant way of presenting information here IMHO. I think its also the place where things like this can happen at the meeting, with something like collab edit. All in all, the two of you want to see things written down and recorded, i would like to test it with collabedit.com, maybe then its not the job of one person to write down "meeting-minutes" rather than of many people which makes it easier for each. So lets leave things from the past in the past, and lets evalulate how this new approach worked on the 18th :) Greetings, bu5hm4n On Wed, May 9, 2018 at 12:14 PM Carsten Haitzler wrote: On Wed, 09 May 2018 13:58:52 + Mike Blumenkrantz said: Typically for meetings where items of substance are discussed, the minutes will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes we already did that fr the past 2 irc meetings 2 weeks ago so i see no reason this won't be the same. On Tue, May 8, 2018 at 1:26 PM Marcel Hollerbach wrote: On 05/08/2018 06:35 PM, Mike Blumenkrantz wrote: I think it's important to create a page which tracks meeting "minutes" for each meeting so that at any time people can review the contents of meetings they were unable to attend or, for newer community members, see what the community has been doing recently. I am not exactly sure what you mean by "tracks meeting 'minutes'". I would create a event in the calendar, you can import them then to your private one and use the notifications you prefer for that event. But i agree in general that there should be a wiki page for monitoring contents of the meetings and some them up. I think there can be a script for that, as conduit seems to have a API for that. Probably the easiest way to do this would be to have something like an etherpad where everyone can copy/paste/summarize things said on IRC and then copy the contents of the etherpad to the wiki after the meeting ends. There is http://collabedit.com which works without users etc. seems reasonable for me. What do you think? Greetings, bu5hm4n On Tue, May 8, 2018 at 11:32 AM Stephen Houston < smhousto...@gmail.com> wrote: Yes - We have already forgotten about so much of this. The review thread needs to be bumped and discussed more and the release thread needs to be bumped and discussed more as well. Everything has already gone back silent. On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: On 08/05/18 21:24, Marcel Hollerbach wrote: Updated version: Rathe
Re: [E-devel] RFC unforgettable weekly meetings
On 10/05/18 13:20, Carsten Haitzler wrote: > On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz > said: > >> While I can see some summarization of meeting items on the relatively >> obscure https://phab.enlightenment.org/V33, which is inaccessible to anyone >> who has not been avidly following the mailing list archives--ie. will never >> be visible to any new community members--this is not quite the same as >> recording the minutes of a meeting. > > see the ticket that this was all about. it's there in the ticket itself in the > body. that is where the conversation was happening so it's summarized there. > > https://phab.enlightenment.org/T6740 > > i don't see why etherpad is needed. we have plenty of tools on phab for this. > no one disagreed with a wiki page. > > you were talking as if people need to have it explained to them what minutes > are: > > "Typically for meetings where items of substance are discussed, the minutes > will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes"; > > marcel already said: > > "But i agree in general that there should be a wiki page for monitoring > contents of the meetings and some them up." > > ... so again. i see no reason why minutes will not be taken and recorded. > What I would like to see and I think what Mike is getting at is a wiki page either on the main wiki or somewhere on phab, which atleast lists all the links to the meeting summaries rather then just having obscure phab links to them. Even better would be if all the summaries were also just in one page so you didn't have to click links to follow the previous meetings. Cheers -- Simon Lees (Simotek)http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B signature.asc Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz said: > While I can see some summarization of meeting items on the relatively > obscure https://phab.enlightenment.org/V33, which is inaccessible to anyone > who has not been avidly following the mailing list archives--ie. will never > be visible to any new community members--this is not quite the same as > recording the minutes of a meeting. see the ticket that this was all about. it's there in the ticket itself in the body. that is where the conversation was happening so it's summarized there. https://phab.enlightenment.org/T6740 i don't see why etherpad is needed. we have plenty of tools on phab for this. no one disagreed with a wiki page. you were talking as if people need to have it explained to them what minutes are: "Typically for meetings where items of substance are discussed, the minutes will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes"; marcel already said: "But i agree in general that there should be a wiki page for monitoring contents of the meetings and some them up." ... so again. i see no reason why minutes will not be taken and recorded. > Aside from the visibility issue (there should be a defined and documented > page on the wiki/site where all of the minutes/logs from meetings can be > found), here is an example of "good" minute-taking from a meeting that I > was present in: https://github.com/servo/servo/wiki/Meeting-2015-05-18 . > Note that this was a phone conference meeting, so someone was required to > more or less sit out of the meeting to transcribe its contents onto an > etherpad which everyone on the call was viewing during the call; since our > meetings are in text form, it should be far simpler to either cut+paste > notable statements or summarize them onto e.g., a > http://collabedit.com/ document > such as was previously suggested. i don't think we should just copy & paste the entire thing. i think there should be a summary of it like the ticket above has. if members of the meeting disagree with the summary then it can be altered etc. having to wade through an hour of irc log to know what a meeting was about is not a brilliant way of presenting information here IMHO. > On Wed, May 9, 2018 at 12:14 PM Carsten Haitzler > wrote: > > > On Wed, 09 May 2018 13:58:52 + Mike Blumenkrantz > > said: > > > > > Typically for meetings where items of substance are discussed, the > > minutes > > > will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes > > > > we already did that fr the past 2 irc meetings 2 weeks ago so i see no > > reason > > this won't be the same. > > > > > On Tue, May 8, 2018 at 1:26 PM Marcel Hollerbach > > wrote: > > > > > > > > > > > On 05/08/2018 06:35 PM, Mike Blumenkrantz wrote: > > > > > I think it's important to create a page which tracks meeting > > "minutes" > > > > for > > > > > each meeting so that at any time people can review the contents of > > > > meetings > > > > > they were unable to attend or, for newer community members, see what > > the > > > > > community has been doing recently. > > > > > > > > I am not exactly sure what you mean by "tracks meeting 'minutes'". > > > > I would create a event in the calendar, you can import them then to > > your > > > > private one and use the notifications you prefer for that event. > > > > > > > > But i agree in general that there should be a wiki page for monitoring > > > > contents of the meetings and some them up. I think there can be a > > script > > > > for that, as conduit seems to have a API for that. > > > > > > > > > > > > > > Probably the easiest way to do this would be to have something like > > an > > > > > etherpad where everyone can copy/paste/summarize things said on IRC > > and > > > > > then copy the contents of the etherpad to the wiki after the meeting > > > > ends. > > > > > > > > > > > > > There is http://collabedit.com which works without users etc. seems > > > > reasonable for me. What do you think? > > > > > > > > Greetings, > > > > bu5hm4n > > > > > > > > > On Tue, May 8, 2018 at 11:32 AM Stephen Houston < > > smhousto...@gmail.com> > > > > > wrote: > > > > > > > > > >> Yes - We have already forgotten about so much of this. The review > > > > thread > > > > >> needs to be bumped and discussed more and the release thread needs > > to be > > > > >> bumped and discussed more as well. Everything has already gone back > > > > >> silent. > > > > >> > > > > >> On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: > > > > >> > > > > >>> > > > > >>> > > > > >>> On 08/05/18 21:24, Marcel Hollerbach wrote: > > > > Updated version: > > > > > > > > > Rather then having to be subscribed to something (or as well as) > > it > > > > > would be nice if something sent a meeting reminder email to this > > list > > > > > 24hrs before each meeting as well. > > > > > > > > > > > > > We can do that the first few weeks, but for the long term i would > > > > stick >
Re: [E-devel] RFC unforgettable weekly meetings
On Wed, 09 May 2018 17:17:14 + Mike Blumenkrantz wrote: > While I can see some summarization of meeting items on the relatively > obscure https://phab.enlightenment.org/V33, which is inaccessible to > anyone who has not been avidly following the mailing list Actually correction, its not accessible to anyone who is not logged into Phabricator. No account, no access, no information. Log out or use a private browsing session for conformation on access. > archives--ie. will never be visible to any new community > members--this is not quite the same as recording the minutes of a > meeting. I am more than happy to help with such, if I can get my phab account re-enabled... Requested many times falls on deaf ears, blind eyes ;) -- William L. Thomson Jr. pgpYN_Ma7W1ft.pgp Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
While I can see some summarization of meeting items on the relatively obscure https://phab.enlightenment.org/V33, which is inaccessible to anyone who has not been avidly following the mailing list archives--ie. will never be visible to any new community members--this is not quite the same as recording the minutes of a meeting. Aside from the visibility issue (there should be a defined and documented page on the wiki/site where all of the minutes/logs from meetings can be found), here is an example of "good" minute-taking from a meeting that I was present in: https://github.com/servo/servo/wiki/Meeting-2015-05-18 . Note that this was a phone conference meeting, so someone was required to more or less sit out of the meeting to transcribe its contents onto an etherpad which everyone on the call was viewing during the call; since our meetings are in text form, it should be far simpler to either cut+paste notable statements or summarize them onto e.g., a http://collabedit.com/ document such as was previously suggested. On Wed, May 9, 2018 at 12:14 PM Carsten Haitzler wrote: > On Wed, 09 May 2018 13:58:52 + Mike Blumenkrantz > said: > > > Typically for meetings where items of substance are discussed, the > minutes > > will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes > > we already did that fr the past 2 irc meetings 2 weeks ago so i see no > reason > this won't be the same. > > > On Tue, May 8, 2018 at 1:26 PM Marcel Hollerbach > wrote: > > > > > > > > On 05/08/2018 06:35 PM, Mike Blumenkrantz wrote: > > > > I think it's important to create a page which tracks meeting > "minutes" > > > for > > > > each meeting so that at any time people can review the contents of > > > meetings > > > > they were unable to attend or, for newer community members, see what > the > > > > community has been doing recently. > > > > > > I am not exactly sure what you mean by "tracks meeting 'minutes'". > > > I would create a event in the calendar, you can import them then to > your > > > private one and use the notifications you prefer for that event. > > > > > > But i agree in general that there should be a wiki page for monitoring > > > contents of the meetings and some them up. I think there can be a > script > > > for that, as conduit seems to have a API for that. > > > > > > > > > > > Probably the easiest way to do this would be to have something like > an > > > > etherpad where everyone can copy/paste/summarize things said on IRC > and > > > > then copy the contents of the etherpad to the wiki after the meeting > > > ends. > > > > > > > > > > There is http://collabedit.com which works without users etc. seems > > > reasonable for me. What do you think? > > > > > > Greetings, > > > bu5hm4n > > > > > > > On Tue, May 8, 2018 at 11:32 AM Stephen Houston < > smhousto...@gmail.com> > > > > wrote: > > > > > > > >> Yes - We have already forgotten about so much of this. The review > > > thread > > > >> needs to be bumped and discussed more and the release thread needs > to be > > > >> bumped and discussed more as well. Everything has already gone back > > > >> silent. > > > >> > > > >> On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: > > > >> > > > >>> > > > >>> > > > >>> On 08/05/18 21:24, Marcel Hollerbach wrote: > > > Updated version: > > > > > > > Rather then having to be subscribed to something (or as well as) > it > > > > would be nice if something sent a meeting reminder email to this > list > > > > 24hrs before each meeting as well. > > > > > > > > > > We can do that the first few weeks, but for the long term i would > > > stick > > > to subscribing to a group on phabricator, as everything else is a > bit > > > verbose IMO, and a few may just not be interested at all :) > > > > > > >>> > > > >>> I think it would be better to keep them, they will have an obvious > > > >>> subject line that people who are not interested can filter out > either > > > >>> automatically or manually, just like its easy to see then not pay > > > >>> attention to comments brought up about a specific patch you have no > > > >>> interest in. > > > >>> > > > >>> It also means that new developers or potential developers in a > year - > > > >>> three years time will immediately be aware that we do irc meetings. > > > >>> > > > >>> But maybe this is just the opinion of someone who has learned to > mostly > > > >>> deal with getting 10,000+ emails a month and sees an extra 2 as no > big > > > >>> issue. > > > >>> > > > >>> -- > > > >>> > > > >>> Simon Lees (Simotek)http://simotek.net > > > >>> > > > >>> Emergency Update Team keybase.io/simotek > > > >>> SUSE Linux Adelaide Australia, UTC+10:30 > > > >>> GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B > > > >>> > > > >>> > > > >>> > > > >> > > > > -- >
Re: [E-devel] RFC unforgettable weekly meetings
On Wed, 09 May 2018 13:58:52 + Mike Blumenkrantz said: > Typically for meetings where items of substance are discussed, the minutes > will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes we already did that fr the past 2 irc meetings 2 weeks ago so i see no reason this won't be the same. > On Tue, May 8, 2018 at 1:26 PM Marcel Hollerbach wrote: > > > > > On 05/08/2018 06:35 PM, Mike Blumenkrantz wrote: > > > I think it's important to create a page which tracks meeting "minutes" > > for > > > each meeting so that at any time people can review the contents of > > meetings > > > they were unable to attend or, for newer community members, see what the > > > community has been doing recently. > > > > I am not exactly sure what you mean by "tracks meeting 'minutes'". > > I would create a event in the calendar, you can import them then to your > > private one and use the notifications you prefer for that event. > > > > But i agree in general that there should be a wiki page for monitoring > > contents of the meetings and some them up. I think there can be a script > > for that, as conduit seems to have a API for that. > > > > > > > > Probably the easiest way to do this would be to have something like an > > > etherpad where everyone can copy/paste/summarize things said on IRC and > > > then copy the contents of the etherpad to the wiki after the meeting > > ends. > > > > > > > There is http://collabedit.com which works without users etc. seems > > reasonable for me. What do you think? > > > > Greetings, > > bu5hm4n > > > > > On Tue, May 8, 2018 at 11:32 AM Stephen Houston > > > wrote: > > > > > >> Yes - We have already forgotten about so much of this. The review > > thread > > >> needs to be bumped and discussed more and the release thread needs to be > > >> bumped and discussed more as well. Everything has already gone back > > >> silent. > > >> > > >> On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: > > >> > > >>> > > >>> > > >>> On 08/05/18 21:24, Marcel Hollerbach wrote: > > Updated version: > > > > > Rather then having to be subscribed to something (or as well as) it > > > would be nice if something sent a meeting reminder email to this list > > > 24hrs before each meeting as well. > > > > > > > We can do that the first few weeks, but for the long term i would > > stick > > to subscribing to a group on phabricator, as everything else is a bit > > verbose IMO, and a few may just not be interested at all :) > > > > >>> > > >>> I think it would be better to keep them, they will have an obvious > > >>> subject line that people who are not interested can filter out either > > >>> automatically or manually, just like its easy to see then not pay > > >>> attention to comments brought up about a specific patch you have no > > >>> interest in. > > >>> > > >>> It also means that new developers or potential developers in a year - > > >>> three years time will immediately be aware that we do irc meetings. > > >>> > > >>> But maybe this is just the opinion of someone who has learned to mostly > > >>> deal with getting 10,000+ emails a month and sees an extra 2 as no big > > >>> issue. > > >>> > > >>> -- > > >>> > > >>> Simon Lees (Simotek)http://simotek.net > > >>> > > >>> Emergency Update Team keybase.io/simotek > > >>> SUSE Linux Adelaide Australia, UTC+10:30 > > >>> GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B > > >>> > > >>> > > >>> > > >> > > -- > > >>> Check out the vibrant tech community on one of the world's most > > >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > >>> ___ > > >>> enlightenment-devel mailing list > > >>> enlightenment-devel@lists.sourceforge.net > > >>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > >>> > > >> > > >> > > -- > > >> Check out the vibrant tech community on one of the world's most > > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > >> ___ > > >> enlightenment-devel mailing list > > >> enlightenment-devel@lists.sourceforge.net > > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > >> > > > > > -- > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > ___ > > > enlightenment-devel mailing list > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > > > ---
Re: [E-devel] RFC unforgettable weekly meetings
Typically for meetings where items of substance are discussed, the minutes will be recorded for posterity: https://en.wikipedia.org/wiki/Minutes On Tue, May 8, 2018 at 1:26 PM Marcel Hollerbach wrote: > > On 05/08/2018 06:35 PM, Mike Blumenkrantz wrote: > > I think it's important to create a page which tracks meeting "minutes" > for > > each meeting so that at any time people can review the contents of > meetings > > they were unable to attend or, for newer community members, see what the > > community has been doing recently. > > I am not exactly sure what you mean by "tracks meeting 'minutes'". > I would create a event in the calendar, you can import them then to your > private one and use the notifications you prefer for that event. > > But i agree in general that there should be a wiki page for monitoring > contents of the meetings and some them up. I think there can be a script > for that, as conduit seems to have a API for that. > > > > > Probably the easiest way to do this would be to have something like an > > etherpad where everyone can copy/paste/summarize things said on IRC and > > then copy the contents of the etherpad to the wiki after the meeting > ends. > > > > There is http://collabedit.com which works without users etc. seems > reasonable for me. What do you think? > > Greetings, > bu5hm4n > > > On Tue, May 8, 2018 at 11:32 AM Stephen Houston > > wrote: > > > >> Yes - We have already forgotten about so much of this. The review > thread > >> needs to be bumped and discussed more and the release thread needs to be > >> bumped and discussed more as well. Everything has already gone back > >> silent. > >> > >> On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: > >> > >>> > >>> > >>> On 08/05/18 21:24, Marcel Hollerbach wrote: > Updated version: > > > Rather then having to be subscribed to something (or as well as) it > > would be nice if something sent a meeting reminder email to this list > > 24hrs before each meeting as well. > > > > We can do that the first few weeks, but for the long term i would > stick > to subscribing to a group on phabricator, as everything else is a bit > verbose IMO, and a few may just not be interested at all :) > > >>> > >>> I think it would be better to keep them, they will have an obvious > >>> subject line that people who are not interested can filter out either > >>> automatically or manually, just like its easy to see then not pay > >>> attention to comments brought up about a specific patch you have no > >>> interest in. > >>> > >>> It also means that new developers or potential developers in a year - > >>> three years time will immediately be aware that we do irc meetings. > >>> > >>> But maybe this is just the opinion of someone who has learned to mostly > >>> deal with getting 10,000+ emails a month and sees an extra 2 as no big > >>> issue. > >>> > >>> -- > >>> > >>> Simon Lees (Simotek)http://simotek.net > >>> > >>> Emergency Update Team keybase.io/simotek > >>> SUSE Linux Adelaide Australia, UTC+10:30 > >>> GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B > >>> > >>> > >>> > >> > -- > >>> Check out the vibrant tech community on one of the world's most > >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >>> ___ > >>> enlightenment-devel mailing list > >>> enlightenment-devel@lists.sourceforge.net > >>> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >>> > >> > >> > -- > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot > >> ___ > >> enlightenment-devel mailing list > >> enlightenment-devel@lists.sourceforge.net > >> https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > >> > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel >
Re: [E-devel] RFC unforgettable weekly meetings
Lets try it. here is the group you can join for getting a invite: https://phab.enlightenment.org/project/view/204/ Here is the event with the linked wiki page: https://phab.enlightenment.org/E15 Greetings, bu5hm4n On 05/09/2018 03:54 AM, Carsten Haitzler (The Rasterman) wrote: On Tue, 8 May 2018 13:54:09 +0200 Marcel Hollerbach said: I'm in on this. Already added it to my own personal calendar with notifications etc. :) Updated version: i) We do two meetings a month: 1) 1st Tuesday of each month at 8h UTC 2) 3rd Thursday of each month at 16h UTC (Times can be discussed, they are copied from https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx Christophe Sadoine) ii) We create 'Recurring Events' for each of the events on phab, there is already a committers group. I would create another group where people can join who want to get notified that a meeting is happening. iii) *Someone* is summing up what was said and concluded, those things are written into a wiki page. More answers below. On 05/08/2018 01:44 PM, Simon Lees wrote: On 08/05/18 20:16, Marcel Hollerbach wrote: Hello, It has been now over 10 days of the last meeting, we concluded that we should do them every second week and somehow already almost forgot about it. So here is another proposal that makes things more scheduled: i) We do two meetings a month: 1) 1st of each month at 8h UTC 2) 17st of each month at 16h UTC (Times can be discussed, they are copied from https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx Christophe Sadoine) ii) We create 'Recurring Events' for each of the events on phab, there is already a committers group. I would create another group where people can join who want to get notified that a meeting is happening. iii) *Someone* is summing up what was said and concluded, those things are written into a wiki page. We should announce the meetings regularly, and haven't does that for this week, maybe we should just start on the 17th? What do you think about it? Greetings, bu5hm4n To make it easier with peoples schedules I think picking a day (or maybe 2 different days if that works better would be easier to remember) Like the first and Third Monday of each month for example, the 1st and 17th will fall on weekends / friday nights at some point and people wont want to join. Good point. Rather then having to be subscribed to something (or as well as) it would be nice if something sent a meeting reminder email to this list 24hrs before each meeting as well. We can do that the first few weeks, but for the long term i would stick to subscribing to a group on phabricator, as everything else is a bit verbose IMO, and a few may just not be interested at all :) Greetings, bu5hm4n -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On Tue, 8 May 2018 13:54:09 +0200 Marcel Hollerbach said: I'm in on this. Already added it to my own personal calendar with notifications etc. :) > Updated version: > > i) We do two meetings a month: > 1) 1st Tuesday of each month at 8h UTC > 2) 3rd Thursday of each month at 16h UTC > (Times can be discussed, they are copied from > https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx > Christophe Sadoine) > > ii) We create 'Recurring Events' for each of the events on phab, there > is already a committers group. I would create another group where people > can join who want to get notified that a meeting is happening. > > iii) *Someone* is summing up what was said and concluded, those things > are written into a wiki page. > > More answers below. > > On 05/08/2018 01:44 PM, Simon Lees wrote: > > On 08/05/18 20:16, Marcel Hollerbach wrote: > >> Hello, > >> > >> It has been now over 10 days of the last meeting, we concluded that we > >> should do them every second week and somehow already almost forgot about > >> it. > >> > >> So here is another proposal that makes things more scheduled: > >> > >> i) We do two meetings a month: > >> 1) 1st of each month at 8h UTC > >> 2) 17st of each month at 16h UTC > >> (Times can be discussed, they are copied from > >> https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx > >> Christophe Sadoine) > >> > >> ii) We create 'Recurring Events' for each of the events on phab, there > >> is already a committers group. I would create another group where people > >> can join who want to get notified that a meeting is happening. > >> > >> iii) *Someone* is summing up what was said and concluded, those things > >> are written into a wiki page. > >> > >> We should announce the meetings regularly, and haven't does that for > >> this week, maybe we should just start on the 17th? > >> > >> What do you think about it? > >> > >> Greetings, > >> bu5hm4n > >> > > > > To make it easier with peoples schedules I think picking a day (or maybe > > 2 different days if that works better would be easier to remember) Like > > the first and Third Monday of each month for example, the 1st and 17th > > will fall on weekends / friday nights at some point and people wont want > > to join. > > > > Good point. > > > Rather then having to be subscribed to something (or as well as) it > > would be nice if something sent a meeting reminder email to this list > > 24hrs before each meeting as well. > > > > We can do that the first few weeks, but for the long term i would stick > to subscribing to a group on phabricator, as everything else is a bit > verbose IMO, and a few may just not be interested at all :) > > Greetings, > bu5hm4n > > > > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > > > > > > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On Tue, 8 May 2018 19:26:16 +0200 Marcel Hollerbach wrote: > On 05/08/2018 06:35 PM, Mike Blumenkrantz wrote: > > I think it's important to create a page which tracks meeting > > "minutes" for each meeting so that at any time people can review > > the contents of meetings they were unable to attend or, for newer > > community members, see what the community has been doing recently. > > I am not exactly sure what you mean by "tracks meeting 'minutes'". Likely a page, list that has links to each meetings minutes/summary. This also includes a full log, which cannot really hurt either. https://wiki.gentoo.org/wiki/Project:Council/Meeting_logs This seems like a bit overkill, but its also for a different purpose. Foundations tend to need to report more details and prettier for donors. https://wiki.gentoo.org/wiki/Category:Foundation_Meetings That does show a meeting template like I was talking about before. -- William L. Thomson Jr. pgpn9bqthUwZK.pgp Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On Tue, 8 May 2018 21:31:22 +0930 Simon Lees wrote: > On 08/05/18 21:24, Marcel Hollerbach wrote: > > Updated version: > > > >> Rather then having to be subscribed to something (or as well as) it > >> would be nice if something sent a meeting reminder email to this > >> list 24hrs before each meeting as well. > >> > > > > We can do that the first few weeks, but for the long term i would > > stick to subscribing to a group on phabricator, as everything else > > is a bit verbose IMO, and a few may just not be interested at all :) > > > > I think it would be better to keep them, they will have an obvious > subject line that people who are not interested can filter out either > automatically or manually, just like its easy to see then not pay > attention to comments brought up about a specific patch you have no > interest in. Sounds like a job for cron. Generic email reminder emailed out on interval. Maybe just 1 to this list vs to each individual. I recall an automated email already being sent on like coverage or something. -- William L. Thomson Jr. pgppHgmn9P2Nt.pgp Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On 05/08/2018 06:35 PM, Mike Blumenkrantz wrote: I think it's important to create a page which tracks meeting "minutes" for each meeting so that at any time people can review the contents of meetings they were unable to attend or, for newer community members, see what the community has been doing recently. I am not exactly sure what you mean by "tracks meeting 'minutes'". I would create a event in the calendar, you can import them then to your private one and use the notifications you prefer for that event. But i agree in general that there should be a wiki page for monitoring contents of the meetings and some them up. I think there can be a script for that, as conduit seems to have a API for that. Probably the easiest way to do this would be to have something like an etherpad where everyone can copy/paste/summarize things said on IRC and then copy the contents of the etherpad to the wiki after the meeting ends. There is http://collabedit.com which works without users etc. seems reasonable for me. What do you think? Greetings, bu5hm4n On Tue, May 8, 2018 at 11:32 AM Stephen Houston wrote: Yes - We have already forgotten about so much of this. The review thread needs to be bumped and discussed more and the release thread needs to be bumped and discussed more as well. Everything has already gone back silent. On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: On 08/05/18 21:24, Marcel Hollerbach wrote: Updated version: Rather then having to be subscribed to something (or as well as) it would be nice if something sent a meeting reminder email to this list 24hrs before each meeting as well. We can do that the first few weeks, but for the long term i would stick to subscribing to a group on phabricator, as everything else is a bit verbose IMO, and a few may just not be interested at all :) I think it would be better to keep them, they will have an obvious subject line that people who are not interested can filter out either automatically or manually, just like its easy to see then not pay attention to comments brought up about a specific patch you have no interest in. It also means that new developers or potential developers in a year - three years time will immediately be aware that we do irc meetings. But maybe this is just the opinion of someone who has learned to mostly deal with getting 10,000+ emails a month and sees an extra 2 as no big issue. -- Simon Lees (Simotek)http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
True, maybe things are getting better if we pick such things up each meeting. However, this thread is about the structure, can you bump the other two ? :) On 05/08/2018 05:31 PM, Stephen Houston wrote: Yes - We have already forgotten about so much of this. The review thread needs to be bumped and discussed more and the release thread needs to be bumped and discussed more as well. Everything has already gone back silent. On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: On 08/05/18 21:24, Marcel Hollerbach wrote: Updated version: Rather then having to be subscribed to something (or as well as) it would be nice if something sent a meeting reminder email to this list 24hrs before each meeting as well. We can do that the first few weeks, but for the long term i would stick to subscribing to a group on phabricator, as everything else is a bit verbose IMO, and a few may just not be interested at all :) I think it would be better to keep them, they will have an obvious subject line that people who are not interested can filter out either automatically or manually, just like its easy to see then not pay attention to comments brought up about a specific patch you have no interest in. It also means that new developers or potential developers in a year - three years time will immediately be aware that we do irc meetings. But maybe this is just the opinion of someone who has learned to mostly deal with getting 10,000+ emails a month and sees an extra 2 as no big issue. -- Simon Lees (Simotek)http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
I think it's important to create a page which tracks meeting "minutes" for each meeting so that at any time people can review the contents of meetings they were unable to attend or, for newer community members, see what the community has been doing recently. Probably the easiest way to do this would be to have something like an etherpad where everyone can copy/paste/summarize things said on IRC and then copy the contents of the etherpad to the wiki after the meeting ends. On Tue, May 8, 2018 at 11:32 AM Stephen Houston wrote: > Yes - We have already forgotten about so much of this. The review thread > needs to be bumped and discussed more and the release thread needs to be > bumped and discussed more as well. Everything has already gone back > silent. > > On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: > > > > > > > On 08/05/18 21:24, Marcel Hollerbach wrote: > > > Updated version: > > > > > >> Rather then having to be subscribed to something (or as well as) it > > >> would be nice if something sent a meeting reminder email to this list > > >> 24hrs before each meeting as well. > > >> > > > > > > We can do that the first few weeks, but for the long term i would stick > > > to subscribing to a group on phabricator, as everything else is a bit > > > verbose IMO, and a few may just not be interested at all :) > > > > > > > I think it would be better to keep them, they will have an obvious > > subject line that people who are not interested can filter out either > > automatically or manually, just like its easy to see then not pay > > attention to comments brought up about a specific patch you have no > > interest in. > > > > It also means that new developers or potential developers in a year - > > three years time will immediately be aware that we do irc meetings. > > > > But maybe this is just the opinion of someone who has learned to mostly > > deal with getting 10,000+ emails a month and sees an extra 2 as no big > > issue. > > > > -- > > > > Simon Lees (Simotek)http://simotek.net > > > > Emergency Update Team keybase.io/simotek > > SUSE Linux Adelaide Australia, UTC+10:30 > > GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B > > > > > > > -- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
Yes - We have already forgotten about so much of this. The review thread needs to be bumped and discussed more and the release thread needs to be bumped and discussed more as well. Everything has already gone back silent. On Tue, May 8, 2018 at 7:02 AM Simon Lees wrote: > > > On 08/05/18 21:24, Marcel Hollerbach wrote: > > Updated version: > > > >> Rather then having to be subscribed to something (or as well as) it > >> would be nice if something sent a meeting reminder email to this list > >> 24hrs before each meeting as well. > >> > > > > We can do that the first few weeks, but for the long term i would stick > > to subscribing to a group on phabricator, as everything else is a bit > > verbose IMO, and a few may just not be interested at all :) > > > > I think it would be better to keep them, they will have an obvious > subject line that people who are not interested can filter out either > automatically or manually, just like its easy to see then not pay > attention to comments brought up about a specific patch you have no > interest in. > > It also means that new developers or potential developers in a year - > three years time will immediately be aware that we do irc meetings. > > But maybe this is just the opinion of someone who has learned to mostly > deal with getting 10,000+ emails a month and sees an extra 2 as no big > issue. > > -- > > Simon Lees (Simotek)http://simotek.net > > Emergency Update Team keybase.io/simotek > SUSE Linux Adelaide Australia, UTC+10:30 > GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B > > > -- > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On 08/05/18 21:24, Marcel Hollerbach wrote: > Updated version: > >> Rather then having to be subscribed to something (or as well as) it >> would be nice if something sent a meeting reminder email to this list >> 24hrs before each meeting as well. >> > > We can do that the first few weeks, but for the long term i would stick > to subscribing to a group on phabricator, as everything else is a bit > verbose IMO, and a few may just not be interested at all :) > I think it would be better to keep them, they will have an obvious subject line that people who are not interested can filter out either automatically or manually, just like its easy to see then not pay attention to comments brought up about a specific patch you have no interest in. It also means that new developers or potential developers in a year - three years time will immediately be aware that we do irc meetings. But maybe this is just the opinion of someone who has learned to mostly deal with getting 10,000+ emails a month and sees an extra 2 as no big issue. -- Simon Lees (Simotek)http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B signature.asc Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
Updated version: i) We do two meetings a month: 1) 1st Tuesday of each month at 8h UTC 2) 3rd Thursday of each month at 16h UTC (Times can be discussed, they are copied from https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx Christophe Sadoine) ii) We create 'Recurring Events' for each of the events on phab, there is already a committers group. I would create another group where people can join who want to get notified that a meeting is happening. iii) *Someone* is summing up what was said and concluded, those things are written into a wiki page. More answers below. On 05/08/2018 01:44 PM, Simon Lees wrote: On 08/05/18 20:16, Marcel Hollerbach wrote: Hello, It has been now over 10 days of the last meeting, we concluded that we should do them every second week and somehow already almost forgot about it. So here is another proposal that makes things more scheduled: i) We do two meetings a month: 1) 1st of each month at 8h UTC 2) 17st of each month at 16h UTC (Times can be discussed, they are copied from https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx Christophe Sadoine) ii) We create 'Recurring Events' for each of the events on phab, there is already a committers group. I would create another group where people can join who want to get notified that a meeting is happening. iii) *Someone* is summing up what was said and concluded, those things are written into a wiki page. We should announce the meetings regularly, and haven't does that for this week, maybe we should just start on the 17th? What do you think about it? Greetings, bu5hm4n To make it easier with peoples schedules I think picking a day (or maybe 2 different days if that works better would be easier to remember) Like the first and Third Monday of each month for example, the 1st and 17th will fall on weekends / friday nights at some point and people wont want to join. Good point. Rather then having to be subscribed to something (or as well as) it would be nice if something sent a meeting reminder email to this list 24hrs before each meeting as well. We can do that the first few weeks, but for the long term i would stick to subscribing to a group on phabricator, as everything else is a bit verbose IMO, and a few may just not be interested at all :) Greetings, bu5hm4n -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
On 08/05/18 20:16, Marcel Hollerbach wrote: > Hello, > > It has been now over 10 days of the last meeting, we concluded that we > should do them every second week and somehow already almost forgot about > it. > > So here is another proposal that makes things more scheduled: > > i) We do two meetings a month: > 1) 1st of each month at 8h UTC > 2) 17st of each month at 16h UTC > (Times can be discussed, they are copied from > https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx > Christophe Sadoine) > > ii) We create 'Recurring Events' for each of the events on phab, there > is already a committers group. I would create another group where people > can join who want to get notified that a meeting is happening. > > iii) *Someone* is summing up what was said and concluded, those things > are written into a wiki page. > > We should announce the meetings regularly, and haven't does that for > this week, maybe we should just start on the 17th? > > What do you think about it? > > Greetings, > bu5hm4n > To make it easier with peoples schedules I think picking a day (or maybe 2 different days if that works better would be easier to remember) Like the first and Third Monday of each month for example, the 1st and 17th will fall on weekends / friday nights at some point and people wont want to join. Rather then having to be subscribed to something (or as well as) it would be nice if something sent a meeting reminder email to this list 24hrs before each meeting as well. -- Simon Lees (Simotek)http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B signature.asc Description: OpenPGP digital signature -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] RFC unforgettable weekly meetings
Hello, It has been now over 10 days of the last meeting, we concluded that we should do them every second week and somehow already almost forgot about it. So here is another proposal that makes things more scheduled: i) We do two meetings a month: 1) 1st of each month at 8h UTC 2) 17st of each month at 16h UTC (Times can be discussed, they are copied from https://wiki.blender.org/index.php/Dev:Doc/Contact#Weekly_Meetings thx Christophe Sadoine) ii) We create 'Recurring Events' for each of the events on phab, there is already a committers group. I would create another group where people can join who want to get notified that a meeting is happening. iii) *Someone* is summing up what was said and concluded, those things are written into a wiki page. We should announce the meetings regularly, and haven't does that for this week, maybe we should just start on the 17th? What do you think about it? Greetings, bu5hm4n On 03/09/2018 02:10 PM, Jonathan Aquilina wrote: There is another option which Allows text and voice communications and that is discord. Thoughts on that? Sent from my iPhone On 09 Mar 2018, at 10:53, Simon Lees wrote: Slack is now in the process of killing there irc bridge so this won't work for much longer, goodbye slack. (The bots are terrible you have no idea who's actually active in the other chat room). On 09/03/18 20:07, Jérémy Zurcher wrote: smack slack !! https://get.slack.help/hc/en-us/articles/201727913-Connect-to-Slack-over-IRC-and-XMPP long life to irc clients On Friday 09 March 2018 10:08, Jonathan Aquilina wrote : Hi Stefan you forgot there is slack and can speak in the channel on Irc that way if we have the bot there as well they can join us through slack Sent from my iPhone On 09 Mar 2018, at 10:03, Stefan Schmidt wrote: Hello. On 03/08/2018 06:40 PM, William L. Thomson Jr. wrote: One thing I have seen be of benefit in other communities is having regular meetings. It was definitely beneficial to Gentoo Java Team, long ago. This some what helped create a team, and definitely helped keep people on the same page, helped with communication, etc. When meetings ended, so did the team over time. They helped make the team and broke it... Does the E developer community ever meet beyond like EDD? Like regular monthly meetings in IRC or other? No we don't and I think it is a good idea you brought up here. I think we should try it out and see how it flies for us. I would propose IRC as medium (already heavily in use, suitable for many attendees even if just lurking around, video calls might be awkward and problematic with many attendees) I would also propose it to be bi-weekly. That misses the nice regularity of weekly meetings, but I think that might be a bit to often. Maybe I am wrong and weeklies would be better. Hard to say. Finding the right time slot is problematic though. As far as I see it we might have attendance from US west and east coast, Europe as well as Asia. What should we do about it? regards Stefan Schmidt -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel --- Hell'O from Yverdoom Jérémy (jeyzu) -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -- Simon Lees (Simotek)http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B -- Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel -
