Confirmed users
34
edits
Reps/Council/Elections/Fall2013: Difference between revisions
Jump to navigation
Jump to search
→Reporting monthly on reps.mozilla.org consume to much time and no one actually read these reports. Is it really needed?
| Line 37: | Line 37: | ||
* '''Nikos''': First of all I'm not sure that no one read these reports. Mentors do, or at least they should :) We need a way of determining if a Rep is active or not on a regular basis. I agree though that the report system at its current form served its purpose well but it's time to move to something more efficient. Monthly reports indeed consume much time to fill and in several cases a Rep may not remember activities she/he did in the beginning of a month. What we need ia a continuous report workflow. We are already used of publishing small status updates in other aspects of our lives, about things we do. We need to implement a way that every Rep can report her/his activities even the day after the event, weather this is a link to blog post, a tweet, a gallery (or auto-fetch all these from the event's hashtag ;)), or just a quick post or event report right on reps portal. | * '''Nikos''': First of all I'm not sure that no one read these reports. Mentors do, or at least they should :) We need a way of determining if a Rep is active or not on a regular basis. I agree though that the report system at its current form served its purpose well but it's time to move to something more efficient. Monthly reports indeed consume much time to fill and in several cases a Rep may not remember activities she/he did in the beginning of a month. What we need ia a continuous report workflow. We are already used of publishing small status updates in other aspects of our lives, about things we do. We need to implement a way that every Rep can report her/his activities even the day after the event, weather this is a link to blog post, a tweet, a gallery (or auto-fetch all these from the event's hashtag ;)), or just a quick post or event report right on reps portal. | ||
* '''Sayak''': | * '''Sayak''': | ||
* '''Majda''': | * '''Majda''': Short answer: yes, reporting is needed! Monthly reports are the best way for mentors to keep track of what their mentees (you!) are up to. In my opinion, the solution isn't to get rid of reports, but rather to: | ||
** make it near-effortless to fill a report i.e. automate wherever possible. This is in constant improvement thanks to the web-dev efforts in the reps portal. For example: currently when a rep creates an event, or marks himself as an attendee, it is automatically added to his report. We should aim for the same kind of automation for blog posts, tweets and so on, until it becomes seemless to fill your reports. Reports shoudln't feel as such a pain in the neck, they don't have to include every little detail and can litterally take 5min to fill. | |||
** encourage mentors to comment on their mentees reports to acknowledge that they've read them or to congratulate the rep on their efforts. I totally get your concern, and already had mentees of mine ask me the exact same question about the usefulness of the reports and if somone actually reads them. Introducing this change helped a lot. As mentors, we DO read your reports, and we DO care. | |||
** remember that reports are also what you showcase to the world (and are for everyone to see). Otherwise, how is anyone going to learn about all your awesome efforts? | |||
* '''Gauthamraj''': Yes , it is really needed. To start with , what if someone says you aren’t not an active rep even though you are doing a great job ? Yes , you can share your blog post reports about your various activities as a Rep but what will happen if our blog got corrupted / deleted ( this personally happened to me ) ? How can I prove , I am active ? To be on the safer side , file the months reports in the portal very shortly not as huge essays ( like my answers here ) .So , we need to be a role model for other mozillians / student ambassadors / etc.. Rep should be the one who lead and show the path for others and doesn't EXPECT much ( it’s fine if none see our reports) but Mozilla will make sure you get what you deserve ! Anyways , more automations are one the way for reports such as you can fill up your reports using twitter :D Finally , in the selection of ROM these reports plays a crucial role. | * '''Gauthamraj''': Yes , it is really needed. To start with , what if someone says you aren’t not an active rep even though you are doing a great job ? Yes , you can share your blog post reports about your various activities as a Rep but what will happen if our blog got corrupted / deleted ( this personally happened to me ) ? How can I prove , I am active ? To be on the safer side , file the months reports in the portal very shortly not as huge essays ( like my answers here ) .So , we need to be a role model for other mozillians / student ambassadors / etc.. Rep should be the one who lead and show the path for others and doesn't EXPECT much ( it’s fine if none see our reports) but Mozilla will make sure you get what you deserve ! Anyways , more automations are one the way for reports such as you can fill up your reports using twitter :D Finally , in the selection of ROM these reports plays a crucial role. | ||
* '''Guillermo''': | * '''Guillermo''': | ||
==== Different Reps seem to have very different types of contributions. Should we make adjustments on the program based on this fact? ==== | ==== Different Reps seem to have very different types of contributions. Should we make adjustments on the program based on this fact? ==== | ||
* '''Nikos''': First we need to identify this diversity. Currently we have functional areas, where every Rep can state contribution areas where she/he is more interested at. We should take this one step further and make it more visible. If I want to know which other Reps contribute to Webmaker initiative I should be able to find out and communicate with them in an easy way. Different type of contributions often need different kind of approach. | * '''Nikos''': First we need to identify this diversity. Currently we have functional areas, where every Rep can state contribution areas where she/he is more interested at. We should take this one step further and make it more visible. If I want to know which other Reps contribute to Webmaker initiative I should be able to find out and communicate with them in an easy way. Different type of contributions often need different kind of approach. | ||