workflow
Notes to Developers
I've been both developer and manager for years on both large and small projects with various sized teams. During the week to week management of these teams I tend to send little notes to help guide our work process. This week I have been breaking in a new team.
I thought it might be useful to other technical project managers and team leaders if I shared some of this week’s raw notes. I hope it’s useful for other managers to have a glimpse into the day to day notes of another in their same place.
Time Sheets
Please enter your time regularly into Fresh Books. Smaller more frequent time entries are preferred. Try to break them down by tickets and tasks in those tickets. Please always include the ticket number you were working on.
Please keep your entries up to date daily while on a project.
SVN
I believe in update and commit often.
Make sure you update and resolve conflicts before committing.
Enter in notes about what you are committing and when possible, enter the relevant ticket number.
Commits will auto deploy to the server within a few minutes. If you break something, you can roll it back but email the rest of the team to let us know so we can make sure to match our revision to the latest version on the dev server.
To roll back, log into [Spring Loops], choose the project, and then deploy the previous version number.
Remember that other devs are working in SVN too. So, update often, typically before starting a new change set. And commit often. I can help with any merging issues if you need it.
[Info here on how to contact me for an urgent need.]
Further Notes on SVN
The following is just a brief reminder about steps to take to not over write others work.
Building a Publishing Workflow with Scheduled Transitions at Node Creation
Introduction
The Need
Our clients and other Drupal site administrators would like to use the Workflow module to schedule transition states in their publishing workflow.
The Problem
Currently, within the Workflow module a node cannot be assigned a scheduled state change upon node creation. A node must be saved first, then edited a second time by the user.
After reading this comment in the Workflow module issue que: http://drupal.org/node/189572#comment-704334 I decided to try to add a little more automation to the process of creating a node and adding a scheduled state change.
In this Post
You’ll learn how to create a publishing workflow for your website, and how to improve the process of scheduling a transition change during node creation.
Let’s begin.
Note: This demonstration is build on Drupal 6. The process outlined below may be adapted for Drupal 5 install.
Install and Enable the Necessary Modules
1. Download, install, and enable the necessary third-party modules
o Workflow - http://drupal.org/project/workflow
o Token - http://drupal.org/project/token
o Token actions (part of Token module)
2. Enable Drupal’s core Trigger module @ /admin/build/modules
Set Your Permission Settings
Allow at least one user role a permission to schedule workflow transitions @ /admin/user/permissions#module-workflow
Building a Publishing Workflow with Scheduled Transitions at Node Creation
Introduction
The Need
Our clients and other Drupal site administrators would like to use the Workflow module to schedule transition states in their publishing workflow.
The Problem
Currently, within the Workflow module a node cannot be assigned a scheduled state change upon node creation. A node must be saved first, then edited a second time by the user.
After reading this comment in the Workflow module issue queue: http://drupal.org/node/189572#comment-704334 I decided to try to add a little more automation to the process of creating a node and adding a scheduled state change.
In this Post
You'll learn how to create a publishing workflow for your website, and how to improve the process of scheduling a transition change during node creation.
Let's begin.
Posted on TreeHouseAgency.com - Read more
