diff --git a/.nojekyll b/.nojekyll new file mode 100644 index 0000000..e69de29 diff --git a/Gruntfile.js b/Gruntfile.js index b52e29d..0b82eb0 100644 --- a/Gruntfile.js +++ b/Gruntfile.js @@ -31,8 +31,8 @@ module.exports = function(grunt) { 'css/pack.css': [ 'css/normalize.css', 'css/jquery.fancybox.css', - 'css/style.css', - 'css/small.css' + 'css/small.css', + 'css/custom.css' ] } } diff --git a/bump-version.js b/bump-version.js index 331707d..c3ac95e 100755 --- a/bump-version.js +++ b/bump-version.js @@ -13,10 +13,10 @@ var die = (err) => { }; var updateVersion = (version, tag, timestamp, url) => { - var regex = /
.*?<\/div>/gm; - var replacement = '
.*?<\/p>/gm; + var replacement = '

Version ' + version + '

'; + + timestamp + '">Version ' + version + '

'; fs.writeFileSync('latest-version.txt', version); fs.writeFileSync('latest-tag.txt', tag); const urlPrefix = `https://github.com/git-for-windows/git/releases/download/${tag}`; diff --git a/css/custom.css b/css/custom.css new file mode 100644 index 0000000..bed33f3 --- /dev/null +++ b/css/custom.css @@ -0,0 +1,116 @@ +body { + padding-top: 5%; +} + +.navbar-dark .navbar-nav .nav-link { + color: #b2b8bd; +} + +.lcolor{ + color: #07488f; +} + +.ncolor { + color: #0b6bd3; +} + +section { + padding-top: 5rem; + padding-bottom: 5rem; +} + +.lnr { + display: inline-block; + fill: currentColor; + width: 1em; + height: 1em; + vertical-align: -0.05em; + stroke-width: 1; +} + +.services-icon { + margin-bottom: 20px; + font-size: 30px; +} + +.quote-icon { + font-size: 40px; + margin-bottom: 20px; +} + +.gittext { + color: #646464; + font-family: 'Open Sans', sans-serif; +} + +.lowercase { + text-transform: lowercase; +} + +h1, +h2, +h3, +h4 { + font-weight: 300; +} + +h1 { + font-size: 2.5em; + text-align: center; +} + +h1 span { + color: #969696; + font-size: 0.42em; + margin-left: 0.476em; +} + +h2 { + font-size: 3em; + line-height: 1.3; +} + +h3 { + font-size: 1.875em; + line-height: 1.3; +} + +h4 { + font-size: 1.5em; + line-height: 1.1; +} + +li.borderless { + border-top: 0 none; + border-bottom: 0 none; + border-right: 0 none; + border-left: 0 none; +} + +.img-git-logo { + width: 80%; +} + +.img-git-sdk-logo { + width: 30%; +} + +.img-other-logos { + width: 90% +} + +.footer { + padding: 28px 0; + margin-top: 55px; + background-color: #00478f; +} +.footer span, +.footer a { + color: #BBBBBB; + -webkit-transition: all 0.3s linear; + -o-transition: all 0.3s linear; + transition: all 0.3s linear; +} +.footer a:hover { + color: #80BDFF; +} diff --git a/css/style.css b/css/style.css deleted file mode 100644 index a2750f9..0000000 --- a/css/style.css +++ /dev/null @@ -1,351 +0,0 @@ -html { - font: 16px/1 'Open Sans', 'Helvetica Neue', Helvetica, Arial, sans-serif; -} - -li a { - font-size: .875em; -} - -a { - color: #4B8CD2; - text-decoration: none; -} - -.gittext { - color: #646464; - font-weight: bold; -} - -.lowercase { - text-transform: lowercase; -} - -h1, -h2, -h3, -h4 { - font-weight: 300; -} - -h1 { - font-size: 3.125em; -} - -h1 span { - color: #969696; - font-size: .42em; - margin-left: .476em; -} - -h2 { - font-size: 3em; - line-height: 1.3; -} - -h3 { - font-size: 1.875em; - line-height: 1.3; -} - -h4 { - font-size: 1.5em; - line-height: 1.1; -} - -.content { - margin-left: auto; - margin-right: auto; - width: 65%; - min-width: 33em; - max-width: 56.25em; -} - -header { - background-color: #E1E1E1; - background-image: -webkit-gradient(radial, center center, 0px, center center, 100%, color-stop(0%, rgba(235, 235, 235, 0.7)), color-stop(50%, rgba(200, 200, 200, 0.3)), color-stop(100%, rgba(30, 30, 30, 0.25))); /* Chrome,Safari4+ */ - background-image: -webkit-radial-gradient(center, ellipse cover, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* Chrome10+,Safari5.1+ */ - background-image: -moz-radial-gradient(center, ellipse cover, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* FF3.6+ */ - background-image: -ms-radial-gradient(center, ellipse cover, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* IE10+ */ - background-image: -o-radial-gradient(center, ellipse cover, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* Opera 12+ */ - background-image: radial-gradient(ellipse at center, rgba(235, 235, 235, 0.7) 0%, rgba(200, 200, 200, 0.3) 50%, rgba(30, 30, 30, 0.25) 100%); /* W3C */ - filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#B3EBEBEB', endColorstr='#401E1E1E',GradientType=1); /* IE6-9 fallback on horizontal gradient */ - background-repeat: repeat; - height: 30.3125em; - padding-top: 0.6em; -} - -header h1 { - margin-top: .18em; -} - -header h2 { - font-size: 2.5em; - margin-top: 0; -} - -footer { - background-color: #C8C8C8; /* Old browsers */ - background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%, #C8C8C8), color-stop(100%, #FFFFFF)); /* Chrome,Safari4+ */ - background-image: -webkit-linear-gradient(top, #C8C8C8 0%, #FFFFFF 100%); /* Chrome10+,Safari5.1+ */ - background-image: -moz-linear-gradient(top, #C8C8C8 0%, #FFFFFF 100%); /* FF3.6+ */ - background-image: -ms-linear-gradient(top, #C8C8C8 0%, #FFFFFF 100%); /* IE10+ */ - background-image: -o-linear-gradient(top, #C8C8C8 0%, #FFFFFF 100%); /* Opera 11.10+ */ - background-image: linear-gradient(to bottom, #C8C8C8 0%, #FFFFFF 100%); /* W3C */ - filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#c8c8c8', endColorstr='#ffffff',GradientType=0); /* IE6-9 */ - border-top: solid 1px #F0F0F0; -} - -footer div { - padding-top: 0.9375em; -} - -footer h1 { - font-size: 1.375em; - margin-top: -0.273em; -} - -footer .gittext { - color: #969696; -} - -nav { - border-bottom: solid 1px #C8C8C8; - -webkit-box-sizing: border-box; - -moz-box-sizing: border-box; - box-sizing: border-box; - height: 4.375em; - margin-bottom: 2em; - padding: 0 1.3em; -} - -nav h1 { - float: left; -} - -nav ul, -footer a { - float: right; -} - -nav ul { - margin-top: 2.375em; -} - -nav li, -footer li { - text-transform: uppercase; - float: left; - margin-left: 1.5625em; -} - -div.version { - position: absolute; - margin-top: 5em; - text-transform: uppercase; - color: #646464; -} - -.feature article { - position: relative; - padding-right: 0px; - width: 49.2%; - margin-left: auto; - margin-right: 0em; - height: 20em; -} - -.feature h2 { - border-bottom: solid 1px #BEBEBE; - color: #828282; - line-height: 1.625em; - margin-bottom: 0.375em; - padding: 0.125em 0.375em; -} - -.button { - background-color: #4B8CE9; /* Old browsers */ - background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#4B8CE9), color-stop(100%,#2C66B8)); /* Chrome,Safari4+ */ - background-image: -webkit-linear-gradient(top, #4B8CE9 0%,#2C66B8 100%); /* Chrome10+,Safari5.1+ */ - background-image: -moz-linear-gradient(top, #4B8CE9 0%, #2C66B8 100%); /* FF3.6+ */ - background-image: -ms-linear-gradient(top, #4B8CE9 0%,#2C66B8 100%); /* IE10+ */ - background-image: -o-linear-gradient(top, #4B8CE9 0%,#2C66B8 100%); /* Opera 11.10+ */ - background-image: linear-gradient(to bottom, #4B8CE9 0%,#2C66B8 100%); /* W3C */ - filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#4B8CE9', endColorstr='#2C66B8',GradientType=0); /* IE6-9 */ - -webkit-box-shadow: inset 0 1px 0 hsla(0, 100%, 100%, 0.2), inset 0 0 2px hsla(0, 100%, 100%, 0.2), 0 1px 2px hsla(0, 0%, 0%, 0.29); - -moz-box-shadow: inset 0 1px 0 hsla(0, 100%, 100%, 0.2), inset 0 0 2px hsla(0, 100%, 100%, 0.2), 0 1px 2px hsla(0, 0%, 0%, 0.29); - box-shadow: inset 0 1px 0 hsla(0, 100%, 100%, 0.2), inset 0 0 2px hsla(0, 100%, 100%, 0.2), 0 1px 2px hsla(0, 0%, 0%, 0.29); - -webkit-border-radius: 0.238em; - -moz-border-radius: 0.238em; - border-radius: 0.238em; - border: 1px solid #0A3A7D; - color: white; - display: inline-block; - font-size: 1.3125em; - padding: 0.476em 3%; - text-align: center; - text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.4); -} - -.featurebutton { - float: left; - margin: 0 1%; - width: 41%; -} - -.imagerollover { - float: left; - position: relative; - width: 46.5%; -} - -.imagerollover img { - position: absolute; - -webkit-transition: opacity 1s ease-in-out; - -moz-transition: opacity 1s ease-in-out; - -o-transition: opacity 1s ease-in-out; - transition: opacity 1s ease-in-out; - width: 100%; - height: auto; -} - -.imagerollover .top:hover { - opacity: 0; -} - -.vcentercontainer { - display: table; - height: 100%; -} - -.vcentercontainer div { - display: table-cell; -} - -.vcentercontainer div, -.vcentercontainer img { - vertical-align: middle; -} - -.vcentercontainer img { - margin: 2.8125em auto; -} - -.details { - background-color: #2C66B8; -} - -.details article { - border-bottom: solid 0.3125em #00478F; - border-top: solid 0.3125em #00478F; -} - -.details .gittext { - color: #FFFFFF; -} - -.details p { - margin-top: 0; -} - -.details p a { - color: #A3CFFF; - text-decoration: underline; -} - -.details h2 { - background-color: #4A7CC2; - border-bottom: solid 0.104em #7198C1; - border-top: solid 0.104em #7198C1; - -webkit-box-shadow: 0 0 0.8333em rgba(0, 0, 0, 0.4); - -moz-box-shadow: 0 0 0.8333em rgba(0, 0, 0, 0.4); - box-shadow: 0 0 0.8333em rgba(0, 0, 0, 0.4); - clear: both; - color: #FFFFFF; - margin-bottom: 0.625em; - margin-top: 0.9375em; - padding: 0.1875em 0; - text-align: center; - text-shadow: 0 -1px rgba(0, 0, 0, 0.5); -} - -.details h3 { - color: #F5F5F5; - margin-bottom: 0; - margin-top: 0.8333em; - text-shadow: 0 -1px rgba(0, 0, 0, 0.35); -} - -.details h4 { - color: #F5F5F5; - margin-bottom: 0; - margin-top: 0.75em; - text-shadow: 0 -1px rgba(0, 0, 0, 0.35); -} - -.details .button { - border: 1px solid #464646; - background-color: #E0E0E0; /* Old browsers */ - background-image: -webkit-gradient(linear, left top, left bottom, color-stop(0%,#E0E0E0), color-stop(100%,#A3A3A3)); /* Chrome,Safari4+ */ - background-image: -webkit-linear-gradient(top, #E0E0E0 0%,#A3A3A3 100%); /* Chrome10+,Safari5.1+ */ - background-image: -moz-linear-gradient(top, #E0E0E0 0%, #A3A3A3 100%); /* FF3.6+ */ - background-image: -ms-linear-gradient(top, #E0E0E0 0%,#A3A3A3 100%); /* IE10+ */ - background-image: -o-linear-gradient(top, #E0E0E0 0%,#A3A3A3 100%); /* Opera 11.10+ */ - background-image: linear-gradient(to bottom, #E0E0E0 0%,#A3A3A3 100%); /* W3C */ - filter: progid:DXImageTransform.Microsoft.gradient(startColorstr='#E0E0E0', endColorstr='#A3A3A3',GradientType=0); /* IE6-9 */ - margin-right: 1%; - text-shadow: 0 -1px 0 rgba(0, 0, 0, 0.6); -} - -.details .content { - height: 39.0625em; -} - -.details p { - color: #EBEBEB; - line-height: 1.9375em; - margin-bottom: 0.3125em; - text-shadow: 0 -1px rgba(0, 0, 0, 0.35); -} - -.details .vcentercontainer:first-child { - margin-right: 5%; -} - -.verticalgallery { - float: none; - text-align: center; -} - -.verticalgallery img { - border: solid 0.3125em #5881BD; - -webkit-box-shadow: 0 0 2.8125em rgba(0, 0,0, 0.17); - -moz-box-shadow: 0 0 2.8125em rgba(0, 0, 0, 0.17); - box-shadow: 0 0 2.8125em rgba(0, 0, 0, 0.17); - margin: 1.875em auto; - width: 100%; - height: auto; -} - -.detailstext { - float: left; - width: 58%; -} - -.detailsimg { - float: left; - width: 35%; -} - -.contributecontent .detailsimg * { - width: 100%; - height: auto; -} - -.list-unstyled { - list-style-type: none; - padding-left: 0; -} - -.stud { - clear: both; -} diff --git a/governance-model.html b/governance-model.html index 5f737c2..fa7070b 100644 --- a/governance-model.html +++ b/governance-model.html @@ -6,166 +6,210 @@ Git for Windows - - - + + + + + + + - -
+ + +
+
-

Git for Windows governance model

-

Overview

-

Git for Windows is led by a benevolent dictator (Johannes Schindelin) and managed by the community. That is, -the community actively contributes to the day-to-day maintenance of the project, but the general strategic -line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the -benevolent dictator’s job to resolve disputes within the community and to ensure that the project is able to -progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the benevolent -dictator through active engagement and contribution.

-

Roles and responsibilities

-

Benevolent dictator (project lead)

-

Typically, the benevolent dictator, or project lead, is self-appointed. However, because the community -always has the ability to fork, this person is fully answerable to the community. The project lead’s role is a -difficult one: -they set the strategic objectives of the project and communicate these clearly to the -community. They also have to understand the community as a whole and strive to satisfy as many -conflicting needs as possible, while ensuring that the project survives in the long term.

-

In many ways, the role of the benevolent dictator is less about dictatorship and more about -diplomacy. The key is to ensure that, as the project expands, the right people are given influence -over it and the community rallies behind the vision of the project lead. The lead’s job is then to ensure -that the committers (see below) make the right decisions on behalf of the project. Generally speaking, -as long as the committers are aligned with the project’s strategy, the project lead will allow them to -proceed as they desire.

-

Committers

-

Committers are contributors who have made several valuable contributions to the project and are -now relied upon to both write code directly to the repository and screen the contributions of others. In -many cases they are programmers but it is also possible that they contribute in a different -role. Typically, a committer will focus on a -specific aspect of the project, and will bring a level of expertise and understanding that earns them -the respect of the community and the project lead. The role of committer is not an official one, it is -simply a position that influential members of the community will find themselves in as the project lead -looks to them for guidance and support.

-

Committers have no authority over the overall direction of the project. However, they do have the ear -of the project lead. It is a committer’s job to ensure that the lead is aware of the community’s needs -and collective objectives, and to help develop or elicit appropriate contributions to the project. Often, -committers are given informal control over their specific areas of responsibility, and are assigned -rights to directly modify certain areas of the source code. That is, although committers do not have -explicit decision-making authority, they will often find that their actions are synonymous with the -decisions made by the lead.

-

Contributors

-

Contributors are community members who either have no desire to become committers, or have not -yet been given the opportunity by the benevolent dictator. They make valuable contributions, such as -those outlined in the list below, but generally do not have the authority to make direct changes to the -project code. Contributors engage with the project through communication tools, such as the -mailing list, -GitHub, via reports of issues -and via pull requests in the issue tracker, as detailed in our -how to participate document.

-

Anyone can become a contributor. There is no expectation of commitment to the project, no specific -skill requirements and no selection process. To become a contributor, a community member simply -has to perform one or more actions that are beneficial to the project.

-

Some contributors will already be engaging with the project as users, but will also find themselves -doing one or more of the following:

-
    -
  • supporting new users (current users often provide the most effective new user support)
    • -
  • reporting bugs
    • -
  • identifying requirements
    • -
  • supplying graphics and web design
    • -
  • programming
    • -
  • assisting with project infrastructure
    • -
  • writing documentation
    • -
  • fixing bugs
    • -
  • adding features
    • -
-

As contributors gain experience and familiarity with the project, they may find that the project lead -starts relying on them more and more. When this begins to happen, they gradually adopt the role of -committer, as described above.

-

Users

-

Users are community members who have a need for the project. They are the most important -members of the community: without them, the project would have no purpose. Anyone can be a user; -there are no specific requirements.

-

Users should be encouraged to participate in the life of the project and the community as much as -possible. User contributions enable the project team to ensure that they are satisfying the needs of -those users. Common user activities include (but are not limited to):

-
    -
  • evangelising about the project
    • -
  • informing developers of project strengths and weaknesses from a new user’s perspective
    • -
  • providing moral support (a ‘thank you’ goes a long way)
    • -
  • providing financial support
    • -
-

Users who continue to engage with the project and its community will often find themselves becoming -more and more involved. Such users may then go on to become contributors, as described above.

-

Support

-

All participants in the community are encouraged to provide support for new users within the project -management infrastructure. This support is provided as a way of growing the community. Those -seeking support should recognise that all support activity within the project is voluntary and is -therefore provided as and when time allows. A user requiring guaranteed response times or results -should therefore seek to purchase a support contract from a vendor. (Of course, that vendor should -be an active member of the community.) However, for those willing to engage with the project on its -own terms, and willing to help support other users, the community support channels are ideal.

-

Contribution process

-

Anyone can contribute to the project, regardless of their skills, as there are many ways to contribute. -For instance, a contributor might be active on the project mailing list and issue tracker, or might supply -pull requests. The various ways of contributing are described -in more detail in our how to participate document.

-

The Git for Windows issue tracker is the most appropriate -place for a contributor to ask for help when making their first contribution. Please also read the projects -issue reporting guidelines

-

Decision-making process

-

The benevolent dictatorship model does not need a formal conflict resolution process, since the -project lead’s word is final. If the community chooses to question the wisdom of the actions of a -committer, the project lead can review their decisions by checking the email archives, and either -uphold or reverse them.

+

Git for Windows governance model

+

Overview

+

Git for Windows is led by a benevolent dictator (Johannes Schindelin) and managed by the + community. That is, + the community actively contributes to the day-to-day maintenance of the project, but the general + strategic + line is drawn by the benevolent dictator. In case of disagreement, they have the last word. It is the + benevolent dictator’s job to resolve disputes within the community and to ensure that the project is + able to + progress in a coordinated way. In turn, it is the community’s job to guide the decisions of the + benevolent + dictator through active engagement and contribution.

+

Roles and responsibilities

+

Benevolent dictator (project lead)

+

Typically, the benevolent dictator, or project lead, is self-appointed. However, because the community + always has the ability to fork, this person is fully answerable to the community. The project lead’s + role is a + difficult + one: + they set the strategic objectives of the project and communicate these clearly to the + community. They also have to understand the community as a whole and strive to satisfy as many + conflicting needs as possible, while ensuring that the project survives in the long term.

+

In many ways, the role of the benevolent dictator is less about dictatorship and more about + diplomacy. The key is to ensure that, as the project expands, the right people are given influence + over it and the community rallies behind the vision of the project lead. The lead’s job is then to + ensure + that the committers (see below) make the right decisions on behalf of the project. Generally speaking, + as long as the committers are aligned with the project’s strategy, the project lead will allow them to + proceed as they desire.

+

Committers

+

Committers are contributors who have made several valuable contributions to the project and are + now relied upon to both write code directly to the repository and screen the contributions of others. In + many cases they are programmers but it is also possible that they contribute in a different + role. Typically, a committer will focus + on a + specific aspect of the project, and will bring a level of expertise and understanding that earns them + the respect of the community and the project lead. The role of committer is not an official one, it is + simply a position that influential members of the community will find themselves in as the project lead + looks to them for guidance and support.

+

Committers have no authority over the overall direction of the project. However, they do have the ear + of the project lead. It is a committer’s job to ensure that the lead is aware of the community’s needs + and collective objectives, and to help develop or elicit appropriate contributions to the project. + Often, + committers are given informal control over their specific areas of responsibility, and are assigned + rights to directly modify certain areas of the source code. That is, although committers do not have + explicit decision-making authority, they will often find that their actions are synonymous with the + decisions made by the lead.

+

Contributors

+

Contributors are community members who either have no desire to become committers, or have not + yet been given the opportunity by the benevolent dictator. They make valuable contributions, such as + those outlined in the list below, but generally do not have the authority to make direct changes to the + project code. Contributors engage with the project through communication tools, such as the + mailing list, + GitHub, via reports of issues + and via pull requests in the issue tracker, + as detailed in our + how to participate + document.

+

Anyone can become a contributor. There is no expectation of commitment to the project, no specific + skill requirements and no selection process. To become a contributor, a community member simply + has to perform one or more actions that are beneficial to the project.

+

Some contributors will already be engaging with the project as users, but will also find themselves + doing one or more of the following:

+
    +
  • supporting new users (current users often provide the most effective new user support)
    • +
  • reporting bugs
    • +
  • identifying requirements
    • +
  • supplying graphics and web design
    • +
  • programming
    • +
  • assisting with project infrastructure
    • +
  • writing documentation
    • +
  • fixing bugs
    • +
  • adding features
    • +
+

As contributors gain experience and familiarity with the project, they may find that the project lead + starts relying on them more and more. When this begins to happen, they gradually adopt the role of + committer, as described above.

+

Users

+

Users are community members who have a need for the project. They are the most important + members of the community: without them, the project would have no purpose. Anyone can be a user; + there are no specific requirements.

+

Users should be encouraged to participate in the life of the project and the community as much as + possible. User contributions enable the project team to ensure that they are satisfying the needs of + those users. Common user activities include (but are not limited to):

+
    +
  • evangelising about the project
    • +
  • informing developers of project strengths and weaknesses from a new user’s perspective
    • +
  • providing moral support (a ‘thank you’ goes a long way)
    • +
  • providing financial support
    • +
+

Users who continue to engage with the project and its community will often find themselves becoming + more and more involved. Such users may then go on to become contributors, as described above.

+

Support

+

All participants in the community are encouraged to provide support for new users within the project + management infrastructure. This support is provided as a way of growing the community. Those + seeking support should recognise that all support activity within the project is voluntary and is + therefore provided as and when time allows. A user requiring guaranteed response times or results + should therefore seek to purchase a support contract from a vendor. (Of course, that vendor should + be an active member of the community.) However, for those willing to engage with the project on its + own terms, and willing to help support other users, the community support channels are ideal.

+

Contribution process

+

Anyone can contribute to the project, regardless of their skills, as there are many ways to contribute. + For instance, a contributor might be active on the project mailing list and issue tracker, or might + supply + pull requests. The various ways of + contributing are described + in more detail in our how to + participate document.

+

The Git for Windows issue tracker is + the most appropriate + place for a contributor to ask for help when making their first contribution. Please also read the + projects + issue reporting + guidelines

+

Decision-making process

+

The benevolent dictatorship model does not need a formal conflict resolution process, since the + project lead’s word is final. If the community chooses to question the wisdom of the actions of a + committer, the project lead can review their decisions by checking the email archives, and either + uphold or reverse them.

-
-
+ - - + + + + + }); + diff --git a/index.html b/index.html index 50e4712..0648374 100644 --- a/index.html +++ b/index.html @@ -1,140 +1,166 @@ - - - - Git for Windows - - - - - - + + + + + + - - -
- -
-
- Git Logo - Git Logo + + + + + +
+
+
+
+

