search

OperationCode / operationcode_old_site

Our open source website. We're on a mission to help the military community learn software development, enter the tech industry, and code the future.
https://www.operationcode.org/
MIT License
230 stars 156 forks source link

Build contracting portal #759

Open rickr opened 7 years ago

rickr commented 7 years ago

Businesses should be able to submit a proposal for a project to be worked on by our members.

Definitions

client - an Operation Code member that needs work to be done proposal - a unit of work to be done admin - an Operation Code member that will be maintaining the jobs portal member - an Operation Code member interested in working on a proposal

Scenarios

As a client

Proposals

In order to maintain quality each new proposal should move through several states. When a proposal first comes in it should be in the New state. An email should be sent to admins for each new proposal.

The next state will be In review. Admins will be reviewing the proposal to make sure it's valid and for more complex proposals possibly contact the client to identify milestones and timelines.

After the proposal is valid it will be moved to the Client Review state. In this state contacts will be drawn up and the client can verify the final proposal.

From 'Client Review' the client can chose to go to either the 'Ready' state or the 'Published' state. The only difference between the two states is Ready won't show up in the user proposal list, where Published will. A user should be able to transition from Ready to Published at any time.

During the Published state members will be able to apply to the proposal. Admins should contact each applicant to make sure they're capable of the required tasks and to determine what resources they might need.

From the Published state a client should be able to move to the Canceled state. This will close the proposal and no more actions can be taken.

From the Published state an admin should be able to move to the Accepted state. This means members have applied and been approved to work on the project and work can begin.

From the Accepted state an admin should be able to move to the In Progress state. This means members have begun work.

From the Accepted state an admin should be able to move to the Client Acceptance state. At this point work will be demonstrated to the client.

From Client Acceptance a client should be able to move to the Client Accepted state. This means the work demonstrated is valid and the project is complete. Any code or artifacts should be delivered.

From Client Acceptance a client should be able to move to the Changes Requested state. This means changes are needed to meet the client's needs. Admins should be notified to make sure the changes still fit the scope of the proposal.

From Changes Requested the client should be able to move to the Client Accepted state.

From Client Accepted an admin should be able to move to the Billing state.

From the Billing state an admin should be able to move to the Completed state.

MVP Criteria

sethbergman commented 7 years ago

I wasn't able to push to the other repo you created. https://github.com/OperationCode/job-portal

rickr commented 7 years ago

Can you try again?

sethbergman commented 7 years ago

It's been pushed to the requested repo, https://github.com/OperationCode/jobs.git and can be viewed here:

Demo: => Jobs Portal <=

davidmolina commented 7 years ago

👌🏻

On Aug 4, 2017, at 1:04 AM, Seth Bergman notifications@github.com wrote:

It's been pushed to the requested repo, https://github.com/OperationCode/jobs.git and can be viewed here:

Demo: => Jobs Portal <=

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.