Re: [E-devel] Goodbye
Hey I am sorry for losing chance working with you any more. I have loved your elegant words and lines in the EFL world. Thank you for having that kind of delight. I hope you find your own great way leading to happiness. Good luck and God bless you! Sincerely Shinwoo Kim 2019년 2월 19일 (화) 오전 11:25에 Hermet Park 님이 작성: > Derek, > > Though it's shame that your're leaving the community, > But I believe you have a better opportunity for your way. > > Thanks for your huge contribution for years. > > Good Luck! > > Best Regards, > > On Sat, Feb 16, 2019 at 12:48 AM Stephen Houston > wrote: > > > Thank you for all of your valuable contributions. It was a privilege to > > work with you and get to know you. Best of luck in your future > endeavors! > > > > Stephen > > > > On Thu, Feb 14, 2019 at 10:00 PM Derek Foreman < > > derek.foreman.sams...@gmail.com> wrote: > > > > > As some of you already know, today is my last day working for Samsung, > > and > > > I no longer have a financial incentive to contribute to EFL. > > > > > > One of my primary reasons for leaving this position is that it was tied > > to > > > a continued requirement to work on EFL, and I've grown weary of doing > > that, > > > so I won't be lingering as a community developer. > > > > > > Over the years there have been times when I've felt EFL was on the cusp > > of > > > outgrowing its hobby project roots and making a shift towards grown-up > > > standards (incorporating peer review, CI, a push for better > > documentation), > > > followed by events that felt like major setbacks on that path. Some > days > > > it felt like we were reducing the insurmountable mountain of technical > > > debt, and other days hopelessly watching it increase. > > > > > > EFL is currently in a situation where leadership is frequently at odds > > with > > > the majority of contributors, and this leads to developers finding > > > themselves worrying that work they've been paid to do (and maybe > > sometimes > > > have even done well) will be unilaterally reverted, possibly with > threats > > > of commit right revocation. This makes contributing pointlessly > > stressful, > > > and drives developers away. > > > > > > I hope I've left my small corners of the project a little better than I > > > found them, and I thank you all for an opportunity to contribute. I've > > met > > > some excellent people in my time here, and hope to keep in touch. I'll > > > still be around on all the regular IRC servers, feel free to contact > me*. > > > > > > Best of luck, > > > Derek > > > > > > * Just not about EFL. Ever. Seriously. > > > > > > ___ > > > enlightenment-devel mailing list > > > enlightenment-devel@lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > > -- > Regards, Hermet > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Goodbye
Derek, Though it's shame that your're leaving the community, But I believe you have a better opportunity for your way. Thanks for your huge contribution for years. Good Luck! Best Regards, On Sat, Feb 16, 2019 at 12:48 AM Stephen Houston wrote: > Thank you for all of your valuable contributions. It was a privilege to > work with you and get to know you. Best of luck in your future endeavors! > > Stephen > > On Thu, Feb 14, 2019 at 10:00 PM Derek Foreman < > derek.foreman.sams...@gmail.com> wrote: > > > As some of you already know, today is my last day working for Samsung, > and > > I no longer have a financial incentive to contribute to EFL. > > > > One of my primary reasons for leaving this position is that it was tied > to > > a continued requirement to work on EFL, and I've grown weary of doing > that, > > so I won't be lingering as a community developer. > > > > Over the years there have been times when I've felt EFL was on the cusp > of > > outgrowing its hobby project roots and making a shift towards grown-up > > standards (incorporating peer review, CI, a push for better > documentation), > > followed by events that felt like major setbacks on that path. Some days > > it felt like we were reducing the insurmountable mountain of technical > > debt, and other days hopelessly watching it increase. > > > > EFL is currently in a situation where leadership is frequently at odds > with > > the majority of contributors, and this leads to developers finding > > themselves worrying that work they've been paid to do (and maybe > sometimes > > have even done well) will be unilaterally reverted, possibly with threats > > of commit right revocation. This makes contributing pointlessly > stressful, > > and drives developers away. > > > > I hope I've left my small corners of the project a little better than I > > found them, and I thank you all for an opportunity to contribute. I've > met > > some excellent people in my time here, and hope to keep in touch. I'll > > still be around on all the regular IRC servers, feel free to contact me*. > > > > Best of luck, > > Derek > > > > * Just not about EFL. Ever. Seriously. > > > > ___ > > enlightenment-devel mailing list > > enlightenment-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > > > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > -- Regards, Hermet ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] phab down ?
Also the website is down from at least 10 hours Il giorno lun 18 feb 2019 alle ore 07:59 Vincent Torri < vincent.to...@gmail.com> ha scritto: > hello > > i can't use arc diff and when loading a phab diff, i get an error > > Vincent > > > ___ > enlightenment-devel mailing list > enlightenment-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/enlightenment-devel > ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
On Mon, 18 Feb 2019 09:15:06 + Jonathan Aquilina said: > Hi Raster, > > What about those end users that might want more bleeding edge stuff to test > etc? Currently how often are new tarballs generated prior to a stable release? git master. why do they need bleeding edge tarballs? > Regards, > Jonathan > > On 18/02/2019, 09:34, "Carsten Haitzler" wrote: > > On Mon, 18 Feb 2019 06:07:18 + Jonathan Aquilina > said: > > > Morning Simon, > > > > What I am thinking is the master branch would have the weekly releases > > for developers and stable releases would be once a month. > > why weekly releases? that's not going to have any release PROCESS done > other than "make distcheck" or "ninja dist" - i don't see any stabilization > work or QA being done beyond that (it won't be sustainable at that rate > without basically no QA). at that point we have git master itself - so anyone > interested in such things can just use git master. > > > What do you think about this? > > > > Regards, > > Jonathan > > > > -Original Message- > > From: Simon Lees > > Sent: 17 February 2019 23:16 > > To: enlightenment-devel@lists.sourceforge.net > > Subject: Re: [E-devel] 1.22 schedule proposal - updated > > > > > > > > On 16/02/2019 20:24, Jonathan Aquilina wrote: > > > Hi Simon, > > > > > > My idea for that is more for developers to have more frequent > > > snapshots granted there is the repository that one can pull from but > > > that will always be the latest commits you will be pulling from the > > > repo. > > > > > But these snapshots would be different, most developers are following > > the master branch rather then the 1.22 branch that we use for doing > > point releases > > > > -- > > > > 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 > > > > > > ___ > > 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 > > > -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
On 18/02/2019 19:45, Jonathan Aquilina wrote: > Hi Raster, > > What about those end users that might want more bleeding edge stuff to test > etc? Currently how often are new tarballs generated prior to a stable release? > > Regards, > Jonathan Regularly once we get to the Alpha / Beta stage but they are tagged as 1.22.0-alpha1 / 1.22.0- beta1, before 1.22.0 is released. Theyll generally be once a week leading upto the next release. But we haven't done them during the development period as they won't be anymore stable then just running git master which for regularly updating users is easier anyway. -- 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 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
Hi Raster, What about those end users that might want more bleeding edge stuff to test etc? Currently how often are new tarballs generated prior to a stable release? Regards, Jonathan On 18/02/2019, 09:34, "Carsten Haitzler" wrote: On Mon, 18 Feb 2019 06:07:18 + Jonathan Aquilina said: > Morning Simon, > > What I am thinking is the master branch would have the weekly releases for > developers and stable releases would be once a month. why weekly releases? that's not going to have any release PROCESS done other than "make distcheck" or "ninja dist" - i don't see any stabilization work or QA being done beyond that (it won't be sustainable at that rate without basically no QA). at that point we have git master itself - so anyone interested in such things can just use git master. > What do you think about this? > > Regards, > Jonathan > > -Original Message- > From: Simon Lees > Sent: 17 February 2019 23:16 > To: enlightenment-devel@lists.sourceforge.net > Subject: Re: [E-devel] 1.22 schedule proposal - updated > > > > On 16/02/2019 20:24, Jonathan Aquilina wrote: > > Hi Simon, > > > > My idea for that is more for developers to have more frequent snapshots > > granted there is the repository that one can pull from but that will always > > be the latest commits you will be pulling from the repo. > > > But these snapshots would be different, most developers are following the > master branch rather then the 1.22 branch that we use for doing point releases > > -- > > 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 > > > ___ > 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 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
On Mon, 18 Feb 2019 06:07:18 + Jonathan Aquilina said: > Morning Simon, > > What I am thinking is the master branch would have the weekly releases for > developers and stable releases would be once a month. why weekly releases? that's not going to have any release PROCESS done other than "make distcheck" or "ninja dist" - i don't see any stabilization work or QA being done beyond that (it won't be sustainable at that rate without basically no QA). at that point we have git master itself - so anyone interested in such things can just use git master. > What do you think about this? > > Regards, > Jonathan > > -Original Message- > From: Simon Lees > Sent: 17 February 2019 23:16 > To: enlightenment-devel@lists.sourceforge.net > Subject: Re: [E-devel] 1.22 schedule proposal - updated > > > > On 16/02/2019 20:24, Jonathan Aquilina wrote: > > Hi Simon, > > > > My idea for that is more for developers to have more frequent snapshots > > granted there is the repository that one can pull from but that will always > > be the latest commits you will be pulling from the repo. > > > But these snapshots would be different, most developers are following the > master branch rather then the 1.22 branch that we use for doing point releases > > -- > > 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 > > > ___ > 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 ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] 1.22 schedule proposal - updated
On Mon, 18 Feb 2019 08:46:29 +1030 Simon Lees said: > > > On 16/02/2019 20:24, Jonathan Aquilina wrote: > > Hi Simon, > > > > My idea for that is more for developers to have more frequent snapshots > > granted there is the repository that one can pull from but that will always > > be the latest commits you will be pulling from the repo. > > > But these snapshots would be different, most developers are following > the master branch rather then the 1.22 branch that we use for doing > point releases which means it's better to do more frequent minor releases rather than micro bug-fix releases. (it's more in-line with what is being actually tested and run by developers day to day). having a trimmed down release process would be needed for that to happen though. -- - Codito, ergo sum - "I code, therefore I am" -- Carsten Haitzler - ras...@rasterman.com ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] arc diff error
hello i want to update my diff, arc diff fails below is the log with arc diff --trace. If someone knows what I have to do... thank you Vincent $ arc diff --trace ARGV "E:/Documents/programmes_x64/msys2/home/vtorri/gitroot/arcanist/bin/../scripts/arcanist.php" "diff" "--trace" LOAD Loaded "phutil" from "E:\Documents\programmes_x64\msys2\home\vtorri\gitroot\libphutil\src". LOAD Loaded "arcanist" from "E:\Documents\programmes_x64\msys2\home\vtorri\gitroot\arcanist\src". Config: Reading user configuration file "C:\Users\vtorri\AppData\Roaming/.arcrc"... Config: Did not find system configuration at "C:\ProgramData\Phabricator/Arcanist/config". Working Copy: Reading .arcconfig from "E:\Documents\programmes_x64\msys2\home\vtorri\gitroot\efl2/.arcconfig". Working Copy: Path "E:\Documents\programmes_x64\msys2\home\vtorri\gitroot\efl2" is part of `git` working copy "E:\Documents\programmes_x64\msys2\home\vtorri\gitroot\efl2". Working Copy: Project root is at "E:\Documents\programmes_x64\msys2\home\vtorri\gitroot\efl2". Config: Did not find local configuration at "E:\Documents\programmes_x64\msys2\home\vtorri\gitroot\efl2\.git\arc/config". >>> [0] (+0) https://phab.enlightenment.org/api/user.whoami <<< [0] (+47) 47,499 us [2019-02-18 07:56:46] EXCEPTION: (HTTPFutureHTTPResponseStatus) [HTTP/503] 503 - Enlightenment server trouble https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
