j.fp.o design process strawman (criticism please!)
mmcgrath at redhat.com
Mon Jul 13 00:39:25 UTC 2009
On Sat, 11 Jul 2009, Mel Chua wrote:
> As I pore through Websites stuff tonight and think about how to tackle
> join.fp.o, I'm realizing that I have a very dim notion (actually, "dim" is
> generous) of what a good design process to go through for this kind of thing
> would be. http://en.wikipedia.org/wiki/Engineering_design_process seems to...
> not exactly fit, but I will stab in the dark and try to use it, and hope
> better alternatives present themselves.
> *Please* criticize this gameplan. It's put up here so that it can be ripped
> apart - I'm stuck on finding a better way to think about this, so I figured
> I'd try something (anything) and then let y'all tell me what my mistakes are.
> 1. Identify a need: "j.fp.o doesn't really get people to join fedora."
I've always found one of the biggest problems with joining is setting
expectations, fedora is a HUGe place. I think people get lost and don't
know what we expect from them. This is especially true of more passive
volunteers that just want to be told what to do. I've found they don't
know what to do, don't enjoy being told what to do and generally don't
have a good experience after joining.
More information about the websites