[TYPO3-dev] The neverending sf story

[Sven Wilhelm]

Hi,

> you should really read the core list ;) We discussed just the above
> and some people (including me) like to use svn and trac for TYPO3
> development, for exactly the reasons you mention above.

ok, i'm not on the core list, so I can't recognize such discussion.
But if such points are discussed on the core (a complete closed list),
it's perfect for the others outside to see nothing early of the there
discussed topics :)

> 1. We need some people to manage the repos and trac (Karsten, Peter
> and I have volunteered for this)
> 2. We need a server and bandwith (which probably is not too costly)
> 3. We need to import stuff, test and make things happen
> I can only help with 1 and 3, but if someone provides 2, we can have
> a working test setup by the end of next week, promise.

I can offer help for all three parts. I also don't have a big timeslot
for doing such work at the moment, but seeing SF services permanently
down, lets the wish for an alternative solution growing.

To the points:
1. I work with subversion for some our own projects, don't know which
   knowhow therefore I still missing
2. For setting up a testing environment, preparing a rock solid tested
   environment I would setup a virtual server.
   For final serving the server should have enough RAM, but this one
   could be one the list when testing of point 1. is finished.
   As I told I would sponsor money therefore.
3. I can also help get this point happen, but I would not recursiv
   import the whole history of the project, starting a new baseline
   is better.


I like to share some other ideas at this point knowing "that other
people have talked about this points in the past" as I get told about it
several time :) I have something told déjà vu several time :)

Enhancement for the developing (and served by the repository server)
could be an automated unit test which displays result as a webpage like
implemented by the Eclipse project. There you can see the modules,
extensions or call it how you like it, that fault the tests an so having
a better overview where problems in the software are located.

Just one idea :)
Also help for that is offered if someone has an inspiration how that
would be implementable with the current core.

Sven