Ready to contribute #46
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In the next release, we have to update the minor version because of losing compatibillity with Node 6.14.2 and 6.14.3 (See #45). It means that reachs to the first stable release. To allow contributions into marp-core, we filled the lacked docs and contributing guideines.
Issue tracker also will open as soon as.
Our concern about opening an issue tracker is if we can keep tracking with in the correct repository when we have to track MANY issues as like as yhatt/marp. Most issue reporters would not mind about internal package structure, so it is hard that maintainer keeps tracking across the working repo.
However, it may be resolved by GitHub's new Issue transfer. The issue in the wrong repo could move where it actually belongs by maintainer.