erisu opened a new pull request, #170:
URL: https://github.com/apache/comdev-site/pull/170

   Took me a while to figure out what "CoPDoC" stood for.
   
   I had to search for this acronym and found its meaning from other Apache 
projects, such as:
   
   - 
https://streampark.apache.org/community/contribution_guide/become_committer/
   - 
https://github.com/apache/ignite-3/blob/main/CONTRIBUTING.md#needed-contributions
   - https://www.mail-archive.com/dev@servicecomb.apache.org/msg04675.html
   - https://kyuubi.apache.org/become_pmc_member.html
   
   I was going to submit a PR to add the meaning of the acronym to this page, 
but then I noticed the last commit on this file actually removed it, about 10 
months ago.
   
   - https://github.com/apache/comdev-site/pull/118
   
   If we are removing the acronym's definition, I think we should also remove 
its usage.
   
   In my opinion, I didn't see anything wrong with the acronym, but perhaps the 
"Contributing A Project - CoPDoC" section could have been merged with the 
"Anyone Can Become A Committer" section at the point it's first used.
   
   It seems the acronym was added by SorraTheOrc in 2011 and mentioned a few 
times in the mailing list, but I couldn't find a discussion thread about its 
creation.
   
   The primary reason I encountered this acronym is because I am seeking to 
enhance the contributing documentation for the project I am involved with. I 
aimed to clearly communicate that anyone could contribute to various aspects of 
the project, including Project (CI, team communication, task flow, etc.), 
Community (supporting users in how to use the project or responding to 
tickets), Documentation, and Code. Not limited to code only.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@community.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to