On Tue, Jun 12, 2018 at 11:15 AM, Terry Brown wrote:
> On Tue, 12 Jun 2018 09:30:51 -0500
> "Edward K. Ream" wrote:
>
> > > And I say Leo's architecture could be way more simpler and more
> > > modular, allowing people to more easily contribute with less
> > > control from anyone. There is only
On Tue, 12 Jun 2018 09:30:51 -0500
"Edward K. Ream" wrote:
> > And I say Leo's architecture could be way more simpler and more
> > modular, allowing people to more easily contribute with less
> > control from anyone. There is only a minimal neccessary core for
> > what leo is doing, the rest is
On Tue, Jun 12, 2018 at 7:20 AM, 'Marcel Franke' via leo-editor <
leo-editor@googlegroups.com> wrote:
> Leo's source code is difficult in places because it's always dealing with
>> the DAG. That can't be helped. Leo devs are special people.
>>
>
> And I say Leo's architecture could be way more
Am Dienstag, 12. Juni 2018 12:43:11 UTC+2 schrieb Edward K. Ream:
Terry, Vitalije, Ville Vainio, Bernhard Mulder, Kent Tenney, Marc-Antoine
> Parent, Paul Paterson and others have all made significant contributions to
> Leo. By any reasonable measure, Leo is open software.
>
It's not whether
Am Dienstag, 12. Juni 2018 12:50:00 UTC+2 schrieb vitalije:
> But just FYI here is the explanation from github how they count
contributions.
Ok, I see where you are coming from. Did you confirm that commits to
develop are not appearing in your contribution-list after devel was merged
to
>
> a) I understand the general idea of the contribution and
> b) That I have a git branch to evaluate.
>
Both these items were on my todo list. I have planed to share code perhaps
in some branch or in its own repository, and surely I planed to explain the
model in full detail once it has
On Tue, Jun 12, 2018 at 4:18 AM, 'Marcel Franke' wrote:
> On surface
> [Leo is] open source, but the source if unnecessarily complicated and
> unhealthy highly integrated, while still controlled by one single instance
> of authority. Access is hard, relevant contribution even harder.
>
Terry,
On Mon, Jun 11, 2018 at 8:48 AM, vitalije wrote:
> An ancient Greek philosopher Socrates said something like this: "Trying to
> teach someone faster than he can learn is dangerous and unwise". To be a
> good teacher one needs to be tremendously patient.
>
Patience is always a good idea ;-)
>
Am Montag, 11. Juni 2018 15:48:00 UTC+2 schrieb vitalije:
Since March 2018, when it was declared that only Edward should commit to
> the master brunch, no contribution is counted for any other developer in
> leo-editor team.
>
This is not true. The individual commits of every developer are
On Tuesday, June 12, 2018 at 9:04:18 AM UTC+2, jkn wrote:
>
>
>
> Vitalije has replied with great thoughtfullness and dignity. It's a pity
> that your contributions seem consistently at the trollish end to me.
>
> Sorry, you see it that way. I don't want to argue with you, but these have
been my
On Tuesday, June 12, 2018 at 6:44:34 AM UTC+1, rengel wrote:
>
> What an eloquent heart-breaking account.
> A well-meaning soul, hurt but stiil not (yet) giving up.
> Reading it, just makes me sad.
> It will never be known how many just walked away silently...
>
> Reinhard
>
Vitalije has
What an eloquent heart-breaking account.
Reading it, just makes me sad.
It will never be known how many just walked away silently...
Reinhard
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving
An ancient Greek philosopher Socrates said something like this: "Trying to
teach someone faster than he can learn is dangerous and unwise". To be a
good teacher one needs to be tremendously patient.
As a teacher I am very happy with the progress we made. About a year ago I
have studied
Terry, Reinhard, Offray, Jon many thanks for your support and understanding.
Edward thank you. You didn't have to apologize, but since you did, thanks.
Apologize accepted.
I had to focus on something else and I couldn't afford to enter into
lengthy discussions, so, I had to ban myself out of
Here is an exchange that happened privately. Imo, it should be public:
EKR:
> > My new work is itself an important demo. It conclusively proves that
> > the read-logic speedups are completely independent not only of new
> > positions, but *any* positions. Everything happens in "vnode space":
I agreed with Jon. There are some parts of the discussion that are quite
technical (that's why my other proposal of being able to test features
and docs in Leo prototypes) and I think that only when Vitalije comes
back from his 10 days immersion we will be able to follow what has been
mostly a
Speaking for myself - but I suspect I am not along...
I think Edward's response has seemed very positive, in general, and I see
both him and Vitalije as being remarkebly ego-free in all of this. This is
another reason this part of the internet is so refreshing.
I suspect one reason there has
On Friday, June 1, 2018 at 3:37:55 PM UTC-5, Terry Brown wrote:
I think, Edward, that sometimes you re-write code as means to fully
> understanding it, I'm sure that's effective, but it's also hard on the
> contributor who understood the code the way they wrote it. There are big
> chunks of
On 02/06/18 16:11, Edward K. Ream wrote:
> *Future prototypes*
>
> I do hope I haven't made you shy about making further contributions.
> That would be a big loss to the whole Leo community.
>
+1000.
Please find the way that works for having prototypes going in this
community with proper
On Friday, June 1, 2018 at 2:57:52 PM UTC-5, vitalije wrote:
This is exactly why I was reluctant to share unfinished prototype. I did
> beg you though, not to make any decisions before the prototype is finished,
> but it seems too hard to resist. I couldn't resist the temptation to share
> the
+++
Well said!
A Not-Invented-Here-so-let's-redo-it attitude is prone to block motivation
and creativity.
Reinhard
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email
On Fri, Jun 1, 2018 at 2:57 PM, vitalije wrote:
> This is exactly why I was reluctant to share unfinished prototype. I did
> beg you though, not to make any decisions before the prototype is finished,
> but it seems too hard to resist. I couldn't resist the temptation to share
> the unfinished
This is exactly why I was reluctant to share unfinished prototype. I did
beg you though, not to make any decisions before the prototype is finished,
but it seems too hard to resist. I couldn't resist the temptation to share
the unfinished code, you couldn't resits to make decisions.
I'll write
Here are my thoughts after several days of intense study of Vitalije's
prototype.
1. The top priority will be to accelerate Leo's read code, using
xml.etree.ElementTree and much faster scanning of external files. The goal
will be to be able to do without caching. Imo, it's doable. I'll create
24 matches
Mail list logo
