<commit_before><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<!--
Copyright 2003-2004 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<document>
  <header>
    <title>Contributing to XML-Security</title>
  </header>
  <body>
    <section>
      <title>Introduction</title>
      <p> 
	The XML Security Project is an 
	<link href="http://www.opensource.org/">Open Source</link> 
        volunteer project released
	under a very open license. This means there are many ways to contribute to the
	project - either with direct participation (coding, documenting, answering
	questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by
	resource donations (money, time, publicity, hardware, software, conference
	presentations, speeches, etc...). 
      </p>
      <p> 
	To begin with, we suggest you to subscribe to the
        <link href="site:mail-lists">XML-Security mailing list</link> (follow the link for
	information on how to subscribe and to access the mail list archives).
	Listen-in for a while, to hear how others make contributions. 
      </p>
      <p>
	You can get your local working copy of the
        <link href="http://svn.apache.org/repos/asf/xml/security/trunk/">latest and
	  greatest code</link> (which you find in the xml/security module in the Subversion code
	repository). Review the todo list, choose a task (or perhaps you have noticed
	something that needs patching). Make the changes, do the testing, generate a
	patch, and post to the dev mailing list. (Do not worry - the process is easy
	and explained below.) 
      </p>
    </section>
    <section>
     <title>Help Wanted Here</title>
      <p> 
	The rest of this document is mainly about contributing new or
        improved code and/or documentation, but we would also be glad to have extra
        help in any of the following areas: 
      </p>
      <ul>
        <li>
	  Answering questions on the mailing list - there
          is often a problem of having too many questioners and not enough experts to
          respond to all the questions.
	</li>
        <li>
	  Testing the package (especially its less-frequently-used features) on
          various configurations and reporting back.
	</li>
        <li>
	  Debugging - producing reproduceable test cases and/or finding
          causes of bugs. Some known bugs are informally listed on To Do, and some are
          recorded in Bugzilla (see <link href="#procedure">explanation
	    below</link>).
	</li>
      <li>
	  Specifying/analysing/designing new features - and beyond. (If you
	  wish to get involved with this, please join the mailing list, install
	  and try out xml-security and read some of the 
	  <link href="site:mail-lists">mail archives</link>. You should have a strong
          "fluency" in XML technologies especially XMLDSig and XML Encryption,
	  Java or C++ and a basic understanding of the architecture of this
	  package.
	</li>
      </ul>
    </section> <anchor id="cvshowto"/>
    <section>
    <title>Subversion (SVN) Usage Overview</title>
      <p>
	An overview of how to use Subversion to participate in the XML Security development.
        Do not be afraid - you cannot accidently destroy the actual code repository,
        because you are working with a local copy as an anonymous user. Therefore, you
        do not have the system permissions to change anything. You can only update your
        local repository and compare your revisions with the real repository. 
      </p>
      <p> 
	(Further general Subversion usage information is at
        <link href="http://subversion.tigris.org/">subversion.tigris.org</link> and your local
	user documentation.) 
      </p>
      <p> 
	Have a look at the <link href="site:java/installation">Java</link> or
	<link href="site:c/install">C++</link> installation pages to see
	how to get a local copy of the source.
      </p>
    </section> <anchor id="ssh"/>
    <section>
    <title>CVS Committer with Secure Shell access</title>
      <p>
	After a developer has consistently provided contributions (code,
        documentation and discussion), then the rest of the dev community may vote to
        grant this developer commit access to CVS. 
      </p>
      <p>
	You will need secure access to the repository to be able to commit
        patches. Here are some resources that help to get your machine configured to
        use the repository over SSH. 
      </p>
      <ul>
        <li><link href="http://cvsbook.red-bean.com/">The CVS Book</link></li>
	<li><link href="http://www.cvshome.org/">www.cvshome.org</link></li>
      </ul>
    </section> <anchor id="procedure"/>
    <section>
    <title>Procedure for Raising Development Issues</title>
      <p> 
	There are two methods for discussing development and submitting
        patches. So that everyone can be productive, it is important to know which
        method is appropriate for a certain situation and how to go about it without
        confusion. This section explains when to use the <code>developer</code>
        <link href="site:mail-lists">mailing list</link> the bug database. 
      </p>
      <p> 
	Research your topic thoroughly before beginning to discuss a new
        development issue. Search and browse through the email archives - your issue
        may have been discussed before. Prepare your post clearly and
	concisely. 
      </p><commit_msg>More CVS-SVN updates.<commit_after><?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE document PUBLIC "-//APACHE//DTD Documentation V1.1//EN" "document-v11.dtd">
<!--
Copyright 2003-2004 The Apache Software Foundation

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
-->
<document>
  <header>
    <title>Contributing to XML-Security</title>
  </header>
  <body>
    <section>
      <title>Introduction</title>
      <p> 
	The XML Security Project is an 
	<link href="http://www.opensource.org/">Open Source</link> 
        volunteer project released
	under a very open license. This means there are many ways to contribute to the
	project - either with direct participation (coding, documenting, answering
	questions, proposing ideas, reporting bugs, suggesting bug-fixes, etc..) or by
	resource donations (money, time, publicity, hardware, software, conference
	presentations, speeches, etc...). 
      </p>
      <p> 
	To begin with, we suggest you to subscribe to the
        <link href="site:mail-lists">XML-Security mailing list</link> (follow the link for
	information on how to subscribe and to access the mail list archives).
	Listen-in for a while, to hear how others make contributions. 
      </p>
      <p>
	You can get your local working copy of the
        <link href="http://svn.apache.org/repos/asf/xml/security/trunk/">latest and
	  greatest code</link> (which you find in the xml/security module in the Subversion code
	repository). Review the todo list, choose a task (or perhaps you have noticed
	something that needs patching). Make the changes, do the testing, generate a
	patch, and post to the dev mailing list. (Do not worry - the process is easy
	and explained below.) 
      </p>
    </section>
    <section>
     <title>Help Wanted Here</title>
      <p> 
	The rest of this document is mainly about contributing new or
        improved code and/or documentation, but we would also be glad to have extra
        help in any of the following areas: 
      </p>
      <ul>
        <li>
	  Answering questions on the mailing list - there
          is often a problem of having too many questioners and not enough experts to
          respond to all the questions.
	</li>
        <li>
	  Testing the package (especially its less-frequently-used features) on
          various configurations and reporting back.
	</li>
        <li>
	  Debugging - producing reproduceable test cases and/or finding
          causes of bugs. Some known bugs are informally listed on To Do, and some are
          recorded in Bugzilla (see <link href="#procedure">explanation
	    below</link>).
	</li>
      <li>
	  Specifying/analysing/designing new features - and beyond. (If you
	  wish to get involved with this, please join the mailing list, install
	  and try out xml-security and read some of the 
	  <link href="site:mail-lists">mail archives</link>. You should have a strong
          "fluency" in XML technologies especially XMLDSig and XML Encryption,
	  Java or C++ and a basic understanding of the architecture of this
	  package.
	</li>
      </ul>
    </section> <anchor id="cvshowto"/>
    <section>
    <title>Subversion (SVN) Usage Overview</title>
      <p>
	An overview of how to use Subversion to participate in the XML Security development.
        Do not be afraid - you cannot accidently destroy the actual code repository,
        because you are working with a local copy as an anonymous user. Therefore, you
        do not have the system permissions to change anything. You can only update your
        local repository and compare your revisions with the real repository. 
      </p>
      <p> 
	(Further general Subversion usage information is at
        <link href="http://subversion.tigris.org/">subversion.tigris.org</link> and your local
	user documentation.) 
      </p>
      <p> 
	Have a look at the <link href="site:java/installation">Java</link> or
	<link href="site:c/install">C++</link> installation pages to see
	how to get a local copy of the source.
      </p>
    </section> <anchor id="ssh"/>
    <section>
    <title>Subversion Committer with HTTPS access</title>
      <p>
	After a developer has consistently provided contributions (code,
        documentation and discussion), then the rest of the dev community may vote to
        grant this developer commit access to SVN. 
      </p>
      <p>
	You will need secure access to the repository to be able to commit
        patches. Here are some resources that help to get your machine configured to
        use the repository via HTTPS. 
      </p>
      <ul>
        <li><link href="http://apache.org/dev/version-control.html#https-svn">Apache Committer Subversion Access</link></li>
	<li><link href="http://svnbook.red-bean.com/">Subversion book</link></li>
      </ul>
    </section> <anchor id="procedure"/>
    <section>
    <title>Procedure for Raising Development Issues</title>
      <p> 
	There are two methods for discussing development and submitting
        patches. So that everyone can be productive, it is important to know which
        method is appropriate for a certain situation and how to go about it without
        confusion. This section explains when to use the <code>developer</code>
        <link href="site:mail-lists">mailing list</link> the bug database. 
      </p>
      <p> 
	Research your topic thoroughly before beginning to discuss a new
        development issue. Search and browse through the email archives - your issue
        may have been discussed before. Prepare your post clearly and
	concisely. 
      </p>
{'fraction_non_alphanumeric': 0.08284714119019837, 'fraction_numerical': 0.0031671945324220703, 'mean_word_length': 3.0117017719826147, 'pattern_counts': {'":': 0, '<': 189, '<?xml version=': 2, '>': 189, 'https://': 0, 'lorem ipsum': 0, 'www.': 6, 'xml': 8}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '4327670', 'n_tokens_mistral': 3302, 'n_tokens_neox': 3126, 'n_words': 1482}