do + ldo for developers(full)

12
http://drupal.org Community DO & LDO as developer workspace GIT , sandbox , projects , documentation , patching

Upload: andriy-podanenko

Post on 15-Jan-2015

969 views

Category:

Education


2 download

DESCRIPTION

http://iteducation.com.ua/training/osnovy-razrabotki-modulei-dlya-drupal-7-0Вводная презентация с тренинга

TRANSCRIPT

Page 2: Do + ldo for developers(full)

DO + LDO Profile = CV + Developer ERP + Project Management + CRM

Page 3: Do + ldo for developers(full)

DO Profile tabs

Page 4: Do + ldo for developers(full)

LDO dashboard and tabs

Page 5: Do + ldo for developers(full)

LDO attribution

1. Install l10n_client and l10n_update for every user site and connect it to L.D.O under own user ID

2. Upload own translations into L.D.O translation queue

3. Upload user translated strings under Multiple Contributors account

4. Check in D.O. Profile an I contributed Drupal translations option.

5. Join http://drupal.ua/groups/i18n group at http://drupal.ua

Page 6: Do + ldo for developers(full)

DO Docs (saving work in user profile(count))Allowed for own site links (english only!)

Page 7: Do + ldo for developers(full)

http://drupal.org/node/add/project-project

Creating projects (sandbox or full)

Page 8: Do + ldo for developers(full)

DO GIT Attribution ( console!!! )

Page 9: Do + ldo for developers(full)

GIT push for created projectmkdir example_git_project_creationcd example_git_project_creationgit initecho "name = Example GIT project creation" > example_git_project_creation.infogit add example_git_project_creation.infogit commit -m "Initial commit."git remote add origin [email protected]:sandbox/podarok/1594268.gitgit push origin master

from http://drupal.org/project/1594268/git-instructions

After initial git push - project become as usual project page with full GIT instructions for pushing and patching

PS. And You can delete sandbox project despite full projectUsefull linkshttp://www.cheat-sheets.org/saved-copy/git-cheat-sheet.pdf

Page 10: Do + ldo for developers(full)

Creating patch for any project1. Clone the project into local directory

git clone --recursive --branch master [email protected]:project/dfw.gitcd dfw

2. Make changes in files with any type of editor3. Create .patch file for issue queue

git diff > [description]-[issue-number]-[comment-number].patch 4. Upload [description]-[issue-number]-[comment-number].patch file into previously created issue at DO for selected project http://drupal.org/node/add/project-issue/PROJECT_NAME

In every project there is a short cheat sheet for GIT instructionsFE. http://drupal.org/project/dfw/git-instructionsAny project http://drupal.org/project/PROJECT_NAME/git-instructions

Usefull Links● Advanced patch contributor guide● Troubleshooting 'git clone'● Identifying yourself to GIT● Branching and tagging● Coder module project

Page 11: Do + ldo for developers(full)

Fixing errors in Drupal code http://drupal.org/node/317

1. Search it at project issue queue2. Search it at http://drupal.org and local Drupal

community sites (FE http://drupal.ua) and search engines

3. Post an issue into issue queue with #123456 links to relative issues in issue description like "support request"

4. Make patch if You can fix it. 5. Make patch - You can fix it!6. Connect to other developers from

community for help making patch

Page 12: Do + ldo for developers(full)

Andriy Podanenko @podarok

Questions?