On Tue, Jun 19, 2012 at 10:14 AM, Ulrich Telle <ulrich.telle@...> wrote:
> Hi Andrea,
>> I would like to have a new wxCode home on github (so to use Git instead
>> SVN as SCM system).
I don't know if I'm ready for Git yet, I'm just getting accustomed to
SVN after having dropped CVS, but see the bottom for a solution that
may perhaps work.
> As SourceForge put up several restrictions regarding project maintenance
> and administration which makes maintaining wxCode sometimes quite
> cumbersome and as a single SourceForge project is not very well suited
> for maintaining a big collection of only loosely coupled components I
> definitely support your experiment.
As perhaps the only active developer on it besides Ulrich, one of the
earliest adopters of wxCode, and an absentee administrator, I have to
say that it has not worked out as planned.
The real reason is not technical, but simply manpower and interest.
Projects need to be marked as working, updated to 2.9, documentation,
working builds, etc and nobody has the time or interest.
> For the wxCode SourceForge project in effect every project member could
> work on *all* components. The SourceForge SVN doesn't support a
> fine-grained access control.
This has never been a problem as far as I know.
>> This will be something I would like to try to do as an experimental/demo
>> project to let you see how it will works and also get possible
>> suggestions time by time and, if successful, consider a future transition.
> I think it's an interesting idea and I'm curious to hear about the first
> experiences of you. Maybe this could give wxCode a new impulse to get a
> better image and to get into a better shape.
There is a "live" SVN -> Git translator and wxWidgets uses it. Perhaps
this could work here as well?