Difference between revisions of "Websites/creativecommons.org"
m (Corrected the link to Transifex) |
|||
| (6 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
The [https://creativecommons.org creativecommons.org] site is our main website, which has significant traffic (.5m/month). | The [https://creativecommons.org creativecommons.org] site is our main website, which has significant traffic (.5m/month). | ||
| − | Because the site has many internal components that must inter-operate correctly for the site to function, and also due to the traffic load, the site must be carefully updated in a coordinated way. We have developed a weekly release schedule with different stages for development | + | Because the site has many internal components that must inter-operate correctly for the site to function, and also due to the traffic load, the site must be carefully updated in a coordinated way. We have developed a weekly release schedule with different stages for development and localization, which you can read about below. |
= Release Schedule = | = Release Schedule = | ||
| Line 10: | Line 10: | ||
;Development | ;Development | ||
| − | : Beginning with the Tuesday morning push, the source tree is re-opened for changes. Approved patches (changes) may be committed until the tree closes on Thursday night. | + | : Beginning with the Tuesday morning push, the source tree is re-opened for changes. Approved patches (changes) may be committed until the tree closes on Thursday night, but CC will endeavor to make changes to strings marked for localization by end of the day Tuesday where possible. |
;String Freeze | ;String Freeze | ||
| − | : At the end of Thursday (midnight Friday) the source tree enters a '''string freeze'''. This means that no changes are allowed which would modify or add strings marked for localization. This allows our translators 3 full days (including the weekend) to work on translations. | + | : At the end of Thursday (midnight Friday) the source tree enters a '''string freeze'''. This means that no changes are allowed which would modify or add strings marked for localization. This allows our translators a minimum of 3 full days (including the weekend) to work on translations, although as noted above, translators will typically have a full week to translate because CC will attempt to commit all changes to the English on Tuesdays. |
| − | : | + | :Note: changes which modify/add strings '''may''' land on a branch which can be merged at a later date (for a future release). |
| − | ; | + | ;Release |
| − | : | + | : Changes to the production site happen only on Tuesday mornings. Changes are not pushed to the live site at any other time, with the exception of emergency situations or any pre-approved releases (at the discretion of the module owner). |
| − | |||
| − | + | = Sources = | |
| − | + | Sources for the creativecommons.org site are available on [https://github.com/creativecommons/creativecommons.org GitHub]. Proposed changes can be submitted as pull requests to the appropriate module(s). | |
| − | = | + | = Editing Guide = |
| − | + | We've developed a [https://docs.google.com/a/creativecommons.org/document/d/1SJnLpEYR_Z6MlSSdCTDzW_ZIh3msvrCw3uZKUnLCd8c/edit#heading=h.87xn7dh4juh0 guide] explaining how to edit the website, step by step (assumes you have the necessary permissions to do so). | |
= Issues = | = Issues = | ||
| − | + | All issues, including both bugs (problems) as well as desired changes must be reported on the [https://github.com/creativecommons/creativecommons.org/issues GitHub issue tracker]. In case of emergency, please also email [mailto:webmaster@creativecommons.org webmaster@creativecommons.org]. | |
| + | |||
| + | Issues are evaluated at the weekly triage meeting, where we decide what we will work on, and in what order. | ||
| + | |||
| + | = Localization = | ||
| + | |||
| + | String localization is done on [https://www.transifex.com/nkinkade/CC/deeds-choosers/ Transifex]. Please contact a team member if you need to get set-up. | ||
| + | |||
| + | Strings are automatically updated every 15 minutes during the time the tree is open, from Tuesday morning (after the push to production) until the end of the string freeze on Tuesday morning. These changes are visible for testing on the [https://staging.creativecommons.org staging] site. | ||
Latest revision as of 13:55, 28 November 2016
The creativecommons.org site is our main website, which has significant traffic (.5m/month).
Because the site has many internal components that must inter-operate correctly for the site to function, and also due to the traffic load, the site must be carefully updated in a coordinated way. We have developed a weekly release schedule with different stages for development and localization, which you can read about below.
Release Schedule
All times in Pacific Time (GMT-8 or GMT-7, depending on daylight savings).
The release schedule repeats these stages weekly:
- Development
- Beginning with the Tuesday morning push, the source tree is re-opened for changes. Approved patches (changes) may be committed until the tree closes on Thursday night, but CC will endeavor to make changes to strings marked for localization by end of the day Tuesday where possible.
- String Freeze
- At the end of Thursday (midnight Friday) the source tree enters a string freeze. This means that no changes are allowed which would modify or add strings marked for localization. This allows our translators a minimum of 3 full days (including the weekend) to work on translations, although as noted above, translators will typically have a full week to translate because CC will attempt to commit all changes to the English on Tuesdays.
- Note: changes which modify/add strings may land on a branch which can be merged at a later date (for a future release).
- Release
- Changes to the production site happen only on Tuesday mornings. Changes are not pushed to the live site at any other time, with the exception of emergency situations or any pre-approved releases (at the discretion of the module owner).
Sources
Sources for the creativecommons.org site are available on GitHub. Proposed changes can be submitted as pull requests to the appropriate module(s).
Editing Guide
We've developed a guide explaining how to edit the website, step by step (assumes you have the necessary permissions to do so).
Issues
All issues, including both bugs (problems) as well as desired changes must be reported on the GitHub issue tracker. In case of emergency, please also email webmaster@creativecommons.org.
Issues are evaluated at the weekly triage meeting, where we decide what we will work on, and in what order.
Localization
String localization is done on Transifex. Please contact a team member if you need to get set-up.
Strings are automatically updated every 15 minutes during the time the tree is open, from Tuesday morning (after the push to production) until the end of the string freeze on Tuesday morning. These changes are visible for testing on the staging site.
