Re: Organizing projects in

Hi, Scott:

Yes, I will resolve the Beta_Requirements
/WPD:Project_Status <>
issue. I'm not sure we'll need a beta requirements page on docs.* going
forward, because it'll be fully outlined with great visualization on

As far as renaming WPD:Proposals to WPD:Projects: The original purpose of
WPD:Proposals was to allow anyone to post a proposal within our namespace,
and not have to go to github or google docs or wherever. It's like a
sketching area. I don't think we'll need a WPD:Projects area, because as
soon as a proposal is accepted, it, and all of it's related issues, can move
to project.*

Regarding bundling these meta pages: I agree. I will be working on the site
map, so it'll be interesting to discover more pages!

Makes sense?


From:  Scott Rowe <>
Date:  Wednesday, March 20, 2013 2:21 PM
To:  julee <>
Cc:  "" <>
Subject:  Re: Organizing projects in

Hi Julee, 

There are two documents that relate to the overall status of the project:

Could you resolve the differences between these and make one document?

Also, I've been gathering various WPD: pages under either WPD:Community or
WPD:Proposals in an attempt to put some sanity into the organization of
these "meta pages." With a lack of navigation and search, it's awfully hard
to keep track of these if they are just created anywhere.

Could you put the "Project_Status/Beta_Requirements" page under

I was thinking of renaming WPD:Proposals to WPD:Projects; do you think
that's a good idea, too?


On Wed, Mar 20, 2013 at 1:02 PM, Julee <> wrote:
> Hi, everyone:
> To help get <>  finished
> and to get our beta work fully integrated[1], I've created a proposal for how
> we might set up projects:
> I'll work with Garbee to see what we can actually do with The Bug Genie.
> Please let us know what you think.
> Regards.
> Julee
> [1]
> ----------------------------
> @adobejulee

Received on Wednesday, 20 March 2013 21:42:26 UTC