Meet the new maintainer
I originally started maintaining Sparse as a result of trying to merge various patches related to my PhD research. Now I don't have frequent Sparse patches of my own anymore, and due to my PhD studies and other projects, I've become significantly less responsive, while Sparse itself has enjoyed increased development interest. Thus, it seems only fair that I should hand off maintainership to someone else who has a pile of patches they want to merge.
Christopher Li has done an excellent job hacking on Sparse, and has already demonstrated the ability to maintain a Sparse tree and merge other people's patches. I believe Chris would make an excellent maintainer for Sparse.
I still plan to listen in on the Sparse community, and perhaps submit some future patches, but effective immediately^Wa while ago, Chris will start running the show and accepting your patches and contributions.
- Josh Triplett
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Quoted 11 lines · Josh Triplett
I originally started maintaining Sparse as a result of trying to merge various patches related to my PhD research. Now I don't have frequent Sparse patches of my own anymore, and due to my PhD studies and other projects, I've become significantly less responsive, while Sparse itself has enjoyed increased development interest. Thus, it seems only fair that I should hand off maintainership to someone else who has a pile of patches they want to merge.
Christopher Li has done an excellent job hacking on Sparse, and has already demonstrated the ability to maintain a Sparse tree and merge other people's patches. I believe Chris would make an excellent maintainer for Sparse.
Agreed!
Quoted 3 lines
I still plan to listen in on the Sparse community, and perhaps submit some future patches, but effective immediately^Wa while ago, Chris will start running the show and accepting your patches and contributions.
Can you weigh in on the licensing threads, pretty please? That is still blocked on you, AFAIK.
Jeff
Sparse licensing
Quoted 2 lines · Jeff Garzik
Can you weigh in on the licensing threads, pretty please? That is still blocked on you, AFAIK.
Sure.
For my part, I'd *love* to see Sparse relicensed to something more palatable. Ideally, I'd love to see Sparse become GPL-compatible. I'd prefer a stronger copyleft over a weaker one.
I have no problem with relicensing Sparse to any of the following licenses, in rough order of preference:
- GPL (v2 or v3, with or without "or any later version")
- LGPL (v2.1 or v3, with or without "or any later version")
- Either of the above with some kind of additional exception similar to those used for GCC and related libraries.
- Any of the above dual-licensed with the OSL, if people care about preserving that for some reason. Seems unnecessarily complex to do so, though.
I'd prefer not to see Sparse relicensed to something entirely non-copyleft like the MIT license, but if the rest of the Sparse community wants that for some reason, I won't stand in the way.
If you need any more formal approval from me, please let me know.
Thanks,
Josh Triplett
Re: Sparse licensing
Quoted 25 lines · Josh Triplett
Quoted 2 lines · Jeff Garzik
Can you weigh in on the licensing threads, pretty please? That is still blocked on you, AFAIK.
Sure.
For my part, I'd *love* to see Sparse relicensed to something more palatable. Ideally, I'd love to see Sparse become GPL-compatible. I'd prefer a stronger copyleft over a weaker one.
I have no problem with relicensing Sparse to any of the following licenses, in rough order of preference:
- GPL (v2 or v3, with or without "or any later version")
- LGPL (v2.1 or v3, with or without "or any later version")
- Either of the above with some kind of additional exception similar to those used for GCC and related libraries.
- Any of the above dual-licensed with the OSL, if people care about preserving that for some reason. Seems unnecessarily complex to do so, though.I'd prefer not to see Sparse relicensed to something entirely non-copyleft like the MIT license, but if the rest of the Sparse community wants that for some reason, I won't stand in the way.
Quoted 5 lines
If you need any more formal approval from me, please let me know.
Thanks,
Josh Triplett
--
I'm not a lawyer or anything. Does this mean we're done? Can the Debian people move sparse out of non-free? Can I re-license smatch?
I used the following command to find who might have to sign off.
git log 1bcc92138dcdf718dc3e0c694565f56e669d6ee3 master | grep Author | cut -d : -f 2- | cut -d '<' -f 1 | sort | uniq -c | sort -n | less
Here are the list of people with other 5 commits. Maybe you should need at least 10 to get a vote?
6 Blue Swirl
6 Kamil Dudka
6 Michael Stefaniuc
7 Alexey Dobriyan
7 Damien Lespiau
7 [email protected]
8 Arnaldo Carvalho de Melo
8 Johannes Berg
9 Dave Olien
12 Pavel Roskin
16 Alexey Zaytsev
16 Oleg Nesterov
20 Luc Van Oostenryck
45 Alexander Viro
45 Jeff Garzik
69 Christopher Li
75 [email protected]
124 Al Viro
195 Josh Triplett
1250 Linus Torvaldsregards,
dan carpenter
Quoted 7 lines · Josh Triplett
I originally started maintaining Sparse as a result of trying to merge various patches related to my PhD research. Now I don't have frequent Sparse patches of my own anymore, and due to my PhD studies and other projects, I've become significantly less responsive, while Sparse itself has enjoyed increased development interest. Thus, it seems only fair that I should hand off maintainership to someone else who has a pile of patches they want to merge.
Quoted 8 lines
Christopher Li has done an excellent job hacking on Sparse, and has already demonstrated the ability to maintain a Sparse tree and merge other people's patches. I believe Chris would make an excellent maintainer for Sparse.
I still plan to listen in on the Sparse community, and perhaps submit some future patches, but effective immediately^Wa while ago, Chris will start running the show and accepting your patches and contributions.
I want to thank Josh for his wonderful contribution for the sparse project. I still have a lot of to learn to maintain a project like sparse. I will try my best.
Let me share you with my view of the project. In my mind, sparse has two roles:
1) A general purpose C compiler front end.
2) A sanitize checker for the Linux kernel source.
I like to see the project continue to evolve in this two directions. At the same time I want to maintain the current style of lean and fast.
Now I like to heard your view of the project as well. Where you want to the project go. After all, this is a community project.
Thanks for all your support.
Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-sparse" in the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html