[adobe-source-commits] sandbox/adobe-source/adobe/documentation/sources/structure contributing.dox,1.1,1.2

[Foster B. <fos...@us...>]

Update of /cvsroot/adobe-source/sandbox/adobe-source/adobe/documentation/sources/structure
In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv4121/adobe/documentation/sources/structure

Modified Files:
	contributing.dox 
Log Message:
bug fixes, additions to array_t, documentation update

Index: contributing.dox
===================================================================
RCS file: /cvsroot/adobe-source/sandbox/adobe-source/adobe/documentation/sources/structure/contributing.dox,v
retrieving revision 1.1
retrieving revision 1.2
diff -C2 -d -r1.1 -r1.2
*** contributing.dox	19 Mar 2005 00:16:42 -0000	1.1
--- contributing.dox	31 Mar 2005 18:51:01 -0000	1.2
***************
*** 2,21 ****
  We are very excited to allow other developers the opportunity to work on the Adobe Source Libraries with us. Here we will discuss the general guidelines we will use to manage the development and release of the Adobe Source Libraries.
  
! \section asl_contrib_guidelines Development Guidelines
  
  The fundamental philosophy by which we will manage development and contributions to the ASL is by a mainline/sandbox method.
  
! \subsection asl_contrib_guidelines_mainline The Mainline
  
  <code>./adobe-source</code> is the mainline trunk and is the latest official state of the Adobe Source Libraries. Currently Sean Parent and Foster Brereton will manage all the code changes that are made into this trunk.
  
! \subsection asl_contrib_guidelines_sandbox The Sandbox
! 
  <code>./sandbox</code> is a sibling directory to <code>./adobe-source</code> and is the main location for hacking. The main sandbox branch will be in <code>./sandbox/adobe-source</code>. Developers are encouraged to collaborate with other developers on code, but branching of the sandboxes is also acceptable. Sub-branches should reside in the sandbox folder.
  
! \subsection asl_contrib_guidelines_review The Review Process
  
  In order to have code merged from a sandbox to the mainline, the code must undergo a formal review process. Basically all this means is that you notify Sean or Foster of a change you would like to have propagated to the mainline trunk. They will examine your changes, review them, and provide necessary changes or comments. If the suggestion is ultimately accepted, they will merge the change back to the mainline branch.
  
  Hopefully this results in an environment in which people are comfortable working, ultimately resulting in the best code we can produce as a community. Please let us know if you have any questions or comments- we would love to hear them. Thank you again for the interest you have expressed in the Adobe Source Libraries and the contributions you have made thus far!
  */
--- 2,31 ----
  We are very excited to allow other developers the opportunity to work on the Adobe Source Libraries with us. Here we will discuss the general guidelines we will use to manage the development and release of the Adobe Source Libraries.
  
! \section asl_contrib_license_guidelines License Guidelines
! 
! All code contributions must be under the MIT license and copyright of the Adobe opensource project. By contributing code you agree that we can distribute the contribution under the terms of the MIT license, that it can be distributed without any royalties, copyright, trademark, patent or other legal lock ups. Open source means no discrimination against any group or individual that may wish to use the code.
! 
! \section asl_contrib_submit_guidelines Submission Guidelines
  
  The fundamental philosophy by which we will manage development and contributions to the ASL is by a mainline/sandbox method.
  
! \subsection asl_contrib_submit_mainline The Mainline
  
  <code>./adobe-source</code> is the mainline trunk and is the latest official state of the Adobe Source Libraries. Currently Sean Parent and Foster Brereton will manage all the code changes that are made into this trunk.
  
! \subsection asl_contrib_submit_sandbox The Sandbox
!  
  <code>./sandbox</code> is a sibling directory to <code>./adobe-source</code> and is the main location for hacking. The main sandbox branch will be in <code>./sandbox/adobe-source</code>. Developers are encouraged to collaborate with other developers on code, but branching of the sandboxes is also acceptable. Sub-branches should reside in the sandbox folder.
  
! \subsection asl_contrib_submit_review The Review Process
  
  In order to have code merged from a sandbox to the mainline, the code must undergo a formal review process. Basically all this means is that you notify Sean or Foster of a change you would like to have propagated to the mainline trunk. They will examine your changes, review them, and provide necessary changes or comments. If the suggestion is ultimately accepted, they will merge the change back to the mainline branch.
  
+ \section asl_contrib_coding_guidelines When in Rome...
+ 
+ Please try to keep the format of the code in line with the rest of the project. Code formatting is a highly-debated issue between programmers (even internally Adobe has many seasoned developers with widely differing formatting styles). We request code submissions to have as close to the same format as what is already present in the code base. Granted there are inconsistencies in the code base already- we are trying to keep it to a minimum going forward.
+ 
+ \section asl_contrib_conclusion Conclusion
+ 
  Hopefully this results in an environment in which people are comfortable working, ultimately resulting in the best code we can produce as a community. Please let us know if you have any questions or comments- we would love to hear them. Thank you again for the interest you have expressed in the Adobe Source Libraries and the contributions you have made thus far!
  */