--- /dev/null
+HOW TO USE GIT FOR RELEASE TRANSLATION
+
+This year there are only two ways to submit your translations for the 9.1 Release: email, and Git on git.postgresql.org. Of these two, Git is preferred because:
+
+- You can version-control your own work
+- You can use it to do version control between multiple translators
+- Your translated documents won't get mangled by email servers
+
+Also, since Git is now the version control system for developing PostgreSQL, you might as well learn it.
+
+1. Community Account
+--------------------
+In order to use the git repo, you need a PostgreSQL.org community account. This is the same account you use on www.postgresql.org, planet.postgresql.org, and several other places (but not pgfoundry). If you do not already have one, obtain one here:
+
+http://www.postgresql.org/community/signup
+
+Once you have a community account, email Josh Berkus (josh@agliodbs.com) so that he can grant you write access to git.postgresql.org/press.
+
+2. Install Git
+--------------
+While you're waiting for your community account with Git access, please install Git on your workstation/laptop if you don't already have it. On Linux or FreeBSD this is simple through your packaging system. On Mac OSX, you should use Fink (http://www.finkproject.org/) or MacPorts (http://www.macports.org/) to install Git, or the DMG here: http://code.google.com/p/git-osx-installer/. For Windows users, there is a list of suggested Git clients here: http://kylecordes.com/2010/git-gui-client-windows and a help guide here: http://help.github.com/win-set-up-git/
+
+3. Clone Git Repo
+-----------------
+From the command line, switch to a directory where you want to work with the PR files. Then do:
+
+git clone ssh://git@git.postgresql.org/press.git
+
+This will make a full copy of the press repository, including the last several sets of release translations. It make take a few minutes.
+
+4. Create Directories
+---------------------
+You will be adding your translated versions to the directory press/releases/9.1/xx, where "xx" is your two-letter ISO language code. For example, if you're translating Portuguese, then add this directory:
+
+press/releases/9.1/pt
+
+***DO NOT save anything to the "translate" directory***
+
+5. Translate the Release
+------------------------
+Translate both files, presskit91.html and release.txt. Create the translated versions as presskit91.html and release.txt in your language directory (not, for example, presskit91.html.pt).
+
+NOTE: last year we tried creating a git branch for each language. This did not work well. So please make all of your edits on the "master" branch. Also, please be careful to edit ONLY files in your language directory in order to prevent making conflicting edits.
+
+6. Commit and Push
+------------------
+First, from your language directory, do:
+
+git add *
+
+Then do:
+
+git commit -a
+
+This will bring up your default text editor to write a commit message. Please indicate in the commit message whether or not this is the final completed translation of your release and presskit, so I know when you're done.
+
+Finally, you need to sync your local copy with the git.postgresql.org server, with:
+
+git push
+
+7. Repeat if Necessary
+----------------------
+If you are translating in several sessions, or coordinating with other volunteers with your same language, then you should do several commits and pushes. Do these as often as you like.
+
+8. Final Commit & Push
+----------------------
+When you are completely done translating the presskit and release, then do a final commit and push with a commit message like:
+
+"Translation of release and presskit for DE completed."
+
+This will let me know when you're done translating.
+
+9. If you run into trouble
+--------------------------
+Ask for help on the translators@postgresql.org mailing list.
\ No newline at end of file
--- /dev/null
+Logging In/Account Creation
+---------------------------------
+If you have never had an @postgresql.org account before, or for some reason
+can't get into yours, please e-mail josh@agliodbs.com a password which you want to use.
+
+Your Address
+----------------------------------
+Your e-mail address will be the 2-letter ISO country code for your country,
+followed by @postgresql.org. For example, Diogo has br@postgresql.org.
+The exceptions to this are Devrim, who has devrim@postgresql.org due to his
+work on the website, and Tatsuo/JPUG, who prefer to use their list address.
+ We will not be using people's personal addresses, because the @postgresql.org
+addresses make possible an easy transition from one regional contact to
+another. It also looks more professional.
+
+Appropriate Uses of Your @Postgresql.org address
+--------------------------------------------------------
+Your @postgresql.org address is intended strictly for use when doing volunteer
+advocacy for PostgreSQL.org. It is NOT intended for a general mailbox or
+business address; remember, it may be assigned to someone else at any time
+which you are unable to volunteer.
+ This can particularly be a challenge for consultants. My rule is, if you're
+answering queries from @postgresql.org, you can recommend your own business
+for consulting ... but you MUST mention other appropriate consultants in the
+area as well. Nor should you take referral fees for business referred
+through your @postgresql.org address. (Sorry if this seems pedantic, but
+there have already been some misunderstandings.)
+ I will be forwarding e-mails received from the public to your @postgresql.org
+address from time to time. This is much, much easier for me than keeping
+track of personal addresses. As such, it's important that you continue to
+check the address (see below) for the next year, or tell me when you are
+stopping.
+ Also, please remember that you are not personally able to make decisions on
+behalf of the whole PostgreSQL.org community. No-one is, not even the
+members of Core Team. We are a democratic organization. I have to tell
+reporters and businesspeople that all the time.
+
+How to Access Your PostgreSQL.org Address
+--------------------------------------------------
+WEB: Go to http://webmail.postgresql.org and log in. This gets you into
+RoundCube, a fairly slow but very full-featured webmail interface (which runs
+on postresql!). It is even multi-lingual.
+
+POP/IMAP: You can access mail.postgresql.org via POP or IMAP. You must:
+ Downloading Mail: authenticate as "username" to mail.postgresql.org
+ with your password.
+ e.g. login: cl password: ******** server: imap.postgresql.org.
+ Sending Mail: you must use SMTP authentication. Login as
+ "username@postgresql.org" to "smtp.postgresql.org" with
+ your mail password.
+
+You must now use SSL or STARTTLS encryption with all @postgresql.org accounts.
+
+Sharing Your @postgresql.org Account
+-----------------------------------------------
+Several regions, such as DE, have more than one person sharing an account to
+collaborate. There are two ways you can make this work:
+1) Use webmail/IMAP. Which messages are replied to and what has been
+recieved will be obvious.
+2) Use forwarding rules: set up forwarding to multiple accounts, and treat
+the @postgresql address like it was a mailing list.
+
+Forwarding E-mail
+------------------
+
+You can forward all email to your @postgresql.org email account to another account. This is recommended if you don't share a mailbox with other community volunteers, since mails to your @postgresql.org account can be rather infrequent.
+
+1. Log into webmail.postgresql.org.
+2. Select "Settings" in the upper right corner.
+3. Select the "Filters" tab
+4. If you're seeing a text editor with some cryptic code in it, click on the little gear icon in the lower left corner and select "Standard Editor" from the pop-up menu. If not, proceed.
+5. Click on the + symbol in the lower left corner.
+6. In the filter editor, give the filter the name "Autoforward"
+7. Select "All messages".
+8. Select "Redirect To" and enter your email address.
+9. Click "save".
+10. Click the gear near the lower left corner, and select "Activate this ruleset" from the pop-up menu.
+
+Deleting Huge Masses of Spam
+------------------------------------------------
+If you are not forwarding mail, your account can accumulated huge amounts of spam and become inoperative.
+
+Unfortunately, there is currently not a quick way for you to clean out your mailbox. The team is working on this.
+
projects / press.git / commitdiff