-
Notifications
You must be signed in to change notification settings - Fork 367
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
Comments
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. |
So I ran 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. |
I agree with an open source license for this project. |
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. |
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. |
i don't think this is me. i believe, i never contributed to this project. |
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. |
sure 👍 |
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... |
I also agree with adding an open source license for this project. |
Not sure how my name got here, I don’t recall contributing to this project.
From: Evandro Coan <[email protected]>
Reply-To: SublimeText/LaTeXTools <[email protected]>
Date: Wednesday, July 12, 2017 at 3:52 PM
To: SublimeText/LaTeXTools <[email protected]>
Cc: Jeffrey Spencer <[email protected]>, Mention <[email protected]>
Subject: Re: [SublimeText/LaTeXTools] Can it be a open source project? (#1175)
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:
nº
GitHub User Name
Information
* 1 | @5chdn<https://github.com/5chdn> | Afri/GitHub
* 2 | @ra<https://github.com/ra> | Andre Rein/Andre Rein
* 3 | @antonio<https://github.com/antonio> | Antonio Sanchez/Antonio Sanchez
* 4 | @Bobo1239<https://github.com/bobo1239> | Boris Zhou/Boris Zhou
* 5 | @btstream<https://github.com/btstream> | btstream/btstream
* 6 | @daizw<https://github.com/daizw> | DaiZW/DaiZW
* 7 | @dfleischhacker<https://github.com/dfleischhacker> | Daniel Fleischhacker/Daniel Fleischhacker
* 8 | @danschrage<https://github.com/danschrage> | danschrage/danschrage
* 9 | @deterenkelt<https://github.com/deterenkelt> | deterenkelt/GitHub
* 10 | @edoddridge<https://github.com/edoddridge> | Ed Doddridge/Ed Doddridge
* 11 | @evandrocoan<https://github.com/evandrocoan> | evandrocoan/evandrocoan
* 12 | @flo<https://github.com/flo> | Florian Zimmermann/Florian Zimmermann
* 13 | @hanneskaeufler<https://github.com/hanneskaeufler> | Hannes Kaeufler/Hannes Kaeufler
* 14 | @HughParsonage<https://github.com/hughparsonage> | HughParsonage/GitHub
* 15 | @huisunsh<https://github.com/huisunsh> | Hui Sun/Hui Sun
* 16 | @ig0774<https://github.com/ig0774> | Ian/Ian
* 17 | @trukanduk<https://github.com/trukanduk> | Ilya Uvarenkov/Ilya Uvarenkov
* 18 | @jbrooksuk<https://github.com/jbrooksuk> | James Brooks/James Brooks
* 19 | @jspencer-cmm<https://github.com/jspencer-cmm> | Jeff Spencer/Ian
* 20 | @jeremy<https://github.com/jeremy> | Jeremy Jay/Jeremy Jay
* 21 | @josef<https://github.com/josef> | Josef Friedrich/Josef Friedrich
* 22 | @eloo<https://github.com/eloo> | Joseph Weigl/Joseph Weigl
* 23 | @jrast<https://github.com/jrast> | Juerg Rast/Juerg Rast
* 24 | @lucasnanni<https://github.com/lucasnanni> | Lucas Nanni/Lucas Nanni
* 25 | @Mads86<https://github.com/mads86> | Mads Mobæk/Mads Mobæk
* 26 | @margie<https://github.com/margie> | Marciano Siniscalchi/Marciano Siniscalchi
* 27 | @msiniscalchi<https://github.com/msiniscalchi> | Maximilian Berger/Maximilian Berger
* 28 | @git-commit<https://github.com/git-commit> | Michael Walter/GitHub
* 29 | @blowfish880<https://github.com/blowfish880> | Mikey Saugstad/GitHub
* 30 | @misaugstad<https://github.com/misaugstad> | msiniscalchi/msiniscalchi
* 31 | @florian<https://github.com/florian> | omniearth/omniearth
* 32 | @petereichinger<https://github.com/petereichinger> | Peter Eichinger/Peter Eichinger
* 33 | @pkazmierczak<https://github.com/pkazmierczak> | Piotr Kaźmierczak/Piotr Kaźmierczak
* 34 | @rlerm<https://github.com/rlerm> | Rafael Lerm/Rafael Lerm
* 35 | @i<https://github.com/i> | Ray Fang/Ray Fang
* 36 | @r-stein<https://github.com/r-stein> | Richard Stein/Richard Stein
* 37 | @skuroda<https://github.com/skuroda> | Scott Kuroda/Scott Kuroda
* 38 | @interestinglythere<https://github.com/interestinglythere> | Sean Zhu/Sean Zhu
* 39 | @faergeek<https://github.com/faergeek> | Sergey Slipchenko/Sergey Slipchenko
* 40 | @dozed<https://github.com/dozed> | Stefan Ollinger/Stefan Ollinger
* 41 | @tobiasdiez<https://github.com/tobiasdiez> | Tobias Diez/GitHub
* 42 | @RoyalTS<https://github.com/royalts> | Tobias Schmidt/Tobias Schmidt
* 43 | @UlrichThomasGabor<https://github.com/ulrichthomasgabor> | Ulrich Gabor/Ulrich Gabor
* 44 | @cwwwu<https://github.com/cwwwu> | Wallace Wu/Wallace Wu
* 45 | @Westacular<https://github.com/westacular> | Wes Campaigne/Wes Campaigne
* 46 | @williamledoux<https://github.com/williamledoux> | William Ledoux/William Ledoux
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub<#1175 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/AQ5B-J7z1mwHaAQ-Ul-5dUjSRgMbLXyPks5sNSP-gaJpZM4OVDxI>.
This electronic transmission is confidential and intended solely for the addressee(s). If you are not an intended addressee, do not disclose, copy or take any other action in reliance on this transmission. If you have received this transmission in error, please delete it from your system and notify CoverMyMeds LLC at [email protected]. Thank you.
|
Sure, I'm ok with an open source license for this project. |
You can put any license you want on my contribution. |
Any open-source license is fine with me.
…On Wed, Jul 12, 2017 at 1:34 PM, Ulrich Gabor ***@***.***> wrote:
You can put any license you want on my contribution.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1175 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AODQ2QE_De406-Qq2DBGXPqPWBXQx0VFks5sNS3cgaJpZM4OVDxI>
.
|
Sure, I agree with an open source license for this project |
Any license is fine with me |
I also agree with any open source license. |
Great idea! I agree with any open-source license. |
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. |
@evandrocoan I've never contributed to this project. I believe you meant @cantonios based on the contributors list. |
I agree with any open-source license for my minuscule contribution. |
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. |
I agree with any open source license for my contribution |
@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). |
Updated mine, of course I agree :) |
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 |
I also agree with licensing this project under any open source license :) |
I also agree with any license for my contribution. |
I've also only had one commit but obviosuly would agree to any open source
license.
…On Thu, Jul 13, 2017 at 9:25 PM Boris-Chengbiao Zhou < ***@***.***> wrote:
I also agree with any license for my contribution.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1175 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAtO1rctBbHB0TdOSTI4V57ANY6wpGAzks5sNgzMgaJpZM4OVDxI>
.
|
Just seeing this now, I agree |
I agree with any open source license! |
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? |
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. |
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? |
Hi! |
I agree to re-license my code under the terms of the MIT License. |
I agree to re-license my code under the terms of the MIT License |
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. |
I agree to re-license my code under the terms of the MIT License.
…On Thu, Dec 29, 2022 at 21:52 Charles Baynham ***@***.***> wrote:
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.
—
Reply to this email directly, view it on GitHub
<#1175 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLVKMO45SZ6NM4GDOQ3QRTWPWCSTANCNFSM4DSUHREA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks for organizing, I agree to re-license my code under the terms of the MIT License. |
I agree to re-license my code under the terms of the MIT License
…On Thu, Dec 29, 2022 at 11:33 daviehh ***@***.***> wrote:
Thanks for organizing, I agree to re-license my code under the terms of
the MIT License.
—
Reply to this email directly, view it on GitHub
<#1175 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABLJMZM5MDEZMHVRCEWPFI3WPW4O7ANCNFSM4DSUHREA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Just chiming in to say I'm very happy to see this is happening! |
I agree to re-license my code under the terms of the MIT License |
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 |
I agree to re-license my code under the terms of the MIT License.
…On Thu, Dec 29, 2022, at 04:45, Nikita Karamov wrote:
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 <https://help.github.com/articles/github-terms-of-service/>, one cannot modify your code your “without the danger/liability of being prosecuted by violating the *All rights reserved* copyright granted by Berne convention <https://en.wikipedia.org/wiki/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:
* Hadi Safari ***@***.*** <https://github.com/hadisfr>)
* 27519ca handle UnicodeDecodeError in `cwl`s
* 3a65bf0 add support of `#include:` in cwl files
* 7fd465a fix some pep8 incompatibilities
* 80e78f7 Merge branch 'version4' into enhance_cwl_support
* Stefan Ollinger ***@***.*** <https://github.com/dozed>)
* ef86e75 Added linux configuration and fix for ctypes exception.
* aa52701 Added linux default keymap.
* 5b33ba3 Re-added ctypes import.
* Crypto Jerônimo ***@***.*** <https://github.com/crypto-jeronimo>)
* 27b944b Fix typos, spelling and remove extra whitespace.
* 340cfa4 More typo fixes, spelling and removal of extra whitespace.
* Vince Vu ***@***.*** <https://github.com/vqv>):
* 6fe2473 Added command for toggling starred version of surrounding environment
* 2284c09 Added check for empty new_regions and safe detection of star. ...
* Allan L. R. Hansen ***@***.*** <https://github.com/AllanLRH>):
* a7c301e Added github-links to the .sublime-completions
* Charles Baynham ***@***.*** <https://github.com/charlesbaynham>):
* 16ec7bf Fix bug where unfinished lines were not being detected
* Eric Taylor ***@***.*** <https://github.com/ericjtaylor>):
* 089ad59 Fixed a small typo in the install docs (#1510 <#1510>)
* Hui Sun ***@***.*** <https://github.com/JimAmuro>):
* 2c0ecee fix trigger toggle for \epsilon and \varepsilon
* Randy Lai ***@***.*** <https://github.com/randy3k>):
* 7f5a783 blackslash is now handled correctly in sublime text 4 (#1454 <#1454>)
* Rens Baardman ***@***.*** <https://github.com/rensbaardman>):
* b27fc39 Fix error message when jumping to pdf from non-.tex-file (#1472 <#1472>)
* Tongzhou Wang ***@***.*** <https://github.com/ssnl>):
* f6c0dbe copy_on_build should not fail on nonexistent extensions (#1502 <#1502>)
* assombrance ***@***.*** <https://github.com/assombrance>):
* 21d3bcc typo fix for subscript snippet (#1534 <#1534>)
* david ***@***.*** <https://github.com/daviehh>):
* 6a4ca21 fix parsing for "Incomplete \if...; all text was ignored after line"
* Florian Mueller ***@***.*** <https://github.com/omniearth>):
* 7c0b8db Added snippets for creating a figure and for a table, as well as completions for the Beamer package
* victorkwan ***@***.*** <https://github.com/victorkwan>):
* edaa630 Update README.markdown (#1306 <#1306>)
* wdyggh ***@***.*** <https://github.com/wdyggh>):
* 45e428d Fix an encoding issue when looking for ImageMagick (#1515 <#1515>)
These are the *only* people left that we need the permission from. @evandrocoan <https://github.com/evandrocoan> could you add those to your checklist at the top?
—
Reply to this email directly, view it on GitHub <#1175 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABWR2EROJKLKF2U3RUUZE4LWPWBX3ANCNFSM4DSUHREA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
|
I agree to re-license my code under the terms of the MIT License.
On Fri, Dec 30, 2022 at 4:27 AM Rens Baardman ***@***.***>
wrote:
… I agree to re-license my code under the terms of the MIT License.
On Thu, Dec 29, 2022, at 04:45, Nikita Karamov wrote:
>
>
> 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 <
https://help.github.com/articles/github-terms-of-service/>, one cannot
modify your code your “without the danger/liability of being prosecuted by
violating the *All rights reserved* copyright granted by Berne convention <
https://en.wikipedia.org/wiki/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:
>
> * Hadi Safari ***@***.*** <https://github.com/hadisfr>)
> * 27519ca handle UnicodeDecodeError in `cwl`s
> * 3a65bf0 add support of `#include:` in cwl files
> * 7fd465a fix some pep8 incompatibilities
> * 80e78f7 Merge branch 'version4' into enhance_cwl_support
> * Stefan Ollinger ***@***.*** <https://github.com/dozed>)
> * ef86e75 Added linux configuration and fix for ctypes exception.
> * aa52701 Added linux default keymap.
> * 5b33ba3 Re-added ctypes import.
> * Crypto Jerônimo ***@***.*** <https://github.com/crypto-jeronimo>)
> * 27b944b Fix typos, spelling and remove extra whitespace.
> * 340cfa4 More typo fixes, spelling and removal of extra whitespace.
> * Vince Vu ***@***.*** <https://github.com/vqv>):
> * 6fe2473 Added command for toggling starred version of surrounding
environment
> * 2284c09 Added check for empty new_regions and safe detection of star.
...
> * Allan L. R. Hansen ***@***.*** <https://github.com/AllanLRH>):
> * a7c301e Added github-links to the .sublime-completions
> * Charles Baynham ***@***.*** <https://github.com/charlesbaynham>):
> * 16ec7bf Fix bug where unfinished lines were not being detected
> * Eric Taylor ***@***.*** <https://github.com/ericjtaylor>):
> * 089ad59 Fixed a small typo in the install docs (#1510 <
#1510>)
> * Hui Sun ***@***.*** <https://github.com/JimAmuro>):
> * 2c0ecee fix trigger toggle for \epsilon and \varepsilon
> * Randy Lai ***@***.*** <https://github.com/randy3k>):
> * 7f5a783 blackslash is now handled correctly in sublime text 4 (#1454 <
#1454>)
> * Rens Baardman ***@***.*** <https://github.com/rensbaardman>):
> * b27fc39 Fix error message when jumping to pdf from non-.tex-file
(#1472 <#1472>)
> * Tongzhou Wang ***@***.*** <https://github.com/ssnl>):
> * f6c0dbe copy_on_build should not fail on nonexistent extensions (#1502
<#1502>)
> * assombrance ***@***.*** <https://github.com/assombrance>):
> * 21d3bcc typo fix for subscript snippet (#1534 <
#1534>)
> * david ***@***.*** <https://github.com/daviehh>):
> * 6a4ca21 fix parsing for "Incomplete \if...; all text was ignored after
line"
> * Florian Mueller ***@***.*** <https://github.com/omniearth>):
> * 7c0b8db Added snippets for creating a figure and for a table, as well
as completions for the Beamer package
> * victorkwan ***@***.*** <https://github.com/victorkwan>):
> * edaa630 Update README.markdown (#1306 <
#1306>)
> * wdyggh ***@***.*** <https://github.com/wdyggh>):
> * 45e428d Fix an encoding issue when looking for ImageMagick (#1515 <
#1515>)
> These are the *only* people left that we need the permission from.
@evandrocoan <https://github.com/evandrocoan> could you add those to your
checklist at the top?
>
>
> —
> Reply to this email directly, view it on GitHub <
#1175 (comment)>,
or unsubscribe <
https://github.com/notifications/unsubscribe-auth/ABWR2EROJKLKF2U3RUUZE4LWPWBX3ANCNFSM4DSUHREA
>.
> You are receiving this because you were mentioned.Message ID:
***@***.***>
>
—
Reply to this email directly, view it on GitHub
<#1175 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AEEGLUMI5ZHNIP23R26W4T3WP2TG7ANCNFSM4DSUHREA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I agree to re-license my code under the terms of the MIT License. |
I agree to re-license my code under the terms of the MIT License, and I'm glad to see this change :) |
I am happy to see this happening if I still need to agree.
…On Thu, Dec 29, 2022 at 7:51 AM Stefan Ollinger ***@***.***> wrote:
I agree to re-license my code under the terms of the MIT License
—
Reply to this email directly, view it on GitHub
<#1175 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFU5VRHOYDD2GQBNK7VJTDWPWCOZANCNFSM4DSUHREA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Searching through the repository, I cannot find any mention to open source license:
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 typeI agree with this license for my code.
as the pull-request view message:List of users contributing to this project, which agree to open source license to their contribution:
@ra| @xrayn Andre Rein/Andre Rein - Can it be an open source project? #1175 (comment) $315436254@antonio| @cantonios Antonio Sanchez/Antonio Sanchez - Can it be an open source project? #1175 (comment)@flo| @PoByBolek Florian Zimmermann/Florian Zimmermann - Can it be an open source project? #1175 (comment) -$315322849[x] 15 |(duplicated entry)@huisunsh| @JimAmuro Hui Sun/Hui Sun@jspencer-cmm | Jeff Spencer/Ian@excetara2 /Jeffrey Spencer - Can it be an open source project? #1175 (comment) $315067793@jeremy| @pbnjay Jeremy Jay/Jeremy Jay - Can it be an open source project? #1175 (comment) $315186443@josef| @Josef-Friedrich Josef Friedrich/Josef Friedrich - Can it be an open source project? #1175 (comment) $315092011@Mads86| @mobmad Mads Mobæk/Mads Mobæk[] 26 | @margie | Marciano Siniscalchi/Marciano Siniscalchiduplicated entrymsiniscalchi/msiniscalchiMarciano Siniscalchi - Can it be an open source project? #1175 (comment) $314882674@blowfish880| Mikey Saugstad/GitHub @misaugstad - Can it be an open source project? #1175 (comment) $314912739@misaugstad | Mikey Saugstad@catch22 Michael Walter - Can it be an open source project? #1175 (comment) $315428323[ ] 31 |(duplicated entry)@florian | omniearth/omniearth@omniearth /Florian Mueller@i| @LazarusX Ray Fang/Ray Fang - Can it be an open source project? #1175 (comment) $315264046@interestinglythere| @szhu Sean Zhu/Sean Zhu - Can it be an open source project? #1175 (comment) $315185499[ ] 40 | @dozed | Stefan Ollinger/Stefan Ollinger(duplicated entry)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.So far, the names I mistake were:
I am applying a
Hooray
to each reply I already counted/looked into and fixed the mistake.Update 2
License suggestion copied from the files:
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.
Changelog:
Sublime Text
toLaTeXTools Contributors
.The text was updated successfully, but these errors were encountered: