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.

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

Can it be an open source project? #1175

Open
52 of 59 tasks
evandrocoan opened this issue Jul 12, 2017 · 61 comments · May be fixed by #1570
Open
52 of 59 tasks

Can it be an open source project? #1175

evandrocoan opened this issue Jul 12, 2017 · 61 comments · May be fixed by #1570

Comments

@evandrocoan
Copy link
Contributor

evandrocoan commented Jul 12, 2017

Searching through the repository, I cannot find any mention to open source license:

  1. https://github.com/SublimeText/LaTeXTools/search?utf8=%E2%9C%93&q=license&type=

By this project being on Github, I am allowed to fork it by the Github TOS (Terms Of Service). However, I am not allowed to create derivative works from it (pull requests). Meaning I cannot fork this repository, change its code and perform pull requests without the danger/liability of being prosecuted by violating the All rights reserved copyright granted by berne convention law.


Update 2022-12-29

To approve the open-source license, go to the pull-request #1570, and hit the review now button at the sidebar, as shown in the following image, and type I agree with this license for my code. as the pull-request view message:

  1. image
  2. image

List of users contributing to this project, which agree to open source license to their contribution:

GitHub User Name Information

Update

When I ran the command I got not all names correctly, so I tried to manually fix it, but seems I made some mistakes. This is the original output:

I replaced the @ by <at>, in hope to avoid some robot spammers.

git log --pretty="%an/%cn, %ae/%cn" | sort | uniq
 1. Afri/GitHub, 5chdn<at>users.noreply.github.com/GitHub
 2. Andre Rein/Andre Rein, ra<at>ra23.net/Andre Rein
 3. Antonio Sanchez/Antonio Sanchez, antonio<at>panthera.ca/Antonio Sanchez
 4. Antonio Sánchez/Antonio Sánchez, antonio<at>panthera.ca/Antonio Sánchez
 5. Boris Zhou/Boris Zhou, bobo1239<at>web.de/Boris Zhou
 6. btstream/btstream, btstream<at>gmail.com/btstream
 7. btstream/btstream, btstream<at>hotmail.com/btstream
 8. btstream/Ian, btstream<at>gmail.com/Ian
 9. DaiZW/DaiZW, nonnullpointer<at>gmail.com/DaiZW
