You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@mina.apache.org by Benoit Hudzia <be...@gmail.com> on 2007/02/12 14:32:36 UTC
heartbeat and connection monitoring
Hi,
A couple of month ago, somebody mentioned the possibility to add a
heartbeat monitoring system for connection as filter. This filter would have
been based on an implementation done in another project.
Did anybody implemented it? If not, can somebody point me to the project so
I can have a look and see if I can implement it myself?
I currently rely on the tcp timeout but I need to move on to a more reliable
monitoring system because in a long term I plan to move on a reliable udp
filter I m working on .
Cheers
Benoit Hudzia
Parallel Computing Research Group
School of Computer Science & Informatics
University College Dublin
Ireland
Tel: +353 1 716 2403
Fax: +353 1 269 7262
E-mail: benoit [dot] hudzia [at] ucd [dot] ie
Re: heartbeat and connection monitoring
Posted by Trustin Lee <tr...@gmail.com>.
Hi Eero,
2007-02-14 (수), 11:55 +0200, Eero Nevalainen 쓰시길:
> Trustin Lee wrote:
> > The heartbeat code was from Qpid project (in Apache incubator), but they
> > told me that their code had turned out to be not usable as we expected.
> > Implementing an heartbeat filter is very easy though. Let me add a JIRA
> > issue for it.
> >
> > https://issues.apache.org/jira/browse/DIRMINA-350
>
> Hi,
>
> I implemented this kind of thing a while ago as a part of our company
> project and thought about posting it, since it's something the framework
> could very well provide.
>
> The company gave a preliminary approval of sharing and participating
> with MINA, but we haven't cleared out all the terms yet. I think I saw
> somewhere that all @author tags and copyright notices would need to be
> removed if the code is published with the Apache license. Am I
> remembering correctly? The company would like to have at least some
> "thanks to" mention if we send stuff..
>
> This is not a major problem though as like Trustin said, it's very easy
> to implement. I'd still like to know though..
I think it's OK for us to mention the code donation like that. We could
probably list your company in this page:
http://mina.apache.org/donations.html
HTH,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Re: Detailed documentation for software grant procedure? (Was: Re: heartbeat and connection monitoring)
Posted by Niclas Hedhman <ni...@hedhman.org>.
> 2007-02-18 (일), 17:46 +0200, Eero Nevalainen 쓰시길:
> > Thank you Robert and Alex for your explanations. I took a look at
> > http://www.apache.org/legal/ and http://incubator.apache.org/.
> > The CCLA and software grant seem appropriate to me but the Incubator
> > process sounds like overkill, because it's just four classes.
Incubator has a so called "IP Clearance" process, which is in place for these
kind of situations. It is a matter of properly recording the contribution and
have everything on file in known locations.
Once the paperwork is done, you commit in the code in Incubator, get an ACK
from the Incubator PMC, then make a svn copy to the project. With a bit of
flow it can be done in a week or so.
> > - What kind of extra security does the employee "whitelisting" bring? If
> > we have a malevolent/incompetent new employee who posts company code,
> > are we somehow more protected?
It means that the company explicitly states who has the blessing of the
company to contribute. The purpose varies from jurisdiction to jurisdiction.
One of the major points is that the company signals that "Hey, we know that
these individuals are working on ASF codebases, and that is fine with us.",
so that the company later can't come running saying "That code is ours..."
even if it has clearly been developed in an open manner.
If an employee contributes code that are not intended for open sourcing, I
think the ASF will "play nice" and pull it as soon as a flag is raised to the
Board. Your legal standing with the individual, though, would depend on your
jurisdiction and the role of the individual in the company. I doubt that the
CCLA would bring any additional favours.
The "IP Clearance" process also exist as a watchdog against this. Any larger
contribution would hit the Incubator first, and the company would need to
sign off. If the individual claim and signs that it is "private code", the
company will have a very strong case of fraud and misrepresentation, thanks
to the "IP Clearance" process.
I hope that answers some of the questions.
Cheers
Niclas
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: heartbeat and connection monitoring
Posted by Eero Nevalainen <ee...@indagon.com>.
robert burrell donkin wrote:
> On 2/18/07, Eero Nevalainen <ee...@indagon.com> wrote:
>> - Any advice or examples on how the software grant is supposed to be
>> worded? IANAL either.
>
> use the standard software grant
done and faxed.
>> After I've faxed our CCLA and my CLA is there something else that needs
>> to be done before sending code? Also, what's the preferred way to
>> actually transfer the code?
>
> zip up the source. either create an openPGP compatible signature or a
> checksum and reference that in the grant. create a JIRA and attach the
> source.
<sigh> Not done. The JIRA was very slow and hasn't responded for a few
minutes. I'll try again in the evening.
>> Visibility stuff:
>> <quote Robert>
>> > apache seems comfortable with an attribution in the NOTICE file
>> > similar to the apache notice:
>> >
>> > "This product includes software developed at The Apache Software
>> > Foundation (http://www.apache.org/)."
>> >
>> > for example http://svn.apache.org/repos/asf/db/derby/code/trunk/NOTICE
>> >
>> > if the company is looking for more than that (for example, links from
>> > the web site) then this is leading into areas outside the comfort
>> > zone...
>>
>> The mention in the NOTICE file seems fine. I was originally thinking
>> about maybe leaving something like "Thanks to Indagon for the original"
>> in the class files, WDYT?
>
> you'll find that would be a PITA: expect to be contacted by lawyers
> for the next N years asking you to confirm the grant and asking for
> proof that you created the originals. this is one reason why apache
> relocates attributions to the NOTICE file. (there are others.)
>
> "Thanks to Indagon for the original" is a (legally) ambiguous attribution.
>
> "This product includes software developed at Indagon
> (http://www.???.???/)." is the recommended wording. it's worked the
> best over the years.
The address would be http://www.indagon.com/ Since you already seem to
have more than enough experience, then let's do as you suggested and
steer clear of the PITA.
-Eero
Re: heartbeat and connection monitoring
Posted by Trustin Lee <tr...@gmail.com>.
Hi Robert,
Thank you for a clear guide. It's easier than I initially thought all thank
to you and Alex's help. :D
Regard,
Trustin
On 2/22/07, robert burrell donkin <ro...@gmail.com> wrote:
>
> On 2/18/07, Eero Nevalainen <ee...@indagon.com> wrote:
> > <flush quotes>
> >
> > Thank you Robert and Alex for your explanations. I took a look at
> > http://www.apache.org/legal/ and http://incubator.apache.org/.
> > The CCLA and software grant seem appropriate to me but the Incubator
> > process sounds like overkill, because it's just four classes.
>
> the quantity of code doesn't matter: it's policy set by the board. the
> incubator just checks that the paperwork is in order (and we try to
> provide helpful advice such as this). the MINA PMC will manage the
> process.
>
> > I got an "All ok" from my bosses on friday. Benoit: If you're not in
> > hurry I can probably get the details cleared for Mon 26. or one week
> > from that at the latest. (I have a week of vacation starting today).
>
> (have a good holiday)
>
> > Practical stuff:
> > At the end of the Corporate CLA are Schedules A and B. I understand
> > we're supposed to replace the content in brackets. Few questions:
> >
> > - What kind of extra security does the employee "whitelisting" bring? If
> > we have a malevolent/incompetent new employee who posts company code,
> > are we somehow more protected?
>
> probably not better protected but it is less legally ambiguous
>
> in your example case, it would be clear in that apache would have no
> moral rights to the code and it should be removed from the repository
> as soon as we were notified of the problem.
>
> > - Any advice or examples on how the software grant is supposed to be
> > worded? IANAL either.
>
> use the standard software grant
>
> > After I've faxed our CCLA and my CLA is there something else that needs
> > to be done before sending code? Also, what's the preferred way to
> > actually transfer the code?
>
> zip up the source. either create an openPGP compatible signature or a
> checksum and reference that in the grant. create a JIRA and attach the
> source.
>
> MINA then votes to accept the grant and fills in the paperwork in the
> incubator
>
> > Visibility stuff:
> > <quote Robert>
> > > apache seems comfortable with an attribution in the NOTICE file
> > > similar to the apache notice:
> > >
> > > "This product includes software developed at The Apache Software
> > > Foundation (http://www.apache.org/)."
> > >
> > > for example http://svn.apache.org/repos/asf/db/derby/code/trunk/NOTICE
> > >
> > > if the company is looking for more than that (for example, links from
> > > the web site) then this is leading into areas outside the comfort
> > > zone...
> >
> > The mention in the NOTICE file seems fine. I was originally thinking
> > about maybe leaving something like "Thanks to Indagon for the original"
> > in the class files, WDYT?
>
> you'll find that would be a PITA: expect to be contacted by lawyers
> for the next N years asking you to confirm the grant and asking for
> proof that you created the originals. this is one reason why apache
> relocates attributions to the NOTICE file. (there are others.)
>
> "Thanks to Indagon for the original" is a (legally) ambiguous attribution.
>
> "This product includes software developed at Indagon
> (http://www.???.???/)." is the recommended wording. it's worked the
> best over the years.
>
> - robert
>
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Re: heartbeat and connection monitoring
Posted by robert burrell donkin <ro...@gmail.com>.
On 2/18/07, Eero Nevalainen <ee...@indagon.com> wrote:
> <flush quotes>
>
> Thank you Robert and Alex for your explanations. I took a look at
> http://www.apache.org/legal/ and http://incubator.apache.org/.
> The CCLA and software grant seem appropriate to me but the Incubator
> process sounds like overkill, because it's just four classes.
the quantity of code doesn't matter: it's policy set by the board. the
incubator just checks that the paperwork is in order (and we try to
provide helpful advice such as this). the MINA PMC will manage the
process.
> I got an "All ok" from my bosses on friday. Benoit: If you're not in
> hurry I can probably get the details cleared for Mon 26. or one week
> from that at the latest. (I have a week of vacation starting today).
(have a good holiday)
> Practical stuff:
> At the end of the Corporate CLA are Schedules A and B. I understand
> we're supposed to replace the content in brackets. Few questions:
>
> - What kind of extra security does the employee "whitelisting" bring? If
> we have a malevolent/incompetent new employee who posts company code,
> are we somehow more protected?
probably not better protected but it is less legally ambiguous
in your example case, it would be clear in that apache would have no
moral rights to the code and it should be removed from the repository
as soon as we were notified of the problem.
> - Any advice or examples on how the software grant is supposed to be
> worded? IANAL either.
use the standard software grant
> After I've faxed our CCLA and my CLA is there something else that needs
> to be done before sending code? Also, what's the preferred way to
> actually transfer the code?
zip up the source. either create an openPGP compatible signature or a
checksum and reference that in the grant. create a JIRA and attach the
source.
MINA then votes to accept the grant and fills in the paperwork in the incubator
> Visibility stuff:
> <quote Robert>
> > apache seems comfortable with an attribution in the NOTICE file
> > similar to the apache notice:
> >
> > "This product includes software developed at The Apache Software
> > Foundation (http://www.apache.org/)."
> >
> > for example http://svn.apache.org/repos/asf/db/derby/code/trunk/NOTICE
> >
> > if the company is looking for more than that (for example, links from
> > the web site) then this is leading into areas outside the comfort
> > zone...
>
> The mention in the NOTICE file seems fine. I was originally thinking
> about maybe leaving something like "Thanks to Indagon for the original"
> in the class files, WDYT?
you'll find that would be a PITA: expect to be contacted by lawyers
for the next N years asking you to confirm the grant and asking for
proof that you created the originals. this is one reason why apache
relocates attributions to the NOTICE file. (there are others.)
"Thanks to Indagon for the original" is a (legally) ambiguous attribution.
"This product includes software developed at Indagon
(http://www.???.???/)." is the recommended wording. it's worked the
best over the years.
- robert
Re: Detailed documentation for software grant procedure? (Was: Re:
heartbeat and connection monitoring)
Posted by Trustin Lee <tr...@gmail.com>.
2007-02-20 (화), 19:37 -0800, Jean T. Anderson 쓰시길:
> Trustin Lee wrote:
> > Hi,
> >
> > MINA PMC is trying to deal with software grant process, but I don't have
> > enough knowledge on this area. People at legal-discuss could help
> > me. :)
>
> I find the instructions at the top of the ip clearance template to be
> the most helpful:
>
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The form itself (everything below the "cut here" line) fills in the
> other steps that need to be done.
Great! This is exactly what I was looking for.
Thanks,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Re: Detailed documentation for software grant procedure? (Was: Re:
heartbeat and connection monitoring)
Posted by Trustin Lee <tr...@gmail.com>.
2007-02-20 (화), 19:37 -0800, Jean T. Anderson 쓰시길:
> Trustin Lee wrote:
> > Hi,
> >
> > MINA PMC is trying to deal with software grant process, but I don't have
> > enough knowledge on this area. People at legal-discuss could help
> > me. :)
>
> I find the instructions at the top of the ip clearance template to be
> the most helpful:
>
> http://incubator.apache.org/ip-clearance/ip-clearance-template.html
>
> The form itself (everything below the "cut here" line) fills in the
> other steps that need to be done.
Great! This is exactly what I was looking for.
Thanks,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Re: Detailed documentation for software grant procedure? (Was: Re:
heartbeat and connection monitoring)
Posted by "Jean T. Anderson" <jt...@apache.org>.
Trustin Lee wrote:
> Hi,
>
> MINA PMC is trying to deal with software grant process, but I don't have
> enough knowledge on this area. People at legal-discuss could help
> me. :)
I find the instructions at the top of the ip clearance template to be
the most helpful:
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The form itself (everything below the "cut here" line) fills in the
other steps that need to be done.
-jean
---------------------------------------------------------------------
DISCLAIMER: Discussions on this list are informational and educational
only. Statements made on this list are not privileged, do not
constitute legal advice, and do not necessarily reflect the opinions
and policies of the ASF. See <http://www.apache.org/licenses/> for
official ASF policies and documents.
---------------------------------------------------------------------
To unsubscribe, e-mail: legal-discuss-unsubscribe@apache.org
For additional commands, e-mail: legal-discuss-help@apache.org
Re: Detailed documentation for software grant procedure? (Was: Re:
heartbeat and connection monitoring)
Posted by "Jean T. Anderson" <jt...@apache.org>.
Trustin Lee wrote:
> Hi,
>
> MINA PMC is trying to deal with software grant process, but I don't have
> enough knowledge on this area. People at legal-discuss could help
> me. :)
I find the instructions at the top of the ip clearance template to be
the most helpful:
http://incubator.apache.org/ip-clearance/ip-clearance-template.html
The form itself (everything below the "cut here" line) fills in the
other steps that need to be done.
-jean
Detailed documentation for software grant procedure? (Was: Re:
heartbeat and connection monitoring)
Posted by Trustin Lee <tr...@gmail.com>.
Hi,
MINA PMC is trying to deal with software grant process, but I don't have
enough knowledge on this area. People at legal-discuss could help
me. :)
2007-02-18 (일), 17:46 +0200, Eero Nevalainen 쓰시길:
> <flush quotes>
>
> Thank you Robert and Alex for your explanations. I took a look at
> http://www.apache.org/legal/ and http://incubator.apache.org/.
> The CCLA and software grant seem appropriate to me but the Incubator
> process sounds like overkill, because it's just four classes.
>
> I got an "All ok" from my bosses on friday. Benoit: If you're not in
> hurry I can probably get the details cleared for Mon 26. or one week
> from that at the latest. (I have a week of vacation starting today).
>
>
> Practical stuff:
> At the end of the Corporate CLA are Schedules A and B. I understand
> we're supposed to replace the content in brackets. Few questions:
>
> - What kind of extra security does the employee "whitelisting" bring? If
> we have a malevolent/incompetent new employee who posts company code,
> are we somehow more protected?
AFAIK, there's no protection for such a situation, but I guess
legal-discuss list might give us a better answer.
>
> - Any advice or examples on how the software grant is supposed to be
> worded? IANAL either.
It's here: http://www.apache.org/licenses/software-grant.txt
> After I've faxed our CCLA and my CLA is there something else that needs
> to be done before sending code? Also, what's the preferred way to
> actually transfer the code?
I couldn't find a detailed documentation on this process. Robert once
raised this issue, but I can't find any answer either.
>
> Visibility stuff:
> <quote Robert>
> > apache seems comfortable with an attribution in the NOTICE file
> > similar to the apache notice:
> >
> > "This product includes software developed at The Apache Software
> > Foundation (http://www.apache.org/)."
> >
> > for example http://svn.apache.org/repos/asf/db/derby/code/trunk/NOTICE
> >
> > if the company is looking for more than that (for example, links from
> > the web site) then this is leading into areas outside the comfort
> > zone...
>
> The mention in the NOTICE file seems fine. I was originally thinking
> about maybe leaving something like "Thanks to Indagon for the original"
> in the class files, WDYT?
It sounds OK to me.
Please refer to the original thread if you are interested in the whole
story:
Please refer to the following thread to find more out:
http://www.nabble.com/heartbeat-and-connection-monitoring-tf3213604.html
Thanks in advance,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Detailed documentation for software grant procedure? (Was: Re:
heartbeat and connection monitoring)
Posted by Trustin Lee <tr...@gmail.com>.
Hi,
MINA PMC is trying to deal with software grant process, but I don't have
enough knowledge on this area. People at legal-discuss could help
me. :)
2007-02-18 (일), 17:46 +0200, Eero Nevalainen 쓰시길:
> <flush quotes>
>
> Thank you Robert and Alex for your explanations. I took a look at
> http://www.apache.org/legal/ and http://incubator.apache.org/.
> The CCLA and software grant seem appropriate to me but the Incubator
> process sounds like overkill, because it's just four classes.
>
> I got an "All ok" from my bosses on friday. Benoit: If you're not in
> hurry I can probably get the details cleared for Mon 26. or one week
> from that at the latest. (I have a week of vacation starting today).
>
>
> Practical stuff:
> At the end of the Corporate CLA are Schedules A and B. I understand
> we're supposed to replace the content in brackets. Few questions:
>
> - What kind of extra security does the employee "whitelisting" bring? If
> we have a malevolent/incompetent new employee who posts company code,
> are we somehow more protected?
AFAIK, there's no protection for such a situation, but I guess
legal-discuss list might give us a better answer.
>
> - Any advice or examples on how the software grant is supposed to be
> worded? IANAL either.
It's here: http://www.apache.org/licenses/software-grant.txt
> After I've faxed our CCLA and my CLA is there something else that needs
> to be done before sending code? Also, what's the preferred way to
> actually transfer the code?
I couldn't find a detailed documentation on this process. Robert once
raised this issue, but I can't find any answer either.
>
> Visibility stuff:
> <quote Robert>
> > apache seems comfortable with an attribution in the NOTICE file
> > similar to the apache notice:
> >
> > "This product includes software developed at The Apache Software
> > Foundation (http://www.apache.org/)."
> >
> > for example http://svn.apache.org/repos/asf/db/derby/code/trunk/NOTICE
> >
> > if the company is looking for more than that (for example, links from
> > the web site) then this is leading into areas outside the comfort
> > zone...
>
> The mention in the NOTICE file seems fine. I was originally thinking
> about maybe leaving something like "Thanks to Indagon for the original"
> in the class files, WDYT?
It sounds OK to me.
Please refer to the original thread if you are interested in the whole
story:
Please refer to the following thread to find more out:
http://www.nabble.com/heartbeat-and-connection-monitoring-tf3213604.html
Thanks in advance,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Re: heartbeat and connection monitoring
Posted by Eero Nevalainen <ee...@indagon.com>.
<flush quotes>
Thank you Robert and Alex for your explanations. I took a look at
http://www.apache.org/legal/ and http://incubator.apache.org/.
The CCLA and software grant seem appropriate to me but the Incubator
process sounds like overkill, because it's just four classes.
I got an "All ok" from my bosses on friday. Benoit: If you're not in
hurry I can probably get the details cleared for Mon 26. or one week
from that at the latest. (I have a week of vacation starting today).
Practical stuff:
At the end of the Corporate CLA are Schedules A and B. I understand
we're supposed to replace the content in brackets. Few questions:
- What kind of extra security does the employee "whitelisting" bring? If
we have a malevolent/incompetent new employee who posts company code,
are we somehow more protected?
- Any advice or examples on how the software grant is supposed to be
worded? IANAL either.
After I've faxed our CCLA and my CLA is there something else that needs
to be done before sending code? Also, what's the preferred way to
actually transfer the code?
Visibility stuff:
<quote Robert>
> apache seems comfortable with an attribution in the NOTICE file
> similar to the apache notice:
>
> "This product includes software developed at The Apache Software
> Foundation (http://www.apache.org/)."
>
> for example http://svn.apache.org/repos/asf/db/derby/code/trunk/NOTICE
>
> if the company is looking for more than that (for example, links from
> the web site) then this is leading into areas outside the comfort
> zone...
The mention in the NOTICE file seems fine. I was originally thinking
about maybe leaving something like "Thanks to Indagon for the original"
in the class files, WDYT?
-Eero Nevalainen
Re: heartbeat and connection monitoring
Posted by Trustin Lee <tr...@gmail.com>.
Robert and Alex,
Thank you for your kind explanation. It was very very helpful. I
forwarded the message to legal-discuss to find more about remaining
issues.
Thanks,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Re: heartbeat and connection monitoring
Posted by Alex Karasulu <ak...@apache.org>.
Hi Trustin,
Hope you're enjoying your new year celebrations.
I'll try to help to the best of my ability as well. I'm glad Robert is
here to help too.
For the time being though Robert gave some really good links and sound
advice.
WRT these matters it's feasible to accept patches on existing features
without a [C|I]CLA, if and only if the patch is on an existing feature.
If the patch does not re-factor existing fuctionality but rather
introduces a new feature[s] I'd rather take the safer route of
requesting both a CCLA, and software grant. This is the best way to CYA.
Although this does not seem to be the case, if the contribution is an
entirely new sub-project under the TLP then of curse the incubator or
the software clearance process is an option. For example having
consulted the Incubator PMC we came to the conclusion that Asyncweb
should go through software clearance rather than incubation due to the
committers already being MINA committers among other reasons.
I'd step through the process yourself just to get comfortable with it
since I have a feeling it will happen frequently :).
robert burrell donkin wrote:
> On 2/15/07, Trustin Lee <tr...@gmail.com> wrote:
>> Robert,
>>
>> 2007-02-14 (수), 17:41 +0000, robert burrell donkin 쓰시길:
>> > On 2/14/07, Eero Nevalainen <ee...@indagon.com> wrote:
>> > > Hi,
>> > >
>> > > I implemented this kind of thing a while ago as a part of our company
>> > > project and thought about posting it, since it's something the
>> framework
>> > > could very well provide.
>> > >
>> > > The company gave a preliminary approval of sharing and participating
>> > > with MINA, but we haven't cleared out all the terms yet. I think I
>> saw
>> > > somewhere that all @author tags and copyright notices would need
>> to be
>> > > removed if the code is published with the Apache license. Am I
>> > > remembering correctly?
>> >
>> > this is more apache software foundation policy than the license itself
>> >
>> > the consensus at apache is that (for open source projects) author tags
>> > do more harm than good. not only are they are a long term PITA (users
>> > tend to SPAM @authors to questions that should be asked on the user
>> > lists) but they can be harmful to communication and may expose
>> > committers to undue legal risk. so, most projects don't use them any
>> > more, preferring to list developers on the site.
>> >
>> > sounds like this sort of contribution needs to arrive through a
>> > software grant. this grants the apache software foundation
>> > non-exclusive rights but does not transfer copyright ownership.
>> >
>> > as far as copyright notices are concerned, the apache legal team now
>> > feel that it is more accurate not to include an apache copyright
>> > notice in each file (as the substantive copyright may not actually
>> > belong to apache). the new header notice has different wording and
>> > includes no copyright claim. (this would be added to each document as
>> > part of the import process.)
>> >
>> > for code arriving under a software grant the situation is a little
>> > different. the grantor should own the copyright and so is entitled to
>> > add an accurate copyright. however, retention of these notices with
>> > the apache codebase is felt to be a bad practice (for code that
>> > arrives under a software grant). it is not easy to keep these claims
>> > accurate as the code developers. so, these notices should be moved
>> > into the NOTICE document as part of the processing of the grant.
>>
>> Thank you for explanation. I mistakenly thought it was a contribution
>> of personal code via JIRA which doesn't need software grant once the
>> contributor chooses the 'grant' radio button.
>
> you are right that a contribution through JIRA where the contributor
> chooses the 'grant' radio button does not require JIRA. we will
> probably be covered by http://www.apache.org/licenses/LICENSE-2.0
> clause 5.
>
> however, this does not mean that recommending submission by JIRA is a
> good idea for substantial contributions known to have been developed
> in a corporate environment.
>
> the problem is that some contributors in corporate environments may
> not have a deep understanding of copyright law nor appreciate that
> they may not have the rights required. the individual is (in this
> case) unlikely to be the owner. unless they are careful, this may
> expose the contributor to liability (or may even be a serious crime in
> some jurisdictions).
>
> the apache legal team created the software grant and the CCLA to cover
> contributors in situations such as this. they are standard contracts
> between apache and the corporation. they have been used by some of the
> world's biggest corporations. using these contracts gives greater
> legal certainty and clarity for everyone than AL clause 5.
>
> personally speaking, when an unannounced or small submission is
> received through JIRA, i generally take their submission at face value
> and (unless there is evidence to the contrary) assume that they have
> rights to the code submitted. when a patch is discussed on the list
> and it becomes clear that it isn't an original code submission, i
> mention that code can also be submitted through a software grant and
> that this is better in some circumstances. sometimes the contributor
> opts for a grant, sometimes for JIRA but at least they think a little.
>
>> I am almost ignorant on software grant for now because of my lack of
>> experience. You or Alex could assist Eero and me this time.
>
> IANAL but i try to be helpful as best i can
>
> there is documentation at http://www.apache.org/legal/ and the
> legal-discuss list exists to discuss matters such as IP clearance. the
> incubator PMC (http://incubator.apache.org/) has been asked by the
> board to supervising IP clearance. the general list is another place
> where questions on IP clearance are definitely in scope.
>
> - robert
Re: heartbeat and connection monitoring
Posted by robert burrell donkin <ro...@gmail.com>.
On 2/15/07, Trustin Lee <tr...@gmail.com> wrote:
> Robert,
>
> 2007-02-14 (수), 17:41 +0000, robert burrell donkin 쓰시길:
> > On 2/14/07, Eero Nevalainen <ee...@indagon.com> wrote:
> > > Hi,
> > >
> > > I implemented this kind of thing a while ago as a part of our company
> > > project and thought about posting it, since it's something the framework
> > > could very well provide.
> > >
> > > The company gave a preliminary approval of sharing and participating
> > > with MINA, but we haven't cleared out all the terms yet. I think I saw
> > > somewhere that all @author tags and copyright notices would need to be
> > > removed if the code is published with the Apache license. Am I
> > > remembering correctly?
> >
> > this is more apache software foundation policy than the license itself
> >
> > the consensus at apache is that (for open source projects) author tags
> > do more harm than good. not only are they are a long term PITA (users
> > tend to SPAM @authors to questions that should be asked on the user
> > lists) but they can be harmful to communication and may expose
> > committers to undue legal risk. so, most projects don't use them any
> > more, preferring to list developers on the site.
> >
> > sounds like this sort of contribution needs to arrive through a
> > software grant. this grants the apache software foundation
> > non-exclusive rights but does not transfer copyright ownership.
> >
> > as far as copyright notices are concerned, the apache legal team now
> > feel that it is more accurate not to include an apache copyright
> > notice in each file (as the substantive copyright may not actually
> > belong to apache). the new header notice has different wording and
> > includes no copyright claim. (this would be added to each document as
> > part of the import process.)
> >
> > for code arriving under a software grant the situation is a little
> > different. the grantor should own the copyright and so is entitled to
> > add an accurate copyright. however, retention of these notices with
> > the apache codebase is felt to be a bad practice (for code that
> > arrives under a software grant). it is not easy to keep these claims
> > accurate as the code developers. so, these notices should be moved
> > into the NOTICE document as part of the processing of the grant.
>
> Thank you for explanation. I mistakenly thought it was a contribution
> of personal code via JIRA which doesn't need software grant once the
> contributor chooses the 'grant' radio button.
you are right that a contribution through JIRA where the contributor
chooses the 'grant' radio button does not require JIRA. we will
probably be covered by http://www.apache.org/licenses/LICENSE-2.0
clause 5.
however, this does not mean that recommending submission by JIRA is a
good idea for substantial contributions known to have been developed
in a corporate environment.
the problem is that some contributors in corporate environments may
not have a deep understanding of copyright law nor appreciate that
they may not have the rights required. the individual is (in this
case) unlikely to be the owner. unless they are careful, this may
expose the contributor to liability (or may even be a serious crime in
some jurisdictions).
the apache legal team created the software grant and the CCLA to cover
contributors in situations such as this. they are standard contracts
between apache and the corporation. they have been used by some of the
world's biggest corporations. using these contracts gives greater
legal certainty and clarity for everyone than AL clause 5.
personally speaking, when an unannounced or small submission is
received through JIRA, i generally take their submission at face value
and (unless there is evidence to the contrary) assume that they have
rights to the code submitted. when a patch is discussed on the list
and it becomes clear that it isn't an original code submission, i
mention that code can also be submitted through a software grant and
that this is better in some circumstances. sometimes the contributor
opts for a grant, sometimes for JIRA but at least they think a little.
> I am almost ignorant on software grant for now because of my lack of
> experience. You or Alex could assist Eero and me this time.
IANAL but i try to be helpful as best i can
there is documentation at http://www.apache.org/legal/ and the
legal-discuss list exists to discuss matters such as IP clearance. the
incubator PMC (http://incubator.apache.org/) has been asked by the
board to supervising IP clearance. the general list is another place
where questions on IP clearance are definitely in scope.
- robert
Re: heartbeat and connection monitoring
Posted by Trustin Lee <tr...@gmail.com>.
Robert,
2007-02-14 (수), 17:41 +0000, robert burrell donkin 쓰시길:
> On 2/14/07, Eero Nevalainen <ee...@indagon.com> wrote:
> > Hi,
> >
> > I implemented this kind of thing a while ago as a part of our company
> > project and thought about posting it, since it's something the framework
> > could very well provide.
> >
> > The company gave a preliminary approval of sharing and participating
> > with MINA, but we haven't cleared out all the terms yet. I think I saw
> > somewhere that all @author tags and copyright notices would need to be
> > removed if the code is published with the Apache license. Am I
> > remembering correctly?
>
> this is more apache software foundation policy than the license itself
>
> the consensus at apache is that (for open source projects) author tags
> do more harm than good. not only are they are a long term PITA (users
> tend to SPAM @authors to questions that should be asked on the user
> lists) but they can be harmful to communication and may expose
> committers to undue legal risk. so, most projects don't use them any
> more, preferring to list developers on the site.
>
> sounds like this sort of contribution needs to arrive through a
> software grant. this grants the apache software foundation
> non-exclusive rights but does not transfer copyright ownership.
>
> as far as copyright notices are concerned, the apache legal team now
> feel that it is more accurate not to include an apache copyright
> notice in each file (as the substantive copyright may not actually
> belong to apache). the new header notice has different wording and
> includes no copyright claim. (this would be added to each document as
> part of the import process.)
>
> for code arriving under a software grant the situation is a little
> different. the grantor should own the copyright and so is entitled to
> add an accurate copyright. however, retention of these notices with
> the apache codebase is felt to be a bad practice (for code that
> arrives under a software grant). it is not easy to keep these claims
> accurate as the code developers. so, these notices should be moved
> into the NOTICE document as part of the processing of the grant.
Thank you for explanation. I mistakenly thought it was a contribution
of personal code via JIRA which doesn't need software grant once the
contributor chooses the 'grant' radio button.
I am almost ignorant on software grant for now because of my lack of
experience. You or Alex could assist Eero and me this time.
Thanks,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6
Re: heartbeat and connection monitoring
Posted by robert burrell donkin <ro...@gmail.com>.
On 2/14/07, Eero Nevalainen <ee...@indagon.com> wrote:
> Trustin Lee wrote:
> > Hi Benoit,
> >
> > 2007-02-12 (월), 13:32 +0000, Benoit Hudzia 쓰시길:
> >> Hi,
> >> A couple of month ago, somebody mentioned the possibility to add a
> >> heartbeat monitoring system for connection as filter. This filter would have
> >> been based on an implementation done in another project.
> >>
> >> Did anybody implemented it? If not, can somebody point me to the project so
> >> I can have a look and see if I can implement it myself?
> >
> > The heartbeat code was from Qpid project (in Apache incubator), but they
> > told me that their code had turned out to be not usable as we expected.
> > Implementing an heartbeat filter is very easy though. Let me add a JIRA
> > issue for it.
> >
> > https://issues.apache.org/jira/browse/DIRMINA-350
>
> Hi,
>
> I implemented this kind of thing a while ago as a part of our company
> project and thought about posting it, since it's something the framework
> could very well provide.
>
> The company gave a preliminary approval of sharing and participating
> with MINA, but we haven't cleared out all the terms yet. I think I saw
> somewhere that all @author tags and copyright notices would need to be
> removed if the code is published with the Apache license. Am I
> remembering correctly?
this is more apache software foundation policy than the license itself
the consensus at apache is that (for open source projects) author tags
do more harm than good. not only are they are a long term PITA (users
tend to SPAM @authors to questions that should be asked on the user
lists) but they can be harmful to communication and may expose
committers to undue legal risk. so, most projects don't use them any
more, preferring to list developers on the site.
sounds like this sort of contribution needs to arrive through a
software grant. this grants the apache software foundation
non-exclusive rights but does not transfer copyright ownership.
as far as copyright notices are concerned, the apache legal team now
feel that it is more accurate not to include an apache copyright
notice in each file (as the substantive copyright may not actually
belong to apache). the new header notice has different wording and
includes no copyright claim. (this would be added to each document as
part of the import process.)
for code arriving under a software grant the situation is a little
different. the grantor should own the copyright and so is entitled to
add an accurate copyright. however, retention of these notices with
the apache codebase is felt to be a bad practice (for code that
arrives under a software grant). it is not easy to keep these claims
accurate as the code developers. so, these notices should be moved
into the NOTICE document as part of the processing of the grant.
> The company would like to have at least some
> "thanks to" mention if we send stuff..
many companies of all sizes and individuals donate rights to source
through software grants. apache uses uniform process to ensure that
this operates equitably.
details of grants should be noted in commit records and in the IP
clearance documentation
(http://incubator.apache.org/ip-clearance/index.html).
apache seems comfortable with an attribution in the NOTICE file
similar to the apache notice:
"This product includes software developed at The Apache Software
Foundation (http://www.apache.org/)."
for example http://svn.apache.org/repos/asf/db/derby/code/trunk/NOTICE
if the company is looking for more than that (for example, links from
the web site) then this is leading into areas outside the comfort
zone...
- robert
Re: heartbeat and connection monitoring
Posted by Eero Nevalainen <ee...@indagon.com>.
Trustin Lee wrote:
> Hi Benoit,
>
> 2007-02-12 (월), 13:32 +0000, Benoit Hudzia 쓰시길:
>> Hi,
>> A couple of month ago, somebody mentioned the possibility to add a
>> heartbeat monitoring system for connection as filter. This filter would have
>> been based on an implementation done in another project.
>>
>> Did anybody implemented it? If not, can somebody point me to the project so
>> I can have a look and see if I can implement it myself?
>
> The heartbeat code was from Qpid project (in Apache incubator), but they
> told me that their code had turned out to be not usable as we expected.
> Implementing an heartbeat filter is very easy though. Let me add a JIRA
> issue for it.
>
> https://issues.apache.org/jira/browse/DIRMINA-350
Hi,
I implemented this kind of thing a while ago as a part of our company
project and thought about posting it, since it's something the framework
could very well provide.
The company gave a preliminary approval of sharing and participating
with MINA, but we haven't cleared out all the terms yet. I think I saw
somewhere that all @author tags and copyright notices would need to be
removed if the code is published with the Apache license. Am I
remembering correctly? The company would like to have at least some
"thanks to" mention if we send stuff..
This is not a major problem though as like Trustin said, it's very easy
to implement. I'd still like to know though..
-Eero Nevalainen
Re: heartbeat and connection monitoring
Posted by Trustin Lee <tr...@gmail.com>.
Hi Benoit,
2007-02-12 (월), 13:32 +0000, Benoit Hudzia 쓰시길:
> Hi,
> A couple of month ago, somebody mentioned the possibility to add a
> heartbeat monitoring system for connection as filter. This filter would have
> been based on an implementation done in another project.
>
> Did anybody implemented it? If not, can somebody point me to the project so
> I can have a look and see if I can implement it myself?
The heartbeat code was from Qpid project (in Apache incubator), but they
told me that their code had turned out to be not usable as we expected.
Implementing an heartbeat filter is very easy though. Let me add a JIRA
issue for it.
https://issues.apache.org/jira/browse/DIRMINA-350
> I currently rely on the tcp timeout but I need to move on to a more reliable
> monitoring system because in a long term I plan to move on a reliable udp
> filter I m working on .
You could send a certain message (e.g. NOOP) every 10 seconds and close
the connection when you didn't receive anything last 10 seconds, using
sessionIdle event.
HTH,
Trustin
--
what we call human nature is actually human habit
--
http://gleamynode.net/
--
PGP Key ID: 0x0255ECA6