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

Update README.md #144

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

Update README.md #144

wants to merge 1 commit into from

Conversation

joserochh
Copy link
Contributor

Support notice

@joserochh joserochh requested a review from a team as a code owner July 4, 2023 18:34
Copy link
Contributor

@faberga faberga left a comment

Choose a reason for hiding this comment

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

Hi @joserochh

I understand your concern to inform the community that there is no official support for HEXL, but I'm not sure the tone of this notice is the right one.
Let me rephrase it, while communicating that the code is supplied "as is"

@faberga
Copy link
Contributor

faberga commented Jul 4, 2023

@joserochh Section 7 of the license (See below) already states that HEXL is provided on "AS IS" basis. I will rephrase the README change to emphasize this point,

7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.

@joserochh
Copy link
Contributor Author

@faberga Should we also rephrase Contributing section of the README to not encourage feedback or suggestion while there is no team to address those at the moment?

@faberga
Copy link
Contributor

faberga commented Jul 4, 2023

@joserochh, probably yes, but let me think about it a little more.

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