Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Improved foundation of community standards, project maintenance processes, and tooling #1078

Closed
1 of 4 tasks
joshbruce opened this issue Feb 25, 2018 · 2 comments
Closed
1 of 4 tasks

Comments

@joshbruce
Copy link
Member

joshbruce commented Feb 25, 2018

Under the new organization, we have a lot more freedom to do things. Thinking once we get to the 1.0 stage it would be nice to have things in place to help new contributors come in and get up and running in short order.

This Issue is for conversation related to ways we can make the operation and maintenance of the project itself easier. Things like README + CONTRIBUTING + templates and so on.

  • Why do we have a Makefile?
  • Are we keeping Bower support up to date?
  • What is the purpose of component.json? (Seems like a different type of package.json that is out of date.)
  • What is the purpose of the /man directory and its contents? (Seems like a different type of README this is out of date.) - /man contains the man page that is brought up when you run marked --help.
@joshbruce joshbruce added this to the v1.0.0 - All the nope release milestone Feb 25, 2018
@joshbruce joshbruce self-assigned this Feb 25, 2018
@Feder1co5oave
Copy link
Contributor

Good points. 1,2 and 3 I don't know.

/man contains the man page that is brought up when you run marked --help.
I don't know how to edit that, and if it is up to date.

@joshbruce
Copy link
Member Author

Closing as relatively complete.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
No open projects
Development

No branches or pull requests

2 participants