search

TopKec / pe

0 stars 0 forks source link

Incorrect Acknowledgements in DG #9

Open TopKec opened 5 months ago

TopKec commented 5 months ago

The following shows the Acknowledgements in the DG

image.png

The acknowledgements is missing.

soc-pe-bot commented 5 months ago

Team's Response

No details provided by team.

The 'Original' Bug

[The team marked this bug as a duplicate of the following bug]

DG Acknowledgement

Note from the teaching team: This bug was reported during the Part II (Evaluating Documents) stage of the PE. You may reject this bug if it is not related to the quality of documentation.

It seems like this was not removed properly. But if it was left there intentionally, a better approach would be to remove this section entirely, until there is a need for to declare a reuse.

image.png

[original: nus-cs2103-AY2324S2/pe-interim#3162] [original labels: type.DocumentationBug severity.VeryLow]

Their Response to the 'Original' Bug

[This is the team's response to the above 'original' bug]

Thank you for highlighting the issue regarding the 'Acknowledgements' section in our Developer's Guide. We apologise for any oversight in its removal. We will review the section to ensure that it accurately reflects the sources of all reused or adapted ideas, code, and documentation, as well as their third-party libraries, and will remove it if there are none.

Items for the Tester to Verify

:question: Issue duplicate status

Team chose to mark this issue as a duplicate of another issue (as explained in the Team's response above)

Reason for disagreement: [replace this with your explanation]

## :question: Issue severity Team chose [`severity.VeryLow`] Originally [`severity.High`] - [x] I disagree **Reason for disagreement:** Code attribution is not a minor bug; it is essential that due credit is given to the appropriate sources. Lack of this can contribute to issues of plagiarism, and similar issues. As the Developer Guide is used for a user to understand how the code works, this could lead to misunderstandings on who created the original code. This is a significant issue that could cause a major snowballing effect in code attribution in the future. For example, as it stands now, it can be assumed that CCBot as it stands now has been purely created by the team from scratch, which is incorrect as it builds off AB3. Thus, a `severity.High` is appropriate for this.