311–318 of 318 posts
Earlier quoted context omitted.
Anyone know which of the donation options respects privacy, and isn't paypal? Haha.
What's wrong with their bitcoin option?
Earlier quoted context omitted.
> The latter type of focus, the internal focus, asks "what do _we_ want to do, what interests _us_ as a team, what's next for _us_" and I believe that's always been a feature of GIMP's existence Right now, the focus is on completing the GTK+3 port for v3.0 and making room in API for upcoming serious changes in v3.2 such as non-destructive editing. Sounds good enough? :)
I'm feeling quite spoiled here--updates coming straight to the rabble from the source. :-) And when I'm still catching up with new features from last year! Now this non-destructive editing thing, can it also cure someone who rasterizes all of his text layers without making backups? ;-) (Really it does sound awesome)
Earlier quoted context omitted.
I wonder what kind of wonderland you live in where most senior developers make close to half a million dollars.
$20/hr was a contract rate. Your 1/2 million presumably is a salary (base). Not the same thing. $20/hr is roughly equivalent to $20k salary. $200k salary is reasonable for a competent developer who can hop on adding features to Gimp. In my reality no developer (even a sh *y one) makes $20k.
Earlier quoted context omitted.
(Of course it would be Boudewijn Rempt)--much respect to you and thank you for your question. > gimp developers work on gimp because they like gimp I'd say: GIMP has always been good enough for GIMP developers as its own world to explore--what is it, what can we make it become for the sake of GIMP. I remember the good old days (frankly I'm not sure if this still happens) when a mailing list suggestion like "look, Pho…
> The latter type of focus, the internal focus, asks "what do _we_ want to do, what interests _us_ as a team, what's next for _us_" and I believe that's always been a feature of GIMP's existence Right now, the focus is on completing the GTK+3 port for v3.0 and making room in API for upcoming serious changes in v3.2 such as non-destructive editing. Sounds good enough? :)
Earlier quoted context omitted.
So... I've had to read this about eight times, and two or three of those together with someone to figure this out... But what you're saying is "gimp developers work on gimp because they like gimp, while blender developers work on blender to see what people can do with it -- so they will not be able to spend this money effectively." -- or am I still misunderstanding you?
(Of course it would be Boudewijn Rempt)--much respect to you and thank you for your question. > gimp developers work on gimp because they like gimp I'd say: GIMP has always been good enough for GIMP developers as its own world to explore--what is it, what can we make it become for the sake of GIMP. I remember the good old days (frankly I'm not sure if this still happens) when a mailing list suggestion like "look, Pho…
I myself make monthly donations to Øyvind Kolås, and I think it's important he just does what he thinks he needs to do. No "make Gimp like software X" stuff.
Earlier quoted context omitted.
If you'll provide more detail as to which inconsistencies you've found, I'll take the time to test and write up an actionable bug report.
That would actually be a valuable service. Many users don't know where or how or what to put in a bug report. If some had a site that you could just write free-form prose others more experienced could convert that to actionable bug reports.
That said, I'll _happily_ take any mention of FOSS bugs, verify, and file them at the proper place. Hit me!
Earlier quoted context omitted.
Studies back you up and suggest "Pay enough or not at all." Paying below market rate tends to just piss people off and make them feel insulted and undervalued.
That's interesting. Do you happen to have a link to an article or study about this so that I can learn more?