You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@openoffice.apache.org by Rainer Bielefeld <ra...@bielefeldundbuss.de> on 2014/02/10 11:56:27 UTC
Mentoring new Developers
Hi all,
I know 2 charts, 1 with good news
<https://issues.apache.org/ooo/reports.cgi?product=-All-&datasets=UNCONFIRMED>
and one with bad news:
<https://issues.apache.org/ooo/reports.cgi?product=-All-&datasets=CONFIRMED>
I think we urgently need some assistance for the core developers by
interested newbie developers Does AOO have a systematic approach how to
interest new willing developers and to make sure that they have some
sense of achievement when they start? And is that promoted at prominent
places?
Of course I know <http://openoffice.apache.org/get-involved.html>, but
to me that all sounds bureaucratic and not very inviting.
I think we (additionally) need an alternative approach, let's call it
"Easy Patches". My experience (as a not-developer, but engaged QA
member) is that smaller UI-patches are a nice way to get some first
experience with th code of the project; And mentoring for newbies does
not cost too much time, a simple "you find the code in xy area" and a
review of the patch should be enough in most cases.
Examples for bugs what might need an easy patch might be these [1], I
think there are a lot more.
A part of this idea is to create a short introduction in the Wiki with
an automatically generated list of such promising Easy Patch Bug
reports, some developers willing to mentor and a very short instruction
how to start some first steps to create a patch.
Ideas, concerns, interest to support something like this?
Best regards
Rainer
Used Hyperlinks:
[1]
<https://issues.apache.org/ooo/buglist.cgi?bug_id=124200%2C124186%2C124054%2C124046%2C124012%2C120850%2C89934%2C124183%2C124119%2C124035%2C123931%2C122712&list_id=123278>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
Re: Mentoring new Developers
Posted by Rob Weir <ro...@apache.org>.
On Mon, Feb 10, 2014 at 5:56 AM, Rainer Bielefeld
<ra...@bielefeldundbuss.de> wrote:
> Hi all,
>
> I know 2 charts, 1 with good news
> <https://issues.apache.org/ooo/reports.cgi?product=-All-&datasets=UNCONFIRMED>
> and one with bad news:
> <https://issues.apache.org/ooo/reports.cgi?product=-All-&datasets=CONFIRMED>
>
> I think we urgently need some assistance for the core developers by
> interested newbie developers Does AOO have a systematic approach how to
> interest new willing developers and to make sure that they have some sense
> of achievement when they start? And is that promoted at prominent places?
>
We send new developers to this page, which shows them how to get
started with their first build:
http://openoffice.apache.org/orientation/intro-development.html
> Of course I know <http://openoffice.apache.org/get-involved.html>, but to me
> that all sounds bureaucratic and not very inviting.
>
> I think we (additionally) need an alternative approach, let's call it "Easy
> Patches". My experience (as a not-developer, but engaged QA member) is that
> smaller UI-patches are a nice way to get some first experience with th code
> of the project; And mentoring for newbies does not cost too much time, a
> simple "you find the code in xy area" and a review of the patch should be
> enough in most cases.
>
We have something like this as well. We use the "developer
difficulty" field in Bugzilla to mark bugs that are "easy" or
"simple". These are the ones we point new developers to.
> Examples for bugs what might need an easy patch might be these [1], I think
> there are a lot more.
>
Some of these might be candidates for "easy hacks". I'll take a look.
> A part of this idea is to create a short introduction in the Wiki with an
> automatically generated list of such promising Easy Patch Bug reports, some
> developers willing to mentor and a very short instruction how to start some
> first steps to create a patch.
>
If we do it via Bugzilla then getting a report is easy. In fact it
can be a simple link to a query, yes?
Regards,
-Rob
> Ideas, concerns, interest to support something like this?
>
> Best regards
>
> Rainer
>
>
>
>
> Used Hyperlinks:
>
> [1]
> <https://issues.apache.org/ooo/buglist.cgi?bug_id=124200%2C124186%2C124054%2C124046%2C124012%2C120850%2C89934%2C124183%2C124119%2C124035%2C123931%2C122712&list_id=123278>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
> For additional commands, e-mail: dev-help@openoffice.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@openoffice.apache.org
For additional commands, e-mail: dev-help@openoffice.apache.org
RE: Mentoring new Developers
Posted by "Amin Jacek Pedziwiater,ASUSCOREURUS,�:IBMM" <am...@mm.pl>.
2 with good news
must be developed anyway
http://800notes.com/Phone.aspx/1-742-000-5896#p17267240
6941741903
; b touch.us
oo_=RECONFIRMED
-----Original Message-----
From: Rainer Bielefeld
[mailto:rainerbielefeld_ooo_qa@bielefeldundbuss.de]
Sent: 10 February, 2014 11:56 AM
To: dev@openoffice.apache.org
Cc: qa@openoffice.apache.org
Subject: Mentoring new Developers
Hi all,
I know 2 charts, 1 with good news
<https://issues.apache.org/ooo/reports.cgi?product=-All
-&datasets=UNCONFIRMED>
and one with bad news:
<https://issues.apache.org/ooo/reports.cgi?product=-All
-&datasets=CONFIRMED>
I think we urgently need some assistance for the core
developers by
interested newbie developers Does AOO have a systematic
approach how to
interest new willing developers and to make sure that
they have some
sense of achievement when they start? And is that
promoted at prominent
places?
Of course I know
<http://openoffice.apache.org/get-involved.html>, but
to me that all sounds bureaucratic and not very
inviting.
I think we (additionally) need an alternative approach,
let's call it
"Easy Patches". My experience (as a not-developer, but
engaged QA
member) is that smaller UI-patches are a nice way to
get some first
experience with th code of the project; And mentoring
for newbies does
not cost too much time, a simple "you find the code in
xy area" and a
review of the patch should be enough in most cases.
Examples for bugs what might need an easy patch might
be these [1], I
think there are a lot more.
A part of this idea is to create a short introduction
in the Wiki with
an automatically generated list of such promising Easy
Patch Bug
reports, some developers willing to mentor and a very
short instruction
how to start some first steps to create a patch.
Ideas, concerns, interest to support something like
this?
Best regards
Rainer
Used Hyperlinks:
[1]
<https://issues.apache.org/ooo/buglist.cgi?bug_id=12420
0%2C124186%2C124054%2C124046%2C124012%2C120850%2C89934%
2C124183%2C124119%2C124035%2C123931%2C122712&list_id=12
3278>
-------------------------------------------------------
--------------
To unsubscribe, e-mail:
qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail:
qa-help@openoffice.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: qa-unsubscribe@openoffice.apache.org
For additional commands, e-mail: qa-help@openoffice.apache.org