Comments (7)
Yeah, @adiati98, I think we should add the issue thing to the intro course. It's a good way to get contributors into a better flow of contributing.
from guestbook.
@BekahHW, what do you think? Same to you @adiati98.
from guestbook.
@CBID2 when would 1. be not applicable?
I wonder if we need the documentation section at all. What might be more effective is after the getting started section having a question like:
How have you contributed to this repository?
- Updated documentation (You're finished with the PR template!)
- Added myself as a contributor (move on the the next section)
- Yes!!!
from guestbook.
@CBID2 when would 1. be not applicable?
I wonder if we need the documentation section at all. What might be more effective is after the getting started section having a question like:
How have you contributed to this repository?
Updated documentation (You're finished with the PR template!)
Added myself as a contributor (move on the the next section)
- Yes!!!
@BekahHW, 1 would be if contributors aren't adding their name to the guestbook. Like fixing a bug or updating other aspects of the repo(e.g. docs and adding features), but what you came up with is more effective.
from guestbook.
-
I quite agree with @BekahHW not to have "What type of PR is this?" section (and maybe also "Added to documentation?" section).
I might be wrong, but I think making the PR template focus on adding contributors to the guestbook is more effective here.
This repo is rarely receiving documentation updates except from maintainers. For that purpose, we can always adjust the PR templates ourselves if necessary (like add link PR to the related issue, etc.) or create one from scratch. -
- Put a
## Closes Issue
section after the What Type of PR is this? section
We can always add this one although we usually creates issue only to update docs.
In general, this repo doesn't require issue to add contributors. Except if we want to update the Contributing Guide and apply the suggestion for contributors to learn and practice how to create an issue and link it to the PR. Do we want to do this?
- Put a
from guestbook.
I quite agree with @BekahHW not to have "What type of PR is this?" section (and maybe also "Added to documentation?" section).
I might be wrong, but I think making the PR template focus on adding contributors to the guestbook is more effective here.
This repo is rarely receiving documentation updates except from maintainers. For that purpose, we can always adjust the PR templates ourselves if necessary (like add link PR to the related issue, etc.) or create one from scratch.
- Put a
## Closes Issue
section after the What Type of PR is this? sectionWe can always add this one although we usually creates issue only to update docs.
In general, this repo doesn't require issue to add contributors. Except if we want to update the Contributing Guide and apply the suggestion for contributors to learn and practice how to create an issue and link it to the PR. Do we want to do this?
Good point @adiati98! :) Doing this would be a great way to practice.
from guestbook.
@BekahHW I'll create an issue and work on this. 👍
from guestbook.
Related Issues (20)
- Bug: Unknown contribution type error when trying to run the npm run contributors:add command HOT 8
- Feature: Add a PR Template
- docs: Add extra instruction for manual entry and improve README HOT 3
- Feature: Add explanation to `git commit -am` HOT 3
- Bug: message repeats when contributor edits PR
- Feature: Add a section on how to solve Merge Conflicts to Contributing Guide HOT 2
- docs: Move the content of "Getting Started" and "Update Branch & Resolve Conflicts" sections to Intro to Open Source course HOT 3
- docs: Add screenshot requirement to PR template
- docs: Make adjustments to`CONTRIBUTING.md`
- docs: more adjustments needed in `Contributing.md` file
- Docs: Create an issue template to add users as contributors HOT 1
- Docs: Remove "Adding a New Section to the Documentation" section HOT 2
- Docs: Remove the "Running the Project Locally" from Contributing Guide HOT 2
- Docs: Adjust wording in the Contributing Guide HOT 3
- Feature: Clarification needed in Translation Guide HOT 3
- docs: Clarity about screenshot HOT 4
- Feature: Add @JulesRules65 as a contributor HOT 2
- Feature: add @chrisVCH as a contributor HOT 2
- Feature: Issue for commits pushed to main branch
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from guestbook.