albacore 0.6.2.rc1 → 1.0.0.rc.1

data/spec/support/Tools/NAnt-0.85/README.txt

@@ -0,0 +1,144 @@
+NAnt
+
+What is it? 
+-----------
+NAnt is a .NET based build tool. In theory it is kind of like make without 
+make's wrinkles. In practice it's a lot like Ant. 
+  
+If you are not familiar with Jakarta Ant you can get more information at the
+Ant project web site (http://ant.apache.org/).
+
+
+Why NAnt?
+---------
+Because Ant was too Java specific.
+Because Ant needed the Java runtime.  NAnt only needs the .NET 
+or Mono runtime.
+
+
+The Latest Version
+------------------
+Details of the latest version can be found on the NAnt project web site
+http://nant.sourceforge.net/
+
+
+Compilation and Installation
+-------------------------------
+
+   a. Build Requirements
+   --------------------
+   To build NAnt, you will need the following components:
+
+   on Windows
+
+       * A version of the Microsoft .NET Framework
+
+         Available from http://msdn.microsoft.com/netframework/
+         
+         you will need the .NET Framework SDK as well as the runtime components 
+	 if you intend to compile programs.
+
+         note that NAnt currently supports versions 1.0, 1.1 and 2.0 (Beta 1) 
+	 of the Microsoft .NET Framework. 
+
+       or
+
+       * Mono for Windows (version 1.0 or higher)
+
+         Available from http://www.mono-project.com/downloads/
+   
+   Linux/Unix
+
+       * GNU toolchain - including GNU make
+
+       * pkg-config
+
+           Available from: http://www.freedesktop.org/Software/pkgconfig
+
+       * A working Mono installation and development libraries (version 1.0 or higher)
+
+           Available from: http://www.mono-project.com/downloads/
+
+           
+    b. Building the Software
+    ------------------------
+      
+    Build NAnt using Microsoft .NET
+
+	GNU Make
+	--------
+
+	make install MONO= MCS=csc prefix=<installation path>
+
+	eg. make install MONO= MCS=csc prefix="c:\Program Files"
+
+	NMake
+	-----
+
+	nmake -f Makefile.nmake install prefix=<installation path>
+	
+	eg. nmake -f Makefile.nmake install prefix="c:\Program Files"
+
+
+    Building NAnt using Mono
+
+	GNU Make
+	--------
+
+	make install prefix=<installation path>
+
+	eg. make install prefix="c:\Program Files"
+
+	NMake
+	-----
+
+	nmake -f Makefile.nmake install MONO=mono CSC=mcs prefix=<installation path>
+	
+	eg. nmake -f Makefile.nmake install MONO=mono CSC=mcs prefix=/usr/local/
+
+Note: 
+
+These instructions only apply to the source distribution of NAntContrib, as the binary distribution 
+contains pre-built assemblies.
+
+
+Documentation
+-------------
+Documentation is available in HTML format, in the doc/ directory.
+
+
+License
+-------
+Copyright (C) 2001-2005 Gerry Shaw
+
+This program is free software; you can redistribute it and/or modify
+it under the terms of the GNU General Public License as published by
+the Free Software Foundation; either version 2 of the License, or
+(at your option) any later version.
+
+This program is distributed in the hope that it will be useful,
+but WITHOUT ANY WARRANTY; without even the implied warranty of
+MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
+GNU General Public License for more details.
+
+You should have received a copy of the GNU General Public License
+along with this program; if not, write to the Free Software
+Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA  02111-1307 USA
+
+As a special exception, the copyright holders of this software give you
+permission to link the assemblies with independent modules to produce new
+assemblies, regardless of the license terms of these independent modules,
+and to copy and distribute the resulting assemblies under terms of your
+choice, provided that you also meet, for each linked independent module,
+the terms and conditions of the license of that module. An independent
+module is a module which is not derived from or based on these assemblies.
+If you modify this software, you may extend this exception to your version
+of the software, but you are not obligated to do so. If you do not wish to
+do so, delete this exception statement from your version. 
+
+A copy of the GNU General Public License is available in the COPYING.txt file 
+included with all NAnt distributions.
+
+For more licensing information refer to the GNU General Public License on the 
+GNU Project web site.
+http://www.gnu.org/copyleft/gpl.html

data/spec/support/Tools/NChurn-v0.4/LICENSE.txt

@@ -0,0 +1,133 @@
+Copyright (c) 2010, Dotan Nahum <dotan@paracode.com>
+All rights reserved.
+
+--
+
+Apache License, Version 2.0
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1
+through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by,
+or are under common control with that entity. For the purposes of this definition, "control" means (i) the power,
+direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or
+(ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications, including but not limited to software source
+code, documentation source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form,
+including but not limited to compiled object code, generated documentation, and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License,
+as indicated by a copyright notice that is included in or attached to the work (an example is provided in the
+Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from)
+the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent,
+as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include
+works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative
+Works thereof.
+
+"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications
+or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion
+in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the
+copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written
+communication sent to the Licensor or its representatives, including but not limited to communication on electronic
+mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of,
+the Licensor for the purpose of discussing and improving the Work, but excluding communication that is
+conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been
+received by Licensor and subsequently incorporated within the Work.
+
+2. Grant of Copyright License.
+
+Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or
+Object form.
+
+3. Grant of Patent License.
+
+Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide,
+non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make,
+have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to
+those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone
+or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging
+that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent
+infringement, then any patent licenses granted to You under this License for that Work shall terminate as of
+the date such litigation is filed.
+
+4. Redistribution.
+
+You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You meet the following conditions:
+
+  1. You must give any other recipients of the Work or Derivative Works a copy of this License; and
+  2. You must cause any modified files to carry prominent notices stating that You changed the files; and
+  3. You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent,
+     trademark, and attribution notices from the Source form of the Work, excluding those notices that do not
+     pertain to any part of the Derivative Works; and
+  4. If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You
+     distribute must include a readable copy of the attribution notices contained within such NOTICE file,
+     excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the
+     following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source
+     form or documentation, if provided along with the Derivative Works; or, within a display generated by the
+     Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file
+     are for informational purposes only and do not modify the License. You may add Your own attribution notices
+     within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work,
+     provided that such additional attribution notices cannot be construed as modifying the License.
+  5. You may add Your own copyright statement to Your modifications and may provide additional or different license
+     terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative
+     Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the
+     conditions stated in this License.
+
+5. Submission of Contributions.
+
+Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You
+to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you
+may have executed with Licensor regarding such Contributions.
+
+6. Trademarks.
+
+This License does not grant permission to use the trade names, trademarks, service marks, or product names of the
+Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing
+the content of the NOTICE file.
+
+7. Disclaimer of Warranty.
+
+Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides
+its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied,
+including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS
+FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing
+the Work and assume any risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability.
+
+In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless
+required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any
+Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential
+damages of any character arising as a result of this License or out of the use or inability to use the Work
+(including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction,
+or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility
+of such damages.
+
+9. Accepting Warranty or Additional Liability.
+
+While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for,
+acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole
+responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold
+each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.

data/spec/support/Tools/NChurn-v0.4/README.md

@@ -0,0 +1,171 @@
+NChurn
+======
+
+NChurn is a utility that helps asses the churn level of your files in your repository.  
+Churn can help you detect which files are changed the most in their life time. This helps identify potential bug hives, and improper design.  
+The best thing to do is to plug NChurn into your build process and store history of each run. Then, you can plot the evolution of your repository's churn.  
+**Developers see note about building below, if you want to build from source.**
+
+NChurn currently supports file-level churns for
+
+* Git
+* Hg (Mercurial)
+* SVN
+* TFS (Team Foundation)
+
+
+As outputs, NChurn supports
+
+* Table (plain ASCII)
+* CSV
+* XML (recommended for builds)
+
+
+Amongst others, NChurn can also take top # of items to display, cut off churn level, and a date to go back up to. See "Getting Started".
+
+Background
+----------------
+From this work http://research.microsoft.com/apps/pubs/default.aspx?id=69126
+
+    Code is not static; it evolves over time to meet new requirements. The way code
+    evolved in the past can be used to predict its evolution in the future. In particular,
+    there is an often accepted notion that code that changes a lot is of lower quality—
+    and thus more defect-prone than unchanged code.
+
+    Key Points
+    - The more a component has changed (churned), the more likely it is to have
+      defects.
+    Code churn measures can be used to predict defect-prone components.
+
+NChurn currently gives a view of *file churn* and will hopefully expand into analyzing files and languages themselves in the future.
+
+Getting Started
+---------------
+
+	$ NChurn -h
+  NChurn 0.4.0.0
+  Usage: NChurn
+         NChurn -c 4 -d 24-3-2010 -t 10
+
+  d, from-date    Past date to calculate churn from. Absolute in dd-mm-yyyy or
+                  number of days back from now.
+
+  c, churn        Minimal churn. Specify either a number for minimum, or float
+                  for precent.
+
+  t, top          Return this number of top records.
+
+  r, report       Type of report to output. Use one of: table (default), xml,
+                  csv
+
+  a, adapter      Use a specific versioning adapter. Use one of: auto
+                  (default), git, tf, svn, hg
+
+  p, env-path     Add to PATH. i.e. for svn.exe you might add "c:\tools". Can
+                  add multiple with ;.
+
+  i, input        Get input from a file instead of running a versioning system.
+                  Must specify correct adapter via -a.
+
+  x, exclude      Exclude resources matching this regular expression
+
+  n, include      Include resources matching this regular expression
+
+  help            Dispaly this help screen.
+
+
+
+Any combination of parameters work.
+
+	$ NChurn -t 5 -c 3        # take top 5, cut off at level 3 and below.
+	$ NChurn -c 0.3           # display files that consist 30% of all changes (0.3)
+	$ NChurn -d 24-12-2010    # calculate for 24th of Dec, 2010 up to now.
+	$ NChurn -c 2 -r xml      # cut off at 2, report output as XML.
+	$ NChurn -d 30 -i svn.log -a svn    # go back 30 days, read from pre-made file, adapter is SVN.
+	$ NChurn -p c:\tools\svn -a svn     # specify path and adapter on an environment that hasn't got a PATH.
+	$ NChurn -x exe$                    # exclude resources that end with 'exe' 
+
+Here is a sample of a run, which cuts off at 8, and uses the default table report:
+
+	$ NChurn -c 8
+	+--------------------------------------------------+
+	| lib/rubikon/application/instance_methods.rb | 48 |
+	| lib/rubikon/application.rb                  | 30 |
+	| test/test.rb                                | 30 |
+	| lib/rubikon/command.rb                      | 28 |
+	| lib/rubikon/parameter.rb                    | 17 |
+	| test/application_tests.rb                   | 14 |
+	| Rakefile                                    | 13 |
+	| lib/rubikon/application/dsl_methods.rb      | 12 |
+	| README.md                                   | 11 |
+	| samples/helloworld/hello_world.rb           | 11 |
+	| lib/rubikon.rb                              | 10 |
+	| lib/rubikon/exceptions.rb                   | 10 |
+	| lib/rubikon/flag.rb                         | 10 |
+	| lib/rubikon/action.rb                       | 9  |
+	| lib/rubikon/application/base.rb             | 9  |
+	| lib/rubikon/option.rb                       | 9  |
+	| lib/rubikon/progress_bar.rb                 | 9  |
+	| samples/helloworld.rb                       | 9  |
+	+--------------------------------------------------+
+
+And here is an example of taking the top 4 records on NChurn's git repo, output as xml report.
+
+	$ NChurn -t 4 -r xml
+	<?xml version="1.0" encoding="utf-8"?>
+	<NChurnAnalysisResult xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
+	  <FileChurns>
+	    <FileChurn>
+	      <File>README.md</File>
+	      <Value>2</Value>
+	    </FileChurn>
+	    <FileChurn>
+	      <File>.gitignore</File>
+	      <Value>1</Value>
+	    </FileChurn>
+	    <FileChurn>
+	      <File>AssemblyInfo.cs</File>
+	      <Value>1</Value>
+	    </FileChurn>
+	    <FileChurn>
+	      <File>Gemfile</File>
+	      <Value>1</Value>
+	    </FileChurn>
+	  </FileChurns>
+	</NChurnAnalysisResult>
+
+Building
+----------
+You can build NChurn in 2 ways:
+
+* Visual studio
+* Rake (albacore)
+
+To build with rake (the recommended way), make sure to `bundle install`, then look at your options with `rake -T`.  
+_Note:_ I've excluded tf.log and tf.log.result from the repository, out of discreteness. Make sure to exclude from project or even better contribute back a log we can publicly use.
+
+Contribute
+----------
+
+NChurn is an open-source project. Therefore you are free to help improving it.
+There are several ways of contributing to NChurn's development:
+
+* Build apps using NChurn and spread the word.
+* Bug and features using the [issue tracker][2].
+* Submit patches fixing bugs and implementing new functionality.
+* Create an NChurn fork on [GitHub][1] and start hacking. Extra points for using GitHubs pull requests and feature branches.
+
+License
+-------
+
+This code is free software; you can redistribute it and/or modify it under the
+terms of the Apache License. See LICENSE.txt.
+
+Copyright
+---------
+
+Copyright (c) 2011, Dotan Nahum <dotan@paracode.com>
+
+
+[1]: http://github.com/jondot/nchurn
+[2]: http://github.com/jondot/nchurn/issues