|
Replies:
5
-
Last Post:
Feb 2, 2007 5:45 AM
by: palowoda
|
|
|
|
|
|
|
Re: Community participation
Posted:
Feb 1, 2007 12:34 PM
|
|
[No Body]
|
|
|
Posts:
6,810
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: Community participation
Posted:
Feb 1, 2007 12:34 PM
in response to: Guest
|
|
Peter Tribble writes:
> I think we need to advertise what projects or communities need help at any
> point in time, and for each community or project to identify key issues
> where extra hands would make a difference. At the moment it's very difficult
> even for those of us who've been involved with the project for a while to
> find this
> out, let alone someone coming in afresh.
I agree with this. In addition to (or perhaps instead of ;-}) some of
the standard boilerplate for the projects, there should be "help
wanted" areas, and there should be a roll-up of that information
available somewhere. I think that it'd help, and probably a good bit
more than oss-bite-size.
For what it's worth, I think part of this is "just" a cultural
problem. All of the projects are essentially implicit "help wanted"
invitations. You have to pay attention to the mailing lists, and ask
and offer to help to find out more.
(I can't speak for others, but I know that's true for me. I haven't
specifically said "here's what I expect others to do" because I'm
actually expecting others to see the projects and come calling ...)
--
James Carlson, Solaris Networking <james dot d dot carlson at sun dot com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Re: Re: Community participation
Posted:
Feb 1, 2007 11:18 PM
in response to: carlsonj
|
|
James Carlson wrote On 02/02/07 05:34,:
> Peter Tribble writes:
>
>>I think we need to advertise what projects or communities need help at any
>>point in time, and for each community or project to identify key issues
>>where extra hands would make a difference. At the moment it's very difficult
>>even for those of us who've been involved with the project for a while to
>>find this
>>out, let alone someone coming in afresh.
>
>
> I agree with this. In addition to (or perhaps instead of ;-}) some of
> the standard boilerplate for the projects, there should be "help
> wanted" areas, and there should be a roll-up of that information
> available somewhere. I think that it'd help, and probably a good bit
> more than oss-bite-size.
>
> For what it's worth, I think part of this is "just" a cultural
> problem. All of the projects are essentially implicit "help wanted"
> invitations. You have to pay attention to the mailing lists, and ask
> and offer to help to find out more.
>
> (I can't speak for others, but I know that's true for me. I haven't
> specifically said "here's what I expect others to do" because I'm
> actually expecting others to see the projects and come calling ...)
What if someone made it their business to go around and poke the
projects/communities and creates a centralized TTD list?
Jim
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
6,810
From:
US
Registered:
3/9/05
|
|
|
|
Re: Re: Community participation
Posted:
Feb 2, 2007 4:14 AM
in response to: jimgris
|
|
Jim Grisanzio writes:
> What if someone made it their business to go around and poke the
> projects/communities and creates a centralized TTD list?
I think that person would probably be a pest. Though some project
teams may have already factored out hunks of work that could be done
independently, many others have not. For them, it matters quite a bit
what sort of development skills or special interests the person asking
has. If the answer is "none," then he's probably not going to get a
sensible answer.
In quite a few cases, I think people approaching a project and
offering to help with it have an interest in where the project is
going and want to contribute _unique_ items. Things that, by
definition, the original project team wasn't seriously considering.
Thus I'd rather make it part of the project documentation task.
--
James Carlson, Solaris Networking <james dot d dot carlson at sun dot com>
Sun Microsystems / 1 Network Drive 71.232W Vox +1 781 442 2084
MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
3,835
From:
JP
Registered:
4/6/05
|
|
|
|
Re: Re: Community participation
Posted:
Feb 1, 2007 11:16 PM
in response to: Guest
|
|
Peter Tribble wrote On 02/02/07 05:23,:
> On 2/1/07, *Ben Rockwood* <benr at cuddletech dot com
> <mailto:benr at cuddletech dot com>> wrote:
>
> While that would be handy, we already have a good program in place,
> its just buried. I refer to "Bite Sized Bugs".
>
> ...
>
> The idea here is that if someone sits down on a Saturday afternoon
> and wants a challenge they pull up the list, pull one that looks
> tasty and start working on a solution. Its got to be super easy for
> people to get started this way.
>
>
> Actually, I think the oss-bite-sized stuff isn't helping. I really don't
> think that
> a complete newcomer to the community is going to be excited by a bunch
> of random bugs that ought to have been fixed years ago. And we haven't got
> hundreds of contributors who started out that way. Any thought that this
> process (maybe just in its current form) is a good one is just going to stop
> us developing a good system.
>
> I think we need to advertise what projects or communities need help at any
> point in time, and for each community or project to identify key issues
> where extra hands would make a difference. At the moment it's very difficult
> even for those of us who've been involved with the project for a while
> to find this
> out, let alone someone coming in afresh.
So, one place for people to look at for things to do. I absoulty think
we need to make it easier for new people to get around our place. I
mentioned a bug bounty program (not sure I like the term, but whatever)
to offer people some incentive to playin with some bugs. I'm not sure
what the incentive should be, though. Any suggestions? Or a contest of
some sort?
Jim
> People coming in are presumably doing so for a reason, and may have
> particular skills and interests. How do we make it easy for them to find
> the right place to contribute?
>
> We need a bit of structure for newcomers to fit themselves into. They'll
> branch out and won't need the framework once they've got comfortable.
_______________________________________________
opensolaris-discuss mailing list
opensolaris-discuss at opensolaris dot org
|
|
|
|
|
Posts:
352
From:
Registered:
5/1/05
|
|
|
|
Re: Re: Community participation
Posted:
Feb 2, 2007 5:45 AM
in response to: jimgris
To: OpenSolaris » discuss
|
|
>
>
> Peter Tribble wrote On 02/02/07 05:23,:
> > On 2/1/07, *Ben Rockwood* <benr at cuddletech dot com
> > <mailto:benr at cuddletech dot com>> wrote:
> >
> > While that would be handy, we already have a
> good program in place,
> > its just buried. I refer to "Bite Sized Bugs".
> >
> > ...
> >
> > The idea here is that if someone sits down on a
> Saturday afternoon
> > and wants a challenge they pull up the list,
> pull one that looks
> > tasty and start working on a solution. Its got
> to be super easy for
> > people to get started this way.
> >
> >
> > Actually, I think the oss-bite-sized stuff isn't
> helping. I really don't
> > think that
> > a complete newcomer to the community is going to be
> excited by a bunch
> > of random bugs that ought to have been fixed years
> ago. And we haven't got
> > hundreds of contributors who started out that way.
> Any thought that this
> > process (maybe just in its current form) is a good
> one is just going to stop
> > us developing a good system.
> >
> > I think we need to advertise what projects or
> communities need help at any
> > point in time, and for each community or project to
> identify key issues
> > where extra hands would make a difference. At the
> moment it's very difficult
> > even for those of us who've been involved with the
> project for a while
> > to find this
> > out, let alone someone coming in afresh.
>
>
> So, one place for people to look at for things to do.
> I absoulty think
> we need to make it easier for new people to get
> around our place. I
> mentioned a bug bounty program (not sure I like the
> term, but whatever)
> to offer people some incentive to playin with some
> bugs. I'm not sure
> what the incentive should be, though. Any
> suggestions? Or a contest of
> some sort?
>
The incentive would be to fix the bug database to work in open forum.
---Bob
|
|
|
|
|