+

Git for Windows

+

- -
-
-
-
-

Tools & Features

-
-
-
-

Git for Windows focuses on offering a lightweight, native set of tools that bring the full feature set of the Git SCM to Windows while providing appropriate user interfaces for experienced Git users and novices alike.

-

Git BASH

-

Git for Windows provides a BASH emulation used to run Git from the command line. *NIX users should feel right at home, as the BASH emulation behaves just like the "git" command in LINUX and UNIX environments.

-

Git GUI

-

As Windows users commonly expect graphical user interfaces, Git for Windows also provides the Git GUI, a powerful alternative to Git BASH, offering a graphical version of just about every Git command line function, as well as comprehensive visual diff tools.

-

Shell Integration

-

Simply right-click on a folder in Windows Explorer to access the BASH or GUI.

-
-
-
-
- - Git BASH - - - Git GUI - - - Gitk: Exploring Commits - -
-
+
+
+
+

+ Download + Contribute +

+

+ + Version 2.34.0 + +

-
-

Contribute

-
-
-
- BASH Drawing - Git for Windows Logo -
+
+
+
+
+
+

Tools & Features

+

Git for Windows focuses on offering a lightweight, native set of tools that bring + the full feature set of the Git SCM to Windows while + providing appropriate user interfaces for experienced Git users and novices alike.

