AirBAT Instructions - Revision history

BernardoDalSeno: /* Becoming a member */

2009-07-27T16:10:52Z

‎Becoming a member

BernardoDalSeno: /* Becoming a member */

2009-07-24T17:01:01Z

‎Becoming a member

BernardoDalSeno at 14:08, 3 June 2009

2009-06-03T14:08:37Z

BernardoDalSeno: /* Becoming a member */

2009-05-27T10:56:05Z

‎Becoming a member

BernardoDalSeno at 10:41, 27 May 2009

2009-05-27T10:41:17Z

BernardoDalSeno: /* Becoming a member */

2009-05-27T10:39:33Z

‎Becoming a member

BernardoDalSeno: /* Becoming a member */

2009-05-27T10:30:31Z

‎Becoming a member

BernardoDalSeno: /* Becoming a member */

2009-05-27T10:30:18Z

‎Becoming a member

BernardoDalSeno: /* Rules */

2009-03-27T00:05:50Z

‎Rules

BernardoDalSeno: /* Rules */

2009-03-27T00:04:32Z

‎Rules

@@ Line 4: / Line 4: @@
 AirBAT is based on [http://subversion.tigris.org/ Subversion]; you can find some help in configuring Subversion in the [[Configuring Subversion]] page.  The repository URL is ''<nowiki>https://svn.ws.dei.polimi.it/airbat/</nowiki>''.
-Students who need to work with AirBAT should fill the form at https://acme.ws.dei.polimi.it/request_account.plp with their info and put their supervisor in the "DEI responsible" field.  They should wait for the authorization from their supervisor.
+Students who need to work with AirBAT should fill the form at https://acme.ws.dei.polimi.it/request_account.plp with their info and put their supervisor in the "DEI responsible" field.  They should then ask their supervisor to confirm their account (supervisors, here are [[DEI Subversion Administration#Let users create their own accounts|the instructions for you]]).
 == Structure ==

@@ Line 4: / Line 4: @@
 AirBAT is based on [http://subversion.tigris.org/ Subversion]; you can find some help in configuring Subversion in the [[Configuring Subversion]] page.  The repository URL is ''<nowiki>https://svn.ws.dei.polimi.it/airbat/</nowiki>''.
-Students who need to work with AirBAT should ask their supervisor to create an account for them on https://acme.ws.dei.polimi.it/, and then ask one of the administrators of AirBAT for permissions.
+Students who need to work with AirBAT should fill the form at https://acme.ws.dei.polimi.it/request_account.plp with their info and put their supervisor in the "DEI responsible" field.  They should wait for the authorization from their supervisor.
 == Structure ==

@@ Line 1: / Line 1: @@
-[https://savane.elet.polimi.it/projects/airbat/ AirBAT] is a repository containing software developed in projects related to the [[BioSignal Analysis]] area.
+[https://svn.ws.dei.polimi.it/airbat/ AirBAT] is a repository containing software developed in projects related to the [[BioSignal Analysis]] area.
 == Becoming a member ==
-AirBAT is based on [http://subversion.tigris.org/ Subversion]; you can find some help in configuring Subversion in the [[Configuring Subversion]] page.  The repository URL is ''<nowiki>https://svn.elet.polimi.it/airbat/</nowiki>''.
+AirBAT is based on [http://subversion.tigris.org/ Subversion]; you can find some help in configuring Subversion in the [[Configuring Subversion]] page.  The repository URL is ''<nowiki>https://svn.ws.dei.polimi.it/airbat/</nowiki>''.
 Students who need to work with AirBAT should ask their supervisor to create an account for them on https://acme.ws.dei.polimi.it/, and then ask one of the administrators of AirBAT for permissions.

@@ Line 2: / Line 2: @@
 == Becoming a member ==
-AirBAT is based on [http://subversion.tigris.org/ Subversion]; you can find some help in configuring Subversion in the [[Configuring Subversion]] page.
+AirBAT is based on [http://subversion.tigris.org/ Subversion]; you can find some help in configuring Subversion in the [[Configuring Subversion]] page.  The repository URL is ''<nowiki>https://svn.elet.polimi.it/airbat/</nowiki>''.
 Students who need to work with AirBAT should ask their supervisor to create an account for them on https://acme.ws.dei.polimi.it/, and then ask one of the administrators of AirBAT for permissions.

← Older revision		Revision as of 10:41, 27 May 2009
Line 42:		Line 42:
	;Borland C++		;Borland C++
	:''project_dir'' / ''project_name''.bdsproj		:''project_dir'' / ''project_name''.bdsproj
		+
		+	== Administration ==
		+	Instructions for administration tasks can be found here: [[DEI Subversion Administration]].

@@ Line 4: / Line 4: @@
 AirBAT is based on [http://subversion.tigris.org/ Subversion]; you can find some help in configuring Subversion in the [[Configuring Subversion]] page.
+Students who need to work with AirBAT should ask their supervisor to create an account for them on https://acme.ws.dei.polimi.it/, and then ask one of the administrators of AirBAT for permissions.
-<!--  THIS PROCEDURE IS OUT OF DATE
-Students who need to work with AirBAT should:
-# Register an account on [https://savane.elet.polimi.it/ DEI Savane].
-# Ask to become member of the AirBAT project:
-#* Login and go to the "My Group" page (link in the top left corner).
-#* Search for "AirBAT" and request membership. Please state clearly who you are and what you are working on, so the administrators can identify and authorize you.
-# Create and upload a personal Ssh key on Savane (see [[Configuring Subversion]]).
-# Read the [[Using Subversion]] paget and the other sections below, which contain important information.
-# Wait until your membership is approved (this may take from one minute to about one day, depending on the load of the administrators).
-# Check out the repository and start working (if you have read the documentation, you should know what "check out" means and how to do it).
-−
--2 days may pass after the uploading of Ssh key before it becomes effective and you can start using the repository.  This depends on how the server is setup, so please be patient.
--->
 == Structure ==

@@ Line 34: / Line 34: @@
 Subversion should be used only for source files; so, no executables, object files (.o, .obj), archives (e.g., .jar, .zip) and other binary files.  The reason for the repository is to keep track of versions and share your work with other people; computer-generated files are no good for this.
-Makefiles or project files are definitely source files, as they contain directions for the compiler.  So please add them to the repository.  If you are in doubt about which files are used, try to copy the files on another machine and see which files are needed in order to correctly edit and compile the project.  See [[#Project Files]] for some known files.
+Makefiles or project files are definitely source files, as they contain directions for the compiler.  So please add them to the repository.  If you are in doubt about which files are used, try to copy the files on another machine and see which files are needed in order to correctly edit and compile the project.  See [[#Project Files|the Project Files section below]] for some known files.
 If your project needs some external file or library, don't add it to the repository, but say so in a README and put a link to where to find the library.  The repository remains cleaner, it is clearer what is your contribution, and it is easier to upgrade to a new version of the external library.

@@ Line 33: / Line 33: @@
 Subversion should be used only for source files; so, no executables, object files (.o, .obj), archives (e.g., .jar, .zip) and other binary files.  The reason for the repository is to keep track of versions and share your work with other people; computer-generated files are no good for this.
 If your project needs some external file or library, don't add it to the repository, but say so in a README and put a link to where to find the library.  The repository remains cleaner, it is clearer what is your contribution, and it is easier to upgrade to a new version of the external library.
@@ Line 42: / Line 44: @@
 For the '''bci''' hierarchy, where a '''common''' directory exists, some additional care is needed before committing: you don't want to commit a broken function that you have not yet debugged, as your fellows working on a different project could be hurt (or ''you'' may be hurt, if they revert your changes).  You have two options: either you postpone committing until you have finished debugging (but you lose the advantages of the version control system), or you use [http://en.wikipedia.org/wiki/Branching_%28software%29 branching].  For branching, do a copy with the Subversion copy command (''svn cp'' from the command line) from the '''common''' directory to your own, and use the copy until you are finished changing.  After the debugging is complete, you do a final commit, and then you can import your changes with the ''merge'' command; don't just overwrite the old copy in '''common''', unless you are sure nobody changed it after the branching.