10. Daniel Fleischhacker/Daniel Fleischhacker, fleischhacker.daniel<at>gmail.com/Daniel Fleischhacker
11. danschrage/danschrage, danschrage<at>gmail.com/danschrage
12. deterenkelt/GitHub, deterenkelt<at>users.noreply.github.com/GitHub
13. Ed Doddridge/Ed Doddridge, edoddridge<at>gmail.com/Ed Doddridge
14. evandrocoan/evandrocoan, evandrocoan<at>hotmail.com/evandrocoan
15. Florian Zimmermann/Florian Zimmermann, flo<at>chaos-wg.net/Florian Zimmermann
16. Hannes Kaeufler/Hannes Kaeufler, hannes.kaeufler<at>gmail.com/Hannes Kaeufler
17. HughParsonage/GitHub, hugh.parsonage<at>gmail.com/GitHub
18. Hui Sun/Hui Sun, sunhuijim<at>gmail.com/Hui Sun
19. Ian/Ian, ig0774<at>gmail.com/Ian
20. ig0774/GitHub, ig0774<at>users.noreply.github.com/GitHub
21. ig0774/ig0774, ig0774<at>users.noreply.github.com/ig0774
22. Ilya Uvarenkov/Ilya Uvarenkov, trukanduk<at>gmail.com/Ilya Uvarenkov
23. James Brooks/James Brooks, ukjbrooks<at>gmail.com/James Brooks
24. Jeff Spencer/Ian, jeffspencerd<at>gmail.com/Ian
25. Jeremy Jay/Jeremy Jay, jeremy<at>pbnjay.com/Jeremy Jay
26. Josef Friedrich/Josef Friedrich, josef<at>friedrich.rocks/Josef Friedrich
27. Joseph Weigl/Joseph Weigl, joseph.weigl<at>gmail.com/Joseph Weigl
28. Juerg Rast/Juerg Rast, juergr<at>gmail.com/Juerg Rast
29. Lucas Nanni/Lucas Nanni, lucasnanni<at>gmail.com/Lucas Nanni
30. Mads Mobæk/Mads Mobæk, mads86<at>gmail.com/Mads Mobæk
31. Marciano Siniscalchi/Marciano Siniscalchi, margie<at>Marcianos-MacBook-Pro.local/Marciano Siniscalchi
32. Marciano Siniscalchi/Marciano Siniscalchi, msiniscalchi<at>gmail.com/Marciano Siniscalchi
33. Marciano Siniscalchi/Richard Stein, msiniscalchi<at>gmail.com/Richard Stein
34. Maximilian Berger/Maximilian Berger, snowdragon92<at>gmail.com/Maximilian Berger
35. Michael Walter/GitHub, michael.walter<at>gmail.com/GitHub
36. Mikey Saugstad/GitHub, michaelssaugstad<at>gmail.com/GitHub
37. msiniscalchi/msiniscalchi, msiniscalchi<at>gmail.com/msiniscalchi
38. omniearth/omniearth, florian<at>slurm.(none)/omniearth
39. Peter Eichinger/Peter Eichinger, peter.eichinger<at>gmail.com/Peter Eichinger
40. Piotr Kaz´mierczak/Piotr Kaz´mierczak, piotrkazmierczak<at>me.com/Piotr Kaz´mierczak
41. Rafael Lerm/Rafael Lerm, rafaellerm<at>gmail.com/Rafael Lerm
42. Ray Fang/Ray Fang, i<at>lazarusx.com/Ray Fang
43. Richard Stein/GitHub, r-stein.github<at>web.de/GitHub
44. Richard Stein/Richard Stein, r-stein.github<at>web.de/Richard Stein
45. Scott Kuroda/Scott Kuroda, scott.kuroda<at>gmail.com/Scott Kuroda
46. Sean Zhu/Sean Zhu, interestinglythere<at>gmail.com/Sean Zhu
47. Sergey Slipchenko/Sergey Slipchenko, faergeek<at>gmail.com/Sergey Slipchenko
48. Stefan Ollinger/Stefan Ollinger, Stefan.Ollinger<at>gmx.de/Stefan Ollinger
49. Tobias Diez/GitHub, tobiasdiez<at>gmx.de/GitHub
50. Tobias Schmidt/Tobias Schmidt, royalts<at>gmail.com/Tobias Schmidt
51. Ulrich Gabor/Ulrich Gabor, ulrich.thomas.gabor<at>googlemail.com/Ulrich Gabor
52. Wallace Wu/Wallace Wu, cwwwu<at>uwaterloo.ca/Wallace Wu
53. Wes Campaigne/Wes Campaigne, westacular<at>gmail.com/Wes Campaigne
54. William Ledoux/William Ledoux, william.ledoux<at>gmail.com/William Ledoux
55. williamledoux/williamledoux, william.ledoux<at>gmail.com/williamledoux


So far, the names I mistake were:

Wrong Name Used .................................................... Correct Name After Fix .................................
GitHub User User Name GitHub User User Name
1 @florian Florian Hartmann @omniearth Florian Mueller
2 @blowfish880 Michael Walter @misaugstad Mikey Saugstad
3 @misaugstad Mikey Saugstad @msiniscalchi Marciano Siniscalchi
4 @antonio Antonio Santos @cantonios C. Antonio Sánchez
5 @jspencer-cmm Jeff Spencer @excetara2 Jeffrey Spencer
6 @margie margie @msiniscalchi Marciano Siniscalchi
7 @josef Josef Dunne @Josef-Friedrich Josef Friedrich
8 @huisunsh Hui Sun @JimAmuro Hui Sun
9 @Mads86 mads86 @mobmad Mads Mobæk
10 @misaugstad Mikey Saugstad @catch22 Michael Walter
11 @i Ian Lozinski @LazarusX Ray Fang
12 @jeremy Jeremy Daer @pbnjay Jeremy Jay
13 @flo Florian Köberle @PoByBolek Florian Zimmermann
14 @ra ra @xrayn Andre Rein
15 @interestinglythere Sean Zhu @szhu Sean Zhu

