[ec4ccb]: index.html History

Child: [af8333] (diff)

Download this file

index.html    142 lines (103 with data), 4.7 kB 

  1
  2
  3
  4
  5
  6
  7
  8
  9
 10
 11
 12
 13
 14
 15
 16
 17
 18
 19
 20
 21
 22
 23
 24
 25
 26
 27
 28
 29
 30
 31
 32
 33
 34
 35
 36
 37
 38
 39
 40
 41
 42
 43
 44
 45
 46
 47
 48
 49
 50
 51
 52
 53
 54
 55
 56
 57
 58
 59
 60
 61
 62
 63
 64
 65
 66
 67
 68
 69
 70
 71
 72
 73
 74
 75
 76
 77
 78
 79
 80
 81
 82
 83
 84
 85
 86
 87
 88
 89
 90
 91
 92
 93
 94
 95
 96
 97
 98
 99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
<!DOCTYPE html>

<html>

<head>

<title>OSP Documentation</title>

<link rel="stylesheet" type="text/css" href="docs_style.css">

</head>



<body>

<div id="site-header">

	<div class="wrapper">

		<a href="opensourceprojects.eu" id="header-logo"><img src="logo.png"></a>

	</div>

</div>



<div id="content_base">

	<h1>OSP Documentation</h1>



	<h2>Setting up your Account</h2>



	<img src="img/account.png"/>

	<p>

	To start using the platform you require a user account. You can create one

	from the front page. Fill in your preferred display name, user name and

	email address. You will soon receive an email with activation link and

	your password. Activate your account by clicking the link and following

	the instructions given. Now you can start working on the platform.

	</p>



	<p>

	To login with your existing account, click the top left corner

	login-link and insert your username and password.

	</p>



	<h2>Creating a Project</h2>



	<p>You can create new projects from the projects list (from the top menu under <b>Projects</b>)

	This opens a list of projects available to you. To create one of your

	own, click the <b>Add a Project</b> button from the left side menu.

	This opens the project creation page.

	</p>



	<img src="img/createproject.png" class="narrow"/>



	<p>

	From this page you can select the name of the project, and some of the initial project settings:

	</p>



	<ul>

		<li>Project Name(3-15 characters long</li>

		<li>Project URL name, http://opensourceproject.eu/p/<b>url-name</b></li>

		<li>The tools that will be enabled for this project</li>

		<li>Whether the project is private or not</li>

	</ul>



	<p>

	With exception to the project name/url all these settings can be added at a later time. Afte creating you new project, you will be redirected to the project administration page.

	</p>







	<h2>Project Management</h2>



	<h2>Git</h2>



	<h2>SVN</h2>



	<h2>Issue Tracker</h2>







	<div class="col1">

	<p>

	Issue management is available on the platform as one of the more important

	tools. It directly supports the development process and tickets allow the users

	and developers to interact with the project maintainers and main developers. In

	this section you get a rough overview of how tickets are configured in a

	specific project and how end-users can take advantage of them.

	</p>





	<p>

	Tickets are specific items that correspond to problems identified in the

	software, missing features requested by end users, or general communication

	items between developers and users. In many tools they are also known as

	���issues��� or ���bugs���, and hence the name of issue or bug trackers.

	</p>



	<p>

	The ticket tracker tool is designed to allow for flexibility in how you track

	items of work that need to be completed. This includes bugs, feature requests

	from end users, or any other task you want to keep track of. You can even

	install multiple ticket trackers for different purposes. For example, a large

	project could have individual trackers for the design team, the documentation

	team, the developers, and another for support. Each of these trackers can have

	their own unique list of tickets, as well as custom fields, custom milestones,

	and their own "mailing list." Tickets can even be moved between tickets

	instances, even if they're on different projects.

	</p>

	</div>



	<div class="col2">

	<img src="img/feature-tickets.png"/>

	</div>





	<h2 class="nocol">Wiki</h2>



	<h2 class="nocol">Forum</h2>



	<h2 class="nocol">Blog</h2>



	<p>

	The blog may be installed through the tools menu, as described before,

	by adding the corresponding tool in the administration area via Admin -

	Tools. Once installed, there are a number of configuration options

	available for each Blog. In addition to the common tool options of

	permissions, Label and Delete, you can determine an external feed.

	These external feeds may be updated every three hours and add posts to

	the blog accordingly. Multiple feeds may be added, which can serve to

	aggregate related news about the project. Unchecking a feed will remove

	it from the list.

	</p>









	<p>

	To create a new post, select "New Post" from the left sidebar under the Blog option. Enter a title and description for the post and Save to publish the post. If you save a draft for later editing before making it public, change the State to Draft before saving. Select the Edit link to edit a post or saved draft. You may also delete a post from the Edit view.

	</p>



	<p>

	Like all Allura tools, the blog uses Markdown syntax. Each blog post will also have a discussion section for users to comment on the post.</p>



	<h2>Metrics and Statistics</h2>





<div class="footer">

</div>

</body>



</html>