Be a mentor!

NAVIGATION

CATEGORIES

REFERRENCE

If you have some good idea, Cilck and mail to us please...

LINKS

Home » KDE

Be a mentor!
13 answers - 805 bytes -
I'm working on
This page aims to be part of the entry for users who want to get
involved with kde. See for
the whole thing.
I currently have Junior Jobs as the first tasks for noobs to tackle,
is there anything else like that I can put up?
And please volunteer to be a mentor! Basically that means reply with
your name a one liner about what you do, and I put that up on this
page. Then a noob developer can mail you with a couple questions that
they're too embarassed to ask on the mailing lists and you can point
them in the right direction.
Mentoring is important! I wouldn't be here if it weren't for SoC and Lubos.
Thanks,
Will Entriken

>Visit #unsub to unsubscribe <<
No.1 | | 411 bytes | |
Will Entriken wrote:
And please volunteer to be a mentor! Basically that means reply with
your name a one liner about what you do, and I put that up on this
page. Then a noob developer can mail you with a couple questions that
they're too embarassed to ask on the mailing lists and you can point
them in the right direction.

Eike Hein (application developer; Konversation maintainer).
No.2 | | 458 bytes | |
2006/8/18, Will Entriken <kde.org (AT) phor (DOT) net>:
And please volunteer to be a mentor! Basically that means reply with
your name a one liner about what you do, and I put that up on this
page. Then a noob developer can mail you with a couple questions that
they're too embarassed to ask on the mailing lists and you can point
them in the right direction.

Peter Simonsson (application developer; K devel/Kivio maintainer)
No.3 | | 1757 bytes | |
Friday 18 August 2006 17:59, Will Entriken wrote:
I'm working on

This page aims to be part of the entry for users who want to get
involved with kde. See for
the whole thing.

I currently have Junior Jobs as the first tasks for noobs to tackle,
is there anything else like that I can put up?

And please volunteer to be a mentor! Basically that means reply with
your name a one liner about what you do, and I put that up on this
page. Then a noob developer can mail you with a couple questions that
they're too embarassed to ask on the mailing lists and you can point
them in the right direction.

Mentoring is important! I wouldn't be here if it weren't for SoC and Lubos.

Frank (application developer, Akregator maintainer)

