On 14 Sep 2011, at 13:19, Ross Gardler wrote:

> I'm working with a Wookie newbie right now. I'm a bit concerned about
> the entry points for different types of users. With the release of 0.9
> it has got really confusing for everyone. The main problem is that a
> single page is provided for both users and developers.
> 
> The developers page used to be really clean and simple, checkout the
> source, get these dependencies run ant and your done.
> 
> However, that page has now been hijacked to be the main download page
> for the project and as a result it is confusing - click on the source
> code link under "development" and you get taken to a download page for
> binaries, if you are patient enough you will scroll down and find
> development instructions.
> 
> A further complication is that the binary releases do not include any
> of the tools for building new widgets, checking out the source gives
> you these tools but if you are taking the step from user (binary
> release) to power user (building widgets) you will now have both the
> source and binary releases and you are probably running the binaries
> rather than the source.
> 
> I think we need to clearly separate out the different roles in our
> documentation and we need to provide a tools package for people moving
> to be power users (developing widgets).

That makes sense

> So, to this end I am going to add a new source download page, this
> will be for developers, lets keep it clean. I will also remove the
> developer related content from the download and quickstart page, we
> should keep that page focussed on users. At some point in the future I
> would like to see the widget building tools separated out from trunk
> and made into a separate package (but that can be discussed when
> someone has the time to do it).

I like the idea of widget building as a separate command-line application that 
could be downloaded with the binaries.

> 
> Ross
> 
> -- 
> Ross Gardler (@rgardler)
> Programme Leader (Open Development)
> OpenDirective http://opendirective.com

Reply via email to