Closed yan12125 closed 3 years ago
I'd like to use GPLv3 for this project. What do others think?
I'm fine with using GPLv3 for my prior contributions.
Ping other contributors
@MarvelousBlack @SilverRainZ @VOID001 @Xuanwo @a-wing @attenuation @axionl @bennyyip @cuihaoleo @farseerfc @felixonmars @lilacbot (?) @petronny @renyuneyun @yuyichao @zsrkmyn
lilacbot has a commit c990c5d67e10939b8e85b95e46ea00b7227c5e40. @lilydjwg Is that authored by you?
I'm fine with using GPLv3 for my prior contributions.
I'm fine with using GPLv3 for my prior contributions.
Checkbox for "I'm fine with using GPLv3 for my prior contributions.":
Checkbox for "I'm fine with using GPLv3 for my prior contributions.":
Well, most of packagers do not have write access to this repo, and thus modifying others' comments is not allowed.
lilacbot has a commit c990c5d. @lilydjwg Is that authored by you?
Yes. I forgot to explicitely use my name to commit on the build machine.
I'm fine with using GPLv3 for my prior contributions. (Explicit statement because I cannot change the checkbox)
I'm fine with using GPLv3 for my prior contributions.
I'm fine with using GPLv3 for my prior contributions.
I'm fine with using GPLv3 for my prior contributions.
I'm fine with using GPLv3 for my prior contributions.
I'm fine with using GPLv3 for my prior contributions.
I think there are only spaces and empty lines are left as my contributions. For these spaces and empty lines, I'm fine with GPLv3.
If there are anything else contributed by me, I'm fine with GPLv3 for them as well.
@zsrkmyn A large portion of your valuable contributions to usage.rst is still present in the latest commit (107835f2fb9409a3356dbbea45e578210da39818) [1] and it does provide great information for those who are interested in lilac like me :)
[1] https://github.com/archlinuxcn/lilac/blame/107835f2fb9409a3356dbbea45e578210da39818/usage.rst
I'm fine with using GPLv3 for my prior contributions.
I'm fine with using GPLv3 for my prior contributions.
I'm fine with using GPLv3 for my prior contributions.
I'm fine with using GPLv3 for my prior contributions.
@renyuneyun could you have a look at this?
I'm fine with using GPLv3 for my prior contributions.
(Sorry I didn't check github notifications, and the emails went to a strange place...)
Sorry I didn't check github notifications, and the emails went to a strange place...
No problem!
@cuihaoleo mind to have a look? Your prior contribution is https://github.com/archlinuxcn/lilac/commit/1f81d456d16add2481a2f25723abee32bd96c0ee, and it's still used in today's lilac: https://github.com/archlinuxcn/lilac/blob/f7f64db993c681629a2efa1b24b87bf8995014b8/lilac2/api.py#L425-L440.
I'm fine with using GPLv3 for my prior contributions!!!
Thanks everyone for the agreement! Now that it is OK to relicense this project as GPLv3: #170.
To properly package lilac, a license statement is needed. There are two different levels of formality to do this:
The less formal way - @lilydjwg picks some license and commits a LICENSE file
The formal way. I consider chaging from no license ("All Rights Reserved") to some specific license as some kind of relicensing, so we need to establish an agreement from all previous contributors [1]. Here is an example: [2].
[1] https://github.com/archlinuxcn/lilac/graphs/contributors [2] https://github.com/mpv-player/mpv/issues/2033