eLua Development

issues - general

Classic

List

Threaded

6 messages Options

Karoly Molnar

issues - general

Hi,

Ii have added two new issues to the eLua redmine http://tracker.eluaproject.net/issues/44 and http://tracker.eluaproject.net/issues/45 but I am also OK to fix these. Do you have a kind of process for this? I mean, shall I just propose my changes here in the mail thread for discussion or shall I clone the repo and make pull requests? Do you accept pull requests at all or prefer to keep the code in one hand?

Also I am working on a new eLua MCU porting which is just half ready but I am committed to finish it. Same question as above. Are pull requests accepted and is the normal way to bring in new ports?

Regards
Karoly

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

BogdanM

Re: issues - general

Hi,

On Fri, Aug 24, 2012 at 12:41 PM, Karoly Molnar
<[hidden email]> wrote:
> Hi,
>
> Ii have added two new issues to the eLua redmine
> http://tracker.eluaproject.net/issues/44 and
> http://tracker.eluaproject.net/issues/45 but I am also OK to fix these.

Thank you for using the tracker. Fo some reason, people seem to avoid it.

> Do
> you have a kind of process for this? I mean, shall I just propose my changes
> here in the mail thread for discussion or shall I clone the repo and make
> pull requests? Do you accept pull requests at all or prefer to keep the code
> in one hand?

Pull requests are the way to go. If you want to fix the bugs, you can
also assign yourself to them in our tracker.

>
> Also I am working on a new eLua MCU porting which is just half ready but I
> am committed to finish it. Same question as above. Are pull requests
> accepted and is the normal way to bring in new ports?

Pull requests. Also, very good news. Could you let us know what port
you're working on?

Best,
Bogdan

>
> Regards
> Karoly
>
> _______________________________________________
> eLua-dev mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/elua-dev
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Karoly Molnar

Re: issues - general

Hi Bogdan

> Thank you for using the tracker. Fo some reason, people seem to avoid it.
No problem. I am using Redmine at work too so it was no pain to to use it :) Just the link is a bit hidden on the eLua webpage. Also Redmine uses the "tracker" terminology for the issues so I could find it quickly. Someone with e.g. Bugzilla background would not immediately recognize that this is the link to the issue/bug tracking system. I say this from experience, in a project our business partner did not understand for a while what we mean with "trackers".

> Pull requests are the way to go. If you want to fix the bugs, you can
> also assign yourself to them in our tracker.
OK I can do that. When I have fixed the issues shall I assign the tracker back to you with a reference to the pull request and expect you to close it when the change is migrated?

> Pull requests. Also, very good news. Could you let us know what port
> you're working on?
This is for XMOS event processors. The processors are pretty fast in embedded world but very constrained in terms of memory. Now I will have to separate the eLua code to a number of parallel threads that will run on at least two separate cpu cores and communicate thru the channel mechanism of the chip. So first I have leaned out the code as much as possible using an MBED board as reference. And now I am in the middle of separating it to two threads. I still fear that the port would not conclude to a "full port" because is not likely that all Lua and eLua featues would fit in the memory whatever I do (I may allocate 2x64K RAM that shall contain the Lua VM itself, the Lua program, the stack and the heap as well). I am using the RomFS and a precompiled lua test program and my first is to be able to execute it on the XMOS.
Also a question, do you have a set of tests to verify the lua and eLua functionality of the ports? May be a stupid question but I am an old-school developer and do not like to claim that I am ready unless I have tested my stuff thoroughly. I have found a test script for the rpc in the repo so far.

Regards
Karoly

> From: [hidden email]

> Date: Fri, 24 Aug 2012 12:50:17 +0300
> To: [hidden email]
> Subject: Re: [eLua-dev] issues - general
>
> Hi,
>
> On Fri, Aug 24, 2012 at 12:41 PM, Karoly Molnar
> <[hidden email]> wrote:
> > Hi,
> >
> > Ii have added two new issues to the eLua redmine
> > http://tracker.eluaproject.net/issues/44 and
> > http://tracker.eluaproject.net/issues/45 but I am also OK to fix these.
>
> Thank you for using the tracker. Fo some reason, people seem to avoid it.
>
> > Do
> > you have a kind of process for this? I mean, shall I just propose my changes
> > here in the mail thread for discussion or shall I clone the repo and make
> > pull requests? Do you accept pull requests at all or prefer to keep the code
> > in one hand?
>
> Pull requests are the way to go. If you want to fix the bugs, you can
> also assign yourself to them in our tracker.
>
> >
> > Also I am working on a new eLua MCU porting which is just half ready but I
> > am committed to finish it. Same question as above. Are pull requests
> > accepted and is the normal way to bring in new ports?
>
> Pull requests. Also, very good news. Could you let us know what port
> you're working on?
>
> Best,
> Bogdan
>
> >
> > Regards
> > Karoly
> >
> > _______________________________________________
> > eLua-dev mailing list
> > [hidden email]
> > https://lists.berlios.de/mailman/listinfo/elua-dev
> _______________________________________________
> eLua-dev mailing list
> [hidden email]
> https://lists.berlios.de/mailman/listinfo/elua-dev

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Karoly Molnar

Re: issues - general

One more comment on this:
> Pull requests are the way to go. If you want to fix the bugs, you can
> also assign yourself to them in our tracker.
I have just tried to assign the tracker to myself but am unable to. I guess that I am not added to this project.

Regards
Karoly

From: [hidden email]
To: [hidden email]
Date: Fri, 24 Aug 2012 14:56:55 +0200
Subject: Re: [eLua-dev] issues - general

> From: [hidden email]

_______________________________________________ eLua-dev mailing list [hidden email] https://lists.berlios.de/mailman/listinfo/elua-dev

_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Martin Guy

Re: issues - general

In reply to this post by BogdanM

On 24 August 2012 11:50, Bogdan Marinescu <[hidden email]> wrote:
> Thank you for using the tracker. Fo some reason, people seem to avoid it.

One reason might be that http://tracker.eluaproject.net says

"This is the eLua project tracker
The service is still under maintenance and will be available soon.
Thank you for the patience and for the support."

and has been like that for years.

To be fair, if someone is insistent and recklessly enough to poke
_eLua_ and then _Bugs_ anyway, just to see what happens, it does take
you to a list of bugs, though most of them are bugs in the tracker.
Which is odd, because "eluaservices" should be the tracker subproject
for that. Instead the tracker and website bugs appear both in the
"elua" and the "eluatracker" subsections, with only 4 "elua bugs" out
of 16 that are actually to do with elua.

That's not exactly encouraging people to use it!

We gave up on the eluatracker last year when the server died, the
admins didn;t have *any* backups and no one told us anything for a
month, in which time the Google cache of the issue detail pages had
all expired.
As I said at the time: "a lobotomy to the project".
We use code.google.com/p/mizar32/issues for all our eLua-related issues.

I suggest eluaproject move to a canned solution for an issue tracker,
to get the quality and reliability that any OS project needs in its
tools. The current one has too many issues.

M
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev

Martin Guy

Re: issues - general

On 25 August 2012 15:11, martinwguy <[hidden email]> wrote:
> I suggest eluaproject move to a canned solution for an issue tracker,
> to get the quality and reliability that any OS project needs in its
> tools. The current one has too many issues.

Hang on - github has an issue tracker, tying the issues to the commits.
Why don't we move to that?

M
_______________________________________________
eLua-dev mailing list
[hidden email]
https://lists.berlios.de/mailman/listinfo/elua-dev