Re: [MiNT] Project management (Was: Re: Potential bug on mouse wheel)

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

On Tue, Dec 22, 2009 at 4:22 AM, Jean-Luc CECCOLI
<Jean-Luc.Ceccoli@wanadoo.fr> wrote:
> On Mon, 21 Dec 2009 11:45:51 , Vincent Rivière <vincent.riviere@freesbee.fr> wrote:
>>
>> Miro Kropacek wrote:
>> > I don't know about you but I'm totally lost in this huge amount of mail
>> s
>> > where "everyone" is posting some patches, builds, screenshots, RSC data
>> ,
>> > TBL data, sources, test applications, ...
>>
>> I totally agree.
>> I would like to help testing software, but I don't know which binaries to
>>
>> use, what is required, etc.
>> Big mess.
>>
> So do I.
>
> J.-Luc
>
Any luck here.

The servers are already set up to do this (according to my discussion
on the HighWire list). I would just require "being used".

App integration should not be a problem either, except maybe the lack
of TOS/GEM software (something I was looking into)

Apparently the current servers are more than capable of handling any
new load. And there is a working G-forge on the new AtariForge site.

But I think its just about consolidating whats already there,
outlining Program usage for various platforms, and making that and
access easily available. Combining mail list activity should not be
too much of a problem if everything is on one server, the serve itself
can become a list recipient to grab and process relevant info if need
be.

This would be a good time to overhaul the presentation and
organisation of a complete TOS system all in one place, which would
allow for interelated issues to be easily monitored, discussed, and
tested (ie VDI + AES)

It would be also an opertune time (with a stable point release coming
up) to organize an offsite backup CVS, ofr "just in case" senarios.
The modern issues cause a server to go down are far beyond mere
technical issues, and I would hate to see a slow or stop in CVS
development just because the current CVS's were inaccessible.

All of the put together would allow a consolidated effort (from
organisation and management to development path and testing) for
public consumption, particularly for Coldfire and ACP development

This would allow other non programming related issues and updates to
be more easily accessible to non techos, in particular language, RSC,
and interface related upgrades

Because of TosHyp being on the same server, an integrated TOS (ROM),
MiNT, VDI, and AES upgrade program and path would be easily visualized
and cross development would be a simpler process (AES+VDI)

I dont mind organising everything (and talking to the right people),
as I have plenty of webdev and technical skill to piece things
together, fill in any missing gaps, type up initial documentation and
provide (with testing), web interfaces, devkits, gaurenteed and up to
date download links, etc

In this respect all I need is an outline of what people want to use,
what they currently use, a 1.17 point release, and access to the
current server (AtariForge.net) to make everything available.

I can also provide a breakdown and/or search facility for the list,
including by going over the list and various changelogs to compile
directories also. This would help bring some of the older content to
light.

I have already had the idea of putting something together but I would
prefer to place it on the same server as where things are actually
happening, which wold also simplify "user access".

Let me know what you need. The contents of this thread is a good
practical starting point, but I would not limit option to one thing or
another, but rather provide multiple solutions that can be used side
by side, as per a users preference.

I would also integrate any related info or web sites into the
usability of a consolidated frontend, ie SpareMiNT, EasyMiNT, XaAES
Skins, MyAES Themes, GCC downloads, excetera.. one that is usable for
both developers and end users alike..

Cheers..

Paul