Commit 5b5b84d001dd29b890fc85234f0a5c5b788004b6

more FAQ entries and some contact info

Commit diff

app/views/site/about.html.erb

 
1<h1>About Gitorious</h1>
1<div class="section">
2 <a name="about"></a><h1>About Gitorious</h1>
23
3<p><strong><a href="/p/gitorious">Gitorious</a> aims to provide a great way of doing distributed opensource
4 code collaboration</strong></p>
4 <p><strong><a href="/p/gitorious">Gitorious</a> aims to provide a great way of doing distributed opensource
5 code collaboration</strong></p>
56
6<h3>The idea</h3>
7<p>Traditional code- and project forges offer many great things and has without
8 a question helped developers of open source software. However, there's always
9 the issue of long-term maintainability; as humans we always get distracted,
10 busy and or just plain tired of working with things in the long run.</p>
7 <h2>The idea</h2>
8 <p>Traditional code- and project forges offer many great things and has without
9 a question helped developers of open source software. However, there's always
10 the issue of long-term maintainability; as humans we always get distracted,
11 busy and or just plain tired of working with things in the long run.</p>
1112
12<p>Distributed version control provides a way around this by making everyones
13 copy a full repository, so if people like someone elses stuff better, or
14 that someone else is actively maintaining the project they can just pull from
15 that person instead of the "official" repository. And if the project
16 maintainer decides to, he can pull those changes into his mainline branch.
17 That's what makes open source great.</p>
13 <p>Distributed version control provides a way around this by making everyones
14 copy a full repository, so if people like someone elses stuff better, or
15 that someone else is actively maintaining the project they can just pull from
16 that person instead of the "official" repository. And if the project
17 maintainer decides to, he can pull those changes into his mainline branch.
18 That's what makes open source great.</p>
1819
19<p><strong><a href="/p/gitorious">Gitorious</a></strong> provides a
20 way of keeping track of these clones easily by:</p>
20 <p><strong><a href="/p/gitorious">Gitorious</a></strong> provides a
21 way of keeping track of these clones easily by:</p>
2122
22<ul class="bullet_list">
23 <li>Seeing what they're doing</li>
24 <li>Knowing where they can be found</li>
25 <li>Allowing anyone to contribute without being blessed with "commit bits"</li>
26 <li>Making it easier for maintainers to accept contributions</li>
27</ul>
23 <ul class="bullet_list">
24 <li>Seeing what they're doing</li>
25 <li>Knowing where they can be found</li>
26 <li>Allowing anyone to contribute without being blessed with "commit bits"</li>
27 <li>Making it easier for maintainers to accept contributions</li>
28 </ul>
2829
29<p>Gitorious still under development and there's many many more things I'd like
30 to do with it. If you have ideas for improvements or technical issues please
31 do stop by the <a href="http://groups.google.com/group/gitorious">discussion group</a>.</p>
30 <p>Gitorious still under development and there's many many more things I'd like
31 to do with it. If you have ideas for improvements or technical issues please
32 do stop by the <a href="http://groups.google.com/group/gitorious">discussion group</a>.</p>
3233
33<p>
34 Regards,<br />
35 <a href="/users/johan">Johan Sørensen</a><br />
36 <small>Gitorious.org maintainer</small>
37</p>
34 <p>
35 Regards,<br />
36 <a href="/users/johan">Johan Sørensen</a><br />
37 <small>Gitorious.org maintainer</small>
38 </p>
39</div>
3840
39<h2>FAQ</h2>
4041
41<h4>Why do I need to upload my public SSH key?</h4>
42<p>
43 When you push to a Git repository, your public key is how we authenticate
44 you and if have the permissions required to do a commit to a given repository
45</p>
42<div class="section">
43 <a name="contact"></a><h1>Contact Info</h1>
44 <p>
45 If you experience any technical issues feel free to
46 <a href="mailto:johan@johansorensen.com">send an email</a>, there's also the
47 <a href="http://groups.google.com/group/gitorious">discussion group</a> for more
48 general Gitorious discussions around Gitorious.
49 </p>
50</div>
4651
52<div class="section">
53 <a name="faq"></a><h1>FAQ</h1>
54
55 <h3>How do I point my local Git repository at Gitorious?</h3>
56 <p>
57 Easiest way is to put something like the following in your <code>.git/config</code>
58 file of the repository you wish to push:
59 <pre>
60 [remote "origin"]
61 url = git@gitorious.org:<em>project</em>/<em>repository.git</em>
62 fetch = +refs/heads/*:refs/remotes/origin/*
63 [branch "master"]
64 remote = origin
65 merge = refs/heads/master
66 </pre>
67 and then <code>git push origin master</code> to push the code to Gitorious.
68 </p>
69
70 <hr />
71
72 <h3>Why is my email displayed?</h3>
73 <p>
74 The email you used to signup with Gitorious is displayed to other users, so that they
75 can contact you about your projects if they need to. We do however take light
76 measures against crawlers by not displaying your email in completely plain text. <br />
77 But just to be clear: we won't sell or use any information you give to
78 gitorious.org against you or anyone else for financial and/or personal gains.
79 </p>
80
81 <hr />
82
83 <h3>Why do I need to upload my public SSH key?</h3>
84 <p>
85 When you push to a Git repository, your public key is how we authenticate
86 you and if have the permissions required to do a commit to a given repository
87 </p>
88</div>
89
90<% content_for :sidebar do -%>
91 <ul class="links">
92 <li><a href="#about">About</a></li>
93 <li><a href="#contact">Contact</a></li>
94 <li><a href="#faq">FAQ</a></li>
95 </ul>
96<% end -%>
toggle raw diff

public/stylesheets/base.css

 
441441 color: #ddd;
442442}
443443
444.section {
445 margin-bottom: 3em;
446}
447
444448/* tags */
445449
446450ul.tag_list li {
toggle raw diff