Mailing-List: contact commits-help@subversion.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@subversion.apache.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: Apache subversion Wiki <commits@subversion.apache.org>
To: Apache subversion Wiki <commits@subversion.apache.org>
Date: Tue, 15 Jan 2013 19:44:44 -0000
Message-ID: <20130115194444.88495.29401@eos.apache.org>
Subject: 
 =?utf-8?q?=5BSubversion_Wiki=5D_Update_of_=22walkthroughDirectory=22_by_G?=
 =?utf-8?q?abrielaGibson?=
Auto-Submitted: auto-generated

Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Subversion Wiki" fo=
r change notification.

The "walkthroughDirectory" page has been changed by GabrielaGibson:
http://wiki.apache.org/subversion/walkthroughDirectory?action=3Ddiff&rev1=
=3D4&rev2=3D5

- SVN Walk-through Directory
+ =3D SVN Walk-through Directory -- UNIX =3D
+ Here you find simple walkthroughs for all things SVN on Unix.  There are =
also [[walkthroughDirectoryWindows|Windows]] and [[walkthroughMac|Mac]] wal=
kthrough directories.
  =

- [[Concept|walkthroughDirectoryConcept]]
+ =3D=3D=3D Programmming environments =3D=3D=3D
+  . [[walkthroughUnixC|C]], [[walkthroughUnixC++|C++]], [[walkthroughUnixJ=
ava|java]], [[walkthroughUnixML|ML]],[[walkthroughUnixOctave|Octave]]
  =

- [[Walkthrough Directory Project Page| walkthroughDirectoryProjectPage]]
+ =3D=3D=3D Documenting envinronments: =3D=3D=3D
+  . [[walkthroughUnixWebsite|Websites]], [[walkthroughUnixManuals|Manuals]=
],
  =

+  . (what else?)
- ----------
- A directory of walkthroughs by user goals:
  =

- The quality benchmark of usefulness is that the admin can phone in sick a=
nd get the apprentice(or the PHB) to fix whatever problem occurs with minim=
al phone support, using those walkthroughs.
+ =3D=3D=3D Office environments: =3D=3D=3D
+  . [[walkthroughUnixAccounting|Accounting]],(spreadsheets?) [[walkthrough=
UnixFormletters|Formletters]], [[walkthroughUnixBrochures|Brochures]],
  =

- The other goal is to set people of every kind of skill level up as quickl=
y as possible and to make it easy to get started and start being productive=
, without requiring them to read too much or learn things they do not need =
to know.  If we can get the initial time investment down to 60 minutes or l=
ess, that would be great.
+  . (why does (say) gnumeric not have an SVN dialog plugin?)
  =

- The walkthroughs are categorised by OS, windows users do not need to know=
 unix cmds and vice versa; then split those into useage categories -- someo=
ne who maintains a website will have different needs than a software house,=
 or someone who is using svn as an audit trail or backup device.
+ =3D=3D=3D Creative collaborative environments: =3D=3D=3D
+  . [[walkthroughUnixBook|Writing/editing a book]], [[walkthroughUnixPaper=
|writing/editing a scientific paper]]
  =

- Sub categories and their individual templates:
+ =3D=3D=3D Class room uses: =3D=3D=3D
+  . [[walkthroughUnixAudittrail|audittrail]] facilitate groupwork and prod=
uce an audit trail
  =

- a) programmming environment:
+ =3D=3D=3D Other uses: =3D=3D=3D
  =

-  . Is listing by languages/mixed env useful here?
-   . ie, does a (say) C shop have different needs to a place that uses ML
- =

- b) documenting envinronments:
- =

-  . websites Manuals (what else?)
- =

- c) office environments:
- =

-  . accounting (spreadsheets) forms/ boilerplate letter repository (why do=
es (say) gnumeric not have an SVN dialog plugin?)
- =

- d) creative collaborative environments:
- =

-  . writing/editing a book writing/editing a scientific paper
- =

- e) class room uses:
- =

-  . audit trail for group work, so you can see which student contributed w=
hat.
- =

- e) Other uses that currently elude me.
- =

- It's easy to add new categories and we can probably rope users into writi=
ng the walkthroughs for us, with only minimal editing on our part.  I know =
people keep a plethora of differnt walkthroughs on their web pages, but it'=
s best to strive for 'information supremacy'(a not quite monopoly I mean) h=
ere, since we're 'the horses mouth' (so to speak), we should be the first a=
ddress and also, in a way it is part of the marketing that convinces people=
 to use svn who until now had not considered that it would be useful to the=
m.
- =

- Aside questions:
- =

- How about offering a script to make a typical svn directory that is usefu=
l for their application?  If they will take our advice about the trunk set =
up, why not save their time with a script?  It also neatly serves to standa=
rdise svn usage.
- =

- Also offer poster type print out of the following for pinning on the wall=
 (plus of course, the website page):
- =

- General Walkthrough template:
- =

- ----------
- OS used:
- =

- Application of walkthrough(short desc):
- =

- general description of typical workflow for users' particular application=
(long desc):
- =

- downloading/installing:
- =

- creating a repository:
- =

- your first commit:
- =

- your first checkout:
- =

- subsequent commmits:
- =

- subsequent checkouts:
- =

- Now you're done with the set-up, here are the most frequently used comman=
ds:
- =

- reverting your work:
- =

- making a patch:
- =

- applying a patch:
- =

- removing a patch:
- =

- using a patch to communicate about code:
- =

- looking at a snapshot from date x.y.z:
- =

- copying out a snapshot from date x.y.z:
- =

- Seeking and finding things:
- =

-  . (example scenario: can't remember when, but recalls quirky unique typo=
 that could be search for.)
- =

- seeing the list of changes:
- =

- by time, by user, by section
- =

- seeing who changed/created what:
-=20