Hi Guys,
Goings forwards, we do need to address the issue of maintenance.
I look forwards to Mark's return, but in the meantime, I suggest we need
to show that we can look after ourselves.
Mark writes some of the most elegant and readable code it has been my
privilege to encounter and I hope we will see him again soon, but really
since Mattia's departure he has shouldered the whole responsibility of
maintaining wxPerl on his own. It's a full time job and more.
I would like to suggest that we show that we can motivate and maintain
ourselves without Mark's supportive presence.
I feel Erik's github setup is a good start. It is a way that we can
clone and branch our own modifications and then ripple them up to the
master. We can probably do it with svn as well, but I wouldn't know how.
Here is someone's blog on how to create a clone and a branch under
github, together with some thoughts on patching, I'm sure that there are
others.
https://ariejan.net/2009/10/26/how-to-create-and-apply-a-patch-with-git/
It would be nice if we could have a more distributed maintenance team
where we were all encouraged and able to contribute where we can.
I would be happy to learn and contribute where I can.
I would like to suggest that we could have say three or four maintainers
and that we could communicate and maintain wxPerl without any single one
of us having to shoulder the entire workload. If one drops out, we
should look for another.
I would love to hear your thoughts about this.
Regards
Steve.
