From 0d062fe9bc42eb2a5ae8d3dde79a62e00bb11e3e Mon Sep 17 00:00:00 2001 From: hardythe1 Date: Thu, 9 Oct 2014 17:39:22 +0530 Subject: added about tbc back from python.fossee.in --- tbc/static/templates/disclaimer.html | 2 +- tbc/static/templates/guidelines.html | 3 +- tbc/static/templates/how.html | 71 +- tbc/templates/base.html | 1 + tbc/templates/tbc/about-pytbc.html | 107 ++- tbc/templates/tbc/sample.html | 1744 ++++++++++++++++++++++++++++++++++ tbc/urls.py | 1 + tbc/views.py | 4 + 8 files changed, 1845 insertions(+), 88 deletions(-) create mode 100644 tbc/templates/tbc/sample.html (limited to 'tbc') diff --git a/tbc/static/templates/disclaimer.html b/tbc/static/templates/disclaimer.html index 67883d4..a884e74 100644 --- a/tbc/static/templates/disclaimer.html +++ b/tbc/static/templates/disclaimer.html @@ -6,6 +6,6 @@
  • However, if the book has more than 60 examples, the contributor has to complete the whole book
  • For books having less than 60 examples, honorarium will be provided at Principal Investigator's discretion
  • Exceptional contributions will be rewarded at Principal Investigator's discretion
  • -
  • This work is not meant to count for any academic credit and is totally out of the scope of your curriculum
  • +
  • This work is not meant to count for any academic credit and is totally out of the scope of any curriculum
  • All the code generated (and other content on the site), is licensed under Creative Commons Attribution-ShareAlike 2.5 India (CC BY-SA 2.5)
  • diff --git a/tbc/static/templates/guidelines.html b/tbc/static/templates/guidelines.html index 90047fe..8555b44 100644 --- a/tbc/static/templates/guidelines.html +++ b/tbc/static/templates/guidelines.html @@ -1,7 +1,7 @@

    Guidelines for Coding

    diff --git a/tbc/static/templates/how.html b/tbc/static/templates/how.html index c5794b0..6cc976a 100644 --- a/tbc/static/templates/how.html +++ b/tbc/static/templates/how.html @@ -1,35 +1,36 @@ -

    How to contribute ?

    -
      -
    1. Contributor selects 3 textbooks and sends proposal through mail to textbook[at]fossee[dot]in in the preferred order.
    2. - -
    3. This mail should carry information about the Contributor. Details should be mentioned as under:
    4. - -
    5. Reviewer will have a look at the proposed books, select an appropriate book and allot to the contributor. At this stage, the contributor will be asked to send sample examples (through mail) i.e. solved examples from any one chapter as an IPython Notebook. -Kindly refer to the Sample IPython Notebook
    6. -
    7. Reviewer reviews the sample notebook and if not satisfied, the contributor will be notified to make necessary corrections and send the sample notebook again.
    8. -
    9. Once the reviewer is satisfied with the sample notebook, he/she will give a consent to the contributor to complete the book in 2 months.
    10. -
    11. The contributor has to submit the codes on the interface through Submit Book link when he/she finishes coding the book.
    12. -
    13. The entire submission will then be reviewed and the contributor will be notified about corrections, if required. The review of the book will typically take approximately 25 working days to finish. Each time the codes are submitted, it will be queued up with other review requests and will result in subsequent delays. When no more corrections are required, the book is termed as completed and the contributor will be notified to fill the Internship Forms -
    +{% load static %} + +
      +
    1. Contributor selects 3 textbooks and sends proposal through mail to textbook[at]fossee[dot]in in the preferred order.
    2. + +
    3. This mail should carry information about the Contributor. Details should be mentioned as under:
    4. + +
    5. Reviewer will have a look at the proposed books, select an appropriate book and allot to the contributor. At this stage, the contributor will be asked to send sample examples (through mail) i.e. solved examples from any one chapter as an IPython Notebook.Kindly + refer to the Sample IPython Notebook
    6. +
    7. Reviewer reviews the sample notebook and if not satisfied, the contributor will be notified to make necessary corrections and send the sample notebook again.
    8. +
    9. Once the reviewer is satisfied with the sample notebook, he/she will give a consent to the contributor to complete the book in 2 months.
    10. +
    11. The contributor has to submit the codes on the interface when intimated by the reviewer.
    12. +
    13. The entire submission will then be reviewed and the contributor will be notified about corrections, if required. The review of the book will typically take approximately 25 working days to finish. Each time the codes are submitted, it will be queued up with other review requests and will result in subsequent delays. When no more corrections are required, the book is termed as completed and the contributor will be notified to fill the Internship Forms
    14. diff --git a/tbc/templates/base.html b/tbc/templates/base.html index 9c515f3..a9061be 100755 --- a/tbc/templates/base.html +++ b/tbc/templates/base.html @@ -84,6 +84,7 @@