I am applying a Hooray image to each reply I already counted/looked into and fixed the mistake.


Update 2

License suggestion copied from the files:

  1. SublimeText/LaTeXTools/latextools_utils/quickpanel.py
  2. alliedmodders/amxmodx/public/licenses/LICENSE.txt

This repository do not need to be under this license only. If you do not agree with, we can license you contribution under the license you would like.

The MIT License (MIT)

Copyright (c) 2017 LaTeXTools Contributors

Permission is hereby granted, free of charge, to any person obtaining
a copy of this software and associated documentation files
(the "Software"), to deal in the Software without restriction,
including without limitation the rights to use, copy, modify, merge,
publish, distribute, sublicense, and/or sell copies of the Software,
and to permit persons to whom the Software is furnished to do so,
subject to the following conditions:

The above copyright notice and this permission notice shall be included
in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT.
IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY
CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT,
TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE
SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Some components of LaTeXTools use a license other than the MIT License (MIT)
License. You must also adhere to these additional licenses in all respects. 
Each one of these files will declare under which license they are protected.

Changelog:

@r-stein
Copy link
Member

r-stein commented Jul 12, 2017

The problem with it given a license is that there are 42 contributors and everyone needs to agree to the adding of the license. So we should have added a license from the beginning, but can't add it now. The license for single files has been added because it's either from a different source or (I think) it is useful for other projects and people should have the possibility to reuse it.

However the philosophy behind the project is clearly that we want pull requests to improve LaTeXTools.

@evandrocoan
Copy link
Contributor Author

evandrocoan commented Jul 12, 2017

So I ran git log --pretty="%an/%cn, %ae/%cn" | sort | uniq:

  1. https://git-scm.com/docs/git-log/#_pretty_formats

And found the 46 names, which contributed with commits. Therefore we need everybody to reply here stating whether agree with a open source license for this project. Added them to the first post.

@RoyalTS
Copy link
Contributor

RoyalTS commented Jul 12, 2017

I agree with an open source license for this project.

@florian
Copy link

florian commented Jul 12, 2017

31 | @florian | omniearth/omniearth

I'm fairly certain that's not me, I'm not sure what omniearth is supposed to be and I don't recall contributing to this project.
I'm also not listed on https://github.com/SublimeText/LaTeXTools/graphs/contributors, although that's just commits in the master branch.

@edoddridge
Copy link
Contributor

Totally behind this - but it would be worth specifying which open source licence you want to add to the repo. There are a number of them and they grant different rights.

If there are sections of code that have been incorporated from other projects, then a given licence might not be compatible (if those projects have less permissive licences).

The only one mentioned explicitly above is the MIT licence, which is a very permissive licence, so that's good news.

@blowfish880
Copy link

i don't think this is me. i believe, i never contributed to this project.

@msiniscalchi
Copy link
Contributor

The best place to look for contributors is probably the README. The list above seems to have a few issues. For instance, I am listed several times, sometimes with the wrong handle and sometimes with the right handle but the wrong name :)

Anyway, I am of course all in favor of open-sourcing the plugin. It was totally my mistake not to do this from day one. I actually assumed that MIT licensing was the default for public projects. That's not the case.

However, some of the contributed code may have specific licenses.

@hanneskaeufler
Copy link
Contributor

sure 👍

@jrast
Copy link
Contributor

jrast commented Jul 12, 2017

Wow, long time ago I added 20 Lines or so to this project.

Shure, go ahead and add a license. Not shure which one would fit best...

@cwwwu
Copy link
Contributor

cwwwu commented Jul 12, 2017

I also agree with adding an open source license for this project.

@jspencer-cmm
Copy link

jspencer-cmm commented Jul 12, 2017 via email

@pkazmierczak
Copy link
Contributor

Sure, I'm ok with an open source license for this project.

@UlrichThomasGabor
Copy link

You can put any license you want on my contribution.

@danschrage
Copy link
Contributor

danschrage commented Jul 12, 2017 via email

@Westacular
Copy link
Contributor

