Could I then interest you in the 68k branch or are you fed with Aros at all? It would be a pity because Aros got very far now. And I am convinced that the 68k branch offers the real opportunities for Aros (not X86 like most here think) but I am a minority here :)

i miss jason and staf level of engagement, but understand that concepts may differ, motivation vary and real life interfere. neil deadwood and others have kept it going well for a while now, but it looks like since some weeks it is coming to a halt. the level of transparence that aros provides is naturally much better than that of alternatives, still for a follower it isnt always easy to judge the course it takes.

I think the number of core developers for AROS has been always quite low. So it means if a few devs contribute less it will be noticed heavily. But then connecting some big general trends to it is also useless IMHO; the number of devs is just too low to derive any statistically relevant trend and probably are likely just ventilating one's own frustration. Each of the devs will have it's own specific reason(s).

It is true that for example Jason McMullan has been contributing heavily and at one point did much less because real life; e.g. work interfered. Don't know if that is still the reason. AFAICR, I think his ARIX contributions you allude to were always meant to also be fed back into AROS source tree.

I also have to admit I don't contribute much anymore. There are several reason. (Let) building my own house and now doing the paintworks is one of them. But also that my vision on abiv0/abiv1 seems to be different than the rest of the AROS devs together with my vision on the hacks present in the AROS source code for m68k compatibility. Giving these facts I now enjoy playing with open source EDA software and can't currently motivate myself anymore to do AROS dev work.

@wawa

Well in my opinion development is stagnating because of two main factors:
1)i think the few people left start to be fed up of the actual situation with four similar operating systems,two of it locked up commercially - one of them even sealed up and mostly driven by fanboi-oriented and fanboi-driven business logic and vocal fanbois ready to eat you alive with potatoes once you do something that does not follow "teh true word";
2) there is very little new blood among devs and a lot ego-driven projects that usually try to keep things tight to their pocket while in my opinion what the NG and oldskool world is living is a survival crisis that require common efforts and a good deal of easily affordable - if not fully open source - and reproducible hw/sw projects to keep the existence itself of the amiga and like philosophy alive;

following the commits it unfortunatelly looks like the development stagnates. it is in acvordance of what is reflected in activity within the bigger amiga community, sad though.

Week of October 13th:

- Mounting ISO images with diskimage.device works again (neil)
- Minor fix to french keymap (otigreat)
- Automatic running on test suite when doing nighly builds has been introduced (neil)

Week of October 6th:

- Uncompressing with tar will no longer cause file system errors in certain cases (neil)

Quote:

The GCC 4.8.3 cross compiler had missing internal libgcc math functions when built for m68k - this patch fixes that issue so that it works. It isn't used (yet) to build AROS because the arm target breaks while building the gcc crosscompiler itself with an internal error.

Quote:

4.8.3 is not used to compile AROS yet. As for whether it can compile m68k now, I don't know - you need to ask Jason.

fix for GCC 4.8.3 for 68k compilation. What does that mean? Can everything now be compiled for 68k too?