Re: stdcxx open for business
Heidi Buelow wrote: I read somewhere that the site-publish is generated every two hours but I can't find that now. ... After it is generated and committed (see below) then it is automatically moved into production. Various steps are involved, some automated, some manual. I did find the note that we could just put our stuff on site-author and let someone else publish the site. So that's what we have done. Do I enlist someone to publish or is it automatic and if it is automatic, when could I expect to see the updates on site-publish? We notice the SVN commit messages and someone (probably me :-) will update the site when they get some free time. Later we do hope to automate that as much as is possible. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Setting up incubator pages for Oscar
Hi, I was wondering how we can setup the incubator pages to track the progress of the oscar podling. I remember working on the directory pages but I don't seem to recall who or how these pages were setup for podlings. Thanks, Alex - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting up incubator pages for Oscar
I was wondering how we can setup the incubator pages to track the progress of the oscar podling. I remember working on the directory pages but I don't seem to recall who or how these pages were setup for podlings. I just sent my usual getting started info to oscar-dev. Roy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: stdcxx open for business
Well it's ready for publishing... Some of the commit messages went to stdcxx-commits. I don't think you are on that. Heidi. -Original Message- From: David Crossley [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 20, 2005 12:16 AM To: general@incubator.apache.org Subject: Re: stdcxx open for business Heidi Buelow wrote: I read somewhere that the site-publish is generated every two hours but I can't find that now. ... After it is generated and committed (see below) then it is automatically moved into production. Various steps are involved, some automated, some manual. I did find the note that we could just put our stuff on site-author and let someone else publish the site. So that's what we have done. Do I enlist someone to publish or is it automatic and if it is automatic, when could I expect to see the updates on site-publish? We notice the SVN commit messages and someone (probably me :-) will update the site when they get some free time. Later we do hope to automate that as much as is possible. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting up incubator pages for Oscar
On Wednesday 20 July 2005 20:38, Roy T. Fielding wrote: I was wondering how we can setup the incubator pages to track the progress of the oscar podling. I remember working on the directory pages but I don't seem to recall who or how these pages were setup for podlings. I just sent my usual getting started info to oscar-dev. I decided to check out how this all works. 1. svn cp incubation-status-template.html oscar.html in the site-author/projects directory. 2. Committed that... (Not supposed to be able to do that. See below.) 3. Made a rough initial edit. 4. Committed that, so a STATUS file should now exist. Now, I went on to investigate how come I could commit, and found out that someone has forgotten to clean away graduated projects from the /x1/sv/asf-authorization, and since I am committer on Directory, I was able to do the commit above. Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[VOTE] Graduate Derby as sub-project of Apache DB
Noel said that rather than hassling the Incubator PMC members for release approval, we should just graduate! So please vote on graduating Derby to a sub-project of Apache DB. The developer community continues get the Apache Way and its diversity has increased since the last graduation vote (where it got good reports). We've added five new committers during incubation based upon their contributions, which gives us committers from three independent entities. We've performed two releases (though the latest is waiting approval from the incubator PMC :-) DB-PMC has discussed the inclusion of a sub-set of Derby PPMC members. DB-PMC has voted to accept the project (see status file) http://incubator.apache.org/projects/derby.html - My vote +1. Thanks! Dan. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Derby as sub-project of Apache DB
On Thursday 21 July 2005 02:40, Daniel John Debrunner wrote: DB-PMC has discussed the inclusion of a sub-set of Derby PPMC members. Has the Derby project engaged suitable DB PMC members as committers and PPMC members, to enhance oversight and increase cross-pollination ?? (Sorry if this has been mentioned before, but I have not followed the details of Derby.) Cheers Niclas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
SVN repository disappeared?
Did anyone else notice that the svn repository seems to have disappeared? The directory http://svn.apache.org/repos/ http://svn.apache.org/repos/ is gone. There is a newly created directory called http://svn.apache.org/repository http://svn.apache.org/repository but the stuff inside is different than what was in repos. Help? Heidi.
Re: [proposal] Oscar OSGi Project
Hi, On Sat, 2005-07-16 at 11:45 -0700, Roy T. Fielding wrote: The license to review is the one in the specification documentation, which in essence says nothing other than the fact that you are NOT indemnified against IP claims, which is standard CYA by the OSGi Alliance. It says nothing. It doesn't even provide a license to copy or make derivative work. There is zero license there, only a disclaimer. You might want to coordinate on this with Eclipse. They had similar concerns about some OSGi code. See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=90052 One of the comments in that bugs says: To be specific, OSGi now makes a clear distinction between the specification PDF document (specification) and the java source files which contain the OSGi API typed in from the specification (companion code). OSGi does not consider the companion code to be the specification and thus has agreed to license the companion code under EPL. The specification itself is available under a new specification license which freely allows distribution and implementation of the specification, but all rights to modify the specification are retained by OSGi. This is to prevent forking the specification. Hope that helps. The bug also has email addresses of some contact people if you need them for more clarifications. I am not sure if the current license on the osgi website is already this new license this comment talks about, or if they still have to update the site to clarify this. Cheers, Mark signature.asc Description: This is a digitally signed message part
Re: SVN repository disappeared?
Heidi Buelow wrote: Did anyone else notice that the svn repository seems to have disappeared? Yes, something bad seems to have happened to the SVN repos. I haven't been able to get to svn since sometime between 10 and 11 this morning (US mountain time). Here's the error I've been gettin since then: $ svn ls http://svn.apache.org/repos/asf/incubator/ svn: PROPFIND request failed on '/repos/asf/incubator' svn: Could not open the requested SVN filesystem Martin The directory http://svn.apache.org/repos/ http://svn.apache.org/repos/ is gone. There is a newly created directory called http://svn.apache.org/repository http://svn.apache.org/repository but the stuff inside is different than what was in repos. Help? Heidi. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN repository disappeared?
On Wed, 2005-07-20 at 17:04 -0600, Martin Sebor wrote: Heidi Buelow wrote: Did anyone else notice that the svn repository seems to have disappeared? Yes, something bad seems to have happened to the SVN repos. I haven't been able to get to svn since sometime between 10 and 11 this morning (US mountain time). Here's the error I've been gettin since then: $ svn ls http://svn.apache.org/repos/asf/incubator/ svn: PROPFIND request failed on '/repos/asf/incubator' svn: Could not open the requested SVN filesystem Subversion access is working fine for me (both web browsing and command-line). Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[STATUS] (incubator) Wed Jul 20 23:46:26 2005
APACHE INCUBATOR PROJECT STATUS: -*-indented-text-*-
Last modified at [$Date: 2005-01-20 01:12:13 -0500 (Thu, 20 Jan 2005) $]
Web site: http://Incubator.Apache.Org/
Wiki page: http://wiki.apache.org/incubator/
[note: the Web site is the 'official' documentation; the wiki pages
are for collaborative development, including stuff destined for the
Web site.]
Pending Issues
==
o Clearly and authoritatively document how to edit, generate,
and update the Web site (three separate functions).
o Move the stable wiki pages into the official site.
o We need to be very very clear about what it takes to be accepted
into the incubator. It should be a very low bar to leap, possibly
not much more than 'no problematic code' and the existence of a
healthy community (we don't want to become a dumping ground).
o We need to be very very clear about what it takes for a podling
to graduate from the incubator. The basic requirements obviously
include: has a home, either as part of another ASF project or as
a new top-level project of its own; needs to be a credit to the
ASF and function well in the ASF framework; ...
o Moving the bylaw documentation from the Wiki to the main site
o fix formatting of the project status pages
Resolved Issues
===
o The policy documentation does not need ratification of changes
if there seems consensus. Accordingly, the draft status of these
documents can be removed and we will use the lazy commit first,
discuss later mode common across the ASF for documentation
(http://mail-archives.apache.org/eyebrowse/[EMAIL
PROTECTED]by=threadfrom=517190)
o Coming up with a set of bylaws for the project
(http://mail-archives.apache.org/eyebrowse/[EMAIL
PROTECTED]by=threadfrom=517190)
o All projects under incubation must use a STATUS file (or a
status.xml file if the project prefers XML) that contains
information the PMC needs about the project. This file must
live at the root of the project cvs module
(http://mail-archives.apache.org/eyebrowse/[EMAIL
PROTECTED]by=threadfrom=504543)
o Projects under incubation should display appropriate disclaimers
so that it is clear that they are, indeed, under incubation
(http://mail-archives.apache.org/eyebrowse/[EMAIL
PROTECTED]by=threadfrom=504543)
The Incubation Process
==
This tries to list all the actions items that must be complete for a project
before it can graduate from the incubator. It is probably incomplete.
Identify the project to be incubated:
-- Make sure that the requested project name does not already exist
and check www.nameprotect.com to be sure that the name is not
already trademarked for an existing software product.
-- If request from an existing Apache project to adopt an external
package, then ask the Apache project for the cvs module and mail
address names.
-- If request from outside Apache to enter an existing Apache project,
then post a message to that project for them to decide on acceptance.
-- If request from anywhere to become a stand-alone PMC, then assess
the fit with the ASF, and create the lists and modules under the
incubator address/module names if accepted.
Interim responsibility:
-- Who has been identified as the mentor for the incubation?
-- Are they tracking progress in the file
incubator/projects/{project_name}/STATUS
Copyright:
-- Have the papers that transfer rights to the ASF been received?
It is only necessary to transfer rights for the package, the
core code, and any new code produced by the project.
-- Have the files been updated to reflect the new ASF copyright?
Verify distribution rights:
-- For all code included with the distribution that is not under the
Apache license, do we have the right to combine with Apache-licensed
code and redistribute?
-- Is all source code distributed by the project covered by one or more
of the following approved licenses: Apache, BSD, Artistic, MIT/X,
MIT/W3C, MPL 1.1, or something with essentially the same terms?
Establish a list of active committers:
-- Are all active committers in the STATUS file?
-- Do they have accounts on cvs.apache.org?
-- Have they submitted a contributors agreement?
Infrastructure:
-- CVS modules created and committers added to avail file?
-- Mailing lists set up and archived?
-- Problem tracking system (Bugzilla)?
-- Has the project migrated to our infrastructure?
Collaborative Development:
-- Have all of the active long-term volunteers been identified
and acknowledged as committers on the project?
-- Are there three or more independent committers?
[The legal definition of independent is long and boring, but basically
it means that there is no binding relationship between the
Re: [VOTE] Graduate Derby as sub-project of Apache DB
Niclas Hedhman wrote: Has the Derby project engaged suitable DB PMC members as committers and PPMC members, to enhance oversight and increase cross-pollination ?? (Sorry if this has been mentioned before, but I have not followed the details of Derby.) DB PMC members have been with Derby from the start and have actively been involved in its incubation. Derby has cross pollinated with other Apache projects such as Geronimo and JDO (also under incubation by the DB PMC). THe last time the issue of graduation was raised the primary concern was that the project lacked a diversity of committers having added only one from outside IBM. Since then we have added one independent, three from Sun and continue see a diversity on the dev and user lists that should lead to even more committers in the near future. I believe Derby has demonstrated Apache's community values and is ready to graduate. +1 -- Jeremy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Derby as sub-project of Apache DB
On Thursday 21 July 2005 12:42, Jeremy Boynes wrote: DB PMC members have been with Derby from the start and have actively been involved in its incubation. Derby has cross pollinated with other Apache projects such as Geronimo and JDO (also under incubation by the DB PMC). Great. +1 (non-binding) for graduation from me. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [VOTE] Graduate Derby as sub-project of Apache DB
On 7/20/05, Jeremy Boynes [EMAIL PROTECTED] wrote: I believe Derby has demonstrated Apache's community values and is ready to graduate. +1 +1 as well. I've been lurking on the various Derby lists, and am satisfied that the community gets it what it means to be an Apache project. Craig - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
