Re: [MiNT] MiNTLib / Kernel Future and also SpareMiNT.....

[Paul Wratt <paul.wratt@gmail.com>]

On Fri, May 28, 2010 at 7:19 AM, Helmut Karlowski
<helmut.karlowski@ish.de> wrote:
> Am 27.05.2010, 22:50 Uhr, schrieb Jo Even Skarstein <joska@online.no>:
>
>> But these people usually have some long term goals too, and it would be
>> nice if they could be shared in a roadmap. If this is combined with an
>> actively used bugtracker, I think this will encourage more people to
>> work on the project. It's a good way to get to know the codebase - pick
>> a bug or a small feature and start digging into it.
>
> I fully agree to the bugtracker-usage: If something can not be solved
> immediately, it's still listed in the bugtracker and one does not have to
> scan through the list-archive for it.
>
This need to be more fully tied in with the "new" website.

The old website should be updated as well, it is still a worthy
resource, and fully commited to search engine results, so updating it
makes sense

> So use the bugtracker for the difficult issues and also post your stuff here
> for discussion.
>
You must be thorough, even if the bugs are just fixed on the list,
there is no reason why they should not be logged, even it it was
small, or took 2 seconds to fix.

This is more about the future (when whas this cahnged, when did this
get introduced, who coded this patch, etc)

I believe that it is well within the possibility of "totally useful"
if the list (which is the heart of all current Atari based dev work)
were accessible via the "new website"

I am not talking anything complicated, just "modern communication
methods" for a "modern development cycle", one that would allow
followers to not be forced to subscribe.

The various BBS's (and web boards) around the web are active, but are
basically "excluded" from anything that takes place on the list.

>From a development point of view, this is like "shooting one self in
ones foot". There is no reason why the new web site should not contain
more current "blurb" type info (cvs commits, build updates, comments,
etc).

We could then promote the site to ourselves first (active list
members), something which still needs to be done regarding the
bugtracker. The "new" website should make this promotion (including
the use of the bugtracker) much easier.

This is not the same as "making the list obsolete". Just improving on
exposure, coverage, and potential user participation, especially
people new to the Atari plaforms

Cheers

Paul