Edgewall Software

Changes between Version 1 and Version 2 of CookBook/About


Ignore:
Timestamp:
Jun 4, 2009, 11:16:45 PM (15 years ago)
Author:
Ariel Balter <ariel@…>
Comment:

reasonable start for cookbook "about" page

Legend:

Unmodified
Added
Removed
Modified
  • CookBook/About

    v1 v2  
    11[[PageOutline]]
    22= Trac Cookbook =
    3 My experiences installing and configuring a Trac site, as well as following threads in the [http://groups.google.com/group/trac-users Trac Users Group] have convinced me of the need for a "cookbook" for Trac containing "recipes" for accomplishing particular tasks.  By a "recipe" I mean a clear and reliable set of instructions that have a very high probability of working under a broad range of conditions.  The recipe should also be complete and self-contained in the sense that one should be able to start at the beginning and end up with the desired goal at the end of the steps -- no prerequisites, and no unexplained steps.  Ideally, the "why" for the steps will also be included.
     3== Introduction ==
     4My experiences installing and configuring a Trac site, as well as following threads in the  Trac Users Group have convinced me of the need for a "cookbook" for Trac containing "recipes" for accomplishing particular tasks. By a "recipe" I mean a clear and reliable set of instructions that have a very high probability of working under a broad range of conditions. The recipes should also be complete and self-contained.
    45
    5 I am currently composing offline a document to go here.  Be back soon with the entire thing.
     6== Recipes ==
    67
    7 Thanks, Ariel
     8Loads of information on how to accomplish particular tasks with Trac already exists in one form or another in forum posts, blogs, third party web pages, and even the Trac documentation.  However, this non-centralized information can sometimes be hard to find, especially if the "answer" is buried somewhere in the middle of a forum thread.  Often the prerequisites for the answer -- conceptual, hardware, or software -- are often missing.  Most importantly, there is generally no guarantee that the solution wil work.
    89
    9 {{{Author:  Ariel Balter  Email:  ariel@arielbalter.com   Date:  2009 June 3 13:10 PST}}}
     10A good "recipe" will be a more or less '''complete''' how-to in the sense that, one should be able to start at the beginning and end up with the desired goal at the end of the steps -- no undisclosed prerequisites, and no unexplained steps. Ideally, the "why" for the steps will also be included.
     11
     12== Sources for Recipes ==
     13
     14Ideally, the cookbook will be open to both suggestions for recipes and the recipes themselves.  In order for the cookbook to work, there will need to be some way to moderate or grade the solution so the users can be reasonably sure that the recipes wil work, and at worst not break their Trac.
     15
     16== "Writing" the Cookbook ==
     17
     18There is an ongoing discussion right now in the trac users group on how best to pull in and organize the cookbook content, what to call the cookbook, were it will live, and how it will relate to the Trac "documentation" (in the traditional sense).  More will be posted here soon as these ideas gel.
     19
     20== What next? ==
     21
     22I created this page with the following idea in mind:  The cookbook could initially live here under {{{wiki:CookBook/<topic>/<sub_topic>/<etc.>}}}.  If I can get to where I'm not writing this any more, I might try writing some recipes to get things started.
     23
     24=== Can I submit a recipe? ===
     25
     26Good question.  I'm not sure how best to do this yet.  If you just make a page, will we be sure the recipe works.  I don't want to start flooding trac.edgewall.org with tickets for the cookbook.  Hmmmm.... Not sure yet.
     27
     28
     29Please stay tuned for more...!
     30
     31
     32{{{
     33#!comment
     34Author: Ariel Balter
     35Email: ariel@arielbalter.com
     36Date: 2009 June 3 14:05 PST
     37}}}