Author: hwright
Date: Thu May 27 15:01:42 2010
New Revision: 948856
URL: http://svn.apache.org/viewvc?rev=948856&view=rev
Log:
Add some brief thoughts about repository-dictated configuration.
* notes/repos-dictated-config:
New.
Added:
subversion/trunk/notes/repos-dictated-config (with props)
Added: subversion/trunk/notes/repos-dictated-config
URL:
http://svn.apache.org/viewvc/subversion/trunk/notes/repos-dictated-config?rev=948856&view=auto
==============================================================================
--- subversion/trunk/notes/repos-dictated-config (added)
+++ subversion/trunk/notes/repos-dictated-config Thu May 27 15:01:42 2010
@@ -0,0 +1,46 @@
+Some thoughts on repository-dictated configuration
+
+Introduction
+============
+Many software development shops of non-trivial size desire to have an enforce
+a uniform configuration environment among the various clients which commit
+to their repositories. Although these shops my have the ability to control
+the environment on the client machines (dictating software versions, etc),
+relying up on the client for setting various configuration parameters can
+be time-consuming and problematic.
+
+Subversion already provides the means of enforcing much (but not all) of this
+configuration through the hook script mechanism. What our users desire is
+some way of having the server dictate a default or recommended configuration
+to clients. The parameters of interest typically come from the standard
+client-side config: things like global-excludes or auto-props. Allowing the
+administrator to store a default config on the server, which then gets pushed
+to the clients, would save both time and frustration.
+
+
+Behavioral specification
+========================
+The high-level behavior for repository-dictated configuration is relatively
+simple: the repository maintains a list of configuration parameters and
+values, and upon request, provides these to the client who then applies them
+appropriately.
+
+It should be noted that the configuration the server dictates is only a
+*suggestion* to the client. Clients may choose to override the suggestion
+with a configuration of their own, so appropriate server-side enforcement
+(often via hook scripts) is still recommended.
+
+
+Server-client transmission mechanism
+====================================
+[TODO]
+
+
+Server-side storage
+===================
+[TODO]
+
+
+Client-side storage
+===================
+[TODO]
Propchange: subversion/trunk/notes/repos-dictated-config
------------------------------------------------------------------------------
svn:eol-style = native
