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.

Sign up for GitHub

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

Jump to bottom

Verify EULA (End User License Agreement) #7

Open
speqtr opened this issue Dec 7, 2019 · 7 comments
Open

Verify EULA (End User License Agreement) #7

speqtr opened this issue Dec 7, 2019 · 7 comments
Assignees
@speqtr @nnian
Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Milestone
QWCX v1.0.0

Comments

@speqtr
Copy link
Contributor

speqtr commented Dec 7, 2019

Updated LICENSE.txt per @Xecute0101 request.

And since I'm not a lawyer, I'm opening this issue to discuss (and maybe update) LICENSE.txt content with the team 🙂

cc @exploshot @nnian @Xecute0101 @who-biz
@speqtr speqtr added enhancement New feature or request help wanted Extra attention is needed question Further information is requested labels Dec 7, 2019
@speqtr speqtr added this to the QWCX v1.0.0 milestone Dec 7, 2019
@speqtr
Copy link
Contributor Author

speqtr commented Dec 7, 2019

@Xecute0101 requirement for "splash screen" can be found under 2.3.

@who-biz
Copy link

who-biz commented Dec 7, 2019 •
edited
Loading

I have left the organization, and need time to thoroughly review this, if it applies to my work. For now, LMDB code is public and pretty much functional. I don’t foresee myself being willing to do anymore work beyond finishing that up, where necessary.

If someone could please let me know if this applies to LMDB or not, that would be great.

@Xecute0101
Copy link

Xecute0101 commented Dec 8, 2019 •
edited
Loading

I have left the organization, and need time to thoroughly review this, if it applies to my work. For now, LMDB code is public and pretty much functional. I don’t foresee myself being willing to do anymore work beyond finishing that up, where necessary.

If someone could please let me know if this applies to LMDB or not, that would be great.

This is end user license agreement of wallet, so if you are a software user or a developer who will use the codebase of this particular repo will be subjected to EULA. Nothing to do with LMDB work since it is for daemon.

@nnian
Copy link
Member

nnian commented Dec 10, 2019

Okay i've read the terms. Looks like a default EULA with added 2.3 Slash Screen part?
So the "The Qwertycoin Team" is the new Slogans Tag for all development stuff?

@speqtr
Copy link
Contributor Author

speqtr commented Dec 11, 2019

@nnian, yes, new EULA for QWCX wallet contains mostly standard terms with a small update.

@speqtr
Copy link
Contributor Author

speqtr commented Dec 11, 2019 •
edited
Loading

Regarding "legal name", I had in mind The Qwertycoin Group, The Qwertycoin Team and simply Qwertycoin. Decided to go with The Qwertycoin Team. If it's not right, please, let me know, we can change it to something else if needed.

@Xecute0101, what do you think about this? Which one should we use in your opinion?

@Xecute0101
Copy link

Qwertycoin Project or Qwertycoin Community, I think it is better as Qwertycoin Project in my opinion.

This part is not so critical as it is already uploaded. Please continue with the development.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@speqtr speqtr

@nnian nnian

Labels
enhancement New feature or request help wanted Extra attention is needed question Further information is requested
Projects
None yet
Milestone
QWCX v1.0.0
Development

No branches or pull requests
4 participants
@speqtr @who-biz @Xecute0101 @nnian