I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
where the few core developers are too busy maintaining the product to
spend a lot of time helping new developers come on board.
Gimp is an extremely large and
On Thu, Jan 27, 2011 at 3:43 PM, Eric Grivel g...@lumenssolutions.com wrote:
I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
where the few core developers are too busy maintaining the product to
spend a lot
On 01/27/2011 04:43 PM, Eric Grivel wrote:
I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
where the few core developers are too busy maintaining the product to
spend a lot of time helping new developers come
On Thu, Jan 27, 2011 at 10:02 PM, Pete Bergstrom
petebergst...@gmail.com wrote:
On Thu, Jan 27, 2011 at 3:43 PM, Eric Grivel g...@lumenssolutions.com wrote:
I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
Maybe just a good documentation for GIMP source is needed? Once I tried to
patch TinyScheme interpreter to make it work faster. In files I was working
on was almost no comments.
Łukasz Czerwiński
___
Gimp-developer mailing list
Boot Camp . . . good idea. Docs . . . good idea.
Let the newbie's like me (coming out of boot camp) write some of the Docs.
Presently I have everything compiled and running under Ubuntu, and I am just
reviewing the code to get some sort of context.
It is huge. Incredible, actually. Who wrote
On 01/27/2011 05:29 PM, Øyvind Kolås wrote:
Feel free to drop by the #gimp and #gegl IRC channels to ask directed
smart questions for understanding the code. Also be aware that some of
the existing core contributors both dislike email in the first place,
and are cursed by knowledge thus not
Eric Grivel wrote:
Which is where my thought of a boot camp came in. What if there was a
group of potential new developers all struggling with the same learning
curve? Wouldn't it be great if an experienced Gimp developer could lead
the whole group through a series of exercises, designed to
On Thu, 2011-01-27 at 16:56 -0700, Stephen Greenwalt wrote:
* The project ought to be able to exist in a bubble . . . so as to
avoid confusion . . . regarding copies of dependencies that might
exist in the OS.
Automated builds are typically used to verify dependency issues on
multiple
On 01/27/2011 10:43 PM, Eric Grivel wrote:
I am getting the impression that the Gimp project is trapped in a
chicken-and-egg problem with regard to attracting new contributors,
where the few core developers are too busy maintaining the product to
spend a lot of time helping new developers come
On 01/28/2011 12:56 AM, Stephen Greenwalt wrote:
It is huge. Incredible, actually. Who wrote all of this? Wow.
To see who wrote all this, visit https://www.ohloh.net/p/gimp/contributors
A few comments:
* It seems to work best to put the entire project (all source, and all
build
On 01/28/2011 05:22 PM, Martin Nordholts wrote:
Our nightly builder is found at
http://gimptest.flamingtext.com:8012/waterfall which curiously enough
failed this night to my changes yesterday, but I fixed that already...
It's not curious, it's the beauty of the nightly build. It breaks
On 01/28/2011 05:01 AM, Michael J. Hammel wrote:
* Shouldn't we standardize on a common development IDE (like Eclipse)?
If I am missing something in that area . . . let me know.
IDE's are crutches. Based on the source tree I don't think the
developers use them but I could be wrong. I don't
13 matches
Mail list logo
