samredai opened a new pull request #3414:
URL: https://github.com/apache/iceberg/pull/3414


   I noticed that the community profile (displayed on the Insights tab) is not 
all nice and green so I thought we could tackle these items (read more here: 
[About community profiles for public 
repositories](https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/about-community-profiles-for-public-repositories)).
 This PR adds a simple contributing guideline doc, everyone please chime in 
with things that should be added/removed! :)
   
   <img width="1570" alt="Screen Shot 2021-10-28 at 7 08 32 PM" 
src="https://user-images.githubusercontent.com/43911210/139361966-2528981c-a670-44e3-80c0-0a9cca6cea9d.png";>
   
   As for the Issue template and PR template, I'd like to suggest some 
variation of these templates created by Steven Mao: 
https://github.com/stevemao/github-issue-templates
   
   # *Simple Issues template:*
   
   ## Expected Behavior
   
   
   ## Actual Behavior (please include stacktrace if possible)
   
   
   ## Steps to Reproduce the Problem
   
     1.
     2.
     3.
   
   ## Specifications
   
     - Version of Iceberg:
     - Platform:
   
   
   
   
   
   # *Simple Pull Request template:*
   
   Fixes #
   
   ## Proposed Changes
   
     -
     -
     -
   
   
   
   As for the last item, a repo admin should be able to enable reported content 
from the settings page. Here's more info from the github docs: 
https://docs.github.com/en/communities/moderating-comments-and-conversations/managing-reported-content-in-your-organizations-repository


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to