I wonder if this could be merged with the kde-quality efforts
(http://quality.kde.org). The kde-quality mailing list was created as a
platform for new contributors, but due to the misleading name, it's also used
for discussing quality issues and reporting bugs. It was already planned
about a year ago to rename the list to something else and to use kde-quality
for what the name suggests, quality assurance and management (see [1] and
follow-ups).

Some suggestions for a new name were:

kde-new-people
kde-contributors
kde-new-contributors
join-kde

It would be really great to have a coherent welcome platform for people
willing to contribute.

Regards,

Frank

[1]

>Visit #unsub to unsubscribe <<

PGP SIGNATURE
Version: GnuPG v1.4.2.2 (GNU/Linux)

5yWa1htuYhATMLSvWa3BTMc=
=Nltz
PGP SIGNATURE
No.4 | | 1351 bytes | |
Hey everyone, thanks for the resounding support to be mentors!
Hopefully this site will go live in a couple week and you should start
getting contact from mentees. If you would please mail me about your
experience when this happens, I would appreciate it. If this work, I
would like to create a more formalized KDE mentoring program.

Frank (application developer, Akregator maintainer)

I wonder if this could be merged with the kde-quality efforts
(http://quality.kde.org). The kde-quality mailing list was created as a
platform for new contributors, but due to the misleading name, it's also used
for discussing quality issues and reporting bugs. It was already planned
about a year ago to rename the list to something else and to use kde-quality
for what the name suggests, quality assurance and management (see [1] and
follow-ups).

Some suggestions for a new name were:

kde-new-people
kde-contributors
kde-new-contributors
join-kde

It would be really great to have a coherent welcome platform for people
willing to contribute.

is kde-quality where noobs currently post questions? or do they post
to their respective project like kde-devel?

Thanks!
Will Entriken

>Visit #unsub to unsubscribe <<
No.5 | | 1144 bytes | |
Will Entriken wrote:
Hey everyone, thanks for the resounding support to be mentors!
Hopefully this site will go live in a couple week and you should start
getting contact from mentees. If you would please mail me about your
experience when this happens, I would appreciate it. If this work, I
would like to create a more formalized KDE mentoring program.

FWIW, I can only recommend mentoring: I've found in the
past that explaining things to new developers and answe-
ring seemingly naive questions makes me constantly re-
consider my own assumptions about things and helps me
understand my own thoughts better. I've become a much
better developer by assisting others in becoming better
developers, and continue to be. It's time worth spent
for completely selfish reasons alone; beyond that, it
helps tremendously in making KDE kick arse that much
thanks to a stronger workforce, of course =).

Plus, I wouldn't have gotten off the ground myself with-
out finding friendly people to privately bug about dumb
questions (which include Frank and Peter, I might add).
No.6 | | 881 bytes | |
Friday 18 August 2006 10:59, Will Entriken wrote:
I'm working on

This page aims to be part of the entry for users who want to get
involved with kde. See for
the whole thing.

I currently have Junior Jobs as the first tasks for noobs to tackle,
is there anything else like that I can put up?

And please volunteer to be a mentor! Basically that means reply with
your name a one liner about what you do, and I put that up on this
page. Then a noob developer can mail you with a couple questions that
they're too embarassed to ask on the mailing lists and you can point
them in the right direction.

Mentoring is important! I wouldn't be here if it weren't for SoC and Lubos.

Thanks,
Will Entriken

Matt Rogers (application and library developer; KDevelop Lead Maintainer;
Kopete Lead Developer)
No.7 | | 1850 bytes | |
Saturday 19 August 2006 17:34, Will Entriken wrote:

It would be really great to have a coherent welcome platform for people
willing to contribute.

is kde-quality where noobs currently post questions? or do they post
to their respective project like kde-devel?

from :

"The mailing list is the project's primary communication channel. There you
can ask for help in your activities, post your work (in order to to receive
peer review, announce yourself, and help other team members with the learning
process. If you want to ask for assistance in any KDE related tasks, you are
welcome to do so. If you want to know which KDE applications needs
assistence, please subscribe to the list."

It's very low traffic and I guess not known to all (potential) new
contributors. Most mails which are not about regressions and quality are
introductions of people interested to contribute, introducing themselves,
their background and their interests, looking for concrete tasks or a
subproject they can contribute to.

kde-devel is mostly about coding, and about special coding problems.
It's not that much useful if you are looking for something you can contribute
to, especially for non-hackers who want to contribute but don't have a strong
focus on a specific application or project area. A "beginner list" would be a
good place to get oriented when starting, asking for concrete tasks, to ask
the beginner questions you don't want to bother other lists with, etc.
Such a list could complement the personal mentor project.

Frank

>Visit #unsub to unsubscribe <<

PGP SIGNATURE
Version: GnuPG v1.4.2.2 (GNU/Linux)

5Hne2tHLJdIIc1YUrlmhZk=
=bRg2
PGP SIGNATURE
No.8 | | 597 bytes | |
Will Entriken wrote:

I currently have Junior Jobs as the first tasks for noobs to tackle,
is there anything else like that I can put up?

For the documentation section, you can point to the Documentation Primer:
.

Also, I don't know where it would fit in best, but a mention of bug triage
would be nice - it doesn't need coding skills, but it's kind
of "development" (and of course, very useful). There's a nice howto at:
.

Please feel free to list me as a mentor for both of these (phil (AT) kde (DOT) org)

Regards,
Philip
No.9 | | 1499 bytes | |
Saturday 19 August 2006 11:00, Matt Rogers wrote:
Friday 18 August 2006 10:59, Will Entriken wrote:
I'm working on

This page aims to be part of the entry for users who want to get
involved with kde. See for
the whole thing.

I currently have Junior Jobs as the first tasks for noobs to tackle,
is there anything else like that I can put up?

And please volunteer to be a mentor! Basically that means reply with
your name a one liner about what you do, and I put that up on this
page. Then a noob developer can mail you with a couple questions that
they're too embarassed to ask on the mailing lists and you can point
them in the right direction.

Mentoring is important! I wouldn't be here if it weren't for SoC and
Lubos.

Thanks,
Will Entriken

Matt Rogers (application and library developer; KDevelop Lead Maintainer;
Kopete Lead Developer)

I have been wanting to get more involved for awhile now and am very
appreciative of you for putting up this site. I have been studying my c++ and
qt quite extensively lately and can't wait for the day to lend more of hand.
Even creating docs or whatever I can do to help. I have finally settled in at
a job that gives me time to spend on working on development. Now if I could
just get the kids to leave me be for a few more hours things would really get
moving, heh. Thanks again for the great site and keep up the good owrk sir.
No.10 | | 1473 bytes | |
Hi lostson,

I have been wanting to get more involved for awhile now and am very
appreciative of you for putting up this site. I have been studying my c++
and qt quite extensively lately and can't wait for the day to lend more of
hand. Even creating docs or whatever I can do to help. I have finally
settled in at a job that gives me time to spend on working on development.
Now if I could just get the kids to leave me be for a few more hours
things would really get moving, heh. Thanks again for the great site and
keep up the good owrk sir.

Good luck with the C++ and Qt. If you're itching to get started with
something practical, an easy and quick way can be to do some bug triage:
pick an app you use (any small one is a good place to start), and take a
look on bugs.kde.org for bugs and wishlist items for that app. You can see
if you can reproduce bugs that have been reported, and perhaps you'll see a
wishlist that's easy to implement and want to start coding :-).

The other nice thing about bug triage is that it comes in little bitesize
chunks that you can do in the ten minutes that the kids leave you alone
for[1].

Here are some tips on bug triage:

If you have any other questions, please don't hesitate to ask.

Regards,
Philip

1. Disclaimer: I don't have kids, so I'm wildly guessing about the pattern
of bothering given by them
No.11 | | 1709 bytes | |
Sunday 20 August 2006 11:28, Philip Rodrigues wrote:
Hi lostson,

I have been wanting to get more involved for awhile now and am very
appreciative of you for putting up this site. I have been studying my c++
and qt quite extensively lately and can't wait for the day to lend more
of hand. Even creating docs or whatever I can do to help. I have finally
settled in at a job that gives me time to spend on working on
development. Now if I could just get the kids to leave me be for a few
more hours things would really get moving, heh. Thanks again for the
great site and keep up the good owrk sir.

Good luck with the C++ and Qt. If you're itching to get started with
something practical, an easy and quick way can be to do some bug triage:
pick an app you use (any small one is a good place to start), and take a
look on bugs.kde.org for bugs and wishlist items for that app. You can see
if you can reproduce bugs that have been reported, and perhaps you'll see a
wishlist that's easy to implement and want to start coding :-).

The other nice thing about bug triage is that it comes in little bitesize
chunks that you can do in the ten minutes that the kids leave you alone
for[1].

Here are some tips on bug triage:

>html

Thanks for the info and links will be getting into this later today

If you have any other questions, please don't hesitate to ask.

Regards,
Philip

1. Disclaimer: I don't have kids, so I'm wildly guessing about the pattern
of bothering given by them

The pattern is pretty much 24 hours a day, hehe.
No.12 | | 1678 bytes | |
Will Entriken wrote:
I'm working on

This page aims to be part of the entry for users who want to get
involved with kde. See for
the whole thing.

I currently have Junior Jobs as the first tasks for noobs to tackle,
is there anything else like that I can put up?

And please volunteer to be a mentor! Basically that means reply with
your name a one liner about what you do, and I put that up on this
page.

James Richard Tyrer, retired Electronic Engineer & CS. I was a very
good programmer -- I started using computers when you had to punch holes
in those damn cards.

Then a noob developer can mail you with a couple questions that
they're too embarassed to ask on the mailing lists and you can point
them in the right direction.

Mentoring is important! I wouldn't be here if it weren't for SoC and Lubos.

Yes, Mentoring is a very good idea. It would be a good thing if we had
an organized effort -- perhaps even a mailing list.

I can mentor. I can answer software design and engineering questions.
And, rant about quality. However, I can't really help much with the
specifics of Qt & KDE programing (I probably need a mentor for that as
well). If that doesn't make sense, I note that knowing a computer
language is neither a necessary nor a sufficient condition to know how
to construct a computer program. Just some words of wisdom I learned in
engineering college.

I would suggest that if possible you start with trying to fix bugs. It
may not be the most enjoyable work, but it needs doing and you will
learn a lot by doing it.
No.13 | | 1747 bytes | |
8/20/06, James Richard Tyrer <tyrerj (AT) acm (DOT) orgwrote:
Will Entriken wrote:
I'm working on

This page aims to be part of the entry for users who want to get
involved with kde. See for
the whole thing.

I currently have Junior Jobs as the first tasks for noobs to tackle,
is there anything else like that I can put up?

And please volunteer to be a mentor! Basically that means reply with
your name a one liner about what you do, and I put that up on this
page.

James Richard Tyrer, retired Electronic Engineer & CS. I was a very
good programmer -- I started using computers when you had to punch holes
in those damn cards.

Then a noob developer can mail you with a couple questions that
they're too embarassed to ask on the mailing lists and you can point
them in the right direction.

Mentoring is important! I wouldn't be here if it weren't for SoC and Lubos.

Yes, Mentoring is a very good idea. It would be a good thing if we had
an organized effort -- perhaps even a mailing list.

I can mentor. I can answer software design and engineering questions.
And, rant about quality. However, I can't really help much with the
specifics of Qt & KDE programing (I probably need a mentor for that as
well). If that doesn't make sense, I note that knowing a computer
language is neither a necessary nor a sufficient condition to know how
to construct a computer program. Just some words of wisdom I learned in
engineering college.

I would suggest that if possible you start with trying to fix bugs. It
may not be the most enjoyable work, but it needs doing and you will
learn a lot by doing it.

Re: Be a mentor!

EMSDN.COM

It's a question for 'Be a mentor!' under 'KDE'

KDE

Be a mentor!