Incubator PMC vs Board as sponsor (Re: Proposal for OFBiz to Join the ASF)

2006-01-13 Thread David N. Welton
Niclas Hedhman wrote:
 On Friday 13 January 2006 04:27, David E. Jones wrote:
 
As I understand it in order to become a top level project the Board  
must be the sponsor, which is why the proposal was written that way.  
 
 
 That is a misconception. For projects targetting top-level, EITHER the Board 
 or the Incubator PMC must sponsor.
 Board doesn't like to sponsor, and do so only in exceptional cases. So the 
 Incubator PMC is the right folks to address. (And probably why you get the 
 What is this doing here? response from the Board.)

IMO this is a buglet with
http://incubator.apache.org/incubation/Incubation_Policy.html

which I filed here:

https://issues.apache.org/jira/browse/INCUBATOR-10

If you're reading that for the first time, or even if you're an ASF
member like me who hasn't dealt with incubation before, it doesn't give
you a sense for which one is the best to use.

If someone grants me the relevant SVN karma and points me to the right
checkout url, I will fix this and the other two bugs I filed as well.

-- 
David N. Welton
- http://www.dedasys.com/davidw/

Linux, Open Source Consulting
- http://www.dedasys.com/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



how to update website content (Was: Incubator PMC vs Board as sponsor)

2006-01-13 Thread David Crossley
David N. Welton wrote:
 Niclas Hedhman wrote:
  On Friday 13 January 2006 04:27, David E. Jones wrote:
  
 As I understand it in order to become a top level project the Board  
 must be the sponsor, which is why the proposal was written that way.  
  
  That is a misconception. For projects targetting top-level, EITHER the 
  Board 
  or the Incubator PMC must sponsor.
  Board doesn't like to sponsor, and do so only in exceptional cases. So the 
  Incubator PMC is the right folks to address. (And probably why you get the 
  What is this doing here? response from the Board.)
 
 IMO this is a buglet with
 http://incubator.apache.org/incubation/Incubation_Policy.html
 
 which I filed here:
 
 https://issues.apache.org/jira/browse/INCUBATOR-10
 
 If you're reading that for the first time, or even if you're an ASF
 member like me who hasn't dealt with incubation before, it doesn't give
 you a sense for which one is the best to use.
 
 If someone grants me the relevant SVN karma and points me to the right
 checkout url, I will fix this and the other two bugs I filed as well.

http://incubator.apache.org/guides/website.html

The incubator/public svn is writable by members
and pmc-chairs and also by committers on any
of the incubating projects. So pretty well everyone
can help with improving the content.

I gather that there are some parts of the website
(not sure which) that need the agreement of the
Incubator PMC.

-David

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Updated: (INCUBATOR-11) 'exitting' on Incubation_Policy.html

2006-01-13 Thread Gavin (JIRA)
 [ http://issues.apache.org/jira/browse/INCUBATOR-11?page=all ]

Gavin updated INCUBATOR-11:
---

Attachment: Incubation_Policy.html.diff

I could not find a source xml file, so edited the .html in site-author. 

Found 4 instances of exitting and replaced.

 'exitting' on Incubation_Policy.html
 

  Key: INCUBATOR-11
  URL: http://issues.apache.org/jira/browse/INCUBATOR-11
  Project: Incubator
 Type: Bug
 Reporter: David N. Welton
 Priority: Trivial
  Attachments: Incubation_Policy.html.diff

 http://incubator.apache.org/incubation/Incubation_Policy.html
 Spelling mistake: Exitting - Exiting

-- 
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]



[jira] Updated: (INCUBATOR-12) Process_Description.html navigation improvement

