Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Node.js Removes Its CLA

Post Syndicated from Bradley M. Kuhn original http://ebb.org/bkuhn/blog/2014/06/11/nodejs-no-cla.html

I’ve had my disagreements with Joyent‘s management
of the Node.js project. In fact, I am
generally auto-skeptical of any Open Source and/or Free Software project
run by a for-profit company. However, I also like to give credit where
credit is due.

Specifically, I’d like to congratulate Joyent for making the right
decision today to remove one of the major barriers to entry for
contribution to the Node.js project: its CLA. In
an announcement
today (see section labeled “Easier Contribution”, Joyent
announced Joyent no longer requires contributors to sign the CLA and
will (so it seems) accept contributions simply licensed under the
MIT-permissive license. In short, Node.js is, as of today, an
inbound=outbound
project.

While I’d prefer if Joyent would in addition switch the project
to the Apache License 2.0 — or even better, the Affero GPLv3 —
I realize that neither of those things are likely to happen. 🙂 Given that,
dropping the CLA is the next best outcome possible, and I’m glad it has
happened.

For further reading on my positions against CLAs, please see these two
older blog posts:

Simple example for Node.JS sflow collector

Post Syndicated from Anonymous original http://deliantech.blogspot.com/2014/06/simple-example-for-nodejs-sflow.html

Sometimes you can use the SFlow or Netflow to extra add intelligence to your network. The collectors available on internet are usually there just to collect and store data used for accounting or nice graphics. But the collectors are either not allowing you to execute your own code in case of certain rules/thresholds reached, or do not react in real time (in general, the protocols delays you too. You cannot expect NetFlow accounting to be used in real time at all, while SFlow has modes that are bit more fast to react, by design, it is still not considered to be real-time sampling/accounting).
Just imagine you have a simple goal – you want to automatically detect floods and notify the operators or you can even automatically apply filters.
If you have an algorithm that can distinguish the incorrect traffic from the normal traffic from NetFlow/SFlow sampling you may like to execute an operation immediately when that happens.
The modern DoS attacks and floods may be complex and hard to detect. But mainly it is hard to make the currently available NetFlow/SFlow collector software to do that for you and then trigger/execute external application.
However, it is very easy to program it yourself.
I am giving you a simple example that uses the node-sflow module to collect packet samples, measure how many of them match a certain destination ip address and if they are above certain pps thresholds to execute an external program (that is supposed to block that traffic). Then after a period of time it will execute another program (that is supposed to unblock the traffic).
This program is very small – about 120 lines of code and allows you to use complex configuration file where you can define a list of rules that can match optionally vlans and networks for the sampled packet and then count how many samples you have per destination for that rule. The rule list is executed until first match in the configured order within the array, so that allows you to create black and white lists and different thresholds per networks and vlans, or to have different rules per overlapped ip addresses as long as they belong to different vlans.
Keep in mind this is just an example software there just for your example, showing you how to use node-sflow and pcap modules together! It is not supposed to be used in production, unless you definitely know what you are doing!
The goal of this example it here just to show you how easy is to add extra logic within your network.
The code is available on git-hub here https://github.com/delian/sflow-collector/

The collective thoughts of the interwebz

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.

Close