Hello,
I will handle the first tech meeting tomorrow, as preview. After several considerations, I will be trying “livecoding.tv” (no idea if this is worst or better than twitch… and I’m not very happy with the fact that this is a “tv format” and not a “conversation format”, but well, we’ll see how it goes, maybe we’ll need to review this later). Subject of meeting tomorrow is a general overview about current work on PharoVM, so prepare your questions, and see you there! cheers, Esteban |
Ah yes, I forget the “small detail” of linking my channel :)
(I never tried, so this can fail ;) cheers, Esteban
|
I noticed only in a side conversation recently (rather than an
announcement, did I miss something?) that the change of development process to now just submit slices to inbox and configurations get sorted later (which makes things simpler - but I wonder how configurations are then maintained. Manually would seem susceible to error is fixes being dropped - so could we get an update of development process end to end comparing bug-fixing versus feature development. If too late notice, then could it be lined up for subsequent meeting? cheers -ben On Mon, Sep 26, 2016 at 10:42 PM, Esteban Lorenzano <[hidden email]> wrote: > Ah yes, I forget the “small detail” of linking my channel :) > > https://www.livecoding.tv/estebanlm/ > > (I never tried, so this can fail ;) > > cheers, > Esteban > > On 26 Sep 2016, at 16:40, Esteban Lorenzano <[hidden email]> wrote: > > Hello, > > I will handle the first tech meeting tomorrow, as preview. > After several considerations, I will be trying “livecoding.tv” (no idea if > this is worst or better than twitch… and I’m not very happy with the fact > that this is a “tv format” and not a “conversation format”, but well, we’ll > see how it goes, maybe we’ll need to review this later). > > Subject of meeting tomorrow is a general overview about current work on > PharoVM, so prepare your questions, and see you there! > > cheers, > Esteban > > |
> I noticed only in a side conversation recently (rather than an > announcement, did I miss something?) that the change of development > process to now just submit slices to inbox and configurations get > sorted later (which makes things simpler - but I wonder how > configurations are then maintained. Manually would seem susceible to > error is fixes being dropped - so could we get an update of > development process end to end comparing bug-fixing versus feature > development. If too late notice, then could it be lined up for > subsequent meeting? Hi ben People must maintain their configuration. Now for external projects we do not want deadlock to move so we decided that we publish changes and that the maintainers of external projects can just merge back and continue to propose their change using configurations. Is it clearer? Stef |
In reply to this post by EstebanLM
Hi,
Since I failed to configure the thing correctly (and then streaming breaks after some minutes), we will handle the meeting using discord. This has the advantage that we can all talk, so my idea of having a conversation will work better (ideal world would be to mix both, but for now, this has to work). Here the discord link: cheers, Esteban
|
looks like invite expired, new one:
Esteban
|
Free forum by Nabble | Edit this page |