Revised May 10, 2012
Experienced Drupal developers who wish to work on the back-end of a Community Weaver site hosted on timebanks.org may be granted privileged access to the site's Site-Admin tools after approval of the TimeBank Affiliate of the site, TimeBanks USA, and Geek Gene. (The TimeBank Affiliate is the individual responsible from the TimeBank that signed the agreement with TimeBanks USA.)
To be approved as a Site-Administrator you must read and agree to the following Privileged Access Agreement and fill out the application below to request access. This agreement is intended to make sure you are fully aware, before you begin, of the responsibilities and the potential damage (and costs, and lack of sleep) you could incur for your site as a Site-Admin.
Site-Administrators are requested to ensure that the adaptations made to the site support the Core Values of TimeBanking and Coproduction, which includes building on assets, redefining work, reciprocity, community, respect, and one hour equals one hour.
Site-Administrators will be responsible for fixing any problems that are the result of changes they make to the site. If you cannot fix the problem, this may incur costs for professional support. We ask that you only make changes for which you feel confident that your actions will not cause any problems for your Community Weaver site or for the entire system.
THE AGREEMENT
Privileged access enables an individual to take actions which may affect computing systems, network communication, or the accounts, files, data, or processes of other users on the Community Weaver sites and related server. Privileged access is typically granted to system administrators, network administrators, staff performing computing account administration, or other such employees whose duties require special privileges over a computing system or network.
Individuals with privileged access must respect the rights of the system users, respect the integrity of the Timebank's Server and related physical resources, and comply with any relevant laws or regulations. Individuals also have an obligation to keep themselves informed regarding any procedures, business practices, and operational guidelines pertaining to the activities of their individual Community Weaver website instance.
I. GENERAL PROVISIONS
1. In the event certain damage is incurred to your individual Community Weaver site after privileged permissions are granted and you require the help of Geek Gene LLC to repair that damage, you agree to pay Geek Gene LLC's hourly rate of $80/hr for any required fixes to your site. Emergency fixes or support outside of normal business hours will be charged a rate of $125/hr to compensate for extra rations of cheetos and mountain dew.
2. In the event certain damage is incurred to the entire Community Weaver site which is caused by your activities with privileged permissions which requires the help of Geek Gene LLC to repair that damage, you agree to pay Geek Gene LLC's hourly rate of $80/hr for any required fixes to your site. Emergency fixes or support outside of normal business hours will be charged a rate of $125/hr.
3. Privileged access is granted only to authorized individuals. Privileged access shall be granted to individuals only after they have read and signed the Site-Admin Access Agreement (“Agreement”).
4. Privileged access may be used only to perform assigned jobs on your specific Community Weaver site.
5. Privileged access may be granted to primary coordinators with limited experience as long as they are working under the guidance of a more experienced Site-Administrator (who has signed this agreement) and following good documented directions for each fix or enhancement.
6. All Community Weaver documentation supported by Timebanks USA will reflect "standard" Community Weaver only; not enhancements or changes by Site-Admins. The Site-Admin is responsible for informing the coordinators and members of their site about the new “features” and changes implemented on their site as well as providing information for updating their own version of their documentation.
7. Privileged access may be used to perform standard system-related duties only on machines and networks whose responsibility is part of assigned job duties. Examples include: Custom Drupal Development to existing Community Weaver Software on your Timebank site.
8. Privileged Site-Admin access may be used to grant, change, or deny resources, access, or privilege to other individuals only for authorized Community Weaver account management activities.
9. If a Site-Administrator grants Site-Admin privileges to another individual, the Site-Admin who signs this agreement:
II. TECHNICAL GUIDELINES FOR COMMUNITY WEAVER SITE-ADMINS
1. General Principles.
a. It is very important to understand that Community Weaver is operating in a multi-site environment on a server and that your work should only be done in your particular site's directory so that nothing gets broken for any of the other Community Weaver sites.
b. Writing bad PHP is the main way to cause harm to other sites on the Timebank's server. Please be selective about any PHP added and have EXTRA caution when doing so.
c. If methods other than using privileged access will accomplish an action, those other methods must be used unless the burden of time or other resources required clearly justifies using privileged access.
2. Drupal Core Modules.
When doing development work on your Community Weaver site do not disturb core or contributed Drupal modules, rather extend them with your own modules or you will lose your changes when we perform security updates.
3. Cloned Panels and Views
As a Site-Admin it is essential that you clone (make a copy) all of your panels and views and make changes only to your edited cloned panels and views on your individual site. Do not edit the original view or panel that was provided with CW 2.0. It is not enough to just create another display. Rather you need to clone the whole view. This requires setting each display to show under your new pages and that your menu structures matches your pages.
4. Future Changes to Community Weaver
a. All future changes to CW will be automated pushes. Those sites which have customized any of the views or panels that are being changed in the update will be skipped over. By cloning (or making a copy) of your views and panels this will ensure that our changes do not break your site. We are only going to do the automated push. Once changes have been made to the panels and views of your site it is a manual process for you , the Site-Admin, to integrate the changes.
b. If your site has been customized , TB USA will deliver the list of updates to you so that you can decide if you want those additional changes. If you decide you that you would like the changes pushed to your CW site, you can inform TBUSA who will then schedule the date of the new push. After the changes are pushed, you can look at the new changes and compare them to the old (your current copy) and then decide how you want to combine them or which you like better. As Site-Admin, it is your responsibility to integrate upgrades and feature changes.
c. In order to be able to carry out the above tasks, each Site-Admin must document, for themselves, each and every change thoroughly and in detail. There are two reasons for this. First to be able to “back out” of a change made that you realize is a mistake. Second, to be able to implement your changes that may have been affected by a Community Weaver update.
III. FTP GUIDELINES
a. Access to the Community Weaver Timebanks server via FTP only permits certain access. Specifically, as a Site-Admin, you will not have access to Drupal core or any of the contributed or custom modules shared across all the Timebank sites. This is a Drupal multi-site environment so each site has it's own directories. When you login, you will see only three symlinks, to /files, /modules and /themes. These links take you into directories just for your Timebank.
/files - contains files used only by your site. Mostly this is for user pictures and images uploaded to the site.
/modules - starts out empty. If you want to add any contributed or custom modules only usable by your site, this is where they go.
/themes - starts out empty. If you want to add your own theme(s) and/or css files, this is where they go.
b. These symlinks should suffice for most Drupal development you'll do on your site. However if there's a library you want to install that must go into a /library directory, please contact techsupport@timebanks.org and we can accommodate you.
c. Not all Site-Admin access or changes to your Drupal site will require FTP access. If you don't know what you're doing once you login to FTP, consider asking yourself if you really need FTP access. Another note, some FTP clients cannot navigate symlinks. If you see nothing in any of the directories when you first login, please try another FTP client.
The Emergency contact for all Timebank related issues is techsupport@timebanks.org.
IV. Changes in Technical and FTP Guidelines
As Community Weaver is further developed, the Technical and FTP Guidelines may need to be changed to fit the new technical situation. If that is necessary, Timebanks USA and GeekGene will inform you about the new guidelines which will then become part of this agreement.
AUTHORIZATION
The consent of TimeBanks USA, the The Geek Gene LLC and the TimeBank Affiliate of the Timebank you will be administering must approve you as Site-Administrator before this access will be set up for you.