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

RepsNext: Meta Working Group #347

Closed
8 of 9 tasks
MichaelKohler opened this issue Feb 19, 2016 · 8 comments
Closed
8 of 9 tasks

RepsNext: Meta Working Group #347

MichaelKohler opened this issue Feb 19, 2016 · 8 comments

Comments

@MichaelKohler
Copy link
Member

Goal:

The goal of this working group is to track and answer the broad questions we have around overall, program-wide topics

Success:

All overall questions are answered and we have a plan on how things should work after that.

Related Issues & Links:

Roles:

Required:

  • Start discussion: Figure out where the role of the Reps portal is, how many resources there are for changes from the dev side → open a discourse topic (@Mte90, [medium], Due: Feb. 22)
  • Start discussion: Identify a plan on how to combine different specializations (this might change over the time with the work of the other groups) (@MichaelKohler, [medium], Due: Feb. 22)
  • Organize followup meeting to assign the next steps (@MichaelKohler, [medium], Due: Feb 23)
  • Definition of the process to join a specific specialization (general level) (@christos, [medium], Due: March 10)
  • Figure out a plan on how to do recognition to avoid specialization to be the only recognition (??, [medium], Due: March 20th)
  • Figure out the role of the reps portal in the new settings (@Mte90, [medium], Due: March 20th)
  • Define a plan on how to handle countries with only one/no Rep → not covering all specializations (??, [medium], Due: March 20th)
  • Define a suggestion on how to find a specific Rep with a certain kind of specialization (also consider MoCo teams, outside of Reps) (??, [medium], Due: March 26th)
  • Have final version of our answers (@MichaelKohler, [medium], Due: March 30th)
@ioana-chiorean
Copy link
Contributor

Do you need some help on this one @MichaelKohler?

@MichaelKohler
Copy link
Member Author

Do you need some help on this one @MichaelKohler?

@ioana-chiorean, of course, I would never say no to help :) I will start a conversation on Discourse regarding the combination of specializations tonight, maybe you could jump in there as a first step?

@ioana-chiorean
Copy link
Contributor

Sounds like a plan 🎉

@Mte90
Copy link

Mte90 commented Feb 24, 2016

For the Community Leadership track we are working to create a new survey for understand some feelings from the reps.
I think that we can join the force to create an unique survey.

Ticket: #374
Our working survey: https://docs.google.com/document/d/15GK_FTIPLTupf06ONdxH8szhNGiHT7HJeH3dTeWNxiQ/edit?usp=sharing

We can discuss that on the next meeting.

@MichaelKohler
Copy link
Member Author

The meeting notes from today have several next steps that are not directly documented above, but they would only clutter the "Required" section IMHO. All of these are "baby steps" towards the tasks defined above. https://discourse.mozilla-community.org/t/working-group-meta/7051/26?u=mkohler

@MichaelKohler
Copy link
Member Author

@MichaelKohler
Copy link
Member Author

@Mte90 will do the Reps portal discussion seperately

@Mte90
Copy link

Mte90 commented Apr 2, 2016

I started to write the document about Reps portal but is a draft and unfinished.
https://docs.google.com/document/d/1rghXJw4ulgmvFlEnm75p84F5KdXYqKYkTIE2F_grYaw/edit

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

4 participants