+
+
+ Git Bash +

Git Bash

+

Git for Windows provides a Bash emulation used to run Git from the command line. *NIX users + should feel right at home, as the Bash emulation behaves just like the "git" command in LINUX + and UNIX environments.

+
+
+ Git GUI +

Git GUI

+

As Windows users commonly expect graphical user interfaces, Git for Windows also provides the Git + GUI, a powerful alternative to Git Bash, offering a graphical version of just about every Git + command line function, as well as comprehensive visual diff tools.

+
+
+ Gitk: Exploring Commits +

Shell Integration

+

Simply right-click on a folder in Windows Explorer to access the Bash or GUI.

+
+
+
+
+
+
+

Contribute

+

As an open source project, Git for Windows benefits greatly from both the volunteer work of helpful + developers and good bug + reports made by Git for Windows' users.

+

Governance Model

+

If you are interested in contributing to the Git for Windows project, have a look at the current + governance model. There the roles of those involved in driving this + project further down the road are described in detail.

+

Bug Reports & Feature Requests

+

If you've noticed a bug or simply have an idea that you'd like to see become real, why not work on it? + Bug reports and feature requests are typically submitted to the + issue tracker on our GitHub repository. +

+
+ +

Git for Windows SDK : Contributing Code

+

The Git for Windows SDK is a build environment that includes all the tools necessary for + developers who want to contribute by writing code for Git for Windows.

+

Please look at the technical + overview of the Git for Windows packaging and how to include your changes in your own custom + installer.

+ Download Git for Windows SDK +

To contribute/update this web page, see its Repository.

+
+
+