BRL-CAD is huge. Thousands of files spread across 165 directories. Maintaining a high quality of source code and documentation is a never ending task, but one anyone can help with.
Sound's easy, but you might be surprised because you need to ignore all of the source code and function variables that will easily trip up any automatic spell-check program. You basically only care about spelling mistakes within comments. Even for our documentation, much of it is formatted in xml and you have to ignore all of the xml tags.
This task involves finding and fixing simple spelling mistakes. To complete the task, you need to find 8 or more different spelling mistakes in at least 8 different files. You have to fix all occurrences of the spelling mistake across all those files. Make sense?
Remember to check and fix all occurrences of the mistakes in all 8+ files, make and submit it as a patch file.
BE SURE TO HAVE UP-TO-DATE SOURCES!!! We find and fix spelling mistakes on a daily basis and throughout the day. You have to find mistakes that are not already fixed or reported.
To clarify:
- 1 mistake in 7 different files counts as: 1 and 7
- 20 mistakes in 2 files counts as: 8 and 2
- 5 mistakes across 20 files counts as: 5 and 8
- You need to find: =8 mistakes AND =8 files
File name/URL | File size | Date submitted | |
---|---|---|---|
gcidavidgumberg.patch | 11.9 KB | November 23 2013 00:36 UTC | |
gcidavidgumbergnew.patch | 360 bytes | November 24 2013 07:37 UTC | |
gcidavidgumberfinal.patch | 5.4 KB | November 24 2013 07:43 UTC | |
again.patch | 11.8 KB | November 26 2013 05:02 UTC | |
patch.spell | 28.5 KB | January 05 2014 08:10 UTC |
I would like to work on this task.
This task has been assigned to David Gumberg. You have 72 hours to complete this task, good luck!
Due to an unexpected flood of schoolwork, this task will not be completed in time.
The deadline of the task has been extended with 0 days and 23 hours.
When it says spelling errors, does that include general grammatical errors, or strictly the misspelling of a word?
Not a problem David. I just extended the deadline for your task. We really want you to enjoy working with BRL-CAD and not to make you work in stressful conditions.
If you need more time, you can again inform us.
Best of luck!
Thanks for the extension!
Just to clarify, when it says spelling errors, does that include general grammatical errors, or strictly the misspelling of a word?
For this task, you just need to check spelling errors.
In terms of spelling style, should it be US english or UK english?
It should be in US English.
The work on this task is ready to be reviewed.
Melange has detected that the deadline has passed and no more work can be submitted. The submitted work should be reviewed.
David,
In reviewing your patch, I only count five files with spelling changes and several of the spelling changes were "questionable". That said, fixing the spelling of Acknowledgments is something that will get your file count up past the minimum required. Fix all of them and you will have completed the task. If you use Mac or Linux, you can find them all quickly with this:
grep -r -i acknowledgement doc/* |grep -v svn
42 instances in 24 files.
The deadline of the task has been extended with 1 days and 12 hours.
One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.
I just reviewed my patch file and I must have made a mistake with diff, as I made sure to duly note all my corrections in a seperate document. Can you clarify whoch fixes were questionable? I can replace them with more adequate corrections if necessary.
Please ignore the recently mistakenly uploaded patch file.
The work on this task is ready to be reviewed.
Melange has detected that the deadline has passed and no more work can be submitted. The submitted work should be reviewed.
The deadline of the task has been extended with 1 days and 12 hours.
One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.
David, your previous patch file was "reversed" but that's not a problem. The issue, as I noted, was that there were only a few spelling fixes. Note that fixing grammar or simply swapping one word for another similar/better/different word do not count. The task is spelling fixes.
If you do not see the issue, itemize what mispellings your patch fixes.
That said, I noted that you can attain the minimum required by fixing all instances of acknowledgement to the U.S. spelling, acknowledgment.
p.s. Note that if you have an svn checkout (if you have .svn directories in your source tree, you have a checkout), you can create a suitable patch file with the "svn diff" command: svn diff mychanges.patch
I did reverse the patch, but I added 3 more instances of correcting the word "acknowledgments". Was that not enough? I now have 11 corrections v 8? Anyways, I'm going to add more corrections of the word to satisfy the requirement.
The work on this task is ready to be reviewed.
First and foremost, the submission should be in universal patch format, not just a series of diffs. These instructions may help:
http://brlcad.org/wiki/Deuces#When_You.27re_Done
or
http://brlcad.org/wiki/Patches
That said, please summarize what spelling corrections you've made and in what files here as a comment. Like this:
doc/docbook/file.xml
Note that the task also requires you to fix all occurances of any mistake you made across all the file(s) that you end up editing. I'd suggested earlier that you fix all of them at once:
grep -r -i acknowledgement doc/* |grep -v svn
One of the mentors has sent this task back for more work. Talk to the mentor(s) assigned to this task to satisfy the requirements needed to complete this task, submit your work again and mark the task as complete once you re-submit your work.
The deadline of the task has been extended with 2 days and 0 hours.
Melange has detected that the final deadline has passed and it has reopened the task.
I would like to work on this task.
This task has been assigned to David Gumberg. You have 72 hours to complete this task, good luck!
Melange has detected that the initial deadline has passed and it has set the task status to ActionNeeded. The student has 24 hours to submit the work before the task is reopened and sent back to the pool for other students to claim.
Melange has detected that the final deadline has passed and it has reopened the task.
I would like to work on this task.
This task has been assigned to Deep Inder Singh. You have 72 hours to complete this task, good luck!
Melange has detected that the initial deadline has passed and it has set the task status to ActionNeeded. The student has 24 hours to submit the work before the task is reopened and sent back to the pool for other students to claim.
Sorry for Delay due to my final exams and network problem
Can you please extend my deadline so that i can work on this task.
And can you Please provide me a link from where i download the files from which mistakes has to find.
Thanx.
Regards
The claim on this task has been removed, someone else can claim it now.
I would like to work on this task.
This task has been assigned to Deep Inder Singh. You have 72 hours to complete this task, good luck!
The claim on this task has been removed, someone else can claim it now.
This task is so close to completion, just was submitted in the wrong format. Is nobody really going to claim it and submit it as a proper patch? It's basically done.
I would like to work on this task.
This task has been assigned to Armen. You have 72 hours to complete this task, good luck!
The claim on this task has been removed, someone else can claim it now.
I would like to work on this task.
This task has been assigned to Shardul Chiplunkar. You have 72 hours to complete this task, good luck!
The work on this task is ready to be reviewed.
I've tried to convert David's patch to a unified diff format patch by applying it to a fresh checkout and running `svn diff`, but I'm not sure if all his changes have been correctly applied because his patch would not apply cleanly without some modification.
Your patch was applied in r59281. Thanks Shardul!
It had to be modified slightly. I don't think our usage of the Docbook xml "acknowledgements" tag can be changed (maybe, didn't test). We should probably be using "othercredit" anyways instead.
Congratulations, this task has been completed successfully.