Sure, I agree with an open source license for this project

@williamledoux
Copy link
Contributor

Any license is fine with me

@tobiasdiez
Copy link
Contributor

I also agree with any open source license.

@trukanduk
Copy link
Contributor

Great idea! I agree with any open-source license.

@misaugstad
Copy link
Contributor

I will magnanimously allow my contribution, a correction of a typo in the readme, to be used by any and all in whatever manner they choose. Any open source license will do.

@antonio
Copy link

antonio commented Jul 12, 2017

@evandrocoan I've never contributed to this project. I believe you meant @cantonios based on the contributors list.

@evandrocoan
Copy link
Contributor Author

evandrocoan commented Jul 12, 2017

Sorry for some mistakes on the names, when I ran the command I got not all names correctly,
so I tried to manually fix it, but seems I made some mistakes. This is the original output from git:

I replaced the @ by <at>, in hope to avoid some robot spammers.

git log --pretty="%an/%cn, %ae/%cn" | sort | uniq
 1. Afri/GitHub, 5chdn<at>users.noreply.github.com/GitHub
 2. Andre Rein/Andre Rein, ra<at>ra23.net/Andre Rein
 3. Antonio Sanchez/Antonio Sanchez, antonio<at>panthera.ca/Antonio Sanchez
 4. Antonio Sánchez/Antonio Sánchez, antonio<at>panthera.ca/Antonio Sánchez
 5. Boris Zhou/Boris Zhou, bobo1239<at>web.de/Boris Zhou
 6. btstream/btstream, btstream<at>gmail.com/btstream
 7. btstream/btstream, btstream<at>hotmail.com/btstream
 8. btstream/Ian, btstream<at>gmail.com/Ian
 9. DaiZW/DaiZW, nonnullpointer<at>gmail.com/DaiZW
