Thanh, Hi, I agree with most of what you describe but I personally benefit from JIRA tracking/linking/history/testing/reopen/cross-repo issues. Perhaps you commit your fix - you may later need another fix, or another JIRA may need to reference/test your fix. There is also a small chance that the fix propagates a new issue – it would be nice to get historical info on the change. A smaller detail may be that your fix is part of a change that spans multiple repos – in this case a jira would be required. The JIRA acts a container for related commits. Also the bidirectional linking between the link in the commit message and the jira – are essential. There are orphaned jiras that don’t have the benefit of a link to their fixes in git. Thank you /michael
From: [email protected] [mailto:[email protected]] On Behalf Of Thanh Ha Sent: Friday, September 1, 2017 11:50 To: [email protected] Subject: [onap-tsc] Please consider making it easier for drive by contributions Dear TSC, I'd like to contribute to the ONAP project but one enforced policy makes it difficult for me to contribute. The particular policy is the one that blocks our ability to contribute a patch with this message "Missing issue-id in commit message". As someone who contributes to several open source communities I find this policy makes me less likely to want to contribute small fixes to the project as the time and effort it takes to open a Jira more than the effort it took to submit a patch (which is being blocked). As an example I would like to contribute a patch to the docs project to activate multithreaded docs build. This is a 4 character patch `-j 4 ` which will tell the job to run with 4 threads and speeds up the build a little. It took me less than 10 seconds to create this patch and submit along with a commit message that sufficiently describes the change. However requiring me to open a Jira for this trivial patch would make it take a few minutes for me to open the ticket, explain the change and then apply that JIRA ID to my commit message. This to me is a barrier for contributing to a project, especially an open source project that in my opinion should be accepting of community contributions no matter how small and in any form. It turns away folks who want to contribute small changes to a project including things like performance tweaks, fixing typos, fixing code style, improving code quality, etc... If it takes someone longer to open a Jira than it was for them to create a patch then the effort to open the Jira is unnecessary. I would like to ask the TSC to reconsider this policy of forcing potential contributors to open Jiras for contributions. Thanks for your consideration, Thanh This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at https://www.amdocs.com/about/email-disclaimer <https://www.amdocs.com/about/email-disclaimer>
_______________________________________________ ONAP-TSC mailing list [email protected] https://lists.onap.org/mailman/listinfo/onap-tsc
