I think we can all agree that Kevin has done a fantastic job during his
tenure as wxruby lead. To list off some of his accomplishments:
1) Oversaw the release of version 0.1 through 0.5
2) Created the framework for wxruby-swig
3) Created the wxruby wiki front page which is ever-expanding.
4) Has shown a significant presence on the mailing list.
5) Has shown both excellent management and technical skill
Kevin leaves big shoes to fill, and sadly my shoe size is 8 and a half.
I''m going to try my best to continue the work he did. My goals are
1) To complete the migration to wxruby-swig
2) Improve the wxruby documentation
3) Keep the same level of discussion on the mailing list
4) Increase the wxruby presence on the ruby-talk mailing list
Of course, open source projects are not one-man operations. There are a
number of ways to contribute to the project:
If you''re a C++ developer or have SWIG experience, then we need help
with wxruby-swig. There are still many classes to convert, and lots of
support code to write.
If you''re a wxruby user, then let the list know what you need! Lots of
classes have been added by user requests. Also, contributing articles to
the wiki or adding to the samples is a great way to give your support.
Like I said before, Kevin leaves big shoes to fill. I hope I can rise to
the challenge.
Nick
Kevin Smith wrote:> Greetings all,
>
> Sadly, I must announce my "retirement" as the wxruby project
leader. I
> still believe in the project, and really want it to succeed.
> Unfortunately, there are other projects that are higher priority for me
> right now. I cannot be an effective wxruby lead at this time. Perhaps at
> some point in the future, wxruby will again become a top priority for
> me. If that happens, I''ll evaluate how best to help out at that
time.
>
> For almost a year now, Nick has been the de-facto wxruby lead. He is the
> main reason that progress hasn''t completely stalled. He has agreed
to
> officially become the lead now, although (like most of us who volunteer
> for free software projects) he also has other demands on his time.
>
> Park Heesob initiated the wxruby project, and most of the 0.6.0 code is
> still his work. Anyone who has benefitted from wxruby owes thanks to
> him. I just wanted to say that again.
>
> I have to thank Curt for his "behind-the-scenes" efforts. He has
> contributed greatly to this project in quiet ways.
>
> Finally, thanks to everyone else who has submitted a patch, edited the
> wiki, submitted a bug report, sent an email to the list, or raised
> public awareness of wxruby. This is a community project, and the more
> involvement we get, the healthier the project will be.
>
> Please realize that a project like this NEEDS non-coders who can help
> with publicity, test and file bug reports, update documentation, write
> tutorials and samples, etc. The less of this that the core maintainers
> have to do, the more time and energy they have to actually write code.
>
> Moving forward, I will remain a part of the wxruby community. I still
> believe that wxruby-swig is the future, so any effort I put in will be
> on that side. I will still try to answer questions, and provide input
> when I think it might be helpful.
>
> Cheers,
>
> Kevin
> _______________________________________________
> wxruby-users mailing list
> wxruby-users@rubyforge.org
> http://rubyforge.org/mailman/listinfo/wxruby-users
>
>
>