I meant David Hughes.
···
On Wed, May 11, 2016 at 8:43 AM, Emad Dlala emad.dlala@gmail.com wrote:
First, I wouldn’t call this a show. It’s real work, but I know what you mean.
Second, there are more than one person who contributed to the development to wxPython. So it’s not one, even though Robin has been the main developer.
Third, I wouldn’t speculate too much now about the longer term vision, and if we do, we should keep it in a separate thread, and better after the release of Phoenix. The goal in this thread is to collect bounty for the developers toward the release of Phoenix. So let’s not diverge please.
David Highs,
Any update about the payment procedure? I sent you an email but I haven’t heard back from you. Let’s hit the iron while it’s hot!
Emad
On Wed, May 11, 2016 at 6:25 AM, johnf fabiani.john@gmail.com wrote:
I too have concerns about a one man show. But think about this - there are several GUI lib’s and they too are one man shows - i.e. PyQT - still going strong. The only one I know of that wasn’t a one man show was pyside and that didn’t last very long (although I think they are trying to revive it). There are many one man shows in the open source world.
The other issue is our investment in learning and using wxPython. I for one do not want to lose that investment. And if we can get the word out many will donate just to protect that investment. I don’t know where we are in reaching the goal - but I hope it’s close!
Johnf
On Monday, May 9, 2016 at 11:30:56 PM UTC-7, Brendan Barnwell wrote:
That’s certainly a promising idea, and I’d be willing to pledge money toward that. I’d like to know, though, what “an official first release” means. I’ve asked before on this list about when Phoenix would be ready, and was told that “you can already use it”. So for me to feel like there was a substantive difference between that and an “official” release would have to mean that, basically, I can do anything and everything with Phoenix that I can currently do with wxPython on Python 2. (And, ideally, with minimal code changes required beyond those already required to make any Python 2 code run on Python 3.)
Also, I hate to mention this, but it does make me slightly nervous that the life or death of the entire future of wxPython appears to be completely dependent on a single individual. Does this mean that if (heaven forbid) he gets hit by a bus or something, all hope of wxPython on Python 3 is dashed? Whenever I look at this list (which is admittedly not all that often), I get that feeling. That makes me wonder if it is ultimately worth it to push for getting an initial release out the door. We don’t just need an initial release, we need “wxPython works, smoothly and completely, on Python 3”, with everything that entails, and it’s not clear to me that there’s the wherewithal to make that happen.
Anyway, like I said, I’d be willing to pledge some money toward an initial release, but I think there are some important issues to face up to beyond that.
On Thursday, May 5, 2016 at 6:01:28 AM UTC-7, David Hughes wrote:
To encourage an official first release of Phoenix as soon as can be, it's been suggested we raise a bounty to be paid to Robin when this happens. Going through an onlinefund raising service would not only be a hassle but they will end
up pocketing up to 10% of the cash (e.g. bountysource.com). I have been in touch with Robin about this and he is OK with me coordinating the raising of pledges among ourselves here.I don’t know if it will help to set a target amount but I’m suggesting one of $10,000 US dollars - note, this is a target, not an upper limit . The good news is that we are already half way there and the pledged total is currently $5,000.
If you want to announce a donation, large or small, here in public, that’s fine but in any case please let me know so I can keep track of things and send you the details for making payment when the time comes. Please email forestfield.softwaregmail.com (the public PGP key is attached) or use Whatsapp to contact +44 7971 336995 (which uses end to end encryption) and I will keep you all informed of progress.
I think the best way of making payments will be by direct transfer to a bank account of Robin’s choice, but I’m also able to process debit and credit card payments in Euros, UK pounds and US, Canadian and Australian dollars, although these will incur (credit) card charges and possibly currency exchange costs.
–
RegardsDavid Hughes
Forestfield Software
–
You received this message because you are subscribed to the Google Groups “wxPython-users” group.
To unsubscribe from this group and stop receiving emails from it, send an email to wxpython-users+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Seriously though, the bus factor can be an issue on almost any project whether OSS or not, whether it is a one-pony circus production or a medium-large team. However I do think there are enough people with enough knowledge of wxPython design and implementation that it's possible that wxPython could live on beyond me, given enough time and desire to do so. I'm not sure we can do any better than that without huge changes, like a paid staff.