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

Document options #72

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Document options #72

wants to merge 1 commit into from

Conversation

gabegorelick
Copy link
Collaborator

No description provided.

@rubenv
Copy link
Owner

rubenv commented Jan 12, 2015

Should we have this on the website as well? That keeps everything in one place.

https://angular-gettext.rocketeer.be/dev-guide/

There's an API reference section, but I never had time to add all modules.


## License

(The MIT License)

Copyright (C) 2013-2014 by Ruben Vermeersch <[email protected]>
Copyright (C) 2013-2015 by Ruben Vermeersch <[email protected]>
Copy link
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also add a line here with your details, given the amount of contributions it's only fair to do so :-)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tend to like Copyright (c) 2013-2015 by angular-gettext-tools contributors, especially since there's no copyright assignment, which means individual contributors maintain full rights.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also, this was automatically updated by my editor :-)

@gabegorelick
Copy link
Collaborator Author

The only issue with adding it to the website is if that means we have to update two places to document the API. I'm fine with a link to the README on the website, or automagically incorporating the API docs in this repo into the website though.

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

Successfully merging this pull request may close these issues.

2 participants