Re: Derby post-incubation cleanups: need a site redirect
David Crossley wrote: Jean T. Anderson wrote: Could somebody redirect http://incubator.apache.org/derby to http://db.apache.org/derby ? Once that redirect is in place, I'll remove the files from /www/incubator.apache.org/derby . Noel recently did that. oh excellent! cruft now removed. -jean - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Derby post-incubation cleanups: need a site redirect
Jean T. Anderson wrote:
> Could somebody redirect http://incubator.apache.org/derby to
> http://db.apache.org/derby ? Once that redirect is in place, I'll remove
> the files from /www/incubator.apache.org/derby .
Noel recently did that.
> I completed these two steps below and they should be visible the next
> time the incubator site is built:
>
> 1. http://incubator.apache.org/projects/index.html
>Moved derby from "Currently Incubating" to "Successfully Incubated"
> table.
> 2. http://incubator.apache.org/projects/derby.html
> updated derby.cwiki with link to new website
My fault. I re-generated the site, but forgot the final
manual step on the server to do 'svn up'. Done now
and waiting for rsync.
> Below is a check list I started putting together for incubator clean-up:
>
> [ ] Request repository/karma move from incubator to new location.
> [ ] Move web site from /www/incubator.apache.org/${PROJECT} to new
> destination
> [ ] Request redirect from old incubator URL to new
> [ ] After redirect is verified working, delete web cruft from
> /www/incubator.apache.org/${PROJECT}
> [ ] http://incubator.apache.org/projects/index.html
> Move project from "Currently Incubating" to "Successfully
> Incubated" table.
> [ ] http://incubator.apache.org/projects/${PROJECT}.html
> update with link to new website
>
> Is this list useful to anyone else? and is anything missing that I still
> need to take care of?
It certainly is Jean. We need to create a "Steps for exit"
document - your list can be a start. We also need a
"Steps for establish" document - Roy sent an email list
to one of the recent entrants.
David
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Derby post-incubation cleanups: need a site redirect
Could somebody redirect http://incubator.apache.org/derby to
http://db.apache.org/derby ? Once that redirect is in place, I'll remove
the files from /www/incubator.apache.org/derby .
I completed these two steps below and they should be visible the next
time the incubator site is built:
1. http://incubator.apache.org/projects/index.html
Moved derby from "Currently Incubating" to "Successfully Incubated"
table.
2. http://incubator.apache.org/projects/derby.html
updated derby.cwiki with link to new website
Below is a check list I started putting together for incubator clean-up:
[ ] Request repository/karma move from incubator to new location.
[ ] Move web site from /www/incubator.apache.org/${PROJECT} to new
destination
[ ] Request redirect from old incubator URL to new
[ ] After redirect is verified working, delete web cruft from
/www/incubator.apache.org/${PROJECT}
[ ] http://incubator.apache.org/projects/index.html
Move project from "Currently Incubating" to "Successfully
Incubated" table.
[ ] http://incubator.apache.org/projects/${PROJECT}.html
update with link to new website
Is this list useful to anyone else? and is anything missing that I still
need to take care of?
thanks,
-jean
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (INCUBATOR-5) status file requirement unclear
status file requirement unclear --- Key: INCUBATOR-5 URL: http://issues.apache.org/jira/browse/INCUBATOR-5 Project: Incubator Type: Improvement Environment: all Reporter: Martin Sebor The Incubation Policy mentions two requirements for a status file: http://incubator.apache.org/incubation/Incubation_Policy.html#Ongoing+Activities%0D http://incubator.apache.org/incubation/Incubation_Policy.html#Use+of+Apache+Resources While all podlings have a status Web page, none appears to provide a STATUS file in the expected location, even though the latter is mentioned more prominently in the policy and reiterated in the weekly Incubator status report -- see below: http://mail-archives.apache.org/mod_mbox/incubator-general/200507.mbox/[EMAIL PROTECTED] It's not clear which of these two files is actually required. This is a request to clarify the policy on this question. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Request for Comment : Harmony Contribution Policy
"Roy T. Fielding" <[EMAIL PROTECTED]> wrote on 08/01/2005 06:02:34 PM: > On Aug 1, 2005, at 10:22 AM, Justin Erenkrantz wrote: > > > Furthermore, my understanding of copyright law is that you can't be > > tainted by 'reading' source code years ago and then writing a version > > independently. (In fact, the examples I've heard of are 'minutes > > apart' is legally acceptable.) Of course, patent infringement occurs > > whether you've read the code or not. FWIW, our compiler languages > > class here at UC Irvine teaches Java internals - therefore, they'd all > > be 'tainted' under this definition - which isn't actually the case. > > I agree with Justin. BTW, the two sides of the coin are copyright > and trade secret law. Copyright does not apply to things that you > may have learned in the past. I think that there is a misunderstanding as to what the requirements are for a copyright claim. If we want to get into a more complete discussion, the legal-discuss list would be more appropriate, but in short, the above posts are incorrect. Merely reading another work (in the past, even years in the past) is sufficient as a basis for a copyright claim. Basically, to successfully assert a copyright claim, you need to show 2 things . . . Access and Substantial Similarity. Access does not need to be concurrent. There have been cases where the access was MANY, MANY years prior. Jeff Staff Counsel, IBM Corporation (914)766-1757 (tie)8-826 (fax) -8160 (notes) [EMAIL PROTECTED] (internet) [EMAIL PROTECTED] (home) [EMAIL PROTECTED] (web) http://www.beff.net/
