<article id="Introduction">
<title>Introduction to WinMerge</title>
- <para>WinMerge is an <ulink url="http://www.opensource.org/">Open
+ <para>WinMerge is an <ulink url="https://opensource.org/">Open
Source</ulink> differencing and merging tool for Windows. WinMerge can compare
both folders and files, presenting differences in a visual text format that is
easy to understand and handle.</para>
<para>Please note that WinMerge is not freeware (as many sites on the Web have
stated): it is <ulink
- url="http://www.gnu.org/licenses/gpl-2.0.html">GPL</ulink> licensed. We
+ url="https://www.gnu.org/licenses/gpl-2.0.html">GPL</ulink> licensed. We
provide you with a good tool for free, so please honor your license agreement
and submit improvements to us. We are happy to get help improving WinMerge, to
the advantage of all WinMerge users.</para>
</indexterm></title>
<para>There are three kind of versions available in the <ulink
- url="http://sourceforge.net/projects/winmerge/files/">downloads</ulink>
+ url="https://sourceforge.net/projects/winmerge/files/">downloads</ulink>
page.</para>
<section>
</indexterm>Stable versions</title>
<para><ulink
- url="http://sourceforge.net/projects/winmerge/files/stable/">Stable
+ url="https://sourceforge.net/projects/winmerge/files/stable/">Stable
versions</ulink> are recommended for most users. If you are unsure about
what version to use, use the latest stable version. Stable versions have
an even second number, for example, 2.4, 2.6 and 2.8.</para>
</indexterm>Beta versions</title>
<para><ulink
- url="http://sourceforge.net/projects/winmerge/files/beta/">Beta
+ url="https://sourceforge.net/projects/winmerge/files/beta/">Beta
versions</ulink> are for people who want to test latest features and
improvements made after last stable version. Beta versions are not tested
as extensively as stable versions and probably have some bugs. Beta
</indexterm>Experimental versions</title>
<para><ulink
- url="http://sourceforge.net/projects/winmerge/files/alpha/">Experimental
+ url="https://sourceforge.net/projects/winmerge/files/alpha/">Experimental
versions</ulink> or alpha versions are snapshot releases from our version control system
(Subversion). They have all the latest features and improvements. Some
features may still be buggy or incomplete. These releases are made
compile, and to participate in development discussions concerning new and
changing features. We also appreciate any help testing the current code.
Use experimental versions with care and enable backups! And please <ulink
- url="http://sourceforge.net/p/winmerge/bugs/">report
+ url="https://sourceforge.net/p/winmerge/bugs/">report
bugs</ulink> that you find while using these builds: it really helps with
WinMerge development!</para>
</section>
it may take some time for somebody to answer.</para>
<para>If you find a bug, please submit it as a <ulink
- url="http://sourceforge.net/p/winmerge/bugs/">bug
+ url="https://sourceforge.net/p/winmerge/bugs/">bug
report</ulink>. Please attach as much information as you can: at a minimum,
the version number of WinMerge that you are using. If you can, also attach a
configuration log which, you can display by clicking <menuchoice>
</important>
<para>You must <ulink
- url="https://sourceforge.net/account/registration/">register with
+ url="https://sourceforge.net/user/registration">register with
SourceForge.net</ulink> before posting a bug report (registration is free).
We require registering because anonymous submissions caused a lot of spam
and also because there were no possibility to contact people for asking more
</indexterm>WinMerge source code and development</title>
<para>WinMerge source code is available in the <ulink
- url="http://sourceforge.net/projects/winmerge/files/">downloads</ulink>
- page and from the <ulink
- url="http://sourceforge.net/p/winmerge/code/">public Subversion
- server</ulink>. Anyone can download the sources, study them, and alter them.
+ url="https://sourceforge.net/projects/winmerge/files/">downloads</ulink>
+ page and from the
+ <ulink url="https://bitbucket.org/winmerge/">Bitbucket</ulink> or
+ <ulink url="https://github.com/winmerge/">GitHub</ulink> project pages.
+ Anyone can download the sources, study them, and alter them.
If you find (and fix) bugs, improve something, and so on, please submit your
- changes to us as <ulink
- url="http://sourceforge.net/p/winmerge/patches/">patches</ulink>
- and help improve this product! If you publish your altered version, you are
+ changes to us as patches or pull requests and help improve this product!
+ If you publish your altered version, you are
required to publish the changes to source code too. This is what the <ulink
- url="http://www.gnu.org/licenses/gpl-2.0.html">GPL</ulink> license is about:
+ url="https://www.gnu.org/licenses/gpl-2.0.html">GPL</ulink> license is about:
please respect it.</para>
<para>WinMerge development work is done by people in their spare time.
reports them to us. We really try - we use WinMerge too. But there are
absolutely no promises for new features. We always appreciate any help with
WinMerge, be it testing, documenting, translating, or coding.</para>
-
- <section>
- <title>Participating in WinMerge development</title>
-
- <para>As mentioned above, we look for help in many areas, not just coding.
- Translation, documentation, and testing are important too.</para>
-
- <para>The <ulink url="http://wiki.winmerge.org/">Development Wiki</ulink>
- is a good source of information if you want to help with WinMerge
- development. The <ulink url="http://wiki.winmerge.org/wiki/Help_Needed">Help
- Needed</ulink> page in the wiki has more information about how to help
- with WinMerge development.</para>
-
- <para>The <ulink
- url="http://winmerge.org/support/mailing-lists.php">development-mailing</ulink>
- list is the preferred place for development discussions. Another place is
- in the <ulink
- url="http://forums.winmerge.org/viewforum.php?f=6">developers-forum</ulink>.
- If you are interested in helping with WinMerge development, let us know.
- If you want to fix one of our <ulink
- url="http://sourceforge.net/p/winmerge/bugs/"
- userlevel="">bugs</ulink> or implement a <ulink
- url="http://sourceforge.net/p/winmerge/feature-requests/">new
- feature</ulink>, let us <ulink
- url="http://forums.winmerge.org/viewforum.php?f=6">know</ulink>.</para>
- </section>
</section>
</article>
\ No newline at end of file
OSDN Git Service
