I really liked the idea of 'My First Bug'. I think we should take a
good look at what's open in JIRA and tag some well defined and
constrained bugs as "My First Bug". Then we could have a JIRA filter
that is shown on the Current Needs page. To make this strategy work
we'd have to ensure that someone is monitoring these bugs and when
patches are submitted we act quickly on them. I would think a nice
short list like top ten would be inviting.
Michelle
On 13-Mar-09, at 9:57 AM, Justin wrote:
A while back when the Mozilla guys dropped by to talk, they
mentioned that they have a process to get people started with
committing called something like "My First Bug".
I have been wanting to begin something like this for a while, but
have not yet.
I was thinking it would work something like this.
1) Begin submitting patches for easy to fix bugs.
(These could be one of the many "Trivial" issues we have jira)
2) Begin submitting bug fixes for harder issues
I would imagine that current committers would help these people out
and would eventually nominate them for commit access, when deemed
appropriate.
This is as far as I had been thinking, but now you raise the point
of these "Carrots". This process could then lead them to developing
the "Carrots".
Any thoughts?
- Justin
On 13-Mar-09, at 9:23 AM, Anastasia Cheetham wrote:
On 12-Mar-09, at 2:57 PM, Daphne Ogle wrote:
I .. came up with some additional design enhancements that could
be made to the list reorderer component: http://wiki.fluidproject.org/display/fluid/List+Reorderer+Wireframes
.
I believe those enhancements would be considered "Carrot
enhancements" for post March since the core team is already booked
for the 1.0 release. Has there been any thought as to how we
identify these yummy carrots? Perhaps we just need a dashboard-
style confluence page that lists and briefly describes these
carrots? Actually, how about adding them to the "Current needs"
page, http://wiki.fluidproject.org/display/fluid/Current+Needs?
A first step is to file JIRA tasks for the specific work to be
done, but you raise the excellent question of how do we foster more
active contributions from the wider community?
It think the Current Needs wiki page is a probably a good start.
Right now, it looks a bit sparse, and has an "Under Construction"
warning that would probably deter people. I think it's time we put
a bit of effort into this page, make it more inviting. We could
also link directly to its parent "Get Involved" page from the
website.
What do other people think?
--
Anastasia Cheetham [email protected]
Software Designer, Fluid Project http://fluidproject.org
Adaptive Technology Resource Centre / University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
------------------------------------------------------
Michelle D'Souza
Software Developer, Fluid Project
Adaptive Technology Resource Centre
University of Toronto
_______________________________________________________
fluid-work mailing list - [email protected]
To unsubscribe, change settings or access archives,
see http://fluidproject.org/mailman/listinfo/fluid-work