2006-01-13 Thread Gavin (JIRA)
 [ http://issues.apache.org/jira/browse/INCUBATOR-12?page=all ]

Gavin updated INCUBATOR-12:
---

Attachment: Process_Description.html.diff

Created a link to the Mailing Lists page in appropriate place.

 Process_Description.html navigation improvement
 ---

  Key: INCUBATOR-12
  URL: http://issues.apache.org/jira/browse/INCUBATOR-12
  Project: Incubator
 Type: Improvement
 Reporter: David N. Welton
 Priority: Minor
  Attachments: Process_Description.html.diff

 http://incubator.apache.org/incubation/Process_Description.html
 mentions a mailing lists section of this site, yet provides no link, and it 
 is not at all obvious from the left-hand navigation where that might reside.  
 A link should be provided.
 Thanks,
 Dave

-- 
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: [jira] Created: (INCUBATOR-10) Incubation_Policy.html should specify to use the Incubator PMC

2006-01-13 Thread Gav....
If somebody approves any word changes as below I can create a patch if 
required.

Gav...

- Original Message - 
From: David N. Welton (JIRA) general@incubator.apache.org
To: general@incubator.apache.org
Sent: Sunday, January 08, 2006 1:16 AM
Subject: [jira] Created: (INCUBATOR-10) Incubation_Policy.html should 
specify to use the Incubator PMC


| Incubation_Policy.html should specify to use the Incubator PMC
| --
|
| Key: INCUBATOR-10
| URL: http://issues.apache.org/jira/browse/INCUBATOR-10
| Project: Incubator
|Type: Improvement
|Reporter: David N. Welton
|Priority: Minor
|
|
| This page http://incubator.apache.org/incubation/Incubation_Policy.html
|
| says:
|
| Approval by a Sponsor will generally occur only after a vote within the 
Entity, and will require that the Entity be convinced that the Candidate is 
appropriate for Incubation. A Sponsor may be one of:
|
|* the Board of the Apache Software Foundation;
|* a Top Level Project (TLP) within the Apache Software Foundation 
(where the TLP considers the Candidate to be a suitable sub-project); or
|* the Incubator PMC.
|
| Although in practice it appears that the Incubator PMC is the preferred 
sponsor for projects that would end up a TLP.  The site could say something 
like this:
|
| Where a top level project is not an appropriate sponsor, the Incubator PMC 
is the preferred sponsor.  Requests should be sent to the general (AT) 
incubator.apache.org mailing list.
|
|
| -- 
| 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]
|
|
|
| -- 
| No virus found in this incoming message.
| Checked by AVG Free Edition.
| Version: 7.1.371 / Virus Database: 267.14.15/223 - Release Date: 6/01/2006
|
| 



-- 
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.371 / Virus Database: 267.14.17/228 - Release Date: 12/01/2006



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Apache Juice - Incubation

2006-01-13 Thread Davanum Srinivas
Dear Incubator folks,

Apache Juice was been stalled for some time because of 1 legal issue
on our side, namely the CLA from U of Memphis[1]. This was ok'ed by
legal after quite a delay, but the project lost steam.   AFAIK, all
the legal requirements are taken care of now.

There has been some discussions on security-dev and wss4j-dev [2]. We
want to explore merging juice with existing projects namely Apache XML
Security to carry on the work. Is this a valid option for us? Thoughts
please. Also what do we need in terms of process to import the code to
xml-security SVN and drop juice as a separate project.

thanks,
dims

[1] http://mail-archives.apache.org/mod_mbox/xml-juice-dev/200407.mbox/[EMAIL 
PROTECTED]
[2] http://www.mail-archive.com/security-dev@xml.apache.org/msg02758.html

--
Davanum Srinivas : http://wso2.com/blogs/

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: [jira] Updated: (INCUBATOR-12) Process_Description.html navigation improvement