10. Daniel Fleischhacker/Daniel Fleischhacker, fleischhacker.daniel<at>gmail.com/Daniel Fleischhacker
11. danschrage/danschrage, danschrage<at>gmail.com/danschrage
12. deterenkelt/GitHub, deterenkelt<at>users.noreply.github.com/GitHub
13. Ed Doddridge/Ed Doddridge, edoddridge<at>gmail.com/Ed Doddridge
14. evandrocoan/evandrocoan, evandrocoan<at>hotmail.com/evandrocoan
15. Florian Zimmermann/Florian Zimmermann, flo<at>chaos-wg.net/Florian Zimmermann
16. Hannes Kaeufler/Hannes Kaeufler, hannes.kaeufler<at>gmail.com/Hannes Kaeufler
17. HughParsonage/GitHub, hugh.parsonage<at>gmail.com/GitHub
18. Hui Sun/Hui Sun, sunhuijim<at>gmail.com/Hui Sun
19. Ian/Ian, ig0774<at>gmail.com/Ian
20. ig0774/GitHub, ig0774<at>users.noreply.github.com/GitHub
21. ig0774/ig0774, ig0774<at>users.noreply.github.com/ig0774
22. Ilya Uvarenkov/Ilya Uvarenkov, trukanduk<at>gmail.com/Ilya Uvarenkov
23. James Brooks/James Brooks, ukjbrooks<at>gmail.com/James Brooks
24. Jeff Spencer/Ian, jeffspencerd<at>gmail.com/Ian
25. Jeremy Jay/Jeremy Jay, jeremy<at>pbnjay.com/Jeremy Jay
26. Josef Friedrich/Josef Friedrich, josef<at>friedrich.rocks/Josef Friedrich
27. Joseph Weigl/Joseph Weigl, joseph.weigl<at>gmail.com/Joseph Weigl
28. Juerg Rast/Juerg Rast, juergr<at>gmail.com/Juerg Rast
29. Lucas Nanni/Lucas Nanni, lucasnanni<at>gmail.com/Lucas Nanni
30. Mads Mobæk/Mads Mobæk, mads86<at>gmail.com/Mads Mobæk
31. Marciano Siniscalchi/Marciano Siniscalchi, margie<at>Marcianos-MacBook-Pro.local/Marciano Siniscalchi
32. Marciano Siniscalchi/Marciano Siniscalchi, msiniscalchi<at>gmail.com/Marciano Siniscalchi
33. Marciano Siniscalchi/Richard Stein, msiniscalchi<at>gmail.com/Richard Stein
34. Maximilian Berger/Maximilian Berger, snowdragon92<at>gmail.com/Maximilian Berger
35. Michael Walter/GitHub, michael.walter<at>gmail.com/GitHub
36. Mikey Saugstad/GitHub, michaelssaugstad<at>gmail.com/GitHub
37. msiniscalchi/msiniscalchi, msiniscalchi<at>gmail.com/msiniscalchi
38. omniearth/omniearth, florian<at>slurm.(none)/omniearth
39. Peter Eichinger/Peter Eichinger, peter.eichinger<at>gmail.com/Peter Eichinger
40. Piotr Kaz´mierczak/Piotr Kaz´mierczak, piotrkazmierczak<at>me.com/Piotr Kaz´mierczak
41. Rafael Lerm/Rafael Lerm, rafaellerm<at>gmail.com/Rafael Lerm
42. Ray Fang/Ray Fang, i<at>lazarusx.com/Ray Fang
43. Richard Stein/GitHub, r-stein.github<at>web.de/GitHub
44. Richard Stein/Richard Stein, r-stein.github<at>web.de/Richard Stein
45. Scott Kuroda/Scott Kuroda, scott.kuroda<at>gmail.com/Scott Kuroda
46. Sean Zhu/Sean Zhu, interestinglythere<at>gmail.com/Sean Zhu
47. Sergey Slipchenko/Sergey Slipchenko, faergeek<at>gmail.com/Sergey Slipchenko
48. Stefan Ollinger/Stefan Ollinger, Stefan.Ollinger<at>gmx.de/Stefan Ollinger
49. Tobias Diez/GitHub, tobiasdiez<at>gmx.de/GitHub
50. Tobias Schmidt/Tobias Schmidt, royalts<at>gmail.com/Tobias Schmidt
51. Ulrich Gabor/Ulrich Gabor, ulrich.thomas.gabor<at>googlemail.com/Ulrich Gabor
52. Wallace Wu/Wallace Wu, cwwwu<at>uwaterloo.ca/Wallace Wu
53. Wes Campaigne/Wes Campaigne, westacular<at>gmail.com/Wes Campaigne
54. William Ledoux/William Ledoux, william.ledoux<at>gmail.com/William Ledoux
55. williamledoux/williamledoux, william.ledoux<at>gmail.com/williamledoux


I will keep on the first post a up to date correction table.

I am applying a Hooray image to each reply I already counted/looked into and fixed the mistake.

@rlerm
Copy link
Contributor

rlerm commented Jul 13, 2017

I agree with any open-source license for my minuscule contribution.

@HughParsonage
Copy link
Contributor

Anyone is free to copy, modify, publish, use, compile, sell, or distribute my contribution to this repository ("the software") either in source code form or as a compiled binary, for any purpose, commercial or non-commercial, and by any means.

In jurisdictions that recognize copyright laws, I dedicate any and all copyright interest in the software to the public domain. I make this dedication for the benefit of the public at large and to the detriment of my heirs and successors. I intend this dedication to be an overt act of relinquishment in perpetuity of all present and future rights to this software under copyright law.

@faergeek
Copy link
Contributor

I agree with any open source license for my contribution

@r-stein
Copy link
Member

r-stein commented Jul 13, 2017

@evandrocoan Thanks for you effort. We may also use the contributors page https://github.com/SublimeText/LaTeXTools/graphs/contributors I don't think we need the agreement of people who changed single lines of code (the changes may even not be in the project anymore).

@jbrooksuk
Copy link
Member

Updated mine, of course I agree :)

@5chdn
Copy link
Contributor

5chdn commented Jul 13, 2017

I'm thrilled to find myself on top of that list and I agree with any free software license for my 5 characters of contribution :-D

@git-commit
Copy link
Contributor

I also agree with licensing this project under any open source license :)

@Bobo1239
Copy link
Contributor

I also agree with any license for my contribution.

