[GPC] Process for Creating a New Project (internally)

[Jason Li]

Justin,

A couple of ways to answer your question...

First - from a process perspective, both processes outlined in the previous
email were targeted at brand new projects. We have only loosely defined the
process for "existing" projects that want to come "into the fold" so to
speak. I imagine much of the process should be the same - but that's
certainly something we should discuss and formalize as a committee.

Second - from a logistics perspective, IIRC, SamuraiWTF is already hosted
at SourceForge? Existing projects can be "invited" into the OWASP
neighborhood (and they can likewise later leave the neighborhood as well).
So from a migration perspective, there shouldn't be much to do aside from
inviting the project, accepting the project, and then issuing an award for
the appropriate phase.

-Jason

On Wed, Feb 8, 2012 at 9:47 AM, Justin Searle <justin.searle at owasp.org>wrote:

> Jason, I'm getting ready to move SamuraiWTF over to an OWASP project
> in the coming weeks.  We may also be moving some sister projects like
> the newly launched MobiSec project, a live pentest DVD for testing
> mobile devices (Android, iOS, Blackberry, etc...).  When we are ready
> to start the process, should I use the current Google Docs
> application, or should I touch base to see if we have the new process
> ready?  In fact, If we have the new process ready to go by the end of
> the February, I'd be willing to put these projects through the trial
> ringer.
>
>
>
> On Thu, Feb 2, 2012 at 4:11 PM, Jason Li <jason.li at owasp.org> wrote:
> > As promised from the GPC call today (with 48 minutes to spare on my
> > self-imposed 7pm Eastern deadline).
> >
> > Legacy Process (a summary of the process that Paulo went through to
> > establish a new project):
> > 1) Project leader requests new project
> > 2) Paulo sends email to request project details
> > 3) Leader sends back details
> > 4) Paulo forwards to GPC and requests feedback
> > 5a) No feedback materializes
> > 5b) GPC member asks questions; repeat steps 2-4
> > 6) Paulo create accounts for project leader
> >     a. @owasp.org account
> >     b. Mailman project mailing list
> >     c. Confirm self-provisioned Wiki account
> > 7) Paulo creates Blank Project Page on Wiki
> >     a. Add GPC Project Details page with details from project request
> > (/Projects/PROJECT_NAME using Template:Project About structure)
> >     b. Create redirect page for Project Roadmap
> > (/Projects/PROJECT_NAME/Roadmap)
> >     c. Create redirect page for Releases (if applicable)
> >
> (/Projects/PROJECT_NAME/Releases/Current, /Projects/PROJECT_NAME/Releases/Last
> > Reviewed using Template:Release structure)
> >     d. Create redirect page for Release Notes (if applicable)
> > (/Projects/PROJECT_NAME/Releases/VERSION/Notes)
> >     e. Create blank wiki page with tabbed template structure for project
> > home page
> >     f. Tag project page with appropriate category
> >     g. Add wiki page to project listing page
> >     h. (Optional) Add to Paulo's Projects Dashboard wiki pages
> >     i. User populates content
> > 8) Paulo informs user of wiki page, mailing list, accounts, etc
> > 9) Paulo announces to leader's list new project
> >
> > There were obviously some inefficiencies around steps 2-5 due to
> volunteer
> > latency. Additionally, step 7 is rather unwieldy for the uninitiated wiki
> > user.
> >
> > Transition Process:
> > 1) Project Request arrives via form (http://sl.owasp.org/new-project)
> > 2) ...
> > 3) SUCCESS!
> >
> > Clearly we have some work to do to flesh out the transition process...
> >
> > Draft Future Process:
> > 1) Project Request arrives via form (http://sl.owasp.org/new-project)
> > 2) Project request is posted to a public forum for community
> > feedback. Barring obvious violations of OWASP principles, project is
> > automatically approved after 7 days
> > 3) Accounts are created for project leader
> >     a. @owasp.org account
> >     b. SourceForge account (self provisioned?)
> > 4) Project is created in SourceForge
> >     a. Populate details based on project request form
> >     b. Assign "OWASP Incubator" award to project
> >     c. Assign project ownership to user
> >     d. User populates content (can choose to leverage SF project tools or
> > not)
> >     e. Project is automatically included in OWASP Neighborhood and
> displayed
> > as part of project listings
> > 5) Inform user
> > 6) Announce to community
> >
> > -Jason
>
>
>
> --
> Justin Searle
> Managing Partner - UtiliSec
> 801-784-2052
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.owasp.org/pipermail/global-projects-committee/attachments/20120211/15c45441/attachment.html>