2006-01-13 Thread David Crossley
Gav wrote:
 The website mentions updating the 'source html' files in site-author ( 
 http://incubator.apache.org/guides/website.html) which
 I have done for this Issue and also INCUBATOR-11, is this the preferred way 
 here or maybe us the source .xml files
 where one exists ?

That is absolutely correct. As that doc says html
are the sources. That makes it easier for people to edit
and preview, without needing to actually build.

There are a couple of source files that use xml.

Thanks for doing stuff like this. The whole site needs
a content cleanup.

-David

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Closed: (INCUBATOR-11) 'exitting' on Incubation_Policy.html

2006-01-13 Thread David Crossley (JIRA)
 [ http://issues.apache.org/jira/browse/INCUBATOR-11?page=all ]
 
David Crossley closed INCUBATOR-11:
---

Resolution: Fixed

Patch applied, thanks.

 'exitting' on Incubation_Policy.html
 

  Key: INCUBATOR-11
  URL: http://issues.apache.org/jira/browse/INCUBATOR-11
  Project: Incubator
 Type: Bug
 Reporter: David N. Welton
 Priority: Trivial
  Attachments: Incubation_Policy.html.diff

 http://incubator.apache.org/incubation/Incubation_Policy.html
 Spelling mistake: Exitting - Exiting

-- 
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]



[jira] Commented: (INCUBATOR-12) Process_Description.html navigation improvement

2006-01-13 Thread David Crossley (JIRA)
[ 
http://issues.apache.org/jira/browse/INCUBATOR-12?page=comments#action_12362703 
] 

David Crossley commented on INCUBATOR-12:
-

Thanks anyway, Gavin. However that is not the correct patch. The Learn area 
is a special part of the Incubator website that was to create ASF-wide 
documentation. It has not been attended to. There is docs at the top-level 
www.apache.org that i will link to.

I think that DavidW is also referring to the difficulty in finding the info 
about the Incubator mailing lists.

 Process_Description.html navigation improvement
 ---

  Key: INCUBATOR-12
  URL: http://issues.apache.org/jira/browse/INCUBATOR-12
  Project: Incubator
 Type: Improvement
 Reporter: David N. Welton
 Priority: Minor
  Attachments: Process_Description.html.diff

 http://incubator.apache.org/incubation/Process_Description.html
 mentions a mailing lists section of this site, yet provides no link, and it 
 is not at all obvious from the left-hand navigation where that might reside.  
 A link should be provided.
 Thanks,
 Dave

-- 
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]



[docs] formatting of source files (Was: r368916)

2006-01-13 Thread David Crossley
The source html documents for the Incubator website have paragraphs
that are one long line. This makes it virtually impossible to
read the diffs (see example below).

Of course this is not the concern of Forrest.

We need to use some sort of html tidy program to fix the
whole of the site-author/ tree in one pass.

I am reluctant to do that because there is the intention
to move to some other format for the website sources
and document generation system. However there seem to
be delays.