@excetara2
Copy link
Contributor

excetara2 commented Jul 13, 2017 via email

@cantonios
Copy link

Just seeing this now, I agree

@lucasnanni
Copy link
Contributor

I agree with any open source license!

@kytta
Copy link

kytta commented Dec 28, 2022

I guess this message will ping everyone's mailboxes, for which I apologize in advance. I am working on a different LaTeX-related project, and I wanted to use some of the code from here initially, but have now stumbled upon this issue. A bit bummed to see that since 2018, nothing changed. I mean, the project itself starts to look abandoned: 355 issues and no commits for more than a year.

I was wondering if it still would be possible to get this to the end. Perhaps, email the other contributors individually? Or track down their commits and, if they do not respond and the commits aren't too critical for the project, roll them back?

It'd be a shame if a project this big and this excellent (I use it every day and I love it!) would stay open-code, but not open-source. @evandrocoan any ideas how we may “resurrect” this issue?

@evandrocoan
Copy link
Contributor Author

Of 46 authors, 39 agreed here to add a license. You look into these 7 missing folks and see what code they contributed is and if it too much to be reversed and rewritten. These may be small commits and could be removed and rewritten.

@kytta
Copy link

kytta commented Dec 29, 2022

Hello to all those who haven't been tagged here before.

We are reaching out to you because you have contributed code to this project (https://github.com/SublimeText/LaTeXTools), which at the time didn't have an open-source license. As such, by the GitHub TOS, one cannot modify your code your “without the danger/liability of being prosecuted by violating the All rights reserved copyright granted by Berne convention law.”

Most of the contributors have accepted changing the license to the MIT License (see the proposed license text at the top of the issue).

If you agree that this project becomes open-source too, please, reply to this issue with something along the lines of: “I agree to re-license my code under the terms of the MIT License”. This can be done by just replying to this email, too.


People, who have contributed their code to the project AND whose code is still in the project AND haven't replied to this issue yet, along with their commits:

These are the only people left that we need the permission from. @evandrocoan could you add those to your checklist at the top?

@hadisfr
Copy link
Contributor

hadisfr commented Dec 29, 2022

Hi!
I agree and would be glad to re-license my codes in the LaTeX tools Sublime Text plugin project under the terms of the MIT License, or any other open source licence.

@vqv
Copy link
Contributor

vqv commented Dec 29, 2022

I agree to re-license my code under the terms of the MIT License.

@dozed
Copy link
Contributor

dozed commented Dec 29, 2022

I agree to re-license my code under the terms of the MIT License

@charlesbaynham
Copy link
Contributor

I'm very happy for my contributions to be licensed under MIT or any other widely accepted open source license. Thank you to the maintainers for taking such care.

@victorkwan
Copy link
Contributor

victorkwan commented Dec 29, 2022 via email

@daviehh
Copy link
Contributor

daviehh commented Dec 29, 2022

Thanks for organizing, I agree to re-license my code under the terms of the MIT License.

@ssnl
Copy link
Contributor

ssnl commented Dec 29, 2022 via email

@msiniscalchi
Copy link
Contributor

Just chiming in to say I'm very happy to see this is happening!

@AllanLeanderRostockHansen

I agree to re-license my code under the terms of the MIT License

@evandrocoan
Copy link
Contributor Author

evandrocoan commented Dec 30, 2022

Hi @kytta, I updated my first post and created a pull-request adding the proposed MIT license: #1570. I extended my list with the new names you added and marked all posts.

For a more organized way, anyone agreeing with the open-source license can go to the pull-request #1570, and hit the review now button at the sidebar, as shown in the following image, and type I agree with this license for my code. as the pull-request view message:

  1. image
  2. image

@rensbaardman
Copy link
Contributor

rensbaardman commented Dec 30, 2022 via email

@ericjtaylor
Copy link
Contributor

ericjtaylor commented Dec 31, 2022 via email

@crypto-jeronimo
Copy link
Contributor

I agree to re-license my code under the terms of the MIT License.

@assombrance
Copy link
Contributor

I agree to re-license my code under the terms of the MIT License, and I'm glad to see this change :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.