Textbook Companion (TBC) Project Internship
R Textbook Companion is managed by the FOSSEE project, IIT Bombay. We provide internship certificates to all who participate in this activity. The procedure is as follows:
1) Learn R. Resources are provided here.
2) Submit a book proposal -
2.1) Login to r.fossee.in, else create a new account if you are a new user.
2.2) Propose your preferred choice of books, using the proposal form here.
2.3) Ensure that the proposed book is not in Completed Books or Books in Progress.
3) Book proposal criteria and sample codes -
3.1) Make sure that the proposed book has at least 80 codable solved examples. Please choose a textbook for which R code is not already available. If a book already has R code, do NOT select that book.
3.2) Exclude all theoretical examples which have no scope of computation.
3.3) Send sample code from the proposed book to contact-r(at)fossee(dot)in in a .zip or .tgz file. Please make sure that you send at least five codes for different examples. Since these codes will be the only parameter to evaluate your submission, you should write efficient code i,.e. using at least one pre-defined function (except "c", "print", "cat", "library", "function", "return", "if/else", "ifelse", "while", "repeat", and "for") and one package. The sample codes should be sent utmost by the 3rd day of the proposal. Plagiarism is strictly NOT allowed. All contributors are expected to write fresh code in R. Copy pasting codes from completed textbook companions of other FLOSS like Python, Scilab etc, will result in disapproval of TBC proposal.
3.4) The subject of the email containing sample code should be "New Book Proposal-Sample Codes-(Student Name)".
4) Intimation about the approval or rejection of the proposal will be informed via email within 1 week. The approved textbook will appear under Books in Progress.
5) Once approved, start coding only the solved examples of the textbook and upload the codes on the interface. Once done uploading all the codes, create a document containing information regarding the number of all codable examples, the reason for not coding certain examples with their snapshots, etc. as shown in the template here. Upload the final document on the interface along with the codes.
6) Send an acknowledgement email to contact-r(at)fossee(dot)in once all the codes and the required document is uploaded on the interface. The review will not start until we receive the e-mail. Simultaneously, post the IITB internship forms. For further details click here.
7) Review of the book -
7.1) Initially, the uploaded document shall be analysed to check whether any examples marked as non-codable can be coded in R or not. In case if any examples are found to be codable, then you will be informed via mail. Only after all codable examples get uploaded, you will get the option to mark the code submission as complete.
7.2) Then, the uploaded codes will be reviewed for errors which will typically take 14 working days.
7.3) If any code is found to be erroneous, the intern will have to resubmit the corrected code after ensuring that it is bug-free.
7.4) Once all the submitted codes are bug-free, the output of the codes will be verified with the results in the textbook. This process may take up to 45 days.
7.5) If you submit the codes for review more than once, then it will be queued up with other review requests and will result in subsequent delays and revision of your honorarium.
8) Interns who successfully finish the textbook companion as per the specified procedure will be awarded an internship e-certificate and honorarium.
Terms and Conditions:
- Sample codes are a must and should be sent for the approval of the book.
- Code all the solved examples given in the textbook.
- Complete the coding in 3 months time.
- Be regular, else the internship will be cancelled.
- Use only R and not any other FLOSS.
- If the total number of codable examples in the textbook is less than 80, the intern will be paid reduced honorarium. For further details, click here.
- We cannot provide honorarium until we receive the forms.