IRIDIA Technical reports - Revision history

GabrieleValentini: /* How to register a technical report? */

2012-04-30T07:56:42Z

How to register a technical report?

GabrieleValentini: /* How to register a technical report? */

2012-03-01T20:18:26Z

How to register a technical report?

GabrieleValentini: /* How to submit a revised version of a technical report? */

2012-03-01T20:18:01Z

How to submit a revised version of a technical report?

GabrieleValentini: /* How to submit a revised version of a technical report? */

2012-03-01T20:16:36Z

How to submit a revised version of a technical report?

GabrieleValentini: /* How to register a technical report? */

2012-03-01T20:14:22Z

How to register a technical report?

GabrieleValentini: /* How to register a technical report? */

2012-03-01T20:12:46Z

How to register a technical report?

MLÃ³pez-IbÃ¡Ã±ez: fix link to TR

2011-10-10T14:10:49Z

fix link to TR

Arne: /* How to cite an IRIDIA technical report? */

2010-05-12T11:09:37Z

How to cite an IRIDIA technical report?

MLÃ³pez-IbÃ¡Ã±ez: formatting

2010-03-16T12:34:19Z

formatting

MLÃ³pez-IbÃ¡Ã±ez: update

2010-03-16T12:30:33Z

update

@@ Line 76: / Line 76: @@
   you are not yet registered, ask for a
   [http://iridia.ulb.ac.be/IridiaTrSeries/registration.php  registration]
   <li> Once logged, click on "New Technical Report" from the menu.</li>

@@ Line 92: / Line 92: @@
 The new technical report will be announced on the internal
 mailing list of IRIDIA, and it will be automatically published on the web.
 <ul>

@@ Line 107: / Line 107: @@
 Whenever you feel like submitting a revised version of a technical
-report of yours, just follow the same instructions of [[]] with the
+report of yours, just follow the same instructions of [[#How to register a technical report?]] with the
 difference that, once logged, you need to look for your technical
-report in the homepage and click to the "New Revision" link.
+report in the homepage and click to the "Upload New Revision" link.
 A revised version will contain a "revision history" on the copyright

@@ Line 107: / Line 107: @@
 Whenever you feel like submitting a revised version of a technical
-report of yours, just give a printed copy of the new version to Muriel
+report of yours, just follow the same instructions of [[]] with the
-A revised version must contain a "revision history" on the copyright
+A revised version will contain a "revision history" on the copyright
 page. Please read [[#Numbering of the IRIDIA -- Technical Report Series]] to understand what a revision history is. You
 should also have a look at the documentation of the [[#Where to find the LaTeX IridiaTrCover package? | LaTeX IridiaTrCover package]].
 == Numbering of the IRIDIA -- Technical Report Series ==

@@ Line 73: / Line 73: @@
   <li> Login into the IRIDIA Technical Report
-  [http://iridia.ulb.ac.be/IridiaTrSeries/login.php | homepage] or, if
+  [http://iridia.ulb.ac.be/IridiaTrSeries/login.php  homepage] or, if
   you are not yet registered, ask for a
-  [http://iridia.ulb.ac.be/IridiaTrSeries/registration.php | registration]
+  [http://iridia.ulb.ac.be/IridiaTrSeries/registration.php  registration]
   to the system.</li>

@@ Line 71: / Line 71: @@
   registered in the IRIDIA -- Technical Report Series! If you are a
   Ph.D. student, check with your supervisor.</li>
-  <li> Give Muriel the title of the document and the list of the
+  <li> Insert all the required fields (title, list of authors, latex versions
-  <li> Include number and date in your document. See the documentation
+  <li> Before submitting a document double check that all the inserted
 </ol>
-Muriel will then announce the new technical report on the internal
+The new technical report will be announced on the internal
-mailing list of IRIDIA, and the report will be published on the web.
+mailing list of IRIDIA, and it will be automatically published on the web.
 IMPORTANT: Steps 3 and 5 should be performed with no delay in between!
 <ul>
-  <li> '''DO NOT ask for a technical report date and number unless the'''
+  <li> '''DO NOT submit a document unless the'''
   '''document you want to register is already written, well formatted and'''
-  '''ready to be distributed.'''</li>
+  '''ready to be distributed. Once a document is submitted it cannot be deleted!'''</li>
   <li> '''DO NOT ask to register your technical report with a date that is'''
    '''not the one in which you indeed register it.'''</li>
 </ul>
 == How to submit a revised version of a technical report? ==

@@ Line 196: / Line 196: @@
 == How to use the IridiaTrCover.sty for LaTeX? ==
-Read the technical report [http://iridia.ulb.ac.be/IridiaTrSeries/IridiaTr2005-006r006.pdf TR/IRIDIA/2005-006]
+Read the technical report [http://iridia.ulb.ac.be/IridiaTrSeries/IridiaTr2005-006.pdf TR/IRIDIA/2005-006]
 <pre>
   The IridiaTrCover package for LaTeX:

@@ Line 49: / Line 49: @@
 Here's an example:
 <pre>
-  @TechReport{BirLopBru2005:IridiaTrCover
+  @TechReport{BirLopBru2005:IridiaTrCover,
-    author =      {M. Birattari and M. L{\'o}pez-Ib{\'a}{\~n}ez and A. Brutschy }
+    author =      {M. Birattari and M. L{\'o}pez-Ib{\'a}{\~n}ez and A. Brutschy },
     title =       "The {IridiaTrCover} package for \LaTeX:
                    How to typeset documents for the
@@ Line 60: / Line 60: @@
+  }
 </pre>
 == How to register a technical report? ==

@@ Line 43: / Line 43: @@
 You should consider a report registered in the [http://iridia.ulb.ac.be/IridiaTrSeries IRIDIA -- Technical Report Series] as a publication in itself.
 == How to cite an IRIDIA technical report? ==
@@ Line 59: / Line 60: @@
+  }
 </pre>
 == How to register a technical report? ==
@@ Line 101: / Line 103: @@
    '''not the one in which you indeed register it.'''</li>
 </ul>
 == How to submit a revised version of a technical report? ==
@@ Line 113: / Line 116: @@
 page. Please read [[#Numbering of the IRIDIA -- Technical Report Series]] to understand what a revision history is. You
 should also have a look at the documentation of the [[#Where to find the LaTeX IridiaTrCover package? | LaTeX IridiaTrCover package]].
 == Numbering of the IRIDIA -- Technical Report Series ==
@@ Line 169: / Line 173: @@
 priority, at least for the next couple of months. :)
 -->
 == File name conventions ==
@@ Line 183: / Line 188: @@
 If you revise the report, the PDF of the revised version will be called
 IridiaTrXXXX-YYYr002.pdf and so on.
 == Where to find the LaTeX IridiaTrCover package? ==

@@ Line 4: / Line 4: @@
-== What is a suitable technical report ==
+== What is a suitable technical report? ==
 You should consider registering as a technical report any scientific
@@ Line 42: / Line 42: @@
 submitted and/or published can be registered as technical reports.
-You should consider a report registered in the IRIDIA -- Technical
+You should consider a report registered in the [http://iridia.ulb.ac.be/IridiaTrSeries IRIDIA -- Technical Report Series] as a publication in itself.
-== How to cite a IRIDIA technical report? ==
+== How to cite an IRIDIA technical report? ==
 Here's an example:
@@ Line 61: / Line 60: @@
 </pre>
-== How to register a technical report ==
+== How to register a technical report? ==
 If you have a scientific or technical document that you think fits
-into the description given in the above section "What is a suitable
+into the description given in the above section [[#What is a suitable technical report?]], you might consider registering it in the IRIDIA --
 Technical Report Series. This is the procedure you should follow:
@@ Line 73: / Line 71: @@
   Ph.D. student, check with your supervisor.</li>
-  <li> Typeset the document using the LaTeX
+  <li> Typeset the document using the [[#Where to find the LaTeX IridiaTrCover package? | LaTeX IridiaTrCover package]].</li>
   <li> Give Muriel the title of the document and the list of the
@@ Line 83: / Line 80: @@
   <li> Include number and date in your document. See the documentation
-  of the [[Media:IridiaTrCover-1.6-003.tgz |IridiaTrCover]] package
+  of the [[#Where to find the LaTeX IridiaTrCover package? | LaTeX IridiaTrCover package]]
   to learn how to do this.</li>
@@ Line 92: / Line 89: @@
 Muriel will then announce the new technical report on the internal
-mailing list of iridia, and the report will be published on the web.
+mailing list of IRIDIA, and the report will be published on the web.
 IMPORTANT: Steps 3 and 5 should be performed with no delay in between!
@@ Line 105: / Line 102: @@
 </ul>
-== How to submit a revised version of a technical report ==
+== How to submit a revised version of a technical report? ==
 Whenever you feel like submitting a revised version of a technical
@@ Line 114: / Line 111: @@
 A revised version must contain a "revision history" on the copyright
-page. Please read on to understand what a revision history is. You
+page. Please read [[#Numbering of the IRIDIA -- Technical Report Series]] to understand what a revision history is. You
-should also have a look at the documentation of the IridiaTrCover.sty
+should also have a look at the documentation of the [[#Where to find the LaTeX IridiaTrCover package? | LaTeX IridiaTrCover package]].
-== Understanding the numbering of the IRIDIA -- Technical Report Series ==
+== Numbering of the IRIDIA -- Technical Report Series ==
 The number of a technical report is composed by the string
@@ Line 129: / Line 125: @@
 together with the date.
-A technical report might be "revised". The first version of a
+A technical report might be ''revised''. The first version of a
 technical report is revision number 001. Revision numbers are made of
 digits, possibly left-padded with zeros.
@@ Line 161: / Line 157: @@
 please submit a new technical report.
 Please notice that the numbering conventions adopted for the IRIDIA --
 Technical Report Series let us register 999 revisions of the same
@@ Line 171: / Line 168: @@
 conventions to be adopted starting from Jan 1, 10000 should be a
 priority, at least for the next couple of months. :)
 The PDF file of a technical report should have a name that matches the
 following pattern: IridiaTrXXXX-YYYrZZZ.pdf where XXXX is the year,
 YYY is the number, and ZZZ is the revision. Remember zero-padding
 and Muriel gave you number TR/IRIDIA/XXXX-YYY, you should send to the
 email address [mailto:techrep@iridia.ulb.ac.be <techrep@iridia.ulb.ac.be>]
@@ Line 190: / Line 184: @@
 IridiaTrXXXX-YYYr002.pdf and so on.
-== Where to find the LaTeX IridiaTrCover package ==
+== Where to find the LaTeX IridiaTrCover package? ==
-The most recent version of the LaTeX IridiaTrCover package is available
+The most recent version of the LaTeX IridiaTrCover package is [[Media:IridiaTrCover-2.0-r11.tar.gz|IridiaTrCover-2.0-r11.tar.gz]]
-== How to use the IridiaTrCover.sty for LaTeX ==
+== How to use the IridiaTrCover.sty for LaTeX? ==
 <pre>
   The IridiaTrCover package for LaTeX:
@@ Line 208: / Line 197: @@
 </pre>
-== What if you are not able to use LaTeX ==
+== What if you are not able to use LaTeX? ==
 If you are not able to use LaTeX, you can produce your technical
-report in pdf format and  ask then
+report in PDF format and  ask then
 [mailto:ericyuanzhi@gmail.com Eric] or [mailto:Sabrina.Oliveira@ulb.ac.be Sabrina]
-to generate a cover page and to preappend it to your file.
+to generate a cover page and to prefix it to your file. Apart from this step, please follow the [[#How to register a technical report?|other steps described above for registering your technical report]].