Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread The Rasterman
On Thu, 01 Mar 2018 19:28:15 + Stephen Houston said: Hi! So I was busy with some work and didn't want jump into this in the middle. I also allowed for some feedback from others too. I've read over some of these, and I actually have little to say about the feedback

Re: [E-devel] Ecore - Efl.Loop + Task + Thread + App + Appthread + Exe

2018-03-05 Thread Gustavo Sverzut Barbieri
On Sat, Mar 3, 2018 at 2:02 AM, Carsten Haitzler wrote: > I just pushed: > > eb0b826776b60e0d97218242a5c285d146fb6f3b > > https://git.enlightenment.org/core/efl.git/commit/?id=1bdd9e4dd15fc27da43b50fd29bfb1b0b30ef6bd > > I wrote up a high level design document and

[E-devel] Weekly news from the automated build and QA front

2018-03-05 Thread Stefan Schmidt
Hello. Summary: o The server is coming up to speed again slowly after our hardware problems o No new Coverity results yet, hopefully next week This should give everyone an overview over what has happened in the last week on the QA front. The numbers in parentheses reflect the values from last

Re: [E-devel] [EGIT] [core/efl] master 01/03: efl loop promises - cleare out promise data to null

2018-03-05 Thread Gustavo Sverzut Barbieri
On Sat, Mar 3, 2018 at 6:01 AM, Carsten Haitzler wrote: > raster pushed a commit to branch master. > > http://git.enlightenment.org/core/efl.git/commit/?id=d80ef6d7a98e0cb3ceb995573c58d1df965639e4 > > commit d80ef6d7a98e0cb3ceb995573c58d1df965639e4 > Author: Carsten Haitzler

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread William L. Thomson Jr.
On Mon, 5 Mar 2018 20:57:17 +0900 Carsten Haitzler (The Rasterman) wrote: > > People who do the work get to call the shots. That is a fine balance. I am not really a fan of say ignoring users wishes or others because of who is doing the work and doing it their way vs whats

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread Stefan Schmidt
Hello. I snipped away a lot of text here to make it easier to follow. If you feel I quoted out of context let me know. On 03/05/2018 12:57 PM, Carsten Haitzler (The Rasterman) wrote: > 1. Code reverting. > > I take API breaks seriously. An API break shouldn't happen. It should get > caught as

Re: [E-devel] Donations

2018-03-05 Thread Cedric Bail
On March 4, 2018 9:27 AM, William L. Thomson Jr. wrote: > On Fri, 2 Mar 2018 21:33:17 +0100 > Vincent Torri vincent.to...@gmail.com wrote: > > Hello > > > > The « Enlighenment.fr » association aims to help all the actions > > which are involved in the development

Re: [E-devel] [EGIT] [core/efl] master 01/03: efl loop promises - cleare out promise data to null

2018-03-05 Thread Cedric Bail
On March 5, 2018 5:44 AM, Gustavo Sverzut Barbieri wrote: > On Sat, Mar 3, 2018 at 6:01 AM, Carsten Haitzler ras...@rasterman.com wrote: > > > raster pushed a commit to branch master. > > > >

