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

Have a strategy on Mozactivate on next steps while we keep the momentum on the activities #497

Closed
4 tasks done
couci opened this issue Jan 24, 2017 · 4 comments
Closed
4 tasks done

Comments

@couci
Copy link
Contributor

couci commented Jan 24, 2017

Objective Goal:

Create a mozactivate strategy, while we keep promoting it to our Reps

Item list:

  • Mozactivate kick-off meeting (assigning roles and setting timing) has happened
  • Build a strategy on where we want the project to go (R:)
  • Analyse the survey that went out to 2016 (R:)
  • Decide on budget for mozactivate

Related Issues

[Reference meta issues and past issues] #

@couci couci added this to the Q1 HB1 - February 10th, 2017 milestone Jan 24, 2017
@couci couci self-assigned this Jan 24, 2017
@couci
Copy link
Contributor Author

couci commented Feb 3, 2017

Budget for mozactivate has been discussed with Lucy and the Review Team, will present suggestion on council this Tuesday. Strategy is being drafted here (right now internal and council view) next steps are being identified.
Subha is working on the analysis he will have it by the end of the day

@couci
Copy link
Contributor Author

couci commented Feb 6, 2017

@couci
Copy link
Contributor Author

couci commented Feb 6, 2017

Updating the items list based on the current timing needs. The fist strategy meeting has happened and now we are moving to assigning roles and setting time frames based on the strategy that has been defined.
This repo is going to be used to track high level tasks, we will use the mozactivate repo for in details tasks and technical site tasks

@couci
Copy link
Contributor Author

couci commented Feb 10, 2017

Meeting has happened, going to open github issue with next steps and responsible today. This can be closed

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

No branches or pull requests

1 participant