|
|
| (61 intermediate revisions by 3 users not shown) |
| Line 1: |
Line 1: |
| − | == General Team Wikis Info (all teams access)== | + | == [https://freecycle.org/pages/Teams/General General Team Wikis Info (all teams access)]== |
| − | *[[Team_Wikis:Do%27s_and_Don%27ts_for_Team_Members|Do's and don't for team members]]
| + | This page moved here: https://freecycle.org/pages/Teams/General |
| − | *[[MailSetup|Setting up your Freecycle.org email account]]
| |
| − | *[[Team_Wikis:Team directories|Team directories]]
| |
| − | *[[Training2.0|Training module]] and [[How_To_Use_Mod_Tools|How to use the Mod Tools]]
| |
| − | *[[How to Help|Using and editing the Freecycle Wiki]]
| |
| − | *[[General_Team_Wikis:Training_workflow|Training workflow]]
| |
| − | *[[Recruiting_new_local_mods|Recruiting new local moderators]]
| |
| − | *[[UK_Counties_and_Regions|List of UK Counties and GOA regions]]
| |
| − | *[[Team_Wiki:Group_Naming_Conventions|Group Naming Conventions]]
| |
| − | *[[Team_Wikis:Point-Centered_Groups|Explanation of the point-centered group concept]]
| |
| − | *[https://docs.google.com/spreadsheets/d/14K_P6lHsU8jW6U4u4RAPMxDgpQ4rkL8zuS6F07RlAZU/edit#gid=1660781233 List of all active Freecycle.org groups] and [https://www.google.com/maps/d/viewer?hl=en_US&mid=1UeA7zgRqIUpneA4yCLjDpIhAagw link to the map]
| |
| − | | |
| − | =Tech issue reporting process for team members =
| |
| − | *Member of IMOD/GOA watch group reports a problem to the moderator, GOA/IMOD refers member to myfreecyclesupport. GOA/IMOD can escalate major issues by going directly to GOACoordinator, Hub Coordinator or Hub Coordinator's assistant.
| |
| − | *Mod discovers a problem, [[Moderator_Resources#Technical_problems|mod reports it to FIOD]]
| |
| − | *Mod tells GOA there's a problem. If GOA can't fix it, refer mod to Sitemodhelp. GOA can escalate major issues by going through GOACoordinator/Hub Coordinator/Hub Coordinator's assistant.
| |
| − | *Team member has a problem, team member reports it to TL. TL confirms the issue by reproducing it. TL files a BT or asks Hub Coordinator/Hub Coordinator's assistant to file a BT. [[Team_Wikis:Team_member_tech_problems|Here is the information needed for reporting a problem.]]
| |
| − | *Mail issues: the tech team is unable to address problems that are not related to Freecycle.org's servers. If you are having a problem with Thunderbird that replicates on webmail, please report it. [[Team_Wikis:MailSetup#Email_Clients|Otherwise, please click here.]]
| |
| − | | |
| − | [[General_Team_Wikis:Issue_reporting_process|For those filing BTs, here is a workflow chart for prioritizing issues.]]
| |
| − | | |
| − | =Roles of Teams =
| |
| − | We have a check and balance system to ensure that each team fulfills its duties to the groups while staying within boundaries of their role. If a TFN team member is on one of the groups without prior approval, the appropriate Team Lead will resolve the situation.
| |
| − | | |
| − | | |
| − | == IMOD ==
| |
| − | | |
| − | IMOD team members may be on local groups using @freecycle.org addresses only. IMODs are not generally on groups with moderators except very briefly at GOA's request. Interimmod (Team Leaders only) is the only team with authority to remove moderators from groups, on request from GOA. Deron, the GOA Team Leader, the Outreach Coordinator and the Hub Coordinator may also remove moderators and will let Interimmod know. Interimmod is added to all headless IMOD groups.
| |
| − | | |
| − | IMOD21 is on groups with mods at GOA's request for vacation coverage.
| |
| − | | |
| − | == GOAs ==
| |
| − | | |
| − | GOAs should not be on any local groups (MyF or YG) except when a group is turned over to them by IMOD watch. They may only be on these groups using the GOA official @freecycle.org email address only and not a personal address. In this capacity, they may approve messages (often because it was flagged with a hot word), respond to emails, and remove spam. They should be sending recruitment ADMINs on a regular basis to find new mods.
| |
| − | | |
| − | GOASupport is added to groups with mods in training. GOASupport does not approve or reject posts and normally stays on a group for a week.
| |
| − | | |
| − | == INFO team ==
| |
| − | | |
| − | There are several members of the Info Team.
| |
| − | | |
| − | infocoordinator@freecycle.org has a wide variety of responsibilities, including helping to co-ordinate spam/scam complaints and technical inquiries from moderators and members.The person in this role is the 'official mouthpiece' of Freecycle on the FIOD discussion group and provides regular (weekly) reports to members.
| |
| − | | |
| − | SiteModHelp@freecycle.org helps troubleshoot technical problems on groups. Where a volunteer needs to enter a group to troubleshoot an issue in this capacity, permission is sought from the state/regional GOA first.
| |
| − | | |
| − | spamcontrol̊freecycle.org removes spam and scammers. This volunteer is not expected to need to join any local groups.
| |
| − | | |
| − | help@freecycle.org assists members with their inquiries and forwards emails to the regional/state GOA. This volunteer is not expected to need to join any local groups.
| |
| − | | |
| − | == NGA Team ==
| |
| − | | |
| − | NGAs are responsible for new applications for groups and will work with GOA to establish whether a new group is required and to set up the group. They use NGA1@freecycle.org, NGA2@freecycle.org, etc to email potential mods and other team members. NGAs use their personal IDs in GA like the GOAs do. Once the group is fully established and a local moderator or member of the IMOD team are on the group, this volunteer should leave the group.
| |
| − | | |
| − | == Programmers ==
| |
| − | | |
| − | Programmers--Steev Hise manages the site and has other help. Sometimes they join local groups to troubleshoot technical problems. It is unusual for them to be on a group for longer than 24 hours.
| |
