Distributed Proofreaders 29 titles preserved for the world!
  DP
ID: Password:  ·  Register  ·  Help  
 

Quick links

Task Center http://dphu.aladar.hu/c/tasks.php
Site Admins' mail alias dp-sa @ pgdp.net
developers' mailing list dproofreaders-devel@lists.sourceforge.net
cvs commits mailing list dproofreaders-commits@lists.sourceforge.net
developers' Jabber chat room pgdpdev@conference.jabber.org
general Jabber chat room pgdp@conference.jabber.org
your sandbox http://www.pgdp.org/~your_id/c
test site http://www.pgdp.org/c
production site http://dphu.aladar.hu/c

Development Process Guidelines

The purpose of these guidelines is to increase the efficiency and satisfaction of the DP developers, by reducing wasted effort and site code breakage.

  1. Use the Task Center to document what you are working on and the progress you are making. If you wish to start working on a problem/feature, check the Task Center to see if there is an existing Task which is related to or covers what you wish to work on. If there is, and it hasn't been assigned to anyone, assign it to yourself. If there isn't an existing Task, please create one.

    Be aware that, if a task is a Feature Request, it isn't necessarily a feature that lots of people want. In fact, many people might actively not want it. If you think a feature might be controversial or unpopular, feel free to discuss it on the developers' list.

  2. Note that sometimes, different tasks will involve similar or overlapping changes, so assigning yourself a task doesn't guarantee that you can work in blissful isolation. So use the developers' list as a back-up (or occasionally an alternative) to the coordination provided by the Task Center, and also as a forum for extended or wide-ranging conversations that don't fit well in task comments. In particular, be sure to mail to the list if the scope of your changes is not apparent from a task in the Task Center.

    If you need to get some quick feedback, try the developers' chat room.

  3. Develop your code using a CVS "working copy" on your home system and test changes in a "sandbox" on the test host.

    Before you start working on a change, update your CVS working copy and the snapshot in your sandbox from the CVS master on sourceforge.

    After that, do your editing in your working copy and use scp to copy changed files from your working copy to your sandbox. (If you need help with scp please contact pourlean in Jabber.) Note: If you copy the CVS versions of pinc/site_vars.php or pinc/udb_user.php into your sandbox, it will stop working. If you need to change either of these files, seek help from a Site Admin.

    If you do not have a sandbox set up on the test host and would like one, please form an orderly queue in pourlean's mailbox. She can create an account for you and walk you through the setup.

    Note that, so far, these are only code sandboxes: personal copies of the site code. They do not give you complete isolation, in that they (and the test site) share a single database and a single projects hierarchy. So be careful.

    It's a good idea to get other people to test your code while it's still just in your sandbox (not yet committed to CVS). Announce your changes to the developers' mailing list, including a list of modified files, a description of the changed functionality, and a link into your sandbox. (If your changes address a task in the Task Center, it would be handy to include a link to that too.) Jabberwockies in the general DP chat room are often good test subjects. Make sure they understand what specifically needs testing.

  4. Once initial testing is done, commit your changes to CVS. When supplying a comment for CVS, please add any relevant Task Center task IDs (e.g., "Fixed off-by-one error in 'your neighborhood'. (task #333)", or "Implements project-filtering feature requested in task #456."). If you commit multiple files at once, please ensure that the comment makes sense for each file. Lastly, note that a record of your commit will be mailed to the 'commits' mailing list, so make it a good one!

    Then go to your sandbox and refresh it from CVS, which should pull in your changes. Do a quick check to ensure that the commit process hasn't introduced any problems (e.g., you committed the wrong file, or you didn't commit all the right files, or there was a revision conflict that you didn't resolve well).

  5. If everything still works in your sandbox, contact the Site Admins to have your code installed to the test site. A Site Admin will make your changes visible at http://www.pgdp.org/c as time permits.

    You can then call for more thorough testing of the change in the DP Forums if needed.

    If problems arise during testing in the test site, hopefully you can fix them quickly. If not, we can back out your changes on the test site, and you can continue to work on the fix in your sandbox/home system.

    Once your change is working on the test site, please mark any associated tasks in the Task Center as implemented or fixed. However, leave them open and at 90% progress until the change is visible on the live site.

  6. If your change warrants immediate installation on the production site, contact an Site Admin, and they can make your change visible to the DP community. The associated tasks can then be closed in the Task Center.

This process is open to improvement and comments. If it doesn't work for you, or you can see places where it can be improved, please contact the developers' list or the Site Admins.


Provides a round curve for a navigation bar
Completed Projects:
 Mar 2018 - 0 
 Apr 2018 - 0 
 May 2018 - 0 
 Jun 2018 - 0 
 Jul 2018 - 0 
 Aug 2018 - 0 
 Sep 2018 - 0 
 Oct 2018 - 0 
 Nov 2018 - 0 
 Dec 2018 - 0 
 Jan 2019 - 0 
 Feb 2019 - 0 

More Statistics...

Donate to the Distributed Proofreaders Foundation
 
Copyright Distributed Proofreaders (Page Build Time: 0.004) Report a Bug