On Wed, 18 Oct 2017 09:27:00 + Andrew Williams said:
> And herein lies our circular problem:
>
> 1) Get started writing an app using the EFL
> 2) We are completely rewriting the interfaces that app developers will use
> 3) Developers investigate what can be done to
And herein lies our circular problem:
1) Get started writing an app using the EFL
2) We are completely rewriting the interfaces that app developers will use
3) Developers investigate what can be done to help and get stuck
4) ... wait a while then return to 1 ...
I am putting together trivial
On Wed, 18 Oct 2017 04:38:33 +0200 Jonathan Aquilina
said:
realistically the best way to start is outside of efl. write an application
that uses efl then go from there. pick a small simple app or tool for yourself.
then either expand that or write another one. get more
Here is a very valid question where would a total noob like me start
contributing?
Given the size of the code base it’s a bit scary I would say for new comers.
Sent from my iPhone
> On 18 Oct 2017, at 04:26, Jean-Philippe André wrote:
>
> Hi,
>
> 2017-10-18 9:35 GMT+09:00
Hi,
2017-10-18 9:35 GMT+09:00 Carsten Haitzler :
> On Tue, 17 Oct 2017 11:18:43 + Andrew Williams
> said:
>
> > Hi,
> >
> > There is a concerted effort now to try and fix up the documentation of
> EFL
> > for devs / contributors and for users of
On Tue, 17 Oct 2017 11:18:43 + Andrew Williams said:
> Hi,
>
> There is a concerted effort now to try and fix up the documentation of EFL
> for devs / contributors and for users of our apps.
> The dev portion of this is obviously largely based around the interfaces
>
I would be willing to help triage and help prioritize bugs according to
difficulty if needed so that any new contributors can have a bit more of an
easy point of entry to the project.
Sent from my iPhone
> On 17 Oct 2017, at 13:18, Andrew Williams wrote:
>
> Hi,
>
>
Hi,
There is a concerted effort now to try and fix up the documentation of EFL
for devs / contributors and for users of our apps.
The dev portion of this is obviously largely based around the interfaces
work as everything will be "legacy" at some point in the near future.
We only have a limited
On Tue, 12 Sep 2017 09:50:18 + Andrew Williams said:
> Hi,
>
> This is good to hear. Reflecting on it I think what I missed was the
> clarity that 1.21 would not be released until these interfaces are stable.
Actually that's not set in stone. We may release a 1.21 and
Hi,
This is good to hear. Reflecting on it I think what I missed was the
clarity that 1.21 would not be released until these interfaces are stable.
Having been looking for this since 1.19 I'm thrilled but wonder if everyone
is on the same page (maybe it was only clear within Samsung crew?).
On Mon, 21 Aug 2017 12:08:46 + Andrew Williams said:
> Hi,
>
> In a word no. What that is is an ever growing list of work we would like to
> get done. That's not really a planning tool it's a log.
> Planning for what goes into a release is a different beast - we make a
Hi,
In a word no. What that is is an ever growing list of work we would like to
get done. That's not really a planning tool it's a log.
Planning for what goes into a release is a different beast - we make a list
of what's required, agree on it and start working through.
Surely in planning for a
On Sat, 15 Jul 2017 20:12:34 + Andrew Williams said:
just saying... isn't
https://phab.enlightenment.org/T5301
good enough? i mean it does what's needed. tacks a todo list and even
dependencies... etc.
> Hi team,
>
> As many would probably agree by now we have a
evel@lists.sourceforge.net> Subject: [E-devel] Phab EFL
> ticket management
> As many would probably agree by now we have a very high ticket volume which
> is rather hard to manage... Whilst folk are doing a great job of
> marshalling the incoming tasks I think that some more struct
to the
code Base.
Sent from Samsung tablet. Original message From: Andrew
Williams <a...@andywilliams.me> Date: 15/07/2017 22:12 (GMT+01:00) To:
Enlightenment developer list <enlightenment-devel@lists.sourceforge.net>
Subject: [E-devel] Phab EFL ticket managem
Hi team,
As many would probably agree by now we have a very high ticket volume which
is rather hard to manage... Whilst folk are doing a great job of
marshalling the incoming tasks I think that some more structure would help
us to see what is needed in each area and for the next release etc...
16 matches
Mail list logo