You are viewing a plain text version of this content. The canonical link for it is here.
Posted to legal-discuss@apache.org by Cliff Schmidt <cl...@gmail.com> on 2006/07/17 08:39:37 UTC
Finally posted: src file header and copyright policy
Hey legal-discuss folks,
I've finally posted the "Source Header and Copyright Notice Policy":
http://www.apache.org/legal/src-headers.html.
It's pretty much the same thing I sent to this list a few weeks ago,
plus a FAQ that summarizes the follow-on discussion we had.
As I've mentioned before, my plan is to finish up the other two pieces
and send an email to committers@ with links to all three legal pages.
There's a good possibility I'll have these other two done in the next
couple days, but I thought I'd put this out for legal-discuss review
since it is ready now.
Let me know if you see anything in there that doesn't make sense.
Cliff
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Cliff Schmidt <cl...@gmail.com>.
done -- sorry for the delay on that. It's now updated to Nov 1.
On 8/24/06, John Sisson <js...@internode.on.net> wrote:
> Currently http://www.apache.org/legal/src-headers.html#headers still
> says Sept 1. Can someone with authority please update this to reflect
> the extended date that appears to have been agreed upon in this thread.
>
> Thanks,
> John
>
> Geir Magnusson Jr wrote:
> > Cliff Schmidt wrote:
> >> On 8/5/06, Geir Magnusson Jr <ge...@apache.org> wrote:
> >>
> >>> Can we make this 11/1 or even 1/1/07 given that there's no real
> >>> emergency?
> >> I don't see any problem with pushing this back to November 1st. So,
> >> while there's no emergency...do you really think that projects would
> >> need an additional *four* months after September 1 to get this done?
> >
> > No - I just was suggesting some nice round numbers. We'll do it sooner
> > than later in Harmony, but jamming it in 3 weeks in the dead of August
> > seemed odd.
> >
> >> That seems unnecessarily long to me; at some point, the deadline is so
> >> far away that people just push it off because they can and not for any
> >> practical necessity.
> >>
> >> Any other thoughts on this? I think November 1 seems pretty
> >> reasonable since that will be more than 2.5 months that every single
> >> committer will have had notice and thorough documentation to get it
> >> done. And don't forget that not everything has to be changed by the
> >> deadline; changes just need to be made to the next release after the
> >> deadline, which for some project cycles may give another couple
> >> months.
> >
> > It won't bother derby, as they seem to release on a geological calendar,
> > but I expect things will converge pretty quickly to completion.
> >
> > geir
> >
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by John Sisson <js...@internode.on.net>.
Currently http://www.apache.org/legal/src-headers.html#headers still
says Sept 1. Can someone with authority please update this to reflect
the extended date that appears to have been agreed upon in this thread.
Thanks,
John
Geir Magnusson Jr wrote:
> Cliff Schmidt wrote:
>> On 8/5/06, Geir Magnusson Jr <ge...@apache.org> wrote:
>>
>>> Can we make this 11/1 or even 1/1/07 given that there's no real
>>> emergency?
>> I don't see any problem with pushing this back to November 1st. So,
>> while there's no emergency...do you really think that projects would
>> need an additional *four* months after September 1 to get this done?
>
> No - I just was suggesting some nice round numbers. We'll do it sooner
> than later in Harmony, but jamming it in 3 weeks in the dead of August
> seemed odd.
>
>> That seems unnecessarily long to me; at some point, the deadline is so
>> far away that people just push it off because they can and not for any
>> practical necessity.
>>
>> Any other thoughts on this? I think November 1 seems pretty
>> reasonable since that will be more than 2.5 months that every single
>> committer will have had notice and thorough documentation to get it
>> done. And don't forget that not everything has to be changed by the
>> deadline; changes just need to be made to the next release after the
>> deadline, which for some project cycles may give another couple
>> months.
>
> It won't bother derby, as they seem to release on a geological calendar,
> but I expect things will converge pretty quickly to completion.
>
> geir
>
>
> ---------------------------------------------------------------------
> 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
>
>
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Geir Magnusson Jr <ge...@apache.org>.
Cliff Schmidt wrote:
> On 8/5/06, Geir Magnusson Jr <ge...@apache.org> wrote:
>
>> Can we make this 11/1 or even 1/1/07 given that there's no real
>> emergency?
>
> I don't see any problem with pushing this back to November 1st. So,
> while there's no emergency...do you really think that projects would
> need an additional *four* months after September 1 to get this done?
No - I just was suggesting some nice round numbers. We'll do it sooner
than later in Harmony, but jamming it in 3 weeks in the dead of August
seemed odd.
> That seems unnecessarily long to me; at some point, the deadline is so
> far away that people just push it off because they can and not for any
> practical necessity.
>
> Any other thoughts on this? I think November 1 seems pretty
> reasonable since that will be more than 2.5 months that every single
> committer will have had notice and thorough documentation to get it
> done. And don't forget that not everything has to be changed by the
> deadline; changes just need to be made to the next release after the
> deadline, which for some project cycles may give another couple
> months.
It won't bother derby, as they seem to release on a geological calendar,
but I expect things will converge pretty quickly to completion.
geir
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Cliff Schmidt <cl...@gmail.com>.
On 8/5/06, Geir Magnusson Jr <ge...@apache.org> wrote:
> Why would there be a Sept 1, 2006 deadline for this, and who set that?
I set it. The original intention was to give the same two months
notice that was used for the last header change from Jan-Mar 2004
(IIRC). Sept 1 is well over two months since I sent the accepted
board resolution to this list, but the detailed doc about it with FAQ
and all that was only posted and referenced here on July 16th (less
than two months before Sep 1). In addition, I still haven't sent out
the broad notice to committers@ simply because (silly me thinking this
would be a minor issue...) there has not been consensus over where the
URL should be (have all legal docs in /legal or have some on /dev,
some /licenses/ and some /foundation). I've taken the issue to the
site-dev list and expect we'll have something settled in the next day
or two. After that, I'll finally send out the broad notice with
pointer to committers@.
Because of the delay in having all instructions and FAQ done and
broadly distributed, I've been thinking I should push the deadline
back. In the mean time, I've been helping each individual project
that has pinged me about it.
> Is there some kind of "copyright emergency" we have to deal with?
Nope -- just addressing an important problem that we've known needed
to be fixed since way before I even had this job.
> I agree that sooner than later is better here, but it's summer (in the
> northern hemisphere), Europe is going on vacation en-masse (I never
> understand where they go - maybe they swap countries?), school is
> starting after that, etc, etc.
good point
> Can we make this 11/1 or even 1/1/07 given that there's no real emergency?
I don't see any problem with pushing this back to November 1st. So,
while there's no emergency...do you really think that projects would
need an additional *four* months after September 1 to get this done?
That seems unnecessarily long to me; at some point, the deadline is so
far away that people just push it off because they can and not for any
practical necessity.
Any other thoughts on this? I think November 1 seems pretty
reasonable since that will be more than 2.5 months that every single
committer will have had notice and thorough documentation to get it
done. And don't forget that not everything has to be changed by the
deadline; changes just need to be made to the next release after the
deadline, which for some project cycles may give another couple
months.
Cliff
> Cliff Schmidt wrote:
> > Hey legal-discuss folks,
> >
> > I've finally posted the "Source Header and Copyright Notice Policy":
> > http://www.apache.org/legal/src-headers.html.
> >
> > It's pretty much the same thing I sent to this list a few weeks ago,
> > plus a FAQ that summarizes the follow-on discussion we had.
> >
> > As I've mentioned before, my plan is to finish up the other two pieces
> > and send an email to committers@ with links to all three legal pages.
> > There's a good possibility I'll have these other two done in the next
> > couple days, but I thought I'd put this out for legal-discuss review
> > since it is ready now.
> >
> > Let me know if you see anything in there that doesn't make sense.
> >
> > Cliff
> >
> > ---------------------------------------------------------------------
> > 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
> >
> >
> >
>
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Geir Magnusson Jr <ge...@apache.org>.
Why would there be a Sept 1, 2006 deadline for this, and who set that?
Is there some kind of "copyright emergency" we have to deal with?
I agree that sooner than later is better here, but it's summer (in the
northern hemisphere), Europe is going on vacation en-masse (I never
understand where they go - maybe they swap countries?), school is
starting after that, etc, etc.
Can we make this 11/1 or even 1/1/07 given that there's no real emergency?
geir
Cliff Schmidt wrote:
> Hey legal-discuss folks,
>
> I've finally posted the "Source Header and Copyright Notice Policy":
> http://www.apache.org/legal/src-headers.html.
>
> It's pretty much the same thing I sent to this list a few weeks ago,
> plus a FAQ that summarizes the follow-on discussion we had.
>
> As I've mentioned before, my plan is to finish up the other two pieces
> and send an email to committers@ with links to all three legal pages.
> There's a good possibility I'll have these other two done in the next
> couple days, but I thought I'd put this out for legal-discuss review
> since it is ready now.
>
> Let me know if you see anything in there that doesn't make sense.
>
> Cliff
>
> ---------------------------------------------------------------------
> 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
>
>
>
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Cliff Schmidt <cl...@gmail.com>.
On 7/17/06, Henri Yandell <ba...@apache.org> wrote:
> In
>
> "4. Minor modifications/additions to third-party source files should
> typically be licensed under the same terms as the rest of the source for
> convenience. "
>
> I presume that 'rest of the source' means the non ASL source and not the
> ASL source? Suggested change: "rest of the third-party source".
change applied: see
http://www.apache.org/legal/src-headers.html#3party-minormodsok
> Might want something in the FAQ for images and the like. If an image is
> under someone elses copyright, it should be in NOTICE etc.
added: see http://www.apache.org/legal/src-headers.html#faq-media ("Do
images or other media require a copyright line in the NOTICE file?)
> That's what I presumed the "Does this apply to third-party binaries" bit
> would mean at first.
I tried to clarify this a bit and also mentioned .exe installers as
okay: http://www.apache.org/legal/src-headers.html#faq-binaries
Cliff
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Henri Yandell <ba...@apache.org>.
In
"4. Minor modifications/additions to third-party source files should
typically be licensed under the same terms as the rest of the source for
convenience. "
I presume that 'rest of the source' means the non ASL source and not the
ASL source? Suggested change: "rest of the third-party source".
---
Might want something in the FAQ for images and the like. If an image is
under someone elses copyright, it should be in NOTICE etc.
That's what I presumed the "Does this apply to third-party binaries" bit
would mean at first.
Hen
On Sun, 16 Jul 2006, Cliff Schmidt wrote:
> Hey legal-discuss folks,
>
> I've finally posted the "Source Header and Copyright Notice Policy":
> http://www.apache.org/legal/src-headers.html.
>
> It's pretty much the same thing I sent to this list a few weeks ago,
> plus a FAQ that summarizes the follow-on discussion we had.
>
> As I've mentioned before, my plan is to finish up the other two pieces
> and send an email to committers@ with links to all three legal pages.
> There's a good possibility I'll have these other two done in the next
> couple days, but I thought I'd put this out for legal-discuss review
> since it is ready now.
>
> Let me know if you see anything in there that doesn't make sense.
>
> Cliff
>
> ---------------------------------------------------------------------
> 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
>
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by robert burrell donkin <rd...@apache.org>.
On Wed, 2006-08-02 at 14:31 -0700, Cliff Schmidt wrote:
> On 8/2/06, robert burrell donkin <rd...@apache.org> wrote:
> > On Tue, 2006-08-01 at 17:17 -0400, Henri Yandell wrote:
> > >
> > > On Tue, 1 Aug 2006, Cliff Schmidt wrote:
> > >
> > > > Does anyone else have an opinion on whether all committer
> > > > guidelines/docs should live in /dev, rather than some place like
> > > > /legal or /prc or some other applicable top-level path?
> > >
> > > +1 to within /legal. It'd either be /dev/legal or /legal, and I don't see
> > > any reason not to keep it simple. Not that it seems very important either
> > > way. You can either argue that it's in /legal because it's policy set by
> > > the legal group; or /dev/legal because it's legal policy set for
> > > developers. Six of one...
> >
> > ...half a dozen of the other :-)
> >
> > BTW i'm quite happy about posting the documentation wherever seems
> > reasonable (it's easy to move later using redirects to preserve
> > external links and searching indexes). just seemed like a good chance to
> > think about the bigger picture...
>
> agreed -- will you be taking the bigger picture question to another list?
probably not - the right list is site-dev so i'd most likely be deafened
by the sound of silence...
- robert
Re: Finally posted: src file header and copyright policy
Posted by Cliff Schmidt <cl...@gmail.com>.
On 8/2/06, robert burrell donkin <rd...@apache.org> wrote:
> On Tue, 2006-08-01 at 17:17 -0400, Henri Yandell wrote:
> >
> > On Tue, 1 Aug 2006, Cliff Schmidt wrote:
> >
> > > Does anyone else have an opinion on whether all committer
> > > guidelines/docs should live in /dev, rather than some place like
> > > /legal or /prc or some other applicable top-level path?
> >
> > +1 to within /legal. It'd either be /dev/legal or /legal, and I don't see
> > any reason not to keep it simple. Not that it seems very important either
> > way. You can either argue that it's in /legal because it's policy set by
> > the legal group; or /dev/legal because it's legal policy set for
> > developers. Six of one...
>
> ...half a dozen of the other :-)
>
> BTW i'm quite happy about posting the documentation wherever seems
> reasonable (it's easy to move later using redirects to preserve
> external links and searching indexes). just seemed like a good chance to
> think about the bigger picture...
agreed -- will you be taking the bigger picture question to another list?
/me ducks
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by robert burrell donkin <rd...@apache.org>.
On Tue, 2006-08-01 at 17:17 -0400, Henri Yandell wrote:
>
> On Tue, 1 Aug 2006, Cliff Schmidt wrote:
>
> > Does anyone else have an opinion on whether all committer
> > guidelines/docs should live in /dev, rather than some place like
> > /legal or /prc or some other applicable top-level path?
>
> +1 to within /legal. It'd either be /dev/legal or /legal, and I don't see
> any reason not to keep it simple. Not that it seems very important either
> way. You can either argue that it's in /legal because it's policy set by
> the legal group; or /dev/legal because it's legal policy set for
> developers. Six of one...
...half a dozen of the other :-)
BTW i'm quite happy about posting the documentation wherever seems
reasonable (it's easy to move later using redirects to preserve
external links and searching indexes). just seemed like a good chance to
think about the bigger picture...
- robert
Re: Finally posted: src file header and copyright policy
Posted by Henri Yandell <ba...@generationjava.com>.
On Tue, 1 Aug 2006, Cliff Schmidt wrote:
> Does anyone else have an opinion on whether all committer
> guidelines/docs should live in /dev, rather than some place like
> /legal or /prc or some other applicable top-level path?
+1 to within /legal. It'd either be /dev/legal or /legal, and I don't see
any reason not to keep it simple. Not that it seems very important either
way. You can either argue that it's in /legal because it's policy set by
the legal group; or /dev/legal because it's legal policy set for
developers. Six of one...
Hen
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Henri Yandell <ba...@apache.org>.
On Wed, 2 Aug 2006, Roy T. Fielding wrote:
> I am a bit confused about what Robert is suggesting. The goal should
I believe Robert is suggesting that we have a strategy for the site -
it sounds like you're aware of such a strategy but it's not information
that has remained in the community knowledge.
(...snip...)
> be to make it easy for people to find the right documentation and for
> us to edit the right documentation. The documentation we are talking
> about is maintained by site-dev under the auspices of infrastructure
> because infrastructure is a President's committee tasked with that
> responsibility. The fact that some of the existing documentation
site-dev doesn't have a lot happening with respect to www -
however this conversation needs to go to site-dev. Could you start things
by outlining the strategy below in an email there as a proposed way forward?
Mostly the content that's in your current email I suspect.
(...snip...)
> Right now, all of the documentation for "how to develop software at
> Apache" is under /dev/ except for the bits that have just recently
> been put under /legal/. All of the software licenses that Apache offers
> to the world are under /licenses/ (and that is where export.html should
> be as well, since it is a list of export licenses). All of the ASF
> as a Foundation information is under /foundation/ except for the bits
> that have just recently been put under /legal/.
We also have /jcp, and probably /prc or /press at some point soon.
(...snip...)
> If someone wants to take over the entire site design and build some
> new hierarchy of sensible documentation, that's fine with me.
Robert's doing a great job of moving the site documentation - I think all
we need is some passing down of knowledge on site-dev and things can move
along.
> Individual authors, OTOH, should respect the conventions that we
> already have on site.
I presume they do, in so far as they understand them. This is about
committees creating a presence and Infra not being prepared for that
(no barbs intended to infra, the information architecture of the site is
rightly so not high on their list of priorities).
Hen
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Aug 1, 2006, at 2:01 PM, Cliff Schmidt wrote:
> On 7/23/06, robert burrell donkin <rd...@apache.org> wrote:
>> On Tue, 2006-07-18 at 14:28 -0700, Cliff Schmidt wrote:
>> > On 7/17/06, Roy T. Fielding <fi...@gbiv.com> wrote:
>> > > On Jul 16, 2006, at 11:39 PM, Cliff Schmidt wrote:
>> > >
>> > > > Hey legal-discuss folks,
>> > > >
>> > > > I've finally posted the "Source Header and Copyright Notice
>> Policy":
>> > > > http://www.apache.org/legal/src-headers.html.
>> > >
>> > > The content looks good.
>> > >
>> > > I would prefer that instructions to Apache committers be located
>> > > under <http://www.apache.org/dev/>. Linking them from legal
>> is fine,
>> > > but this is a policy from the board that should be treated
>> like all
>> > > the other documentation.
>>
>> IMO this is a decision that could do with some more thought.
>>
>> ATM infrastructure is charged with oversight of www.apache.org and in
>> particular http://www.apache.org/dev/ but there really isn't very
>> much
>> content in there which isn't at least indirectly related to
>> infrastructure.
>>
>> other groups within apache (for example legal, public relations,
>> conferences) are now starting to create content for
>> www.apache.org. so,
>> we need to think about the right organisation for this new content.
>>
>> in terms of oversight, it seems more convenient to keep all
>> documentation (whether aimed at committers or not) together at the
>> top
>> level and make each group responsible for overseeing everything under
>> that directory.
>>
>> this strategy would create a little more work in terms of
>> indexing. the
>> generated sitemap wouldn't pick up committer content in these other
>> areas but makes no difference to the manual links.
>
> I actually agree with you, Robert. I was just willing to go along
> with Roy's suggestion because I personally didn't feel strongly about
> it and just wanted to get it posted in one place and be done.
> However, you are probably right to think about the big picture here.
I am a bit confused about what Robert is suggesting. The goal should
be to make it easy for people to find the right documentation and for
us to edit the right documentation. The documentation we are talking
about is maintained by site-dev under the auspices of infrastructure
because infrastructure is a President's committee tasked with that
responsibility. The fact that some of the existing documentation
under dev is about creating new accounts is irrelevant. All of it is
about instructions to committers on how to manage projects and make
releases, which is exactly what Cliff is documenting in the src header
and copyright policy. Placing it somewhere else is not helpful.
Right now, all of the documentation for "how to develop software at
Apache" is under /dev/ except for the bits that have just recently
been put under /legal/. All of the software licenses that Apache offers
to the world are under /licenses/ (and that is where export.html should
be as well, since it is a list of export licenses). All of the ASF
as a Foundation information is under /foundation/ except for the bits
that have just recently been put under /legal/.
Not surprisingly, I don't agree with Cliff's individual decision to put
the stuff he authors in a different category than all prior decisions by
the site team. Everything we do at the ASF is "legal", so it doesn't
make any sense as a means of containment even if Cliff is the only one
editing those documents. It makes sense to have an organizational page
for our lawyers somewhere, but the "/legal/" section isn't even linked
from our other pages and the location should be under /foundation/
in any case. In short, the docs are in the wrong place.
If someone wants to take over the entire site design and build some
new hierarchy of sensible documentation, that's fine with me.
Individual authors, OTOH, should respect the conventions that we
already have on site.
....Roy
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Cliff Schmidt <cl...@gmail.com>.
On 7/23/06, robert burrell donkin <rd...@apache.org> wrote:
> On Tue, 2006-07-18 at 14:28 -0700, Cliff Schmidt wrote:
> > On 7/17/06, Roy T. Fielding <fi...@gbiv.com> wrote:
> > > On Jul 16, 2006, at 11:39 PM, Cliff Schmidt wrote:
> > >
> > > > Hey legal-discuss folks,
> > > >
> > > > I've finally posted the "Source Header and Copyright Notice Policy":
> > > > http://www.apache.org/legal/src-headers.html.
> > >
> > > The content looks good.
> > >
> > > I would prefer that instructions to Apache committers be located
> > > under <http://www.apache.org/dev/>. Linking them from legal is fine,
> > > but this is a policy from the board that should be treated like all
> > > the other documentation.
>
> IMO this is a decision that could do with some more thought.
>
> ATM infrastructure is charged with oversight of www.apache.org and in
> particular http://www.apache.org/dev/ but there really isn't very much
> content in there which isn't at least indirectly related to
> infrastructure.
>
> other groups within apache (for example legal, public relations,
> conferences) are now starting to create content for www.apache.org. so,
> we need to think about the right organisation for this new content.
>
> in terms of oversight, it seems more convenient to keep all
> documentation (whether aimed at committers or not) together at the top
> level and make each group responsible for overseeing everything under
> that directory.
>
> this strategy would create a little more work in terms of indexing. the
> generated sitemap wouldn't pick up committer content in these other
> areas but makes no difference to the manual links.
I actually agree with you, Robert. I was just willing to go along
with Roy's suggestion because I personally didn't feel strongly about
it and just wanted to get it posted in one place and be done.
However, you are probably right to think about the big picture here.
Does anyone else have an opinion on whether all committer
guidelines/docs should live in /dev, rather than some place like
/legal or /prc or some other applicable top-level path?
(this is obviously not the right list to address this question, but I
can't think of the right list at the moment -- anyone else who does
should feel free to move it...site-dev?)
Cliff
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by robert burrell donkin <rd...@apache.org>.
On Tue, 2006-07-18 at 14:28 -0700, Cliff Schmidt wrote:
> On 7/17/06, Roy T. Fielding <fi...@gbiv.com> wrote:
> > On Jul 16, 2006, at 11:39 PM, Cliff Schmidt wrote:
> >
> > > Hey legal-discuss folks,
> > >
> > > I've finally posted the "Source Header and Copyright Notice Policy":
> > > http://www.apache.org/legal/src-headers.html.
> >
> > The content looks good.
> >
> > I would prefer that instructions to Apache committers be located
> > under <http://www.apache.org/dev/>. Linking them from legal is fine,
> > but this is a policy from the board that should be treated like all
> > the other documentation.
IMO this is a decision that could do with some more thought.
ATM infrastructure is charged with oversight of www.apache.org and in
particular http://www.apache.org/dev/ but there really isn't very much
content in there which isn't at least indirectly related to
infrastructure.
other groups within apache (for example legal, public relations,
conferences) are now starting to create content for www.apache.org. so,
we need to think about the right organisation for this new content.
in terms of oversight, it seems more convenient to keep all
documentation (whether aimed at committers or not) together at the top
level and make each group responsible for overseeing everything under
that directory.
this strategy would create a little more work in terms of indexing. the
generated sitemap wouldn't pick up committer content in these other
areas but makes no difference to the manual links.
> Sure...but since there will be several more legal docs for committers,
> would you suggest I place all these in /dev/legal/ , rather than
> scatter them throughout /dev?
if they are going in dev then dev/legal would be much better than at top
level dev.
- robert
Re: Finally posted: src file header and copyright policy
Posted by Cliff Schmidt <cl...@gmail.com>.
On 7/17/06, Roy T. Fielding <fi...@gbiv.com> wrote:
> On Jul 16, 2006, at 11:39 PM, Cliff Schmidt wrote:
>
> > Hey legal-discuss folks,
> >
> > I've finally posted the "Source Header and Copyright Notice Policy":
> > http://www.apache.org/legal/src-headers.html.
>
> The content looks good.
>
> I would prefer that instructions to Apache committers be located
> under <http://www.apache.org/dev/>. Linking them from legal is fine,
> but this is a policy from the board that should be treated like all
> the other documentation.
Sure...but since there will be several more legal docs for committers,
would you suggest I place all these in /dev/legal/ , rather than
scatter them throughout /dev?
Cliff
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by "Roy T. Fielding" <fi...@gbiv.com>.
On Jul 16, 2006, at 11:39 PM, Cliff Schmidt wrote:
> Hey legal-discuss folks,
>
> I've finally posted the "Source Header and Copyright Notice Policy":
> http://www.apache.org/legal/src-headers.html.
The content looks good.
I would prefer that instructions to Apache committers be located
under <http://www.apache.org/dev/>. Linking them from legal is fine,
but this is a policy from the board that should be treated like all
the other documentation.
....Roy
---------------------------------------------------------------------
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: Fwd: Finally posted: src file header and copyright policy
Posted by Mike Edwards <mi...@gmail.com>.
Jeremy,
Glad to see that the policy page covers code like the stuff associated
with the SCA & SDO specs:
-----
Treatment of Third-Party Works
0. The term "third-party work" refers to a work not submitted
directly to the ASF by the copyright owner or owner's agent.
1.
2. Do not modify or remove any copyright notices or licenses within
third-party works.
3. Do ensure that every third-party work includes its associated
license, even if that requires adding a copy of the license from the
third-party download site into the distribution.
4. Do not add the standard Apache License header to the top of
third-party source files.
5. Minor modifications/additions to third-party source files should
typically be licensed under the same terms as the rest of the rest of
the third-party source for convenience.
Major modifications/additions to third-party should be dealt with
on a case-by-case basis by the PMC.
-----
Makes it clear that you can include such code - and that you leave alone
the existing headers and license.
Yours, Mike.
Jeremy Boynes wrote:
> Heads up of an upcoming policy change that means we will need to update
> the license boilerplate in our code.
> --
> Jeremy
>
> Begin forwarded message:
>
>> From: "Cliff Schmidt" <cl...@gmail.com>
>> Date: July 16, 2006 11:39:37 PM PDT
>> To: legal-discuss@apache.org
>> Subject: Finally posted: src file header and copyright policy
>>
>> Hey legal-discuss folks,
>>
>> I've finally posted the "Source Header and Copyright Notice Policy":
>> http://www.apache.org/legal/src-headers.html.
>>
>> It's pretty much the same thing I sent to this list a few weeks ago,
>> plus a FAQ that summarizes the follow-on discussion we had.
>>
>> As I've mentioned before, my plan is to finish up the other two pieces
>> and send an email to committers@ with links to all three legal pages.
>> There's a good possibility I'll have these other two done in the next
>> couple days, but I thought I'd put this out for legal-discuss review
>> since it is ready now.
>>
>> Let me know if you see anything in there that doesn't make sense.
>>
>> Cliff
>>
>> ---------------------------------------------------------------------
>> 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
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Finally posted: src file header and copyright policy
Posted by Kevin Williams <ke...@qwest.net>.
Regarding the replacement script, here is a Ruby script we might try
next time we have to go through a similar exercise:
# Scans files - with a given extension - recursively from the current
# directory replacing the old copyright/license header statement with a
# new version
def munge_file(fn, oh, nh)
puts "processing <#{fn}>"
eoh = Regexp.escape(oh)
new_contents = File.read(fn).gsub(Regexp.new(eoh), nh)
File.open(fn, 'w') do |file|
file.puts(new_contents)
end
end
if(!ARGV[0])
STDERR.puts "usage: <file extension> <old header file> <new
header file>"
exit 0
end
ext = ARGV[0]
old_header = File.read(ARGV[1])
new_header = File.read(ARGV[2])
Dir["**/*.#{ext}"].each do |filename|
munge_file( filename, old_header, new_header)
end
This is run from the command line like this:
>ruby replaceheaders.rb oldheader.txt newheader.txt
Luciano Resende wrote:
> Hi Jeremy
>
> I have done necessary updates on das and sample/das files and
> provided a
> patch to http://issues.apache.org/jira/browse/TUSCANY-620. I'm having
> some
> issues around running the perl script to update the xml resources and
> will
> try to finish those tomorrow....
>
> - Luciano
>
> On 7/19/06, Jeremy Boynes <jb...@apache.org> wrote:
>
>>
>>
>> On Jul 19, 2006, at 11:50 AM, Jeremy Boynes wrote:
>>
>> > Is this is good time to do this to the trunk (thinking that most
>> > people will not have any work that will conflict)?
>> >
>> > I'll see if the tools work and if there are no issues think about
>> > doing this later this week.
>>
>> We had a problem with some of the files not having license headers in
>> them :-(
>> so I modified Roy's script to be a little more aggressive and replace
>> everything before the "package" statement with the new header.
>>
>> I ran these on a few files and they seemed to do the right thing but
>> additional review would be appreciated.
>>
>> --
>> Jeremy
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Finally posted: src file header and copyright policy
Posted by Luciano Resende <lu...@gmail.com>.
Hi Jeremy
I have done necessary updates on das and sample/das files and provided a
patch to http://issues.apache.org/jira/browse/TUSCANY-620. I'm having some
issues around running the perl script to update the xml resources and will
try to finish those tomorrow....
- Luciano
On 7/19/06, Jeremy Boynes <jb...@apache.org> wrote:
>
>
> On Jul 19, 2006, at 11:50 AM, Jeremy Boynes wrote:
>
> > Is this is good time to do this to the trunk (thinking that most
> > people will not have any work that will conflict)?
> >
> > I'll see if the tools work and if there are no issues think about
> > doing this later this week.
>
> We had a problem with some of the files not having license headers in
> them :-(
> so I modified Roy's script to be a little more aggressive and replace
> everything before the "package" statement with the new header.
>
> I ran these on a few files and they seemed to do the right thing but
> additional review would be appreciated.
>
> --
> Jeremy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
-----------------------------------------------------
Luciano Resende
SOA Opensource - Apache Tuscany
-----------------------------------------------------
Re: Finally posted: src file header and copyright policy
Posted by Jeremy Boynes <jb...@apache.org>.
Having just made modifications to most of the sca source tree to fix
the CR problems, I plan to make this change later today.
--
Jeremy
On Jul 19, 2006, at 1:43 PM, Jeremy Boynes wrote:
>
> On Jul 19, 2006, at 11:50 AM, Jeremy Boynes wrote:
>
>> Is this is good time to do this to the trunk (thinking that most
>> people will not have any work that will conflict)?
>>
>> I'll see if the tools work and if there are no issues think about
>> doing this later this week.
>
> We had a problem with some of the files not having license headers
> in them :-(
> so I modified Roy's script to be a little more aggressive and
> replace everything before the "package" statement with the new header.
>
> I ran these on a few files and they seemed to do the right thing
> but additional review would be appreciated.
>
> --
> Jeremy
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Finally posted: src file header and copyright policy
Posted by Jeremy Boynes <jb...@apache.org>.
On Jul 19, 2006, at 11:50 AM, Jeremy Boynes wrote:
> Is this is good time to do this to the trunk (thinking that most
> people will not have any work that will conflict)?
>
> I'll see if the tools work and if there are no issues think about
> doing this later this week.
We had a problem with some of the files not having license headers in
them :-(
so I modified Roy's script to be a little more aggressive and replace
everything before the "package" statement with the new header.
I ran these on a few files and they seemed to do the right thing but
additional review would be appreciated.
--
Jeremy
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Finally posted: src file header and copyright policy
Posted by Jeremy Boynes <jb...@apache.org>.
Is this is good time to do this to the trunk (thinking that most
people will not have any work that will conflict)?
I'll see if the tools work and if there are no issues think about
doing this later this week.
--
Jeremy
On Jul 17, 2006, at 10:32 AM, Jeremy Boynes wrote:
> Heads up of an upcoming policy change that means we will need to
> update the license boilerplate in our code.
> --
> Jeremy
>
> Begin forwarded message:
>
>> From: "Cliff Schmidt" <cl...@gmail.com>
>> Date: July 16, 2006 11:39:37 PM PDT
>> To: legal-discuss@apache.org
>> Subject: Finally posted: src file header and copyright policy
>>
>> Hey legal-discuss folks,
>>
>> I've finally posted the "Source Header and Copyright Notice Policy":
>> http://www.apache.org/legal/src-headers.html.
>>
>> It's pretty much the same thing I sent to this list a few weeks ago,
>> plus a FAQ that summarizes the follow-on discussion we had.
>>
>> As I've mentioned before, my plan is to finish up the other two
>> pieces
>> and send an email to committers@ with links to all three legal pages.
>> There's a good possibility I'll have these other two done in the next
>> couple days, but I thought I'd put this out for legal-discuss review
>> since it is ready now.
>>
>> Let me know if you see anything in there that doesn't make sense.
>>
>> Cliff
>>
>> ---------------------------------------------------------------------
>> 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
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Fwd: Finally posted: src file header and copyright policy
Posted by Jeremy Boynes <jb...@apache.org>.
Heads up of an upcoming policy change that means we will need to
update the license boilerplate in our code.
--
Jeremy
Begin forwarded message:
> From: "Cliff Schmidt" <cl...@gmail.com>
> Date: July 16, 2006 11:39:37 PM PDT
> To: legal-discuss@apache.org
> Subject: Finally posted: src file header and copyright policy
>
> Hey legal-discuss folks,
>
> I've finally posted the "Source Header and Copyright Notice Policy":
> http://www.apache.org/legal/src-headers.html.
>
> It's pretty much the same thing I sent to this list a few weeks ago,
> plus a FAQ that summarizes the follow-on discussion we had.
>
> As I've mentioned before, my plan is to finish up the other two pieces
> and send an email to committers@ with links to all three legal pages.
> There's a good possibility I'll have these other two done in the next
> couple days, but I thought I'd put this out for legal-discuss review
> since it is ready now.
>
> Let me know if you see anything in there that doesn't make sense.
>
> Cliff
>
> ---------------------------------------------------------------------
> 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
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Finally posted: src file header and copyright policy
Posted by Chad Schoettger <ch...@gmail.com>.
Ok so I've got all the headers updated (including WSM).
I'm not sure about the $Header:$ string at the bottom of each license.
I don't think it is required since it wasn't part of the license text
on the web page Cliff referenced.
If someone on the list knows why it is there it would be great to have
that documented in the dev list in case the question comes up again.
- Chad
On 8/3/06, Carlin Rogers <ca...@gmail.com> wrote:
> Just curious, do we still need the "$Header:$" string at the bottom of each
> source header? I didn't see it mentioned on the ASF Source Header page.
>
> Carlin
>
> On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> >
> > FWIW, all the source files which were missing headers should now have
> > them. I also checked WSM and didn't find any files with questionable
> > headers.
> >
> > Since it looks like everything is ready to go I'll try to start on the
> > actual header conversion to the new format tomorrow or Friday unless I
> > hear differently.
> >
> > - Chad
> >
> > On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> > > I'll let you know if I come across anything. I should have a commit
> > > for the files which were causing upgrade errors soon. Then I thought
> > > I'd add headers to any source files which are currently missing them.
> > >
> > > - Chad
> > >
> > >
> > >
> > > On 8/2/06, Carlin Rogers <ca...@gmail.com> wrote:
> > > > Chad,
> > > >
> > > > Sounds good. Thanks for doing this work. As you go through the NetUI
> > code,
> > > > let me know if there are issues/conflicts you want me to take care of
> > or
> > > > help with. I know that there are many tests files missing headers but
> > I
> > > > think people have slowly added them as the edit the tests. Again, let
> > me
> > > > know if there's anything you want me to help with.
> > > >
> > > > Carlin
> > > >
> > > > On 8/2/06, Cliff Schmidt <cl...@gmail.com> wrote:
> > > > >
> > > > > On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> > > > > > It appears the discussion on this has died down and all Apache
> > > > > > projects will be required to make this change by Sept 1st. Has
> > any
> > > > > > one on the dev list heard differently?
> > > > >
> > > > > Yep - I'm late in sending out the link to committers@ because I
> > wanted
> > > > > to finish up the other two things, but everything you need to know
> > for
> > > > > copyright is located at http://apache.org/legal/src-headers.html.
> > > > >
> > > > > Cliff
> > > > >
> > > > > >
> > > > > > I'll start with a pass though the Beehive source files and fix any
> > > > > > headers which won't migrate correctly using the update-AL20.plpearl
> > > > > > script and also attempt to make sure that all of our source files
> > have
> > > > > > an apache header.
> > > > > >
> > > > > > Assuming I don't hear differently I'll try to give the update a
> > shot
> > > > > > sometime next week.
> > > > > >
> > > > > > - Chad
> > > > > >
> > > > > > On 7/17/06, Eddie O'Neil <ek...@gmail.com> wrote:
> > > > > > > Heads up on an upcoming source header change to source files
> > in
> > > > > > > "live" branches of ASF source trees. Before taking any steps
> > here,
> > > > > > > let's let the discussion die down on this issue (it's been going
> > on
> > > > > > > for a little while). Would say that we should switch the source
> > > > > > > headers by August 15 at the latest.
> > > > > > >
> > > > > > > Eddie
> > > > > > >
> > > > > > >
> > > > > > > ---------- Forwarded message ----------
> > > > > > > From: Cliff Schmidt <cl...@gmail.com>
> > > > > > > Date: Jul 17, 2006 12:39 AM
> > > > > > > Subject: Finally posted: src file header and copyright policy
> > > > > > > To: legal-discuss@apache.org
> > > > > > >
> > > > > > >
> > > > > > > Hey legal-discuss folks,
> > > > > > >
> > > > > > > I've finally posted the "Source Header and Copyright Notice
> > Policy":
> > > > > > > http://www.apache.org/legal/src-headers.html.
> > > > > > >
> > > > > > > It's pretty much the same thing I sent to this list a few weeks
> > ago,
> > > > > > > plus a FAQ that summarizes the follow-on discussion we had.
> > > > > > >
> > > > > > > As I've mentioned before, my plan is to finish up the other two
> > pieces
> > > > > > > and send an email to committers@ with links to all three legal
> > pages.
> > > > > > > There's a good possibility I'll have these other two done in the
> > next
> > > > > > > couple days, but I thought I'd put this out for legal-discuss
> > review
> > > > > > > since it is ready now.
> > > > > > >
> > > > > > > Let me know if you see anything in there that doesn't make
> > sense.
> > > > > > >
> > > > > > > Cliff
> > > > > > >
> > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > 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: Finally posted: src file header and copyright policy
Posted by Carlin Rogers <ca...@gmail.com>.
Just curious, do we still need the "$Header:$" string at the bottom of each
source header? I didn't see it mentioned on the ASF Source Header page.
Carlin
On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
>
> FWIW, all the source files which were missing headers should now have
> them. I also checked WSM and didn't find any files with questionable
> headers.
>
> Since it looks like everything is ready to go I'll try to start on the
> actual header conversion to the new format tomorrow or Friday unless I
> hear differently.
>
> - Chad
>
> On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> > I'll let you know if I come across anything. I should have a commit
> > for the files which were causing upgrade errors soon. Then I thought
> > I'd add headers to any source files which are currently missing them.
> >
> > - Chad
> >
> >
> >
> > On 8/2/06, Carlin Rogers <ca...@gmail.com> wrote:
> > > Chad,
> > >
> > > Sounds good. Thanks for doing this work. As you go through the NetUI
> code,
> > > let me know if there are issues/conflicts you want me to take care of
> or
> > > help with. I know that there are many tests files missing headers but
> I
> > > think people have slowly added them as the edit the tests. Again, let
> me
> > > know if there's anything you want me to help with.
> > >
> > > Carlin
> > >
> > > On 8/2/06, Cliff Schmidt <cl...@gmail.com> wrote:
> > > >
> > > > On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> > > > > It appears the discussion on this has died down and all Apache
> > > > > projects will be required to make this change by Sept 1st. Has
> any
> > > > > one on the dev list heard differently?
> > > >
> > > > Yep - I'm late in sending out the link to committers@ because I
> wanted
> > > > to finish up the other two things, but everything you need to know
> for
> > > > copyright is located at http://apache.org/legal/src-headers.html.
> > > >
> > > > Cliff
> > > >
> > > > >
> > > > > I'll start with a pass though the Beehive source files and fix any
> > > > > headers which won't migrate correctly using the update-AL20.plpearl
> > > > > script and also attempt to make sure that all of our source files
> have
> > > > > an apache header.
> > > > >
> > > > > Assuming I don't hear differently I'll try to give the update a
> shot
> > > > > sometime next week.
> > > > >
> > > > > - Chad
> > > > >
> > > > > On 7/17/06, Eddie O'Neil <ek...@gmail.com> wrote:
> > > > > > Heads up on an upcoming source header change to source files
> in
> > > > > > "live" branches of ASF source trees. Before taking any steps
> here,
> > > > > > let's let the discussion die down on this issue (it's been going
> on
> > > > > > for a little while). Would say that we should switch the source
> > > > > > headers by August 15 at the latest.
> > > > > >
> > > > > > Eddie
> > > > > >
> > > > > >
> > > > > > ---------- Forwarded message ----------
> > > > > > From: Cliff Schmidt <cl...@gmail.com>
> > > > > > Date: Jul 17, 2006 12:39 AM
> > > > > > Subject: Finally posted: src file header and copyright policy
> > > > > > To: legal-discuss@apache.org
> > > > > >
> > > > > >
> > > > > > Hey legal-discuss folks,
> > > > > >
> > > > > > I've finally posted the "Source Header and Copyright Notice
> Policy":
> > > > > > http://www.apache.org/legal/src-headers.html.
> > > > > >
> > > > > > It's pretty much the same thing I sent to this list a few weeks
> ago,
> > > > > > plus a FAQ that summarizes the follow-on discussion we had.
> > > > > >
> > > > > > As I've mentioned before, my plan is to finish up the other two
> pieces
> > > > > > and send an email to committers@ with links to all three legal
> pages.
> > > > > > There's a good possibility I'll have these other two done in the
> next
> > > > > > couple days, but I thought I'd put this out for legal-discuss
> review
> > > > > > since it is ready now.
> > > > > >
> > > > > > Let me know if you see anything in there that doesn't make
> sense.
> > > > > >
> > > > > > Cliff
> > > > > >
> > > > > >
> ---------------------------------------------------------------------
> > > > > > 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: Finally posted: src file header and copyright policy
Posted by Chad Schoettger <ch...@gmail.com>.
FWIW, all the source files which were missing headers should now have
them. I also checked WSM and didn't find any files with questionable
headers.
Since it looks like everything is ready to go I'll try to start on the
actual header conversion to the new format tomorrow or Friday unless I
hear differently.
- Chad
On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> I'll let you know if I come across anything. I should have a commit
> for the files which were causing upgrade errors soon. Then I thought
> I'd add headers to any source files which are currently missing them.
>
> - Chad
>
>
>
> On 8/2/06, Carlin Rogers <ca...@gmail.com> wrote:
> > Chad,
> >
> > Sounds good. Thanks for doing this work. As you go through the NetUI code,
> > let me know if there are issues/conflicts you want me to take care of or
> > help with. I know that there are many tests files missing headers but I
> > think people have slowly added them as the edit the tests. Again, let me
> > know if there's anything you want me to help with.
> >
> > Carlin
> >
> > On 8/2/06, Cliff Schmidt <cl...@gmail.com> wrote:
> > >
> > > On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> > > > It appears the discussion on this has died down and all Apache
> > > > projects will be required to make this change by Sept 1st. Has any
> > > > one on the dev list heard differently?
> > >
> > > Yep - I'm late in sending out the link to committers@ because I wanted
> > > to finish up the other two things, but everything you need to know for
> > > copyright is located at http://apache.org/legal/src-headers.html.
> > >
> > > Cliff
> > >
> > > >
> > > > I'll start with a pass though the Beehive source files and fix any
> > > > headers which won't migrate correctly using the update-AL20.pl pearl
> > > > script and also attempt to make sure that all of our source files have
> > > > an apache header.
> > > >
> > > > Assuming I don't hear differently I'll try to give the update a shot
> > > > sometime next week.
> > > >
> > > > - Chad
> > > >
> > > > On 7/17/06, Eddie O'Neil <ek...@gmail.com> wrote:
> > > > > Heads up on an upcoming source header change to source files in
> > > > > "live" branches of ASF source trees. Before taking any steps here,
> > > > > let's let the discussion die down on this issue (it's been going on
> > > > > for a little while). Would say that we should switch the source
> > > > > headers by August 15 at the latest.
> > > > >
> > > > > Eddie
> > > > >
> > > > >
> > > > > ---------- Forwarded message ----------
> > > > > From: Cliff Schmidt <cl...@gmail.com>
> > > > > Date: Jul 17, 2006 12:39 AM
> > > > > Subject: Finally posted: src file header and copyright policy
> > > > > To: legal-discuss@apache.org
> > > > >
> > > > >
> > > > > Hey legal-discuss folks,
> > > > >
> > > > > I've finally posted the "Source Header and Copyright Notice Policy":
> > > > > http://www.apache.org/legal/src-headers.html.
> > > > >
> > > > > It's pretty much the same thing I sent to this list a few weeks ago,
> > > > > plus a FAQ that summarizes the follow-on discussion we had.
> > > > >
> > > > > As I've mentioned before, my plan is to finish up the other two pieces
> > > > > and send an email to committers@ with links to all three legal pages.
> > > > > There's a good possibility I'll have these other two done in the next
> > > > > couple days, but I thought I'd put this out for legal-discuss review
> > > > > since it is ready now.
> > > > >
> > > > > Let me know if you see anything in there that doesn't make sense.
> > > > >
> > > > > Cliff
> > > > >
> > > > > ---------------------------------------------------------------------
> > > > > 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: Finally posted: src file header and copyright policy
Posted by Chad Schoettger <ch...@gmail.com>.
I'll let you know if I come across anything. I should have a commit
for the files which were causing upgrade errors soon. Then I thought
I'd add headers to any source files which are currently missing them.
- Chad
On 8/2/06, Carlin Rogers <ca...@gmail.com> wrote:
> Chad,
>
> Sounds good. Thanks for doing this work. As you go through the NetUI code,
> let me know if there are issues/conflicts you want me to take care of or
> help with. I know that there are many tests files missing headers but I
> think people have slowly added them as the edit the tests. Again, let me
> know if there's anything you want me to help with.
>
> Carlin
>
> On 8/2/06, Cliff Schmidt <cl...@gmail.com> wrote:
> >
> > On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> > > It appears the discussion on this has died down and all Apache
> > > projects will be required to make this change by Sept 1st. Has any
> > > one on the dev list heard differently?
> >
> > Yep - I'm late in sending out the link to committers@ because I wanted
> > to finish up the other two things, but everything you need to know for
> > copyright is located at http://apache.org/legal/src-headers.html.
> >
> > Cliff
> >
> > >
> > > I'll start with a pass though the Beehive source files and fix any
> > > headers which won't migrate correctly using the update-AL20.pl pearl
> > > script and also attempt to make sure that all of our source files have
> > > an apache header.
> > >
> > > Assuming I don't hear differently I'll try to give the update a shot
> > > sometime next week.
> > >
> > > - Chad
> > >
> > > On 7/17/06, Eddie O'Neil <ek...@gmail.com> wrote:
> > > > Heads up on an upcoming source header change to source files in
> > > > "live" branches of ASF source trees. Before taking any steps here,
> > > > let's let the discussion die down on this issue (it's been going on
> > > > for a little while). Would say that we should switch the source
> > > > headers by August 15 at the latest.
> > > >
> > > > Eddie
> > > >
> > > >
> > > > ---------- Forwarded message ----------
> > > > From: Cliff Schmidt <cl...@gmail.com>
> > > > Date: Jul 17, 2006 12:39 AM
> > > > Subject: Finally posted: src file header and copyright policy
> > > > To: legal-discuss@apache.org
> > > >
> > > >
> > > > Hey legal-discuss folks,
> > > >
> > > > I've finally posted the "Source Header and Copyright Notice Policy":
> > > > http://www.apache.org/legal/src-headers.html.
> > > >
> > > > It's pretty much the same thing I sent to this list a few weeks ago,
> > > > plus a FAQ that summarizes the follow-on discussion we had.
> > > >
> > > > As I've mentioned before, my plan is to finish up the other two pieces
> > > > and send an email to committers@ with links to all three legal pages.
> > > > There's a good possibility I'll have these other two done in the next
> > > > couple days, but I thought I'd put this out for legal-discuss review
> > > > since it is ready now.
> > > >
> > > > Let me know if you see anything in there that doesn't make sense.
> > > >
> > > > Cliff
> > > >
> > > > ---------------------------------------------------------------------
> > > > 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: Finally posted: src file header and copyright policy
Posted by Carlin Rogers <ca...@gmail.com>.
Chad,
Sounds good. Thanks for doing this work. As you go through the NetUI code,
let me know if there are issues/conflicts you want me to take care of or
help with. I know that there are many tests files missing headers but I
think people have slowly added them as the edit the tests. Again, let me
know if there's anything you want me to help with.
Carlin
On 8/2/06, Cliff Schmidt <cl...@gmail.com> wrote:
>
> On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> > It appears the discussion on this has died down and all Apache
> > projects will be required to make this change by Sept 1st. Has any
> > one on the dev list heard differently?
>
> Yep - I'm late in sending out the link to committers@ because I wanted
> to finish up the other two things, but everything you need to know for
> copyright is located at http://apache.org/legal/src-headers.html.
>
> Cliff
>
> >
> > I'll start with a pass though the Beehive source files and fix any
> > headers which won't migrate correctly using the update-AL20.pl pearl
> > script and also attempt to make sure that all of our source files have
> > an apache header.
> >
> > Assuming I don't hear differently I'll try to give the update a shot
> > sometime next week.
> >
> > - Chad
> >
> > On 7/17/06, Eddie O'Neil <ek...@gmail.com> wrote:
> > > Heads up on an upcoming source header change to source files in
> > > "live" branches of ASF source trees. Before taking any steps here,
> > > let's let the discussion die down on this issue (it's been going on
> > > for a little while). Would say that we should switch the source
> > > headers by August 15 at the latest.
> > >
> > > Eddie
> > >
> > >
> > > ---------- Forwarded message ----------
> > > From: Cliff Schmidt <cl...@gmail.com>
> > > Date: Jul 17, 2006 12:39 AM
> > > Subject: Finally posted: src file header and copyright policy
> > > To: legal-discuss@apache.org
> > >
> > >
> > > Hey legal-discuss folks,
> > >
> > > I've finally posted the "Source Header and Copyright Notice Policy":
> > > http://www.apache.org/legal/src-headers.html.
> > >
> > > It's pretty much the same thing I sent to this list a few weeks ago,
> > > plus a FAQ that summarizes the follow-on discussion we had.
> > >
> > > As I've mentioned before, my plan is to finish up the other two pieces
> > > and send an email to committers@ with links to all three legal pages.
> > > There's a good possibility I'll have these other two done in the next
> > > couple days, but I thought I'd put this out for legal-discuss review
> > > since it is ready now.
> > >
> > > Let me know if you see anything in there that doesn't make sense.
> > >
> > > Cliff
> > >
> > > ---------------------------------------------------------------------
> > > 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: Finally posted: src file header and copyright policy
Posted by Cliff Schmidt <cl...@gmail.com>.
On 8/2/06, Chad Schoettger <ch...@gmail.com> wrote:
> It appears the discussion on this has died down and all Apache
> projects will be required to make this change by Sept 1st. Has any
> one on the dev list heard differently?
Yep - I'm late in sending out the link to committers@ because I wanted
to finish up the other two things, but everything you need to know for
copyright is located at http://apache.org/legal/src-headers.html.
Cliff
>
> I'll start with a pass though the Beehive source files and fix any
> headers which won't migrate correctly using the update-AL20.pl pearl
> script and also attempt to make sure that all of our source files have
> an apache header.
>
> Assuming I don't hear differently I'll try to give the update a shot
> sometime next week.
>
> - Chad
>
> On 7/17/06, Eddie O'Neil <ek...@gmail.com> wrote:
> > Heads up on an upcoming source header change to source files in
> > "live" branches of ASF source trees. Before taking any steps here,
> > let's let the discussion die down on this issue (it's been going on
> > for a little while). Would say that we should switch the source
> > headers by August 15 at the latest.
> >
> > Eddie
> >
> >
> > ---------- Forwarded message ----------
> > From: Cliff Schmidt <cl...@gmail.com>
> > Date: Jul 17, 2006 12:39 AM
> > Subject: Finally posted: src file header and copyright policy
> > To: legal-discuss@apache.org
> >
> >
> > Hey legal-discuss folks,
> >
> > I've finally posted the "Source Header and Copyright Notice Policy":
> > http://www.apache.org/legal/src-headers.html.
> >
> > It's pretty much the same thing I sent to this list a few weeks ago,
> > plus a FAQ that summarizes the follow-on discussion we had.
> >
> > As I've mentioned before, my plan is to finish up the other two pieces
> > and send an email to committers@ with links to all three legal pages.
> > There's a good possibility I'll have these other two done in the next
> > couple days, but I thought I'd put this out for legal-discuss review
> > since it is ready now.
> >
> > Let me know if you see anything in there that doesn't make sense.
> >
> > Cliff
> >
> > ---------------------------------------------------------------------
> > 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: Finally posted: src file header and copyright policy
Posted by Chad Schoettger <ch...@gmail.com>.
It appears the discussion on this has died down and all Apache
projects will be required to make this change by Sept 1st. Has any
one on the dev list heard differently?
I'll start with a pass though the Beehive source files and fix any
headers which won't migrate correctly using the update-AL20.pl pearl
script and also attempt to make sure that all of our source files have
an apache header.
Assuming I don't hear differently I'll try to give the update a shot
sometime next week.
- Chad
On 7/17/06, Eddie O'Neil <ek...@gmail.com> wrote:
> Heads up on an upcoming source header change to source files in
> "live" branches of ASF source trees. Before taking any steps here,
> let's let the discussion die down on this issue (it's been going on
> for a little while). Would say that we should switch the source
> headers by August 15 at the latest.
>
> Eddie
>
>
> ---------- Forwarded message ----------
> From: Cliff Schmidt <cl...@gmail.com>
> Date: Jul 17, 2006 12:39 AM
> Subject: Finally posted: src file header and copyright policy
> To: legal-discuss@apache.org
>
>
> Hey legal-discuss folks,
>
> I've finally posted the "Source Header and Copyright Notice Policy":
> http://www.apache.org/legal/src-headers.html.
>
> It's pretty much the same thing I sent to this list a few weeks ago,
> plus a FAQ that summarizes the follow-on discussion we had.
>
> As I've mentioned before, my plan is to finish up the other two pieces
> and send an email to committers@ with links to all three legal pages.
> There's a good possibility I'll have these other two done in the next
> couple days, but I thought I'd put this out for legal-discuss review
> since it is ready now.
>
> Let me know if you see anything in there that doesn't make sense.
>
> Cliff
>
> ---------------------------------------------------------------------
> 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
>
Fwd: Finally posted: src file header and copyright policy
Posted by Eddie O'Neil <ek...@gmail.com>.
Heads up on an upcoming source header change to source files in
"live" branches of ASF source trees. Before taking any steps here,
let's let the discussion die down on this issue (it's been going on
for a little while). Would say that we should switch the source
headers by August 15 at the latest.
Eddie
---------- Forwarded message ----------
From: Cliff Schmidt <cl...@gmail.com>
Date: Jul 17, 2006 12:39 AM
Subject: Finally posted: src file header and copyright policy
To: legal-discuss@apache.org
Hey legal-discuss folks,
I've finally posted the "Source Header and Copyright Notice Policy":
http://www.apache.org/legal/src-headers.html.
It's pretty much the same thing I sent to this list a few weeks ago,
plus a FAQ that summarizes the follow-on discussion we had.
As I've mentioned before, my plan is to finish up the other two pieces
and send an email to committers@ with links to all three legal pages.
There's a good possibility I'll have these other two done in the next
couple days, but I thought I'd put this out for legal-discuss review
since it is ready now.
Let me know if you see anything in there that doesn't make sense.
Cliff
---------------------------------------------------------------------
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: Finally posted: src file header and copyright policy
Posted by Cliff Schmidt <cl...@gmail.com>.
On 7/17/06, Justin Mason <jm...@jmason.org> wrote:
>
> Hi Cliff -- some minor text tweak suggestions...
<snip/>
> I think it reads better -- ymmv of course.
I agree, and I've made the update -- new page should be live any minute now.
Thanks for proposing a specific suggestion with your comment -- makes
life easier!
Cliff
---------------------------------------------------------------------
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