Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alternative Proposal for next steps #31

Open
des-des opened this issue Apr 30, 2017 · 3 comments
Open

Alternative Proposal for next steps #31

des-des opened this issue Apr 30, 2017 · 3 comments
Labels

Comments

@des-des
Copy link

des-des commented Apr 30, 2017

I have made some objections to this proposal: #30

I think it works better as a long term vision, and may not be the best idea right now. See there for details.

  1. Our spend rate will be set against income.
    • We should set aside a percentage of incoming project budget for the coop
    • Once a sprint has been delivered and paid for in full, if we have not gone over budget and have the planned excess leftover, we will scope the work that we think will most effectively further the aims of the coop.
  2. Everybody should be fully reimbursed for their time, as long as that time and tasks undertaken have been agreed and budgeted before they are undertaken.
    • In the case that someone is owed money by the coop, their payment should be the main priority of project budget excess.
@nogainbar
Copy link

nogainbar commented May 1, 2017

@des-des I like this.
I agree that for now its going to perhaps be hard to execute what @bradreeder suggested in issue #30, I see especially a problem with the full time proposal - as it seems that you @des-des, @sohilpandya and @bradreeder cannot at the moment commit full time and will have to do it on a part time basis.

My situation is pretty flexible at the moment - I can commit full time which would mean figuring out what that role exactly entails but I possibly can also consider a part-time role, depending on whether I can get the rest of my income from elsewhere (freelance gigs that I get)

I feel like your point

Once a sprint has been delivered and paid for in full, if we have not gone over budget and have the planned excess leftover, we will scope the work that we think will most effectively further the aims of the coop.

is a good one for now as these type of coop tasks are still to be defined and we dont all have a clear idea of what that actually means (in terms of time and budget)

At this point I would also want to bring up another point which is that for me its REALLY important right now to understand if our dev team is solid enough because as it stands, the people who are interested in writing code are:
@emilyb7
@jsms90
@des-des (tho part-time)

I would also be happy to contribute with front end code, especially css and html, but less on the solid architecture side and more on the 'fine tuning' of designs side.

What if for example, we have a situation which is highly likely, where two projects are running in parallel?? the anna freud project may well be overlapping at least for a bit with the NHS one.

@des-des
Copy link
Author

des-des commented May 3, 2017

@nogainbar on your point about our dev team, I think it should be okay. I think in a worst case scenario we have two options available to us. one is to recruiter a developer from fac9/10, as a freelance Dev from outside the coop, there may also be more experienced devs about we can pull in around the fac space, secondly, I may be available to work full time, since my main commitments here finish mid June.

@nogainbar
Copy link

lovely stuff @des-des! :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants