[Newbie]Would like to contribute
This discussion is connected to the gimp-developer-list.gnome.org mailing list which is provided by the GIMP developers and not related to gimpusers.com.
This is a read-only list on gimpusers.com so this discussion thread is read-only, too.
| [Newbie]Would like to contribute | Kevin Pellet | 15 Feb 17:44 |
| [Newbie]Would like to contribute | Jehan Pagès | 15 Feb 20:34 |
| [Newbie]Would like to contribute | Jehan Pagès | 15 Feb 20:50 |
| [Newbie]Would like to contribute | Kevin Pellet | 16 Feb 06:53 |
| [Newbie]Would like to contribute | Alexandre Prokoudine | 16 Feb 10:47 |
| [Newbie]Would like to contribute | Shlomi Fish | 16 Feb 13:32 |
| [Newbie]Would like to contribute | Kevin Pellet | 16 Feb 18:53 |
| [Newbie]Would like to contribute | Shlomi Fish | 17 Feb 15:35 |
[Newbie]Would like to contribute
Hi!
I've never posted since my presentation a few months ago, because of a big lack of time (school, work, etc...). But now I have (a little) spare time to give a hand on Gimp. :)
I am a student in IT and more precisely as C/C++ dev' at Epitech Lyon, so I can work on correction of bugs, and I like too to write documentation, articles, and translation.
I heard that the big plan for now is porting every possible thing into GEGL, and that there was some work to do on the wiki. I'd love to do everything but I know I can't ;) And the fact is that I don't really know where to start, if someone could guide me for the firsts steps that would be awesome :D
By the way, I really love the new website!
Have a nice day,
Kevin Pellet (/Ilphrin/) ilphrin@autistici.org www.ilphrin.com
[Newbie]Would like to contribute
Hi,
On Mon, Feb 15, 2016 at 6:44 PM, Kevin Pellet wrote:
Hi!
I've never posted since my presentation a few months ago, because of a big lack of time (school, work, etc...). But now I have (a little) spare time to give a hand on Gimp. :)
I am a student in IT and more precisely as C/C++ dev' at Epitech Lyon, so I can work on correction of bugs, and I like too to write documentation, articles, and translation.
I heard that the big plan for now is porting every possible thing into GEGL, and that there was some work to do on the wiki. I'd love to do everything but I know I can't ;) And the fact is that I don't really know where to start, if someone could guide me for the firsts steps that would be awesome :D
The best way to start is if you use GIMP and experience yourself some bug or other issue that you want fixed. This is an ideal start and much rewarding to yourself, I think. :-)
Other than this, you can have a look at the bugzilla. We have hundreds of bugs: https://bugzilla.gnome.org/page.cgi?id=browse.html&product=GIMP
Easier would be to check the "newcomer bugs" list (link on the right of the page), though I doubt this is a very complete list, so you should also search for other bugs. Easy bugs for a newcomers are:
- crashes, because it allows to follow the stack trace at crash time
with a debugger.
- bugs which output warnings, because you can make warnings crash GIMP
by running it with --gtk-g-fatal-warnings option. And then same as
previous, use a debugger.
- bugs with UI text, because you can grep the visible text to find
where it is in the source files, and from there search for source of
the issue.
Also check the file `HACKING` in our repository. It gives some indication on compilation or the syntax we use in the GIMP project.
And last but not least, any contributor is really encouraged to hang out on IRC (#gimp at irc.gimp.org). This is where you'll get some information faster, and also where you can pressure us a little to review your patches if we forget, or anything like this. :-)
Jehan
By the way, I really love the new website!
Have a nice day,
-- Kevin Pellet (/Ilphrin/)
ilphrin@autistici.org
www.ilphrin.com_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Newbie]Would like to contribute
Oh by the way, if you are interested into OpenCL or GPU programming in general, have a look at this initiative too: http://www.gimp.org/news/2016/01/28/gegl-opencl-streamcomputing/
I have no idea if the project is now full (it was said they would accept up to 20 participants), but if you are interested in learning this technology, this could be a great opportunity for you.
Jehan
On Mon, Feb 15, 2016 at 9:34 PM, Jehan Pagès wrote:
Hi,
On Mon, Feb 15, 2016 at 6:44 PM, Kevin Pellet wrote:
Hi!
I've never posted since my presentation a few months ago, because of a big lack of time (school, work, etc...). But now I have (a little) spare time to give a hand on Gimp. :)
I am a student in IT and more precisely as C/C++ dev' at Epitech Lyon, so I can work on correction of bugs, and I like too to write documentation, articles, and translation.
I heard that the big plan for now is porting every possible thing into GEGL, and that there was some work to do on the wiki. I'd love to do everything but I know I can't ;) And the fact is that I don't really know where to start, if someone could guide me for the firsts steps that would be awesome :D
The best way to start is if you use GIMP and experience yourself some bug or other issue that you want fixed. This is an ideal start and much rewarding to yourself, I think. :-)
Other than this, you can have a look at the bugzilla. We have hundreds of bugs: https://bugzilla.gnome.org/page.cgi?id=browse.html&product=GIMP
Easier would be to check the "newcomer bugs" list (link on the right of the page), though I doubt this is a very complete list, so you should also search for other bugs. Easy bugs for a newcomers are:
- crashes, because it allows to follow the stack trace at crash time with a debugger.
- bugs which output warnings, because you can make warnings crash GIMP by running it with --gtk-g-fatal-warnings option. And then same as previous, use a debugger.
- bugs with UI text, because you can grep the visible text to find where it is in the source files, and from there search for source of the issue.Also check the file `HACKING` in our repository. It gives some indication on compilation or the syntax we use in the GIMP project.
And last but not least, any contributor is really encouraged to hang out on IRC (#gimp at irc.gimp.org). This is where you'll get some information faster, and also where you can pressure us a little to review your patches if we forget, or anything like this. :-)
Jehan
By the way, I really love the new website!
Have a nice day,
-- Kevin Pellet (/Ilphrin/)
ilphrin@autistici.org
www.ilphrin.com_______________________________________________ gimp-developer-list mailing list
List address: gimp-developer-list@gnome.org List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list List archives: https://mail.gnome.org/archives/gimp-developer-list
[Newbie]Would like to contribute
Hi Jehan,
Thanks for the links and the tips!
I'm going to take a look at the bugzilla, I suppose there'll be enough work for me ;) I have to configure xchat to connect in the irc (it's been a while since I use Mibbit for some irc channels...)
On 15/02/2016 21:50, Jehan Pagès wrote:
Oh by the way, if you are interested into OpenCL or GPU programming in general, have a look at this initiative too: http://www.gimp.org/news/2016/01/28/gegl-opencl-streamcomputing/
I have no idea if the project is now full (it was said they would accept up to 20 participants), but if you are interested in learning this technology, this could be a great opportunity for you.
Jehan
I saw this yesterday, it is very interesting but I don't know if I have enough time for four weeks of learning, is the resources or anything about the "course" going to be freely available once it is finished? :D
Thanks again! And maybe see you next time on IRC :)
Kevin Pellet (Ilphrin) ilphrin@autistici.org www.ilphrin.com > > On Mon, Feb 15, 2016 at 9:34 PM, Jehan Pagès wrote: >> Hi, >> >> On Mon, Feb 15, 2016 at 6:44 PM, Kevin Pellet wrote: >>> Hi! >>> >>> I've never posted since my presentation a few months ago, because of a >>> big lack of time (school, work, etc...). But now I have (a little) spare >>> time to give a hand on Gimp. :) >>> >>> I am a student in IT and more precisely as C/C++ dev' at Epitech Lyon, >>> so I can work on correction of bugs, and I like too to write >>> documentation, articles, and translation. >>> >>> I heard that the big plan for now is porting every possible thing into >>> GEGL, and that there was some work to do on the wiki. I'd love to do >>> everything but I know I can't ;) And the fact is that I don't really >>> know where to start, if someone could guide me for the firsts steps that >>> would be awesome :D >> The best way to start is if you use GIMP and experience yourself some >> bug or other issue that you want fixed. This is an ideal start and >> much rewarding to yourself, I think. :-) >> >> Other than this, you can have a look at the bugzilla. We have hundreds of bugs: >> https://bugzilla.gnome.org/page.cgi?id=browse.html&product=GIMP >> >> Easier would be to check the "newcomer bugs" list (link on the right >> of the page), though I doubt this is a very complete list, so you >> should also search for other bugs. Easy bugs for a newcomers are: >> >> - crashes, because it allows to follow the stack trace at crash time >> with a debugger. >> - bugs which output warnings, because you can make warnings crash GIMP >> by running it with --gtk-g-fatal-warnings option. And then same as >> previous, use a debugger. >> - bugs with UI text, because you can grep the visible text to find >> where it is in the source files, and from there search for source of >> the issue. >> >> Also check the file `HACKING` in our repository. It gives some >> indication on compilation or the syntax we use in the GIMP project. >> >> And last but not least, any contributor is really encouraged to hang >> out on IRC (#gimp at irc.gimp.org). This is where you'll get some >> information faster, and also where you can pressure us a little to >> review your patches if we forget, or anything like this. :-) >> >> Jehan >> >>> By the way, I really love the new website! >>> >>> Have a nice day, >>> >>> -- >>> Kevin Pellet (/Ilphrin/) >>> ilphrin@autistici.org >>> www.ilphrin.com >>> >>> _______________________________________________ >>> gimp-developer-list mailing list >>> List address: gimp-developer-list@gnome.org >>> List membership: https://mail.gnome.org/mailman/listinfo/gimp-developer-list >>> List archives: https://mail.gnome.org/archives/gimp-developer-list
[Newbie]Would like to contribute
On Tue, Feb 16, 2016 at 9:53 AM, Kevin Pellet wrote:
I saw this yesterday, it is very interesting but I don't know if I have enough time for four weeks of learning, is the resources or anything about the "course" going to be freely available once it is finished? :D
People who organize this haven't made up their minds yet.
Alex
[Newbie]Would like to contribute
Hi Kevin,
first of all - welcome aboard - and I hope you'll enjoy contributing to GIMP. Also thanks to Jehan for providing some introductory links and guidance.
See below for an important note.
On Tue, 16 Feb 2016 07:53:56 +0100 Kevin Pellet wrote:
Hi Jehan,
Thanks for the links and the tips!
I'm going to take a look at the bugzilla, I suppose there'll be enough work for me ;) I have to configure xchat to connect in the irc (it's been a while since I use Mibbit for some irc channels...)
The original XChat has become unmaintained for several good years now. Luckily, there are some active forks of it including https://hexchat.github.io/ , which should be used instead, because the original XChat may have some unfixed bugs, including security ones. I am using HexChat.
There is a list of some other prominent IRC clients here - http://www.shlomifish.org/open-source/resources/networking-clients/ .
Regards,
Shlomi Fish
----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ https://youtu.be/n6KAGqjdmsk - “Hurt Me Tomorrow” “If it’s not bloat, it’s not us.”, said Richard Stallman, the colourful head of the GNU project, and started to sing the Free Software song. — “The GNU Project Will Integrate GNU Guile into GNU coreutils” Please reply to list if it's a mailing list post - http://shlom.in/reply .
[Newbie]Would like to contribute
On 16/02/2016 14:32, Shlomi Fish wrote:
Hi Kevin, > > first of all - welcome aboard - and I hope you'll enjoy
contributing to GIMP. > Also thanks to Jehan for providing some introductory links and guidance. > > See below for an important note. >
On Tue, 16 Feb 2016 07:53:56 +0100 > Kevin Pellet
wrote: > >> Hi Jehan, >> >> Thanks for the links
and the tips! >> >> I'm going to take a look at the bugzilla, I suppose
there'll be enough >> work for me ;) I have to configure xchat to
connect in the irc (it's >> been a while since I use Mibbit for some irc
channels...) >> > > The original XChat has become unmaintained for
several good years now. Luckily, > there are some active forks of it
including https://hexchat.github.io/ , which > should be used instead,
because the original XChat may have some unfixed bugs, > including
security ones. I am using HexChat. > > There is a list of some other
prominent IRC clients here - >
http://www.shlomifish.org/open-source/resources/networking-clients/ . >
Regards, > > Shlomi Fish >
Hi Shlomi,
Thank you! =D Yeah I know I just understood my mistake but I meant Hexchat of course, I don't use XChat since a long time ;)
Have a nice day!
Kevin Pellet (Ilphrin) ilphrin@autistici.org www.ilphrin.com
[Newbie]Would like to contribute
Hi Kevin,
On Tue, 16 Feb 2016 19:53:17 +0100 Kevin Pellet wrote:
On 16/02/2016 14:32, Shlomi Fish wrote:
Hi Kevin, > > first of all - welcome aboard - and I hope you'll enjoy
contributing to GIMP. > Also thanks to Jehan for providing some introductory links and guidance. > > See below for an important note. >
On Tue, 16 Feb 2016 07:53:56 +0100 > Kevin Pellet
wrote: > >> Hi Jehan, >> >> Thanks for the links and the tips! >> >> I'm going to take a look at the bugzilla, I suppose there'll be enough >> work for me ;) I have to configure xchat to connect in the irc (it's >> been a while since I use Mibbit for some irc channels...) >> > > The original XChat has become unmaintained for several good years now. Luckily, > there are some active forks of it including https://hexchat.github.io/ , which > should be used instead, because the original XChat may have some unfixed bugs, > including security ones. I am using HexChat. > > There is a list of some other prominent IRC clients here - >
http://www.shlomifish.org/open-source/resources/networking-clients/ . >Regards, > > Shlomi Fish >
Hi Shlomi,
Thank you! =D Yeah I know I just understood my mistake but I meant Hexchat of course, I don't use XChat since a long time ;)
Ah, I see. That's good.
Have a nice day!
Thanks! You too.
Regards , -- Shlomi
----------------------------------------------------------------- Shlomi Fish http://www.shlomifish.org/ Apple Inc. is Evil - http://www.shlomifish.org/open-source/anti/apple/ Yesterday I asked one of my students if she knew what an encyclopedia is, and she said: “Is it something like Wikipedia?”. — http://twitter.com/alisonclement/status/8421314259 Please reply to list if it's a mailing list post - http://shlom.in/reply .