[E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread Stephen Houston
I've been pondering writing this email for some time now. As others have mentioned - our community has been trending downwards. Work from Samsung aside, and those that use E/EFL through Samsung's work -- The developer and user base has been getting smaller and smaller. That is regular members

Re: [E-devel] Ecore - Efl.Loop + Task + Thread + App + Appthread + Exe

2018-03-05 Thread Cedric Bail
On March 5, 2018 6:00 AM, Gustavo Sverzut Barbieri wrote: > Well, I already mentioned this to you in irc, but replying here just > to make my point: > > I think the design is upside down, trying to make life easier at some > point resulted in messy at the other side. > >

Re: [E-devel] Donations

2018-03-05 Thread William L. Thomson Jr.
On Mon, 05 Mar 2018 14:15:03 -0500 Cedric Bail wrote: > On March 4, 2018 9:27 AM, William L. Thomson Jr. > wrote: > > On Fri, 2 Mar 2018 21:33:17 +0100 > > Vincent Torri vincent.to...@gmail.com wrote: > > > Hello > > > > > > The « Enlighenment.fr

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread William L. Thomson Jr.
On Tue, 6 Mar 2018 10:55:36 +1030 Simon Lees wrote: > On 06/03/18 03:56, Stefan Schmidt wrote: > > Hello. > > > > I snipped away a lot of text here to make it easier to follow. If > > you feel I quoted out of context let me know. > > > > On 03/05/2018 12:57 PM, Carsten Haitzler

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread Simon Lees
On Tuesday, 6 March 2018 02:18:02 ACDT, William L. Thomson Jr. wrote: > On Mon, 5 Mar 2018 20:57:17 +0900 > Carsten Haitzler (The Rasterman) wrote: >> >> People who do the work get to call the shots. >> If we made everything code-reviewed ala phab, I think it'd be far >>

Re: [E-devel] Donations

2018-03-05 Thread William L. Thomson Jr.
On Mon, 5 Mar 2018 15:20:36 -0500 "William L. Thomson Jr." wrote: > > Why I provided information on Gnome as well. Just realized I omitted Gnome information Gnome seems to be ~$250k-$500k https://www.gnome.org/foundation/reports/ -- William L. Thomson Jr.

Re: [E-devel] Donations

2018-03-05 Thread Vincent Torri
On Mon, Mar 5, 2018 at 9:20 PM, William L. Thomson Jr. wrote: > On Mon, 05 Mar 2018 14:15:03 -0500 > Cedric Bail wrote: > >> On March 4, 2018 9:27 AM, William L. Thomson Jr. >> wrote: >> > On Fri, 2 Mar 2018 21:33:17

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread Simon Lees
On 06/03/18 03:56, Stefan Schmidt wrote: > Hello. > > I snipped away a lot of text here to make it easier to follow. If you feel I > quoted out of context let me know. > > On 03/05/2018 12:57 PM, Carsten Haitzler (The Rasterman) wrote: >> 1. Code reverting. >> >> I take API breaks seriously.

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread Christophe Sadoine
On 6 March 2018 at 10:07, William L. Thomson Jr. wrote: > On Tue, 6 Mar 2018 10:55:36 +1030 > Simon Lees wrote: > >> On 06/03/18 03:56, Stefan Schmidt wrote: >> > Hello. >> > >> > I snipped away a lot of text here to make it easier to follow. If >> >

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread Simon Lees
On 06/03/18 15:50, jaquilina wrote: > Hi simon, > > I think what you are talking about is gerrit code review. I know > Libreoffice use it and for them I think you need to have 3 reviewers > before the code is committed as well the code gets compiled and built as > well to ensure it works. > >

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread The Rasterman
On Tue, 6 Mar 2018 15:01:23 +1030 Simon Lees said: > > > On 06/03/18 12:51, Christophe Sadoine wrote: > > Then, it would be great if there was a tool to detect an api/theme > > break... and additions of api? > > I think a theme break tool is possible and should be done, not

Re: [E-devel] [EGIT] [core/efl] master 01/03: efl loop promises - cleare out promise data to null

2018-03-05 Thread The Rasterman
On Mon, 5 Mar 2018 10:44:09 -0300 Gustavo Sverzut Barbieri said: > On Sat, Mar 3, 2018 at 6:01 AM, Carsten Haitzler wrote: > > raster pushed a commit to branch master. > > > >

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread Simon Lees
On 06/03/18 12:51, Christophe Sadoine wrote: > Then, it would be great if there was a tool to detect an api/theme > break... and additions of api? > I think a theme break tool is possible and should be done, not sure > about the api. > There are API break tools available, currently they

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread Jérémy Zurcher
Rust uses github bot to post commits after testing thus ensure a good state master branch. https://github.com/barosl/homu https://www.youtube.com/watch?v=dIageYT0Vgg On Tuesday 06 March 2018 17:01, Simon Lees wrote : > > > On 06/03/18 15:50, jaquilina wrote: > > Hi simon, > > > > I think

Re: [E-devel] Current State and Future Direction of E/EFL

2018-03-05 Thread jaquilina
Hi simon, I think what you are talking about is gerrit code review. I know Libreoffice use it and for them I think you need to have 3 reviewers before the code is committed as well the code gets compiled and built as well to ensure it works.