Update LICENSE #274
Merged
Update LICENSE #274
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
TomWFox
reviewed
Sep 19, 2019
|
@TomWFox @phillwiggins Hi, we use Parse-SDK-Flutter in our app. We need show LICENSE of open source software we used. Could you help me? |
|
@yulingtianxia As far as I'm concerned it is ultimately up to @phillwiggins what license he wants to use. |
|
I'm really easy to be honest.
I've not done much with licenses before... Any suggestions?
…On Mon, 23 Sep 2019 at 13:38, Tom Fox ***@***.***> wrote:
@yulingtianxia <https://github.com/yulingtianxia> As far as I'm concerned
it is ultimately up to @phillwiggins <https://github.com/phillwiggins>
what license he wants to use.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274?email_source=notifications&email_token=AB4CPXQPJAP36H5SVZ5OH7TQLC2DXA5CNFSM4IYJXEJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7KWVLY#issuecomment-534080175>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB4CPXT3AZNLM2DPPCIIRXTQLC2DXANCNFSM4IYJXEJA>
.
--
Kind Regards
Phill Wiggins
[email protected]
|
Other repos in parse-community use BSD license, so I choose BSD 3-Clause. It's just a suggestion. |
|
Added as suggested.
It's currently on master branch.
…On Mon, Sep 23, 2019, 14:09 杨萧玉 ***@***.***> wrote:
I'm really easy to be honest. I've not done much with licenses before...
Any suggestions?
… <#m_7778373883808831240_>
On Mon, 23 Sep 2019 at 13:38, Tom Fox *@*.***> wrote: @yulingtianxia
<https://github.com/yulingtianxia> https://github.com/yulingtianxia As
far as I'm concerned it is ultimately up to @phillwiggins
<https://github.com/phillwiggins> https://github.com/phillwiggins what
license he wants to use. — You are receiving this because you were
mentioned. Reply to this email directly, view it on GitHub <#274
<#274>?email_source=notifications&email_token=AB4CPXQPJAP36H5SVZ5OH7TQLC2DXA5CNFSM4IYJXEJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7KWVLY#issuecomment-534080175>,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AB4CPXT3AZNLM2DPPCIIRXTQLC2DXANCNFSM4IYJXEJA
.
-- Kind Regards Phill Wiggins ***@***.***
Other repos in parse-community use BSD license, so I choose BSD 3-Clause.
It's just a suggestion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#274?email_source=notifications&email_token=AB4CPXUG4XJYBVMXUVGER6DQLC5ZHA5CNFSM4IYJXEJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD7KZNIY#issuecomment-534091427>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AB4CPXXNM5H2ET5HJWXGXMTQLC5ZHANCNFSM4IYJXEJA>
.
|
phillwiggins
approved these changes
Sep 23, 2019
Just as @TomWFox had said: "The copyright belongs to @phillwiggins." (Not Parse, LLC) |
phillwiggins
added a commit
that referenced
this pull request
Jan 11, 2020
* Release/1.0.25 - Updated versions * Release/1.0.25 - ParseFile change * Fix whereArrayContainsAll (#260) * Bug fix: 'set' method should force update by default. If someone change a property of object from 'get' method and then 'set' it in ParseObject, it should be dirty. (#262) * Fix About Retrieving Sessions (#263) * ParseObject.update/ParseInstallation.create/ParseSession.installationId (#264) * Fix About Retrieving Sessions * parseObject.update/ParseInstallation.put/ParseSession.installation * Refactored ParseUser.logout - resetting session id and deleting local data are now separate functions (#270) * Update LICENSE (#274) * Update LICENSE * Update LICENSE * Update LICENSE * Fixed permission for ACL's getWriteAccess (#277) * Update LICENSE * Fixed permission for ACL's getWriteAccess Fixes #275 * Optimize LiveQuery (#278) * reconsitution * reconnect when network state changed. * reconnect when resume. (#279) * Setting installationId in _Session object during sign-up (#293) Excellent work! * Release/1.0.25 - Add ParseUser update method * Release/1.0.25 - Add ParseUser update method * example app migration to use Sembast v2 (#294) * Setting installationId in _Session object during sign-up * example app migration to use Sembast v2 * cleanup and fixed a broken code (#295) * Setting installationId in _Session object during sign-up * example app migration to use Sembast v2 * updated .gitignore and cleaned unnecessary files in the repo * fixed broken code after rebase * updated .gitignore * Release/1.0.25 - Update dependencies Co-authored-by: 杨萧玉 <[email protected]> Co-authored-by: kidder <[email protected]> Co-authored-by: matskosan <[email protected]> Co-authored-by: Artem Demyanov <[email protected]> Co-authored-by: mregandla <[email protected]>
This was referenced Jan 17, 2020
fischerscode
pushed a commit
to fischerscode/Parse-SDK-Flutter
that referenced
this pull request
Sep 5, 2020
* Release/1.0.25 - Updated versions * Release/1.0.25 - ParseFile change * Fix whereArrayContainsAll (parse-community#260) * Bug fix: 'set' method should force update by default. If someone change a property of object from 'get' method and then 'set' it in ParseObject, it should be dirty. (parse-community#262) * Fix About Retrieving Sessions (parse-community#263) * ParseObject.update/ParseInstallation.create/ParseSession.installationId (parse-community#264) * Fix About Retrieving Sessions * parseObject.update/ParseInstallation.put/ParseSession.installation * Refactored ParseUser.logout - resetting session id and deleting local data are now separate functions (parse-community#270) * Update LICENSE (parse-community#274) * Update LICENSE * Update LICENSE * Update LICENSE * Fixed permission for ACL's getWriteAccess (parse-community#277) * Update LICENSE * Fixed permission for ACL's getWriteAccess Fixes parse-community#275 * Optimize LiveQuery (parse-community#278) * reconsitution * reconnect when network state changed. * reconnect when resume. (parse-community#279) * Setting installationId in _Session object during sign-up (parse-community#293) Excellent work! * Release/1.0.25 - Add ParseUser update method * Release/1.0.25 - Add ParseUser update method * example app migration to use Sembast v2 (parse-community#294) * Setting installationId in _Session object during sign-up * example app migration to use Sembast v2 * cleanup and fixed a broken code (parse-community#295) * Setting installationId in _Session object during sign-up * example app migration to use Sembast v2 * updated .gitignore and cleaned unnecessary files in the repo * fixed broken code after rebase * updated .gitignore * Release/1.0.25 - Update dependencies Co-authored-by: 杨萧玉 <[email protected]> Co-authored-by: kidder <[email protected]> Co-authored-by: matskosan <[email protected]> Co-authored-by: Artem Demyanov <[email protected]> Co-authored-by: mregandla <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix this issue: #271
Using BSD 3-Clause.