-David

 Author: crossley
 Date: Fri Jan 13 15:21:25 2006
 New Revision: 368916
 
 URL: http://svn.apache.org/viewcvs?rev=368916view=rev
 Log:
 Spelling mistake: Exitting - Exiting
 Issue: INCUBATOR-11
 Contributed by: Gavin
 
 Pity about the long paragraphs in the original source.
 The diffs are obscured.
 
 Modified:
 incubator/public/trunk/site-author/incubation/Incubation_Policy.html
 
 Modified: incubator/public/trunk/site-author/incubation/Incubation_Policy.html
 URL: 
 http://svn.apache.org/viewcvs/incubator/public/trunk/site-author/incubation/Incubation_Policy.html?rev=368916r1=368915r2=368916view=diff
 ==
 --- incubator/public/trunk/site-author/incubation/Incubation_Policy.html 
 (original)
 +++ incubator/public/trunk/site-author/incubation/Incubation_Policy.html Fri 
 Jan 13 15:21:25 2006
 @@ -115,7 +115,7 @@
  lithat the Podling continue in Incubation; or /li
  lithat the Podling be escalated out of the Incubator. /li
  /ul
 -pTermination and Escalation are discussed in more detail in section 
 Exitting the Incubator. /p
 +pTermination and Escalation are discussed in more detail in section 
 Exiting the Incubator. /p
  h2Disputing an Assessment#13;
  /h2
  pIf the Podling or Mentor disagree with an assessment, they MAY request 
 the Incubator PMC review the report.  Such a request MUST include a details 
 of what the Podling and/or Mentor is disputing, and their reasons for doing 
 so. /p
 @@ -192,8 +192,8 @@
   /p
  pPeople using Maven, ForrestBot, or any other tool still have to address 
 the SVN publishing requirement that the infrastructure team has laid out.  If 
 that is done, then we just run svn update in that directory to load the 
 site from SVN. /p
  pThe Mentors MUST add the information to the project incubation status 
 file, to describe the SVN module and the directory which holds the published 
 site. /p
 -h1Exitting the Incubator/h1
 -pThis section describes the requirements and process for exitting the 
 Incubator. /p
 +h1Exiting the Incubator/h1
 +pThis section describes the requirements and process for exiting the 
 Incubator. /p
  h2Minimum Exit Requirements/h2
  pPrior to escalation to the ASF, a Podling needs to show that : /p
  ul
 @@ -264,9 +264,9 @@
  h2Termination of a Podling/h2
  pIf you receive a recommendation for termination then you have a problem.  
 Chances are that there are either legal or structural problems with your 
 project that in the opinion of the Incubator PMC are not resolvable within a 
 reasonable time frame.  A termination decision is basically time to close 
 down the project. However, you do have the right to appeal a termination 
 decision with the Board of Directors and/or your Sponsor.  You should be 
 aware that several Members of the Board are also Members of the Incubator PMC 
 and as such, an appeal is unlikely to be successful.  /p
  h2Migration as a Top Level Project/h2
 -pIn cases where a Podling has successfully completed Incubation, and is 
 exitting the Incubator to become a Top Level Project, the Incubator PMC SHALL 
 provide a recommendation to the board that the Podling is ready to escalate.  
 The recommendation SHALL include a draft resolution for the board to vote on. 
 /p
 +pIn cases where a Podling has successfully completed Incubation, and is 
 exiting the Incubator to become a Top Level Project, the Incubator PMC SHALL 
 provide a recommendation to the board that the Podling is ready to escalate.  
 The recommendation SHALL include a draft resolution for the board to vote on. 
 /p
  h2Migration as a sub-project/h2
 -pIn cases where a Podling has successfully completed Incubation, and is 
 exitting the Incubator to become a sub-project within an already existing Top 
 Level Project, the Incubator PMC SHALL provide a recommendation to the TLP 
 that the Podling is ready to escalate. /p
 +pIn cases where a Podling has successfully completed Incubation, and is 
 exiting the Incubator to become a sub-project within an already existing Top 
 Level Project, the Incubator PMC SHALL provide a recommendation to the TLP 
 that the Podling is ready to escalate. /p
  h2Post-Graduation Check List/h2
  p
  The list below summarizes steps a project needs to perform after 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]


[jira] Commented: (INCUBATOR-12) Process_Description.html navigation improvement

2006-01-13 Thread David Crossley (JIRA)
[ 
http://issues.apache.org/jira/browse/INCUBATOR-12?page=comments#action_12362707 
] 

David Crossley commented on INCUBATOR-12:
-

Still not happy with it, but svn r368950 improves the discovery of relevant 
mailing lists. The document was referring to a yet-to-be-written section of 
that Process_Description doc. Dunno, so referred to howtoparticipate.html 
instead.

The other aspect of this issue is that the left-hand navigation needs 
improvement in general. So still open.

Also the issue title shows that the whole document needs review to ensure that 
all links are correct and up-to-date, e.g. some point to a very old ASF Wiki.

 Process_Description.html navigation improvement
 ---

  Key: INCUBATOR-12
  URL: http://issues.apache.org/jira/browse/INCUBATOR-12
  Project: Incubator
 Type: Improvement
 Reporter: David N. Welton
 Priority: Minor
  Attachments: Process_Description.html.diff

 http://incubator.apache.org/incubation/Process_Description.html
 mentions a mailing lists section of this site, yet provides no link, and it 
 is not at all obvious from the left-hand navigation where that might reside.  
 A link should be provided.
 Thanks,
 Dave

-- 
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]