development issues

Greetings,

In the past two days Priyadarshan, Mallikarjun,
Medur, Aparajita, Tejaswi, Marek, and Jagrata
have discussed development issues. Here are
some items promised during those meetings.


1. Access to the staging Zope instance.

The staging Zope instance can be accessed at
http://zopestage.vasudevaservice.com

A user named "tester1" has access to the staging
Zope instance with password "1test3". This user
can view the Zope management screens.

This user's meaning in life is to confirm expected
staging Zope configurations prior to testing and to
diagnose the state of the staging Zope instance in
the event of unexpected behavior. As further ZMI
use cases arise for this user, additional permissions
may be opened up.

Useability tests are done through the web as an
anonymous user or other user, as the test requires.


2. Versions of Products, etc.

To view the current components of the production
Vasudeva Service Application, visit:

http://www.vasudevaservice.com/Members/Jagrata/manifest


3. Coding Standards and Conventions

For writing python code, refer to
http://www.python.org/peps/pep-0008.html

OR

http://www.vasudevaservice.com/documentation/recipes/pep-0008.html

For writing docstrings, refer to:
http://www.python.org/peps/pep-0257.html

OR

http://www.vasudevaservice.com/documentation/recipes/pep-0257.html


4. Zope Unit Testing

We will discuss this further; to read about a testing framework in
Plone, see

http://zope.org/Members/shh/TestRunner
(and other links under http://zope.org/Members/shh)
http://plone.org/documentation/apis/developer/HowToUnitTest


5. Subversion Documentation

http://www.vasudevaservice.com/documentation/recipes/book.pdf/file_view

--------------------------------------------------------------------------
This message is sent to you because you are subscribed to the mailing list <VasudevaService-K9y3B4ipJAZZAIG4hdpdiNBPR1lH4CV8@public.gmane.org>.