* feat: added release process
* fix: removed debug echo's
* fix: fixed typo and bug
- replaced // with /# to remove "v" prefix only, not all "v" in string
* fix: updated docs
* feat: suspending, banning, now propogation
* feat: adapting to `now`
* feat: support auth for suspension/banned
* feat: added trace-id to requests
* feat: new mutation api with hooks support
* feat: added user status filtering, current field
* feat: Implement filter by status, adapt to new USER_STATUS type, add lookup helper <3
* fix: typo
* fix: tests
* chore: rename banned status to ban status
* test: feature test + lots of test helper improvements e.g. types
* fix: add translation to ban user modal
* fix: translation
* fix: test
* feat: added text indexes, query param to edges
* fix: cleaned up, added createdAt index
* fix: improved indexing support
* feat: integrate search into community and stories
* feat: adorn with search button
* test: add tests
* feat: implement stories
* test: add feature test
* fix: id name
* fix: improve word breaks, column widths
* fix: snapshots
* feat: add min width to status dropdown button
* fix: polishing
* feat: Add table ui component
* feat: community user table
* feat: filters and role change
* fix: add some comments
* fix: user viewer
* fix: snapshots
* test: add tests
* fix: better popover experience
* fix: test
* chore: use enum
* feat: prevent server side setting your own role
* fix: cleanup
* feat: support blue color in message
* feat: Show message when comment is in review
* feat: handle non-visible comment status
* test: add feature test for handling invisible comment status
* fix: apply review
* chore: better comment :-)
* Update isVisible.ts
* feat: adhere to char count settings for posting top level comments
* fix: remove bidi characters during test
* test: add feature tests for charCount
* test: update snapshots
* test: add feature test for updating settings
* feat: use red color and warn icon (from review)
* feat: Implement charCount for reply
* feat: charCount for edit comment
* test: update snapshots
* feat: Handle server errors in client
* refactor: use enum ERROR_TYPES
* chore: better comment
* fix: lint
* fix: also look in queries for custom errors
* feat: moved html-webpack-plugin to custom server templates in production
* fix: fixed templates
* fix: removed sri for the time being
* fix: fixed up tests for new field name
* chore: Rename InnerProps to Props
* feat: Render community guidelines
* chore: refactor schema communityGuidelines* settings into it's own type
* test: update snapshots
* feat: moderation config
* feat: configure banned and suspect words
* chore: upgrade react and test libs to the newest version <3
* chore: upgrade typescript + some refactor
* feat: general, organization and advanced configuration panes
* fix: translation
* feat: speedup fetching markdown editor
* feat: localize markdown editor
* chore: refactor container names
* chore: rename infobox to communityGuidelines
* feat: closing comment streams duration config
* test: add feature tests for configurations
* fix: mock only console.error
* chore: upgrade node
* chore: require node >= 10
* fix: better validation and default values
* feat: Make DurationField a general purpose component and reuse for Edit Comment Timeframe
* test: add unit test for duration field
* fix: patch for bug when built in production
* chore: bump npm version to latest
* fix: adapted Dockerfile to new version of node
* refactor: harmonized seconds/milliseconds to seconds
* fix: resolve bug from merge conflict
* feat: added user validation
* fix: adapt client validation to match servers
* fix: snapshots
* feat: moved validation code to common
* chore: renamed utils/validate to helpers/validate
* fix: applied fix for reaction mutation
* fix: removed comment length flag
* feat: added additionalDetails field to flags
* feat: added other flag type
* feat: decision history components
* feat: implement decision history container
* test: add unit tests
* test: integration test
* test: fix remaining snapshots
* test: add more concepts from react-testing-library
* fix: wrap long username into the next line
* fix: fallback to word-break: break-all;
* fix: renamed snake case to camel case
* fix: changed case for mutators
* fix: renamed all snake case to camel case for db
* feat: added support for comment revisions + split comment actions
* fix: updated tests
* feat: implemented CommentModerationAction
* fix: fixed case issues
* feat: enabled WeakMap for wordList processsing
* chore: npm audit
* feat: added mutations for removing + scraping stories
- added mutation for removing stories
- added mutation for scraping stories
- renamed all delete* to remove* to avoid reserved keyword collision
* fix: linting
* feat: implemented createStory
* feat: added support for createStory
* feat: improved Story deletion
- Deletes comments on the deleted Story
- Deletes actions of comments that were deleted via new
`root_item_id` parameter for Comment Action's
- Added logging around critical components of the remove
process
* feat: implemented mergeStory
- Added new merge function for root actions
- Added new merge function for story comments
- Added new merge function for comment status counts
- Added new remove stories function
* fix: fixed story creation method
* fix: added action count merging
* fix: removed outdated file
* fix: removed queue that got duplicated via rebase
* fix: prevent error when action counts are empty
- New Time scalar type is implemented on the Server
- Single Sign-On keys can now be generated
- Single Sign-On keys can be regenerated
- Single Sign-On keys now store the date they were generated on.
- Initial implementation of `AuthenticationTargetFilter`'s
* Fixing the commentCount for 0 comments
* Show signIn when logged-off user reacts to a comment
* Snapshots updated
* removing graphiql
* Reaction: Icon - Label - Count
* 'next-comment-counts' of github.com:coralproject/talk: (53 commits)
fix: Readd and fix App unittest
fix: undesired margin
Correct optimitic updates
fix: correct typings
fix: linting
Optimistic Responses updated
Adding optimisticresponse for deleteCommentReaction
Changes
test: use baseComment and baseAsset in fixtures
fix: lint
test: simplify tests
fix: pass settings to deeper ReplyListContainer
fix: remove debug
fix: test updates
feat: replaced respect with reaction and added some options!
Adding spected
More snapshots
It was the optimistic response
Adding actionCounts to the fixtures
Updated snapshots
...
* 'next' of github.com:coralproject/talk: (53 commits)
fix: localization keys
fix: graphql schema not compiling
Added translations
test: fix snapshots
feat: hide profile tab when not logged in
fix: translations, typings, cleanup and fix view conversation
fix: apply suggestions
fix: improve typings
feat: cleanup of router
feat: simplified view
Presentational components, events, tabs and more
updated snapshots
Updated Snapshots
Adding Snapshots and translations
Adding Snapshots and translations
feat: added Asset edge on the Comment
Setting COMMENTS as activeTab
Setting CommentID
deleting old snap
No need for local state for now
...
* 'next-profile' of github.com:coralproject/talk: (21 commits)
test: fix snapshots
feat: hide profile tab when not logged in
fix: translations, typings, cleanup and fix view conversation
fix: apply suggestions
fix: improve typings
feat: cleanup of router
feat: simplified view
deleting old snap
No need for local state for now
Routing, Navigation, Styles
using found withRouter
Mapping /admin as /admin.html in devMode
Adding found
Adding Found Relay to the Admin side
Add tests
Adapt snapshots
Add tests
Implement Show Conversation Link
First iteration of admin
wip
...
* 'admin' of github.com:coralproject/talk: (23 commits)
[next] SSO Refactor (#1912)
Upgrade rte (#1906)
review: fixes
Simplify getLevelClassName
Refactor indent level className
Remove unused line
Give last level a display name
More comments
More comments
Add some comments
More tests
Implement local reply list for last threading level
fix: test fixes
fix: test patches
fix: fixed issues with sorting
fix: addressed cursor issue
fix: removed dead code comment
fix: updated comment
feat: prime current user in user cache
feat: added root parent edge
...
* 'next-respect' of github.com:coralproject/talk:
Upgrade rte (#1906)
fix: patch for sort bug
feat: added dontAgree create/delete mutations
Simplify getLevelClassName
Refactor indent level className
fix: cleanup of comments service
Remove unused line
feat: added flag creation and deletion mutations
fix: addressed test updates
feat: support deleting comment reactions
Give last level a display name
More comments
feat: added reaction adding mutation
fix: renamed, middleware fixes
More comments
Add some comments
More tests
Implement local reply list for last threading level
fix: restricted action counts on Asset's
Implement LocalReplyListContainer
* 'next-profile' of github.com:coralproject/talk:
Simplify getLevelClassName
Refactor indent level className
Remove unused line
Give last level a display name
More comments
More comments
Add some comments
More tests
Implement local reply list for last threading level
Implement LocalReplyListContainer
* 'next' of github.com:coralproject/talk:
[next] Embed plus (#1877)
[next] Permit (#1899)
Use upstream @types/recompose
[next] Limited threading (#1894)
More clarifying comments
Improve cross browser support
Don't use css capitalize
Upgrade RTE to fix a paste issue
[next] Resubscribe local state (#1884)
Styling fixes
WIP
Update snapshots
Namespace ids
Move styles to button
* 'next-edit' of github.com:coralproject/talk:
Implement SetActiveTabMutation
Change translation strings
Add activeTab to local state
Move files into tab structure
* 'next' of github.com:coralproject/talk:
Adapt snapshot
Fix lint
Only show edit button for the author
Use Message Component
Adapt integration test
Fix integration test
Add edited marker
fix: remove assetID from client queries to edit comment
feat: merge metadata during edit
fix: remove assetID from EditCommentInput
Fix linting
Add integration tests
Add integration test
More unit tests
Fix lint and test
Implement edit
* 'next' of github.com:coralproject/talk:
Adapt snapshot
Fix lint
Only show edit button for the author
Use Message Component
Adapt integration test
Fix integration test
Add edited marker
fix: remove assetID from client queries to edit comment
feat: merge metadata during edit
fix: remove assetID from EditCommentInput
Fix linting
Add integration tests
Add integration test
More unit tests
Fix lint and test
Implement edit
* 'next' of github.com:coralproject/talk:
new snapshots after rebuilding the schema
new snapshots after rebuilding the schema
updated status
changes
Updated tests
Updated tests
Updated tests
Adding MessageIcon
Updated colors
Updated snapshots
Supporting icons with ValidationMessages
Updated API
Adding Message Matching the exact values
* 'ui-message' of github.com:coralproject/talk: (26 commits)
Adapt snapshots
Disable RTE when submitting
Wrap long words
Disable submit button when empty
Fix test
Fix types and tests
Remove outdated workarounds
Remove accidently commited files
Move uuid generation to TalkContext
Full PromisifiedStorage + Simplifications
Update package-lock
Return null cursor when creating comment
Change commentEdge to edge
Update snapshots
Fix types
Reply opens auth popup when not logged in
Better tests
Stream should work outside of iframe for debugging
Add test
Focus RTE when opening reply
...
* 'next' of github.com:coralproject/talk: (26 commits)
Adapt snapshots
Disable RTE when submitting
Wrap long words
Disable submit button when empty
Fix test
Fix types and tests
Remove outdated workarounds
Remove accidently commited files
Move uuid generation to TalkContext
Full PromisifiedStorage + Simplifications
Update package-lock
Return null cursor when creating comment
Change commentEdge to edge
Update snapshots
Fix types
Reply opens auth popup when not logged in
Better tests
Stream should work outside of iframe for debugging
Add test
Focus RTE when opening reply
...
* 'auth-views' of github.com:coralproject/talk: (27 commits)
feat: added token blacklisting
Compile schema when watching client (#1809)
TSLint imports ordered
Missing console.log
Adding variable to the scope and contemplating undefined from the BE
Tests updated
Updated tests and latest changes
User signedIn enters the stream
Adding test for FormField, InputDescription and Spinner
Updated docs
Adding Spinner Component to UI and some corrections to the docs
Working validation from the server using CallOuts
Working validation from the server using CallOuts
Handling error messages
Working type submit for forms - Button Component
Hitting the delete route and deleting the token
SignOff Mutation
Progress
Working signin and comment
Able to Sign In
...
* 'rest-next' of github.com:coralproject/talk:
Support rest and implement SignIn and SignUp Rest + Mutations
Add rest endpoints
Add rest client
Use setAuthToken mutation
Add post message listeners
Add complex value test
Add PostMessage Service
Fix linter
Support authentication
* 'next' of github.com:coralproject/talk:
Readd comments not found
Make readonly and add translations
Add localization
Change text
Add SetViewMutation
Get view from query + tests
Styling, refactor + tests
Add UserBox
Add auth target
Tiny refactor
Merge branch 'next' of github.com:coralproject/talk into permalink
* 'next' of github.com:coralproject/talk:
[next] ClickOutside Component (#1757)
Support for ClickOutside
* 'permalink' of github.com:coralproject/talk: (102 commits)
feat: added support for --only flag
Ready
Support for refs
Working
Any
progress
merge conflicts
Make timeagoFormatter optional
More colors
Colors
Short circuit endless respawn
fix: new mongo parser
Remove jest from watcher config, as it doesnt run well inside
Add jest set
Apply suggestions
Move react-timeago to dev
Upgrade docz
Cleanup docz scripts
Support watcher sets
[next] Support server side jest testing (#1747)
...
Merge pull request #1731 from coralproject/next-watcher-flags
Watcher --only
Use JSDocs comments (#1727)
Merge branch 'next' into prevent-compile-loop-relay
Merge pull request #1726 from coralproject/prevent-compile-loop-relay
[next] Adapt relay watch config
[next] Remove nodemon (#1725)
* Remove old nodemon configs
* Remove nodemon
[next] Jest implementation for React Components (#1733)
* Make jest testing work with custom path and css modules
* Add first test
* feat: added unit tests to ci
* fix: updated package-lock.json
* Update cssTransform.js
* Update cssTransform.js
* Fix test in ci
Adapt files.exclude (#1736)
Permalink ui
Adding Copy to clipboard functionality
WIP
clean request
wip
progress
progress
work in progress
wip
ui functionality
Translations :/
wip
Merge branch 'permalink' of github.com:coralproject/talk into permalink
* 'permalink' of github.com:coralproject/talk: (42 commits)
[next] Support server side jest testing (#1747)
Update snapshots
Add comments
Remove precss
Move react-responsive to dev deps
Remove comment
Mobile first approach
Support standard css variables, dynamically set spacing-unit
Add docs
Fully implement Flex and MatchMedia
Responsive Components <3
fix: linting
fix: adjusted pageInfo
Remove obsoloe snapshot
Move jsdom to dev deps
Mark comments as always returning a value
Add comment
Fix unit tests
Translate, concept for translation and id strings
Add aria props
...
Adding Attachment and Popover Component
merge conflicts
progress
Any
Working
Support for refs
Ready
Merge branch 'permalink' of github.com:coralproject/talk into permalink
* 'permalink' of github.com:coralproject/talk: (101 commits)
Ready
Support for refs
Working
Any
progress
merge conflicts
Make timeagoFormatter optional
More colors
Colors
Short circuit endless respawn
fix: new mongo parser
Remove jest from watcher config, as it doesnt run well inside
Add jest set
Apply suggestions
Move react-timeago to dev
Upgrade docz
Cleanup docz scripts
Support watcher sets
[next] Support server side jest testing (#1747)
Make filter only a pure function
...
* 'permalink' of github.com:coralproject/talk: (101 commits)
Ready
Support for refs
Working
Any
progress
merge conflicts
Make timeagoFormatter optional
More colors
Colors
Short circuit endless respawn
fix: new mongo parser
Remove jest from watcher config, as it doesnt run well inside
Add jest set
Apply suggestions
Move react-timeago to dev
Upgrade docz
Cleanup docz scripts
Support watcher sets
[next] Support server side jest testing (#1747)
Make filter only a pure function
...
Merge pull request #1731 from coralproject/next-watcher-flags
Watcher --only
Use JSDocs comments (#1727)
Merge branch 'next' into prevent-compile-loop-relay
Merge pull request #1726 from coralproject/prevent-compile-loop-relay
[next] Adapt relay watch config
[next] Remove nodemon (#1725)
* Remove old nodemon configs
* Remove nodemon
[next] Jest implementation for React Components (#1733)
* Make jest testing work with custom path and css modules
* Add first test
* feat: added unit tests to ci
* fix: updated package-lock.json
* Update cssTransform.js
* Update cssTransform.js
* Fix test in ci
Adapt files.exclude (#1736)
Permalink ui
Adding Copy to clipboard functionality
WIP
clean request
wip
progress
progress
work in progress
wip
ui functionality
Translations :/
wip
Merge branch 'permalink' of github.com:coralproject/talk into permalink
* 'permalink' of github.com:coralproject/talk: (42 commits)
[next] Support server side jest testing (#1747)
Update snapshots
Add comments
Remove precss
Move react-responsive to dev deps
Remove comment
Mobile first approach
Support standard css variables, dynamically set spacing-unit
Add docs
Fully implement Flex and MatchMedia
Responsive Components <3
fix: linting
fix: adjusted pageInfo
Remove obsoloe snapshot
Move jsdom to dev deps
Mark comments as always returning a value
Add comment
Fix unit tests
Translate, concept for translation and id strings
Add aria props
...
Adding Attachment and Popover Component
merge conflicts
progress
Any
Working
Support for refs
Ready
* 'permalink' of github.com:coralproject/talk: (42 commits)
[next] Support server side jest testing (#1747)
Update snapshots
Add comments
Remove precss
Move react-responsive to dev deps
Remove comment
Mobile first approach
Support standard css variables, dynamically set spacing-unit
Add docs
Fully implement Flex and MatchMedia
Responsive Components <3
fix: linting
fix: adjusted pageInfo
Remove obsoloe snapshot
Move jsdom to dev deps
Mark comments as always returning a value
Add comment
Fix unit tests
Translate, concept for translation and id strings
Add aria props
...
* 'next' of github.com:coralproject/talk:
Adapt files.exclude (#1736)
[next] Jest implementation for React Components (#1733)
[next] Remove nodemon (#1725)
Use JSDocs comments (#1727)
feat: added support for --only flag
Do not rerun relay compiler on its own changes
Merge branch 'next' into timestamp
Fix test and translations
Merge branch 'timestamp' of github.com:coralproject/talk into timestamp
* 'timestamp' of github.com:coralproject/talk:
Fix test and translations
Implement Timestamp
* Make jest testing work with custom path and css modules
* Add first test
* feat: added unit tests to ci
* fix: updated package-lock.json
* Update cssTransform.js
* Update cssTransform.js
* Fix test in ci
* Make jest testing work with custom path and css modules
* Add first test
* feat: added unit tests to ci
* fix: updated package-lock.json
* Update cssTransform.js
* Update cssTransform.js
* Fix test in ci
* wip
* Adding chokidar and types
* specifiying build tasks
* new structure, new types, executor and watchers
* Adding log
* Fully implemented watchers
* adapt vscode launc
* Add .babelrc.js to toplevel tsconfig project
* Typo
* Get schema path from .graphqlconfig
* Use watcher binary
* Add joi validation to watcher
* Remove fb-watchman for now
* Use correct ignore path
* Fix dist folder
* Allow setting watcher
* Per default only spawn one process at a time
* Support runOnInit
* Rename RestartingExecutor to LongRunningExecutor
* Use debounce instead of throttle
* Remove console log
* Debounce command execution
* Simplify debounce
* Watcher name change
* Typos
* Rename "watcher" root level config to "backend"
We expect everyone contributing to The Coral Project to follow this code of conduct. That means the team, contractors we employ, contributors, as well as anyone posting to our public or internal-facing channels.
We created it not because we anticipate any unacceptable behavior, but because we believe that articulating our values and obligations to one another reinforces the already exceptional level of respect among the team, and because having a code provides us with clear avenues to correct our culture should it ever stray from that course.
We commit to enforce and evolve this code over the duration of the project.
## Expected behavior
* Be supportive of each other.
* Be collaborative. Involve others in brainstorms, sketching sessions, code reviews, planning documents, and the like. It’s not only okay to ask for help or feedback often, it’s unacceptable not to do so.
* Be generous and kind in both giving and accepting critique. Critique is a natural and important part of our culture. Good critiques are kind, respectful, clear, and constructive, focused on goals and requirements rather than personal preferences. You are expected to give and receive criticism with grace.
* Be humane. Be polite and friendly in all forms of communication, especially remote communication, where opportunities for misunderstanding are greater. Use sarcasm carefully. Tone is hard to decipher online; make judicious use of emoji to aid in communication.
* Be considerate.
* Be tolerant.
* Respect people’s boundaries.
* Do not make it personal.
* Use welcoming and inclusive language.
* Offer to help if you see someone struggling or otherwise in need of assistance (taking care not to be patronizing or disrespectful).
* If someone approaches you looking for help, be generous with your time; if you’re under a deadline, direct them to someone else who may be of assistance.
* Go out of your way to include people in jokes or memes, recognizing that we want to build an environment free of cliques.
* Show empathy towards other community members
## Unacceptable behavior
We are committed to providing a welcoming and safe environment for people of all races, gender identities, gender expressions, sexual orientations, physical abilities, physical appearances, socioeconomic backgrounds, nationalities, ages, religions, and beliefs.
We expect that you will refrain from demeaning, discriminatory, or harassing behavior and speech.
Harassment includes, but is not limited to: deliberate intimidation; stalking; unwanted photography or recording; sustained or willful disruption of talks or other events; inappropriate physical contact; use of sexual or discriminatory imagery, comments, or jokes; and unwelcome sexual attention.
Furthermore, any behavior or language which is unwelcoming—whether or not it rises to the level of harassment—is also strongly discouraged. Much exclusionary behavior takes the form of microaggressions—subtle put-downs which may be unconsciously delivered. Regardless of intent, microaggressions can have a significant negative impact on victims and have no place on our team.
Other inappropriate behavior:
* Threats
* Slurs
* Pornography
* Spam
* Bullying
* Copyright infringement
* Impersonation of someone else
* Violating someone’s privacy
If you feel that someone has harassed you or otherwise treated you or someone else inappropriately, please alert the project lead at [andrewl@mozillafoundation.org](mailto:andrewl@mozillafoundation.org).
## Our Responsibilities
Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.
## Scope
This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.
## Enforcement
These guidelines are ambitious, and we’re not always going to succeed in meeting them. When something goes wrong—whether it’s a microaggression or an instance of harassment — there are a number of things you can do to address the situation. Depending on your comfort level and the severity of the situation, here are some suggestions:
* Address it directly. If you’re comfortable bringing up the incident with the person who instigated it, pull them aside to discuss how it affected you. Be sure to approach these conversations in a forgiving spirit: an angry or tense conversation will not do either of you any good. If you’re unsure how to go about that, try discussing with your manager or with the people and culture team first—they might have some advice about how to make this conversation happen.
If you’re too frustrated to have a direct conversation, there are a number of alternate routes you can take.
* Talk to a peer or mentor. Your colleagues are likely to have personal and professional experience on which to draw that could be of use to you. If you have someone you’re comfortable approaching, reach out and discuss the situation with them. They may be able to advise on how they would handle it, or direct you to someone who can. The flip side of this, of course, is that you should also be available when your colleagues reach out to you.
* Contact the project lead, Andrew Losowsky, [andrewl@mozillafoundation.org](mailto:andrewl@mozillafoundation.org), or the technical lead. We will work with you to help you figure out how to ensure that any conflict doesn’t interfere with your work, in confidence if you would prefer.
* Talk to Chris Lawrence. Chris oversees the project. He can be contacted at [clawrence@mozillafoundation.org](mailto:clawrence@mozillafoundation.org).
If you feel you have been unfairly accused of violating this code of conduct, you should contact Chris with a concise description of your grievance.
## Conclusion
We welcome your feedback on this and every other aspect of what we do as The Coral Project, and we thank you for working with us to make it a safe, enjoyable, and friendly experience for everyone involved in the project and what we do.
Above text is licensed CC BY-SA 4.0, adapted from the SRCCON code of conduct, FreeBSD’s code of conduct, Vox Media’s product team code of conduct, Medium’s code of conduct, as well as adapted from the Contributor Covenant.
Welcome! We are very excited that you are interested in contributing to Talk.
This document is a companion to help you approach contributing. If it does not do so, please [let us know how we can improve it](https://github.com/coralproject/talk/issues)!
By contributing to this project you agree to the [Code of Conduct](CODE_OF_CONDUCT.md).
## What should I Contribute?
There are at least three ways to contribute to Talk:
* Writing Code
* Writing Docs
* Providing Translations
## Writing Code
Conversation surrounding contributions begins in [issues](https://github.com/coralproject/talk/issues).
### When should I Create an Issue?
File an issue as soon as you have an idea of something you'd like to contribute. We would love to hear what you're thinking and help refine the idea to make it into the Talk ecosystem.
Please file issues if:
* you would like to contribute to Talk Core.
* you are building a Plugin that the current Plugin API doesn't support.
* you are building a Plugin and want advice.
### What should I include?
Coral has adopted an iterative, agile development philosophy. All contributions that make it into the Talk repository should start with a story or this form:
> As a [type of person] I'd like to be able to [do something] so that I can [get some result].
This exercise does two things:
* allows us to ground our technical choices in a clear, simple product need.
* expresses that product need in a way that doesn't imply a specific technical solution allowing for debate as to the best way to solve the problem.
Please feel free to provide as much detail as possible when filing the issue but please do keep the initial issue specific to one need and try to avoid including technical or design solutions.
If you have a specific technical or design solution in mind, please submit it as the first comment on the thread.
## Contributing Documentation
Clear docs are a prerequisite for a successful open source project. Contributing to the documentation is often more important than contributing to the code!
We are looking for _documentarians_ to:
* make clarity, grammar and completeness updates,
* create new / missing sections, and
* take the lead in making sections, or the over all structure better.
Our documentation is stored in markdown files in the [docs](docs) directory. We
use Jekyll to provide our docs. To preview:
```shell
cd docs
bundle install
bundle exec jekyll serve
```
Then visit http://127.0.0.1:4000/talk/.
If you'd like to discuss a contribution, please [file an issue](https://github.com/coralproject/talk/issues) describing the changes you would like to see.
## Contributing Translations
Talk's translations are stored in `.yml` files [here](https://github.com/coralproject/talk/tree/master/locales).
Translations can be submitted via pull request. If you do not use github, you can use 'en.yml' as a template and [email](https://coralproject.net/contact) the translations to us. We can import it into the repository.
## I want to contribute but I'm not sure what to do!
If you want to contribute but don't have a clear idea of exactly what that may be, here are some resources that may help:
### Product Roadmap
Please visit our product roadmap here: https://www.pivotaltracker.com/n/projects/1863625. If you'd like to take on any of our scheduled tasks we'd be forever grateful!
### Discussion Forum
If you'd like to discuss what we're up to, please visit or [community](https://community.coralproject.net/) or [contact us](https://coralproject.net/contact).
### Integrations
Have a favorite analytics engine? Data science service? CMS? Auth platform? Deployment platform or pipeline? Pet project? Consider building a plugin to integrate them!
### Favorite Features?
Do you have a favorite feature of an existing platform that's not yet been done in Talk? Sounds like Talk needs that feature.
Online comments are broken. Our open-source commenting platform, Talk, rethinks how moderation, comment display, and conversation function, creating the opportunity for safer, smarter discussions around your work. [Read more about Talk here](https://coralproject.net/products/talk.html).
Online comments are broken. Our open-source commenting platform, Talk, rethinks
how moderation, comment display, and conversation function, creating the
opportunity for safer, smarter discussions around your work.
[Read more about Talk here](https://coralproject.net/talk).
Built with <3 by The Coral Project & Mozilla.
Built with <3 by The Coral Project, a part of [Vox Media](https://product.voxmedia.com/).
## Try Talk!
Preview Talk easily by running Talk via a Heroku App:
You're just one click away from trying Talk - all you need is a Heroku account and a few minutes of your time.
<!-- START doctoc generated TOC please keep comment here to allow auto update -->
<!-- DON'T EDIT THIS SECTION, INSTEAD RE-RUN doctoc TO UPDATE -->
## Table of Contents
## Technical Documentation
- [Requirements](#requirements)
- [Running](#running)
- [Docker](#docker)
- [Source](#source)
- [Development](#development)
- [Design Language System (UI Components)](#design-language-system-ui-components)
- [Configuration](#configuration)
- [License](#license)
From getting up and running, to advanced configuration, to how to scale Talk, our [Talk Technical Docs](https://coralproject.github.io/talk/) have everything you need to know.
<!-- END doctoc generated TOC please keep comment here to allow auto update -->
## Product Guide
## Requirements
Learn more about Talk, including a deep dive into features for commenters and moderators, and FAQs in our [Talk Product Guide](https://coralproject.github.io/talk/how-talk-works).
When v5 releases to master, you'll be able to select it using
`coralproject/talk:5`.
## End-to-End Testing
### Docker
Talk uses [Nightwatch](https://nightwatchjs.org/) as our e2e testing framework. The testing infrastructure that allows us to run our tests in real browsers is provided with love by our friends at [Browserstack](https://browserstack.com).
The easiest way to get started with Talk is through our published Docker image
and provided example `docker-compose.yml` file. The following assumes that you
have Docker and Docker Compose installed on your local machine:
"description":"Please copy the App Name you choose above. If you did not choose one, please do so now and copy it here. Talk on Heroku will not work without this setting.",
"value":"https://<COPY APP NAME HERE>.herokuapp.com",
Some files were not shown because too many files have changed in this diff
Show More
Reference in New Issue
Block a user
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.