[Freemint-list] FreeMiNT for 21st century

[Miro Kropáček]

Hi Alan,

thanks for your input, much appreciated.

The problem with atariforge.org (and any other 'home cooked' solution) is
that it requires, surprise surprise, maintenance. We could see that now
with the blacklist issue and also when something breaks in the build system
etc. As you said, you're busy doing the cool stuff (and I absolutely don't
have anything against that), Rob is busy, I certainly can't do that either
(I suck at/hate these admin kind of tasks) and I haven't noticed any eager
Linux admins out there.

That's why I'm quite fond of github.com -- it has a bug tracking system
(which, to some extent, can supply a mailing list too), it has a cool UI,
it has pull requests, it has reviews, it has zillions of plugins, most of
them are free for open sources so... why bother. I can't see one single
reason why to stay at atariforge.org (except the cool name).

Btw, everything already *is* in git. All it takes is git clone, add origin
to atariforge and push, voila, you've got your atari repo. But then again,
why would you do that.

On 13 January 2017 at 20:39, Alan Hourihane <alanh at fairlite.co.uk> wrote:

> On 13/01/17 00:39, Miro Kropáček wrote:
>
>
> On 13 January 2017 at 07:54, Peter Slegg <p.slegg at scubadivers.co.uk>
> wrote:
>
>> I had assumed the builds were automated a long time ago or was it
>> just the kernel ?
>>
> They are, it's just a set of scripts after all.
>
> There are several problems with current state of things, though:
>
>    - if something breaks, you'll get to know about it only the next day
>
>
> We could enable post-commit scripts where the build takes place after
> every commit, then you'd know about it immediately.
>
>
>    - to even get to know about it you must convince Alan to commit it
>    first
>
>
> That takes little convincing. I'm all for more people having access to the
> CVS (or git).
>
>
>    - if you commit something terrible, Alan will be very angry ;)
>
>
> Mmm? We should be at least building the patches we commit so we don't
> break the build. Testing is a different matter as there may be subtle
> issues introduced. There aren't that many of us left to do that either.
>
>
>    - perhaps some more
>
>
> Well, from my perspective I was never really handed the batten from Frank
> to handle FreeMiNT. I was the only one actively working on changes at the
> time when Frank was (now known) to be having health issues and I had very
> infrequent contact with him during that time. I ended up being the de-facto
> person just because I was working on code.
>
> I am more than happy for others to jump in and develop the code and have
> direct access to the CVS, as of more recent months/years I've been trying
> to develop hardware so that more people can actually run FreeMiNT on their
> real Ataris. After trying on my STE it was painful in 4MB and on my
> Megafile 30. Hence IDE boards, 8MB memory boards and then the MonSTer.
>
> In that light I've had little time for real FreeMiNT development, and I
> can't see that changing any time soon. I'm concentrated on the Unicorn USB
> drivers recently for TOS, and currently writing the STiNG drivers too.
>
> So MiKRO, feel free to convert to git, move to atariforge.org as there is
> already a FreeMiNT project there, just announce when you're ready and we
> can all shift to development there and more admins can manage the project.
>
> Thanks for your efforts,
>
> Alan.
>
>
> _______________________________________________
> Freemint-list mailing list
> Freemint-list at mail.atariforge.org
> http://mail.atariforge.org/mailman/listinfo/freemint-list
>
>


-- 
MiKRO / Mystic Bytes
http://mikro.atari.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.atariforge.org/pipermail/freemint-list/attachments/20170113/cd3e17ac/attachment.html