Comments (27)
maurizi
commented on May 26, 2024
I am not a contributor to this project. (Readme changes are not relevant
for code licensing AFAIK).
from liquid-rust.
durka
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
epage
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
epage
commented on May 26, 2024
Checklist of post-1/8/2016 contributors that have posted their agreement
- @epage
- @gmalette
- @djwf
- @fiji-flo
- @dzamlo
- @vvv
- @kubahorak
- @solidsnack #62
- @Albibek #141
- @ElijahCaine
- @LucioFranco
- @gchp
- @gnunicorn (Benjamin Kampmann)
- @tcsc
- @BFrog
- @TechMagister
- @kstep (Konstantin Stepanov)
- @bacoboy (Steve Hoffman)
- @badboy #157
- @pop
- @emoon
- @Goncalerta
- @agersant
- @Geobert
- @or17191
More information is in the API guidelines.
from liquid-rust.
tcsc
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
djwf
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
LucioFranco
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
Albibek
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
vvv
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
dzamlo
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
gmalette
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
gchp
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
fiji-flo
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
teburd
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0
license, allowing licensees to chose either at their option
…On Jun 23, 2017 4:24 PM, "Florian Merz" ***@***.***> wrote:
I license past and future contributions under the dual MIT/Apache-2.0
license, allowing licensees to chose either at their option
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#7 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAISn8j6LSQN914UctlPrkOuP6SJZMsMks5sHC0RgaJpZM4HBi9C>
.
from liquid-rust.
pop
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
gnunicorn
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
tak1n
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
kubahorak
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
badboy
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
uwearzt
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
bacoboy
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option 💥
from liquid-rust.
emoon
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
kstep
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option
from liquid-rust.
Goncalerta
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
from liquid-rust.
agersant
commented on May 26, 2024
I license past and future contributions under the dual MIT/Apache-2.0 license, allowing licensees to chose either at their option.
from liquid-rust.
Geobert
commented on May 26, 2024
I agree for relicensing
from liquid-rust.
Related Issues (20)
- Parser ignores value of BlockReflection::end_tag() HOT 7
- Update Readme links & version and liquid (5.0.0) render instead of include HOT 1
- How to use the "Template" class. HOT 33
- Allow accessing renderer state/runtime before rendering HOT 6
- with_time unimplemented HOT 3
- Change `master` branch to `main` HOT 3
- could not compile kstring HOT 1
- Render Tag HOT 3
- EmptyDrop and Object indexing HOT 7
- Make struct InnerError public HOT 1
- Open to the idea of supporting less strict parsing/rendering as an option? HOT 3
- Can't render dates with millisecond precision HOT 1
- No way to return a reference for the values method of trait ObjectView
- Dependency Dashboard
- Question: supporting object literals with unknown keys on custom filters HOT 8
- Thoughts on implementing `From<serde_json::Value> for liquid_core::Value`? HOT 2
- How do you use `{% include x.liquid %}`? HOT 2
- Liquid Tag and Echo Tag
- How would you go about implementing a Drop HOT 3
- Add support for u64 numbers?
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from liquid-rust.