6 Matching Annotations
- Last 7 days
-
github.com github.com
-
ziglang.org ziglang.org
-
Strict No LLM / No AI PolicyNo LLM-generated content, whether it be code or prose.No paraphrasing LLM-generated content.No LLMs for editing, including fixing spelling or grammatical errors.No LLMs for translation. English is encouraged, but not required. You are welcome to post in your native language and rely on others to have their own translation tools of choice to interpret your words.No LLMs for brainstorming and then sharing the results of that brainstorming, even if you create the prose. If you use a chatbot to give you advice on a comment on the issue tracker, that comment is unwelcome.No LLMs for finding bugs.
Seems kind of extreme. But https://www.youtube.com/watch?v=pkndFYSTr0Y gives some more context (an interview) that kind of explains their stance (limited maintainer time/attention; education).
-
- Feb 2021
-
2019.trailblazer.to 2019.trailblazer.to
-
note that TRB source code modifications are not proprietary
In other words, you can build on this software in your proprietary software but can't change the Trailblazer source unless you're willing to contribute it back.
loophole: I wonder if this will actually just push people to move their code -- which at the core is/would be a direction modification to the source code - out to a separate module. That's so easy to do with Ruby, so this restriction hardly seems like it would have any effect on encouraging contributions.
Tags
- well-written
- LGPL
- annotation meta: may need new tag
- loophole/escape hatch
- proprietary software
- reminder
- neutral/dispassionate/impartial/objective wording
- software licensing
- good point
- open-source software: not contributing new code back to project
- wording designed to be more palatable/pleasing/inoffensive
Annotators
URL
-
- Jul 2020
-
github.com github.com
-
Problem is, everyone's busy, so it can be days or even weeks before even a small PR is merged. So I'm stashing my stuff here as I write it. I'll still try to keep the PRs in motion, to gradually get some of this merged.
-
- Apr 2020
-
-
Our hope is that once a formal specification for these extensions is settled, this patchset can be used as a base to upstream the changes in the original project.
What does "can be used as a base to upstream the changes in the original project" mean here?
-
- Nov 2019
-
news.ycombinator.com news.ycombinator.com
-
the main reason we built a new multiprocess architecture is that Chromium's multiprocess support was never contributed to the WebKit project. It has always lived in the separate Chromium tree, making it pretty hard to use for non-Chrome purposes.Before we wrote a single line of what would become WebKit2 we directly asked Google folks if they would be willing to contribute their multiprocess support back to WebKit, so that we could build on it. They said no.
-