Thorsten Scherler wrote:
This is a proposal to enter the incubator.
See http://wiki.apache.org/incubator/DroidsProposal for the most
up-to-date version.
I'm happy to mentor this proposal.
Ross
-
To unsubscribe, e-mail:
On Tue, 2008-09-23 at 10:29 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
This is a proposal to enter the incubator.
See http://wiki.apache.org/incubator/DroidsProposal for the most
up-to-date version.
I'm happy to mentor this proposal.
:)
Thank you very much Ross, I added
I'm happy to mentor as well.
I've added my name to the proposal.
Paul
On Tue, Sep 23, 2008 at 11:08 AM, Thorsten Scherler
[EMAIL PROTECTED] wrote:
On Tue, 2008-09-23 at 10:29 +0100, Ross Gardler wrote:
Thorsten Scherler wrote:
This is a proposal to enter the incubator.
See
On Tue, Sep 23, 2008 at 1:50 PM, [EMAIL PROTECTED] wrote:
we would be glad to welcome you as a mentor for catacomb incubation
process! Your idea to fold catacomb into the HTTP
Server Project is realy nice, maybe later in the incubation process
we could start a discussion with someone from the
So, I'm new to championing (but read the brief docs on the proposal
guide). One question I have is related to the Sponsoring PMC. The
proposal indicates two Sponsoring Entities. When does that need to be
resolved? Or is this going to be a TLP? Or, does it not matter?
-Grant
On Sep
Grant
My view is that at this stage it doesn't matter. I think it helps that
there are two communities that have an active interest in the proposed
podling. Over time the podling can either verge towards one or the
other project or target becoming a TLP.
Paul
On Tue, Sep 23, 2008 at 2:53 PM,
Please vote on accepting Olio into incubation.
The proposal can be found at: http://wiki.apache.org/incubator/OlioProposal
[This proposal was formerly known as Web20Kit]
The text of the proposal:
OlioProposal
Abstract
Apache Olio is a web 2.0 toolkit to help developers evaluate the
Hi All,
Some of you with long memories may recall previous threads about project
diversity.
At the end of one such debate, I put forward some ideas about what items
might benefit from some good practice guidelines (see below).
My special interest is Qpid, as I'll happy submit, and the
+1.
A release is a release is a release. If we are concerned about projects
staying in the incubator, then let's ban them from releasing anymore.
Or, say, only max five releases during incubation. But once a release is
done under the ASL, there's not really much we can do to stop its onward
+1 (binding)
Note: I updated the proposal on the Wiki with my normal e-mail account
([EMAIL PROTECTED]) instead of my work e-mail ([EMAIL PROTECTED])
since my mentoring of this project is unrelated to any aspect of my
work responsibilities).
On Sep 23, 2008, at 10:33 AM, Craig L
Olio sounds good, but there's nothing related with Java, Web, frameworks or
anything else... (or, is just me who couldn't find any information about
this word?)
So, because of the lack of co-relation between Olio and Java Webkits, I
found that there's an word which could fit better: Jawi
By the way, I forgot to mention that Jawi has everything to do with Java (the
Island... @ Malaysia).
Quoting Wikipedia (http://en.wikipedia.org/wiki/Jawi,_Penang):
Jawi is a town on the mainland side of Penang, Malaysia.
And for those who can't go to Wikipedia to check what Jawi is, here is
No longer any known fluent speakers
Perhaps we should have a COBOL implementation, then. :)
On Tue, Sep 23, 2008 at 1:58 PM, Bruno Borges [EMAIL PROTECTED] wrote:
By the way, I forgot to mention that Jawi has everything to do with Java (the
Island... @ Malaysia).
Quoting Wikipedia
Why not? :-)
You could write an web application with COBOL for .NET ... or not. :-)
But still, the part about the Jawi language is just for curiosity.
jwcarman wrote:
No longer any known fluent speakers
Perhaps we should have a COBOL implementation, then. :)
On Tue, Sep 23, 2008
On Tue, 2008-09-23 at 12:11 +0100, Paul Fremantle wrote:
I'm happy to mentor as well.
I've added my name to the proposal.
:)
Thank you very much Paul.
salu2
Paul
On Tue, Sep 23, 2008 at 11:08 AM, Thorsten Scherler
[EMAIL PROTECTED] wrote:
On Tue, 2008-09-23 at 10:29 +0100, Ross
So we had a vote and there were plenty of binding votes for incubation
([VOTE RESULT] -
http://mail-archives.apache.org/mod_mbox/incubator-general/200809.mbox/%3CF7
[EMAIL PROTECTED] )
So now what? Is there supposed to be an acknowledgement by the PMC?
According to the bootstrap section of the
Hmm - I'm not sure about this. Introducing the 'J' letter will give a
Java connotation to the whole thing. The proposed PHP and Rails
implementations will have no Java components in them. I'd rather stick
with a more generic name.
Shanti
Bruno Borges wrote:
Olio sounds good, but there's
On Mon, Sep 22, 2008 at 1:58 AM, David Crossley [EMAIL PROTECTED] wrote:
Today i wanted a list of all projects that are
currently in incubation. However that is not easy.
The two main places are:
[1] http://incubator.apache.org/projects/
[2]
On Mon, Sep 22, 2008 at 1:58 AM, David Crossley [EMAIL PROTECTED] wrote:
Today i wanted a list of all projects that are
currently in incubation. However that is not easy.
The two main places are:
[1] http://incubator.apache.org/projects/
[2]
Jukka Zitting wrote:
[ ] +1 Yes, allow extra release distribution channels like the central
Maven repository
[ ] -1 No, keep the current policy
+1 All releases by ASF PMC's should be equal. If the Incubator PMC
isn't confident of a release then it shouldn't release it. The release
process
On Tue, Sep 23, 2008 at 3:15 PM, Doug Cutting [EMAIL PROTECTED] wrote:
Jukka Zitting wrote:
[ ] +1 Yes, allow extra release distribution channels like the central
Maven repository
[ ] -1 No, keep the current policy
+1 All releases by ASF PMC's should be equal. If the Incubator PMC isn't
Luciano Resende wrote:
Please go ahead and submit CLA's and CCLA's.
Also, work with your mentors and create the necessary JIRAs to create
the new podling infrastructure resources. See some examples in [1]
Also, item 7 is very important, but looks like Etch is already in the
schedule [2]
+1 (non-binding)
I've informed the Wicket team about this incubator request and there
is interest in providing a wicket-based implementation (wicket along
with differing ORM technologies of course, like JPA and Hibernate; the
way I envision it, we'll use profiles in maven to turn on/off
different
I think incubating projects should go through phases. The first
phase is to make sure all IP concerns are cleared up. The second
phase is where the project exhibits that it gets the Apache way of
doing business by doing some internal-only releases (this is where
package names would change and
On Tue, Sep 23, 2008 at 11:45 PM, Marnie McCormack
[EMAIL PROTECTED] wrote:
Hi All,
Some of you with long memories may recall previous threads about project
diversity.
At the end of one such debate, I put forward some ideas about what items
might benefit from some good practice guidelines
On Tue, Sep 23, 2008 at 9:59 PM, Paul Fremantle [EMAIL PROTECTED] wrote:
Grant
My view is that at this stage it doesn't matter. I think it helps that
there are two communities that have an active interest in the proposed
podling. Over time the podling can either verge towards one or the
That sounds great ! The goal of the project is certainly to encourage
implementations using different frameworks. What may make sense is for
interested folks to first evaluate the current application
implementations (unfortunately we don't have any docs yet - we're
working on it) and if it
Jukka Zitting wrote:
Please vote on accepting or rejecting this policy change! This
majority vote is open for a week and only votes from the Incubator PMC
members are binding.
Just as a point of reference, extending a vote for a given period of time
is a good thing to accommodate all input.
Set up the Etch Podling
---
Key: INCUBATOR-83
URL: https://issues.apache.org/jira/browse/INCUBATOR-83
Project: Incubator
Issue Type: Task
Reporter: Niclas Hedhman
The Etch podling has been approved to enter
[
https://issues.apache.org/jira/browse/INCUBATOR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12634007#action_12634007
]
Niclas Hedhman commented on INCUBATOR-83:
-
James Dixon quotes some website
Create Etch project status page.
Key: INCUBATOR-84
URL: https://issues.apache.org/jira/browse/INCUBATOR-84
Project: Incubator
Issue Type: Sub-task
Reporter: Niclas Hedhman
Every Podling has a
Request Mailing lists from INFRA
Key: INCUBATOR-85
URL: https://issues.apache.org/jira/browse/INCUBATOR-85
Project: Incubator
Issue Type: Sub-task
Reporter: Niclas Hedhman
--
This message is
Request SVN from INFRA
--
Key: INCUBATOR-86
URL: https://issues.apache.org/jira/browse/INCUBATOR-86
Project: Incubator
Issue Type: Sub-task
Reporter: Niclas Hedhman
Joe has expressed that the SVN directory
Submission of ICLAs and CCLAs for initial committers
Key: INCUBATOR-87
URL: https://issues.apache.org/jira/browse/INCUBATOR-87
Project: Incubator
Issue Type: Sub-task
Add podling to reporting schedule
-
Key: INCUBATOR-88
URL: https://issues.apache.org/jira/browse/INCUBATOR-88
Project: Incubator
Issue Type: Sub-task
Reporter: Niclas Hedhman
New podlings report
[
https://issues.apache.org/jira/browse/INCUBATOR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated INCUBATOR-84:
Description: Every Podling has a project STATUS page that tracks important
issues. The
Update Incubator Navigation to include Etch podling
---
Key: INCUBATOR-89
URL: https://issues.apache.org/jira/browse/INCUBATOR-89
Project: Incubator
Issue Type: Sub-task
Reporter:
Create a Etch category in JIRA Incubator project
Key: INCUBATOR-90
URL: https://issues.apache.org/jira/browse/INCUBATOR-90
Project: Incubator
Issue Type: Sub-task
Reporter: Niclas
Request User accounts from INFRA
Key: INCUBATOR-91
URL: https://issues.apache.org/jira/browse/INCUBATOR-91
Project: Incubator
Issue Type: Sub-task
Reporter: Niclas Hedhman
Once the CLAs are
On Wed, Sep 24, 2008 at 3:04 AM, James Dixson [EMAIL PROTECTED] wrote:
So we had a vote and there were plenty of binding votes for incubation
([VOTE RESULT] -
http://mail-archives.apache.org/mod_mbox/incubator-general/200809.mbox/%3CF7
[EMAIL PROTECTED] )
So now what? Is there supposed to
[
https://issues.apache.org/jira/browse/INCUBATOR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated INCUBATOR-83:
Description:
The Etch podling has been approved to enter Incubation. We need to go
[
https://issues.apache.org/jira/browse/INCUBATOR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman reassigned INCUBATOR-84:
---
Assignee: Niclas Hedhman
Create Etch project status page.
[
https://issues.apache.org/jira/browse/INCUBATOR-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12634013#action_12634013
]
niclas edited comment on INCUBATOR-87 at 9/23/08 9:41 PM:
[
https://issues.apache.org/jira/browse/INCUBATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman updated INCUBATOR-90:
Summary: Create a Etch project in JIRA under Incubator category (was:
Create a Etch
Add Etch-Notification scheme in JIRA
Key: INCUBATOR-92
URL: https://issues.apache.org/jira/browse/INCUBATOR-92
Project: Incubator
Issue Type: Sub-task
Reporter: Niclas Hedhman
Once the
[
https://issues.apache.org/jira/browse/INCUBATOR-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman resolved INCUBATOR-90.
-
Resolution: Fixed
Create a Etch project in JIRA under Incubator category
On Mon, 2008-09-22 at 13:54 +0100, sebb wrote:
On 22/09/2008, Thomas Fischer [EMAIL PROTECTED] wrote:
I'd reckon that we all now agree that the tomcat jars can be included.
Assuming that they have not included the jars incorrectly.
I will check that the jars in question
Hi James,
It's great that Wicket has an interest in Olio. It's probably too late
to update the wiki page, but folks reading this thread will see your
comments.
I'd encourage you to start working on the Wicket impl during incubation.
Hopefully once the code arrives it will be a bit more
On Mon, 2008-09-22 at 13:54 +0100, sebb wrote:
It's a pity that the Tomcat jars don't contain proper manifests + N
L files; I'll see about raising that with the Tomcat developers.
Huh, what?
On my freshly downloaded apache tomcat 5.5.27, the servlet API contains
Specification-Title: Java
[
https://issues.apache.org/jira/browse/INCUBATOR-88?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman resolved INCUBATOR-88.
-
Resolution: Fixed
Add podling to reporting schedule
[
https://issues.apache.org/jira/browse/INCUBATOR-84?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Niclas Hedhman resolved INCUBATOR-84.
-
Resolution: Fixed
Create Etch project status page.
Gang,
Sorry, I didn't realize that SubTasks would still go to the general@ list...
Hmmm...
As these tasks will be worked on, anyone got a good clue how to avoid
further notification to [EMAIL PROTECTED] ?
Cheers
Niclas
On Mon, 2008-09-22 at 09:34 -0400, Hiram Chirino wrote:
The only reason I suggested including the sigs in the source distro is
because a source build like Apache ServiceMix depends on hundreds of
third party dependencies.. so an end user would need to end up
Yes. Now you are getting closer.
On Mon, 2008-09-22 at 13:42 -0400, Hiram Chirino wrote:
On Mon, Sep 22, 2008 at 10:12 AM, sebb [EMAIL PROTECTED] wrote:
On 22/09/2008, Hiram Chirino [EMAIL PROTECTED] wrote:
The only reason I suggested including the sigs in the source distro is
because a source build like Apache ServiceMix
On Wed, Sep 24, 2008 at 1:20 PM, Henning Schmiedehausen
[EMAIL PROTECTED]wrote:
I enjoy your scenarios...
And again, there is no high nineties security. Your solution is either
secure or it is not.
For accuracy; This is not true either. AFAIK, no security solution is
totally secure. You will
Henning Schmiedehausen wrote:
How do you validate that the pub key presented to you is genuine?
Every project worth it's salt has a www.apache.org/dist/{tlp}/KEYS
file which contain that project's contributors signatures, countersigned
or not. Ideally, they are extensively countersigned.
Hi,
On Fri, Sep 19, 2008 at 6:36 AM, Matt Hogstrom [EMAIL PROTECTED] wrote:
...Please indicate your
preference for accepting VCL to the Incubator...
+1
I revert my previous -1 as 3 mentors are now listed at
http://wiki.apache.org/incubator/VCLProposal:
Alan Cabrera ([EMAIL PROTECTED])
So you assume that that www.apache.org can not be hacked? What if a
signing key *IS* in KEYS but not signed by anyone (because the developer
has never attended an Apache key signing event)?
Ciao
Henning
On Wed, 2008-09-24 at 00:36 -0500, William A. Rowe, Jr. wrote:
58 matches
Mail list logo