Closed realpixelcode closed 2 years ago
Just read it. Very concise and digestible. Now I bet the core team is going to probably ask on how to integrate it into the main license for ease of access, or probably include a reference in the README.md.
Just read it. Very concise and digestible. Now I bet the core team is going to probably ask on how to integrate it into the main license for ease of access, or probably include a reference in the README.md.
Just added a link to the README.md :)
@realpixelcode, I was just rereading your license summary, and I was thinking that if this PR gets merged before mine (#79), I think I could possibly make a template for the summary as well (I would have to ask the core team because it would require different API). What do you think?
In principle, I find that a good idea, I'm just wondering how you would do that? A script would most likely not be sufficiently "intelligent" enough to generate a summary out of a new licence text itself.
I mean to modify the existing context to build the summary from its own template. This is much more simpler than machine learning.
Ok, go ahead then, I guess 😊
Sorry for the late response. I thought I responded earlier.
(edited for grammar)
Still waiting for review from the core team. They may not want to "template-ify" the summary.
Sorry for the late response. I thought I responded earlier.
No worries, mate :) Aren't we multiple time zones apart anyway? 😄 Also, others take much longer. 🤷
Hello @realpixelcode. I can see that this PR is not getting merged; the same is happening for me, so I decided to prefix the title my PR (#79 ) with [Stale!]
, and I'm thinking about closing it entirely and keeping the branch for when someone wants to re-open it.
Sorry for the delay here, thanks for the contribution!
No worries :)
Adds an easy-to-understand summary of the licence. Fixes #72.