On 3/18/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
> Matt Hogstrom wrote:
> > The conversation on OpenJPA has been quiet for about a week so I was
> > wondering if there are outstanding issues that need to be resolved or
> > this could be moved to a vote to accept the project and what the nex
Matt Hogstrom wrote:
The conversation on OpenJPA has been quiet for about a week so I was
wondering if there are outstanding issues that need to be resolved or
this could be moved to a vote to accept the project and what the next
steps are. I'm kind of excited to get it going.
Geir, oh might
Who calls the vote? I'd be happy to do it but don't want to be presumptious :)
Noel J. Bergman wrote:
The conversation on OpenJPA has been quiet for about a week
Reminder for those who want to review:
http://mail-archives.apache.org/mod_mbox/incubator-general/200603.mbox/%3c7D
[EMAIL PROTECT
> The conversation on OpenJPA has been quiet for about a week
Reminder for those who want to review:
http://mail-archives.apache.org/mod_mbox/incubator-general/200603.mbox/%3c7D
[EMAIL PROTECTED]
> so I was wondering if there are outstanding issues that need
> to be resolved or this could be move
The conversation on OpenJPA has been quiet for about a week so I was wondering
if there are outstanding issues that need to be resolved or this could be moved
to a vote to accept the project and what the next steps are. I'm kind of
excited to get it going.
Geir, oh mighty mentor from the moun
On Mar 10, 2006, at 8:58 PM, Niclas Hedhman wrote:
On Saturday 11 March 2006 03:21, Rodent of Unusual Size wrote:
Which is a really long-winded way of saying: At graduation,
maybe it's worthwhile to see whether the podling committers
actually earned any Apache merit.
Agree. That would also a
Niclas Hedhman wrote:
On Saturday 11 March 2006 03:21, Rodent of Unusual Size wrote:
Which is a really long-winded way of saying: At graduation,
maybe it's worthwhile to see whether the podling committers
actually earned any Apache merit.
Agree. That would also allow for a lot lower bar at t
On Saturday 11 March 2006 04:00, Thomas Dudziak wrote:
> For instance, both Cayenne and OpenJPA
> wanted to be sponsored by the Incubator PMC and go TLP immediately
> even though there is already know-how in Apache in this field in the
> DB project so that at least in my opinion, a sponsoring by th
On Saturday 11 March 2006 03:21, Rodent of Unusual Size wrote:
> Which is a really long-winded way of saying: At graduation,
> maybe it's worthwhile to see whether the podling committers
> actually earned any Apache merit.
Agree. That would also allow for a lot lower bar at the start of podlings
Hola,
> > O, I don't know. Since commit access in the podling frequently
> > results in commit access in the TLP, I think it might be reasonable
> > at graduation to take a look at the records of the podling's
> > committers. Commit access in a TLP is earned -- period. Someone
> > who's on a po
Rodent of Unusual Size wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geir Magnusson Jr wrote:
However, I absolutely don't believe that at graduation we need to
closely examine the assets of the project to make some judgment about
individuals as committers.
O, I don't know. Since co
On 3/10/06, Rodent of Unusual Size <[EMAIL PROTECTED]> wrote:
> Thomas Dudziak wrote:
> > Mhmm, I have one major problem with this (as much as with Cayenne),
> > and this is that IMO we (will) have too much ORM engines in Apache
> > (with JPA and Cayenne it will be 6 or 7 ?) with little to no
> >
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Craig L Russell wrote:
>
> I think we might have a better chance at unifying these disparate
> code bases if they are all in one place.
Whose goal is that?
- --
#kenP-)}
Ken Coar, Sanagendamgagwedweinini http://Ken.Coar.Org/
Author, developer
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thomas Dudziak wrote:
> Mhmm, I have one major problem with this (as much as with Cayenne),
> and this is that IMO we (will) have too much ORM engines in Apache
> (with JPA and Cayenne it will be 6 or 7 ?) with little to no
> cooperation (esp. on the c
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Geir Magnusson Jr wrote:
>
> However, I absolutely don't believe that at graduation we need to
> closely examine the assets of the project to make some judgment about
> individuals as committers.
O, I don't know. Since commit access in the podling
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Daniel John Debrunner wrote:
>
> I've seen this comment a couple of times in the last week or so, but I
> don't really understand what it's trying to say.
>
> What makes an Apache project "umbrella-ish"?
One definition: a top-level project that has
Hola,
I don't agree with everything you said, but I have faith. So I'm
going to let go of this topic for now (as I've said along, I didn't
and won't -1 anything at this stage), but I sure will be looking for
great test coverage and documentation from OpenJPA ;) Hopefully
something we can cite as
Yoav Shapira wrote:
So we agree that we allow the current proposed committer list as-is,
but when we look at graduation from the incubator we examine test case
and documentation as well as the product source code itself, because
by bringing these people in as committers through the incubator, t
On Thursday 09 March 2006 06:02, robert burrell donkin wrote:
> the current favourite candidate is a
> more federationish structure with more limited legal duties.
yes, flatten the legal aspects, and allow for orthogonal cross-pollination.
IOW, not "partOf" but "associatedWith", where the associa
Hola,
Brett said:
> Of course, they still have to earn their stripes in the same way -
> consistent contribution that shows they care about the project.
>
> > If Joe Q. Random emailed us saying he thinks [some currently in
> > incubation project] is great and he's a technical writer and would
> >
Hi Guys,
Isn't the whole point of incubation community? We want the community
and we want to grow it while in incubation.
Good doc and QA people will go just as far as good coders in building
a user community (perhaps even further) while making it possible for
the coders to build more cod
On 3/8/06, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> Thomas Dudziak wrote:
>
> > I have one major problem with this (as much as with Cayenne),
> > and this is that IMO we (will) have too much ORM engines in
> > Apache
>
> Not necesarily a bad thing.
Sure. Perhaps I'm being a bit too anti-sourc
On 3/9/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:
> > it's easy to get good open source coders: it's much harder to find
> > good documentors who are willing to contribute to open source
> > projects. demand for good documentation is always high but supply is
> > typically low.
++1. We need to be
Hola,
> > I also suppose we can always review the status of documentation and
> > test cases at the end of incubation, see who did what, and accordingly
> > adjust the commiter list during incubator graduation?
>
> isn't this really an issue about the bootstrapping committer lists?
Yes. The thi
On 3/8/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:
> Hola,
>
> > it's easy to get good open source coders: it's much harder to find
> > good documentors who are willing to contribute to open source
> > projects. demand for good documentation is always high but supply is
> > typically low. i'm willi
On 3/8/06, Thomas Dudziak <[EMAIL PROTECTED]> wrote:
> On 3/8/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
>
> > Is duplication really that bad? So long as the communities are vibrant,
> > why should we care? Also, have you factored in different requirements
> > and different implementation str
Hola,
> it's easy to get good open source coders: it's much harder to find
> good documentors who are willing to contribute to open source
> projects. demand for good documentation is always high but supply is
> typically low. i'm willing to cut good documentors much more slack
> than coders.
Hyp
On 3/8/06, Yoav Shapira <[EMAIL PROTECTED]> wrote:
> > Both QA and docs as proposed committers means to me that this project
> > already has mature processes in place that will be good for the
> > community.
>
> You're more trusting than I am. I still feel like commit access is
> something to be
Hola,
> I like having QA and docs as committers on projects. QA should be
> putting test cases into the code base
Yes, but
> and the only alternative is to have a separate project for QA.
No. They can submit test cases via JIRA.
> Similarly, docs are a very important part of a project and hav
Hi Yoav,
On Mar 7, 2006, at 5:50 PM, Yoav Shapira wrote:
:Core Developers:
Fourteen of the initial committers are BEA employees. One of those
is a
committer on the Apache JDO project. We anticipate that five of these
fourteen will be involved in the core code development, and the other
nine
Thomas Dudziak wrote:
> I have one major problem with this (as much as with Cayenne),
> and this is that IMO we (will) have too much ORM engines in
> Apache
Not necesarily a bad thing.
> [...] with little to no cooperation (esp. on the code level)
> between the ones already here.
The solution i
On 3/8/06, Alan D. Cabrera <[EMAIL PROTECTED]> wrote:
> Is duplication really that bad? So long as the communities are vibrant,
> why should we care? Also, have you factored in different requirements
> and different implementation strategies for the projects in your list of
> duplications? I've
Thomas Dudziak wrote:
Mhmm, I have one major problem with this (as much as with Cayenne),
and this is that IMO we (will) have too much ORM engines in Apache
(with JPA and Cayenne it will be 6 or 7 ?) with little to no
cooperation (esp. on the code level) between the ones already here. So
in short
On 3/8/06, Craig L Russell <[EMAIL PROTECTED]> wrote:
> I think we might have a better chance at unifying these disparate
> code bases if they are all in one place. And I think that DB might be
> just the place.
>
> For the record, the Apache JDO project has no ORM engine. It has the
> testing inf
Hi Tom,
I think we might have a better chance at unifying these disparate
code bases if they are all in one place. And I think that DB might be
just the place.
For the record, the Apache JDO project has no ORM engine. It has the
testing infrastructure for ORM and it has the JDO specificat
Mhmm, I have one major problem with this (as much as with Cayenne),
and this is that IMO we (will) have too much ORM engines in Apache
(with JPA and Cayenne it will be 6 or 7 ?) with little to no
cooperation (esp. on the code level) between the ones already here. So
in short, there is no focus and
Patrick Linskey wrote:
> > Would it make sense for this to go in DB or Jakarta, then?
> Certainly Jakarta's Java-catch-all nature makes it a natural place for
> Open JPA. DB makes some sense too, given that Open JPA is about talking
> to databases.
Jakarta's "java-catch-all" nature is a major rea
robert burrell donkin wrote:
> the only caveat being DB is feeling a little bit umbrella-ish these days.
I've seen this comment a couple of times in the last week or so, but I
don't really understand what it's trying to say.
What makes an Apache project "umbrella-ish"?
How does "umbrella-ish" r
On 3/8/06, Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
>
>
>
> Yoav Shapira wrote:
> > Hola,
> > A couple of questions:
> >
> >> :Core Developers:
> >> Fourteen of the initial committers are BEA employees. One of those is a
> >> committer on the Apache JDO project. We anticipate that five of these
On 3/8/06, Jacek Laskowski <[EMAIL PROTECTED]> wrote:
>
> 2006/3/8, Patrick Linskey <[EMAIL PROTECTED]>:
> > Hi,
> >
> > Below is a proposal to incubate an Open JPA project at Apache. I've also
> > posted this at http://wiki.apache.org/incubator/OpenJPAProposal.
>
> Hi Patrick,
>
> May I be include
2006/3/8, Patrick Linskey <[EMAIL PROTECTED]>:
> Hi,
>
> Below is a proposal to incubate an Open JPA project at Apache. I've also
> posted this at http://wiki.apache.org/incubator/OpenJPAProposal.
Hi Patrick,
May I be included in the initial committers section? I'd love to
contribute to this proj
Yoav Shapira wrote:
Hola,
A couple of questions:
:Core Developers:
Fourteen of the initial committers are BEA employees. One of those is a
committer on the Apache JDO project. We anticipate that five of these
fourteen will be involved in the core code development, and the other
nine will be i
Awesome! This is great news - welcome! :)
James
On 3/8/06, Patrick Linskey <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Below is a proposal to incubate an Open JPA project at Apache. I've also
> posted this at http://wiki.apache.org/incubator/OpenJPAProposal.
>
> Much thanks to Eddie O'Neil, Geir Magnu
See comments inline.
> > :Core Developers:
> > Fourteen of the initial committers are BEA employees. One
> of those is
> > a committer on the Apache JDO project. We anticipate that five of
> > these fourteen will be involved in the core code
> development, and the
> > other nine will be invol
Hola,
A couple of questions:
> :Core Developers:
> Fourteen of the initial committers are BEA employees. One of those is a
> committer on the Apache JDO project. We anticipate that five of these
> fourteen will be involved in the core code development, and the other
> nine will be involved in docu
45 matches
Mail list logo
