Re: How strict should podling release reviews be?

[ant elder]

On 9/28/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
>
> On Friday 28 September 2007 05:12, Yoav Shapira wrote:
>
> > Personally, that's my take on it, and what I've done historically.
>
> I agree with Yoav, but would like to add that I personally have different
> standards for different podlings, i.e.
>
> - The sooner one can expect graduation -> higher bar.
> - Projects with many existing ASFers in it -> higher bar.
> - Projects with high visibility outside Incubator, such as
>some ws.apache.org sponsored ones -> higher bar.
>
> One problem we are facing is that we are unable to track the "delta" of
> issues
> from one release to the next. If we could, then things would be so much
> easier.
> And don't forget, many projects are aiming for one perfect release to
> graduate...
>
> I think the end result of "rather strict than lenient" improves ASF legal
> quality over time, as these concerns will "rub off" on less than perfect
> reviews in other projects through the participation of individuals.
>
>
> Cheers
> Niclas


It sounds reasonable to make part of the graduation criteria being able to
demonstrate some competence in making releases, and thats already on the
graduation checklist in the Incubator policy and graduation guide.  I know
there's no simple way to keep track of  all the issues over all the releases
but that could be part of the review required when deciding how to vote on a
graduation proposal - trawling through the mailing list to see how their
releases went. So couldn't the decision on whether or not to respin a
release still be left up to the the podling anyway? If they're thinking
about graduation and its important to them to be able to demonstrate a
perfect release let them choose to respin themselves.

I'm less keen on having different standards for different projects. One of
the difficulties for incubating projects is finding out about all the
release requirements. One way i've found to do that is by looking at what
other releases do but when the same issues aren't flagged for some releases
it can be quite confusing what the actual requirements are.

Making most issues non-blocking could actually improve reviews as in some
cases it could be easier to mention an issue it if its not going to force a
respin.

Anyway, so i'm thinking more of a benevolent educator than traffic warden
style reviewer role.

   ...ant

Re: How strict should podling release reviews be?

[ant elder]

On 9/28/07, Niclas Hedhman <[EMAIL PROTECTED]> wrote:
>
> On Friday 28 September 2007 16:16, Bertrand Delacretaz wrote:
> > IMHO the incubator PMC doesn't care much about technical issues in
> > podling releases, at least for early releases.
>
> This is an important observation. The reviewers has no opportunity to
> figure
> out if the release at all work. That is up to the Podling, and AFAIA
> concerned, the technical quality can be non-existent.
> IMHO, the mentors are responsible together with the PPMC to bring the
> technical quality to a level expected from ASF projects. But I feel it is
> at
> that group's discretion.
> AFAIR, technical quality hasn't been a problem in the past for
> graduations.


Yes, and there is some quality expectations for real (non-incubating) Apache
releases so Incubator release reviews help podlings learn about those, past
review discussions have brought up various non-legal aspects, for example
consistent artifact naming, distributions not unzipping to the current
folder etc.

   ...ant

Re: How strict should podling release reviews be?

[ant elder]

On 9/28/07, Guillaume Nodet <[EMAIL PROTECTED]> wrote:
>
> On 9/28/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
> >
> > What we care about is that podlings get the "legal stuff" right, and
> > letting releases out without this being ok is not an option, due to
> > potential legal risks.
>
> I thought projects in incubator were not endorsed by the ASF, hence
> the ASF could not be responsible for the legal stuff in podling
> releases...  Did I miss something here ?


This is exactly the question i'm trying to clarify. The policy at
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases says:

- No release made by a Podling will be endorsed by the ASF
- (releases) SHALL NOT occur until all source has been legally transferred
to the ASF.
- the release archive MUST contain the word "incubating" in the filename
- the release archive MUST contain an Incubation disclaimer

and that seems to imply there is no constraint that every podling release
MUST met all the legal requirements expected of a non-incubating ASF
release.

   ...ant

Re: How strict should podling release reviews be?

[ant elder]

On 10/2/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
>
> On 10/2/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> > > i'm thinking more of a benevolent educator than traffic warden
> > > style reviewer role.
> >
> > When it comes to legal issues related to a release, the warden role is
> the
> > more appropriate.  It benefits neither the project nor the ASF if we are
> lax
> > in that regard.
> >
> > Some of the things that they need to do are identified by RAT, and would
> be
> > non-issues if they would correct their build process to do them
> > automatically, e.g., inserting the license and disclaimer files where
> they
> > are supposed to go.
>
> i do believe that there's a definite problem here. there's too much
> energy wasted by everyone.
>
> the IPMC cannot actively oversee the code bases without automation.
> so, the only real oversight happens at release time. this is bad for
> everyone. really, we need to automatically scan and analyse the
> incubator codebases.
>
> i hope that http://wiki.apache.org/incubator/RatProposal may help


That RAT proposal looks really good, its just what we need. I can't promise
to contribute much code but i'd definitely hang around and help test it on
things.

Until that gets implemented (or maybe as part of its design?) could there be
a wiki page documenting each rule RAT would check? That way  we could have a
complete list of each specific requirement in one place to make it easier
for both podlings and reviewers to check manually till RAT is done. If we
had such a list then it could be only the things documented there are
release blockers, or at least if a release is blocked the reason should get
added to the list so we eventually have a fairly compressive list of the
rules so everyone knows what to expect.

I'd have a go at creating such wiki page with the rules I know about if
people think its useful but i expect others would need to help out if its
going to get very comprehensive :)

...ant

[DISCUSS] Graduate Tuscany as top level project

[ant elder]

Over in the Tuscany Incubator project we have been tidying up the loose ends
before we vote in the project community to ask the IPMC to recommend Tuscany
as top level project to the Apache Board.

We have been part of the incubator project for quite some time now and we
believe we have demonstrated our ability to operate in the Apache way,
including supporting users, attracting new committers, creating releases,
completing board reports and forming a PPMC.

Before we start the formal votes on this proposal we want to get feedback
from IPMCers and find out if people have any pending issues.

We are creating a Draft TLP Resolution here [1]

You can follow the discussion we have been having around graduation using
the link from our, currently informal, summary page [2]

   ...ant

[1] http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Draft+TLP+Resolution
[2] 
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Tuscany+Graduation+Checklist

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

Account Request - Amita Vadhavkar - Tuscany (incubating)

[ant elder]

Dear root,

Please create an id for Amita Vadhavkar  on the Tuscany project under
Incubation.

Preferred userid:amita
Full name:Amita Vadhavkar
Forwarding email address: [EMAIL PROTECTED]
Requested Karma for:ws-tuscany

ICLA is on file.

Votes:

tuscany-private Message-ID: <
[EMAIL PROTECTED]>
incubator-private Message-ID: <
[EMAIL PROTECTED]>

Many thanks,

   ...ant

[VOTE] Graduate Tuscany as a top level project

[ant elder]

The Tuscany podling respectfully requests the Incubator to consider its
graduation to a Top Level Project.

While incubating Tuscany has made 14(!) releases, voted in 19 new
committers, survived conflicts, formed its PPMC, learned how to govern
itself, resolved licensing issues and an active community continues to grow
around Tuscany.

The community vote for graduation can be found on the Tuscany dev list at:
   http://www.mail-archive.com/[EMAIL PROTECTED]/msg24675.html

We have prepared the resolution below to be presented for consideration at
the upcoming Board meeting.

We invite everyone to vote to approve this proposal.

Many thanks,

   ...ant

Establish the Apache Tuscany project:

   WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the Foundation's
purpose to establish a Project Management Committee charged with
the creation and maintenance of open-source software that
simplifies the development and deployment of service oriented
applications and provides a managed service-oriented runtime
based on the standards defined by the OASIS OpenCSA group,
for distribution at no charge to the public.

   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Tuscany Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

   RESOLVED, that the Apache Tuscany Project be and hereby is
responsible for the creation and maintenance of software
related to Apache Tuscany;
and be it further

   RESOLVED, that the office of "Vice President, Apache Tuscany" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Tuscany Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Tuscany Project; and be it further

   RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Tuscany Project:

Adriano Crestani
Andrew Borley   
Andy Grove           
ant elder   
Brady Johnson  
Frank Budinsky 
Ignacio Silva-Lepe  
Jean-Sebastien Delfino   
kelvin goodson   
Luciano Resende   
Mike Edwards   
Pete Robbins
Raymond Feng  
Simon Laws  
Simon Nash  
Venkata Krishnan  

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder
be appointed to the office of Vice President, Apache Tuscany, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

   RESOLVED, that the Apache Tuscany Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Tuscany podling; and be it further

   RESOLVED, that all responsibilities pertaining to the Apache
Incubator Tuscany podling encumbered upon the Apache Incubator
Project are hereafter discharged.

Re: [VOTE] Graduate Tuscany as a top level project

[ant elder]

On 10/13/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
>
> On 10/12/07, Mike Edwards <[EMAIL PROTECTED]> wrote:
> > Robert Burrell Donkin wrote:
> > > 
> > >
> > > On 10/12/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> 
>
> > > 2. grrr SOA! i'm unclear what this really means in this case. though
> > > i've been following the lists for quite a while now, i still find it
> > > really hard to understand the target use cases are for tuscany. is it
> > > possible to accurately describe what what tuscany is used for without
> > > using buzzwords?
> > >
> >
> > I must admit that I hadn't perceived "SOA" as a buzzword. I agree that
> > it is a deliberately imprecise term, but that it does describe a general
> > architectural approach to building applications.  Do you think we need
> > to build some paragraphs here that describe what service-oriented
> > architecture means?
>
> the problem with meta-architectures is that most have no canonical
> definition or description and so the same term means different things
> to different people. once a meta-architecture gets hot, it leads to
> outbreaks of Humpty Dumpty syndrome - "When I use a word, it means
> exactly what I intend it to mean, no more, no less.". IMHO SOA has now
> reached this stage.
>
> > As for the target use cases for Tuscany - it is when you want to build a
> > distributed application from independently acting, loosely coupled
> > service components, which may be written using any of a range of
> > programming technologies (Java, C++, Ruby, PHP) and which may be
> > connected using any of a range of communication technologies (Web
> > services, REST, JMS, RMI-IIOP).
>   ^
> some would say that SOA excludes REST. perhaps tuscany may (one day)
> want to wire up ROA as well as SOA ;-)
>
> anyway, tuscany simplifies the development, deployment and management
> of distributed applications composed of independently acting, loosely
> coupled, linguistically hetrogenous components connected using any of
> a wide range of communication technologies
>
> maybe it would be better to state this unambiguously rather than
> relying on the correct interpretation of an ill-defined buzzword
>
> 
>
> > > 4. does tuscany really want to limit itself to a single standard? if
> > > another organisation created standards in this same area, would
> > > tuscany really wish to exclude itself from creating an implementation?
> > >
> >
> > No, Tuscany does not want to limit itself - indeed it already uses other
> > standards like some of the WS-* standards.  We had thought that the
> > wording above didn't imply any limitation, but if we're mistaken in that
> > view, perhaps we need to add some explicit words like:
> >
> > "...based on but not limited to..."
>
> 'based on' worries me - the language seems to me to be uncomfortably
> close to  'derived from'. it's also a long sentence. perhaps something
> like
>
> "Tuscany will implement relevant open standards including ..."
>
> would be better
>
> - robert


So bringing together all the comments so far gives something like:

...establish a Project Management Committee charged with the
creation and maintenance of open-source software that simplifies
the development, deployment and management of distributed
applications composed of independently acting, loosely coupled,
linguistically hetrogenous components connected using any of a
wide range of communication technologies. This software will implement
relevant open standards including, but not limited to, standards defined
by the OASIS OpenCSA group, for distribution at no charge to the public.

I'll wait a while to see if there's any further comments over this and if
not restart a clean vote thread.

   ...ant

Re: [VOTE] Graduate Tuscany as a top level project

[ant elder]

On 10/13/07, Robert Burrell Donkin <[EMAIL PROTECTED]> wrote:
>
> On 10/13/07, ant elder <[EMAIL PROTECTED]> wrote:
> > On 10/13/07, Robert Burrell Donkin <[EMAIL PROTECTED]>
> wrote:
>
> 
>
> > So bringing together all the comments so far gives something like:
> >
> > ...establish a Project Management Committee charged with the
> > creation and maintenance of open-source software that simplifies
> > the development, deployment and management of distributed
> > applications composed of independently acting, loosely coupled,
> > linguistically hetrogenous components connected using any of a
> > wide range of communication technologies. This software will implement
> > relevant open standards including, but not limited to, standards defined
> > by the OASIS OpenCSA group, for distribution at no charge to the public.
>
> the concatination makes last sentence is a little ambiguous. might be
> better to either start another sentence
>
> > This software will implement
> > relevant open standards including, but not limited to, standards defined
> > by the OASIS OpenCSA group. This software will be distribution at no
> charge to the public.
>
> or move the phrase next to open source:
>
> > ...establish a Project Management Committee charged with the
> > creation and maintenance of open-source software for distribution at no
> charge to the public
>
> maybe someone on the board could jump with guideance
>
> - robert


Having both the last two sentences start "This software will..." doesn't
sound perfect to me so if we are able to move the "for distribution at no
charge..." bit up to the top that seems better, which gives:

...establish a Project Management Committee charged with the
creation and maintenance of open-source software for distribution
at no charge to the public, that simplifies the development,
deployment and management of distributed applications composed of
independently acting, loosely coupled, linguistically heterogeneous
components connected using any of a wide range of communication
technologies. This software will implement relevant open standards
including, but not limited to, standards defined by the OASIS
OpenCSA group.

That first sentence is starting to get quite long but unless anyone can come
up with some better wording I could live with that.

   ...ant

Re: [VOTE] Graduate Tuscany as a top level project

[ant elder]

On 10/17/07, Simon Nash <[EMAIL PROTECTED]> wrote:


I wonder if we could shorten this just a little.  How about:
>
> "...establish a Project Management Committee charged with the creation
> and maintenance of open-source software for distribution at no charge
> to the public, that simplifies the development, deployment and management
> of distributed applications built as compositions of service components.
> These components may be implemented with a range of technologies and
> connected using a variety of communication protocols. This software will
> implement relevant open standards including, but not limited to, the
> SCA and SDO standards defined by the OASIS OpenCSA member section."


That sounds ok to me, is everyone else happy with these words?

   ...ant

Re: [RESULT][VOTE] Graduate Tuscany as a top level project

[ant elder]

On 10/19/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
>
> Please don't use [RESULT] in a thread that is still on-going.  There may
> have been a result in the Tuscany PPMC, but there is no result yet from
> the
> Incubator PMC.


This is the Tuscany community vote result thread which was only on the
tuscany-dev list but seems to have inadvertently been replied to to the
general@ list. Apologies to those over here, please  just ignore it.

   ...ant

Re: [VOTE] Graduate Tuscany as a top level project

[ant elder]

On 10/19/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
>
> Paul Fremantle wrote:
>
> > I think Tuscany is ready to graduate because:
> > 1) I understand it to have met the base requirements of the IPMC in
> terms
> of
> >independent committers
>
> Apparently a bare minimum, with very little active work from independents?


If the bare minimum is the "3 legally independent committers" as defined in
the Incubator policy documents then Tuscany has more than the bare minimum -
and thats "active" committers. After two years in Incubation there are
inactive committers but we've been ignoring those for these graduation
discussions.

   ...ant

Re: [RESULT][VOTE] Graduate Tuscany as a top level project

[ant elder]

On 10/20/07, Bertrand Delacretaz <[EMAIL PROTECTED]> wrote:
>
> On 10/20/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> > ...This is the Tuscany community vote result thread which was only on
> the
> > tuscany-dev list but seems to have inadvertently been replied to to the
> > general@ list
>
> BTW, that message says
>
> > ...given the muddied waters how about waiting a little before
> > restarting the vote?...
>
> Is that what's happening now, i.e. does the Tuscany PPMC consider this
> IPMC vote thread cancelled?


Yes, i'd posted to the thread earlier saying i'd restart it once the
proposal words had been settle on, but looks like we'll need to wait now.
I'll post to the vote thread now to make this clear.

   ...ant

Re: [VOTE] Graduate Tuscany as a top level project

[ant elder]

On 10/12/07, ant elder <[EMAIL PROTECTED]> wrote:
>
> The Tuscany podling respectfully requests the Incubator to consider its
> graduation to a Top Level Project.
>
> While incubating Tuscany has made 14(!) releases, voted in 19 new
> committers, survived conflicts, formed its PPMC, learned how to govern
> itself, resolved licensing issues and an active community continues to grow
> around Tuscany.
>
> The community vote for graduation can be found on the Tuscany dev list at:
>http://www.mail-archive.com/[EMAIL PROTECTED]/msg24675.html
>
>
> We have prepared the resolution below to be presented for consideration at
> the upcoming Board meeting.
>
> We invite everyone to vote to approve this proposal.
>
> Many thanks,
>
>...ant
>
> Establish the Apache Tuscany project:
>
>WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the Foundation's
> purpose to establish a Project Management Committee charged with
> the creation and maintenance of open-source software that
> simplifies the development and deployment of service oriented
> applications and provides a managed service-oriented runtime
> based on the standards defined by the OASIS OpenCSA group,
> for distribution at no charge to the public.
>
>NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Tuscany Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
>RESOLVED, that the Apache Tuscany Project be and hereby is
> responsible for the creation and maintenance of software
> related to Apache Tuscany;
> and be it further
>
>RESOLVED, that the office of "Vice President, Apache Tuscany" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Tuscany Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Tuscany Project; and be it further
>
>RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
>     Apache Tuscany Project:
>
> Adriano Crestani org>
> Andrew Borley   
> Andy Grove   
> ant elder   
> Brady Johnson  
> Frank Budinsky 
> Ignacio Silva-Lepe  
> Jean-Sebastien Delfino   
> kelvin goodson   
> Luciano Resende   
> Mike Edwards   
> Pete Robbins        
> Raymond Feng  
> Simon Laws  
> Simon Nash  
> Venkata Krishnan  
>
>NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder
> be appointed to the office of Vice President, Apache Tuscany, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
>RESOLVED, that the Apache Tuscany Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Tuscany podling; and be it further
>
>RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Tuscany podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>
>
Thanks to everyone who's commented on this thread. Looks like we've come up
with words that people are happy with but we shall hold off restarting the
vote till all the discussions around minimum diversity requirements reach
more consensus.

The latest words are:

"...establish a Project Management Committee charged with the creation
 and maintenance of open-source software for distribution at no charge
 to the public, that simplifies the development, deployment and management
 of distributed applications built as compositions of service components.
 These components may be implemented with a range of technologies and
 connected using a variety of communication protocols. This software will
 implement relevant open standards including, but not limited to, the
 SCA and SDO standards defined by the OASIS OpenCSA member section."

   ...ant

Re: [VOTE] Graduate Tuscany as a top level project

[ant elder]

On 10/21/07, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
>
> Ant Elder wrote:
>
> > > Apparently a bare minimum, with very little active work from
> independents?
>
> > If the bare minimum is the "3 legally independent committers" as defined
> in
> > the Incubator policy documents then Tuscany has more than the bare
> minimum -
> > and thats "active" committers.
>
> Can you compare those figures with Jeremy's statment:
>
> > at this time there are only 2 committers active[2] who don't work for
> > that organization, compared to 11 who do. Neither of the two
> > independents are active in the core project areas of Java SCA or SDO
> > (they are committing to the C++ implementation or to DAS).
>
> and Simon Nash's:
>
> > In the last 2 months, 3 new committers have been added, one is in
> progress
> > as Paul has said, and one is being discussed.  Of these 5 people, one is
> > IBM "day job" (me), one is IBM "non-day-job", and 3 are non-IBM.
>
> Simon seems to say three non-IBM and one IBM as a hobby, not day job.  But
> two of the five aren't committers *yet*.  Jeremy says two indepdendents.
> You're saying more than three.


I think the breakdown is: current active committers are from IBM, RougeWave
and two independents.

I'm not sure exactly who does how many hours for a day job but i _think_ at
least 3 of those IBM committers don't participate at all for their day
jobs.

Tuscany has 11 inactive committers (not contributed for months), from BEA,
IBM, IONA and Redhat and two independents, I don't know if any of those will
contribute again, last time i spoke to one of them they said they would but
they were busy on other things just now.

There's two more new people being voted on presently, and the STATUS file
[1] shows new committers have been getting added every month or two over
most of the incubation.

So from that Tuscany does "more than meet" the minimum requirement of "at
least 3 legally independent committers". I've not seen this detail on
diversity and active versus inactive committers in other graduations - how
does Tuscany compare with other previously graduating poddlings?

   ...ant

[1] https://svn.apache.org/repos/asf/incubator/tuscany/STATUS

Re: [VOTE] Accept project Buildr for incubation

[ant elder]

+1

   ...ant

On 10/29/07, Matthieu Riou <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> Following up on the proposal discussed at [1] I'd like to call for a vote
> to
> incubate Buildr. Buildr is a simple and intuitive build system for Java
> projects written in Ruby (and based on Rake), please see the complete
> proposal text at [2] or at the end of this e-mail.
>
> Also we're missing one more mentor so if someone could volunteer, that
> would
> really be great.
>
> Please vote on accepting Buildr into the Apache Incubator. This vote will
> run until Thursday November 1st at 3pm PST.
>
> [ ] +1 Accept Buildr project for incubation
> [ ] 0 Don't care
> [ ] -1 Reject for the following reason :
>
> Thanks!
> Matthieu
>
> [1]
> http://mail-archives.apache.org/mod_mbox/incubator-general/200710.mbox/[EMAIL 
> PROTECTED]
>
> [2] http://wiki.apache.org/incubator/BuildrProposal
>
> ---
>
> = Abstract =
>
> Buildr is a simple and intuitive build system for Java projects.
>
> = Proposal =
>
> Buildr is a build system for Java applications. We wanted something that's
> simple and intuitive to use, so we only need to tell it what to do, and it
> takes care of the rest. But also something we can easily extend for those
> one-off tasks, with a language that's a joy to use. And of course, we
> wanted
> it to be fast, reliable and have outstanding dependency management.
>
> Here's what we got:
>
> * A simple way to specify projects, and build large projects out of
> smaller sub-projects.
> * Pre-canned tasks that require the least amount of configuration,
> keeping the build script DRY and simple.
> * Compiling, copying and filtering resources, JUnit/TestNG test cases,
> APT source code generation, Javadoc and more.
> * A dependency mechanism that only build that which changed since the
> last release.
> * Buildr uses the same file layout, artifact specifications, local and
> remote repositories as Maven 2.
> * All your Ant tasks belong to us! Anything you can do with Ant, you
> can
> do with Buildr.
> * Buildr is Ruby all the way down. No one-off task is too demanding
> when
> you write code using variables, functions and objects.
> * Simple way to upgrade to new versions.
> * Did we mention fast?
>
> = Background =
>
> Buildr is developed using the Ruby language and is layered on top of Rake,
> a
> popular build program for Ruby that provides all the task and task
> dependency infrastructure. It also relies on AntWrap to allow the reuse of
> all existing Ant tasks.
>
> = Rationale =
>
> Buildr's initial focus was to be layered on top of a powerful scripting
> language. It's an internal DSL and therefore enjoys a lot of ease of use
> and
> extensibility. It's also declarative, which gives scripts expressiveness
> (they're easy to read). And there's no XML!
>
> We believe bringing Buildr at Apache is a good way to expand even more the
> build tool space, attract more committers and users to Buildr and have
> people start playing with the Ruby language, both within and outside the
> foundation.
>
> = Current Status =
>
> == Meritocracy ==
>
> Buildr has been mostly developed by Assaf Arkin but others have
> contributed
> either directly or through patches. In addition to contributed patches,
> work
> on Scala and JRuby is done by community members, and we're working to
> cultivate that and add more committers.
>
> == Community ==
>
> A community of standard users but also power users is building around
> Buildr
> and several people are using it in all sort of different projects.
> Currently
> the discussion group has 86 members, more statistics available at
> http://groups.google.com/group/buildr-talk?lnk=srg
>
> == Core Developers ==
>
> Core developers are mostly from a single organization but more and more
> power users are contributing patches and trying to extend Buildr. Also
> current core developers are very experienced in open source and already
> follow the Apache ways.
>
> == Alignment ==
>
> Buildr is in line with the existing strong culture of build tools at
> Apache
> (Ant, Maven, Ivy, ...). It already relies on Maven2 repositories and
> follows
> most of its project structure conventions. It allows reuse of Ant tasks.
> Not
> to mention that other Apache projects could use it for their build (as ODE
> already does).
>
> = Known Risks =
>
> == Orphaned Projects ==
>
> Buildr core development is still very much dependent on Assaf but more and
> more people are getting familiar with the way Buildr works and its
> intricacies. So we're aware of the problem but also confident that we're
> on
> the right track as more and more people get involved.
>
> == Inexperience with Open Source ==
>
> Many committers have experience working on open source projects. Three of
> them are Apache committers.
>
> == Reliance on Salaried Developers ==
>
> Buildr is part of the committers job but is far from being the main
> company
> focus. So i

Re: Diversity requirement

[ant elder]

On 10/31/07, Matt Hogstrom <[EMAIL PROTECTED]> wrote:
>
>
> On Oct 30, 2007, at 11:58 PM, Matthieu Riou wrote:
>
> > "there are at least 3 legally independent committers and there is no
> > single
> > company or entity that is vital to the success of the project"
>
> What does legally independent mean?  Not paid by the same company to
> work on a project?  I'd be ok with that.


I thought i had seen a web page with more about what independent meant but
now i can't find anything other than this email from a wiki edit which says:

"The legal definition of independent is long and boring, but basically it
means that there is no binding relationship between the individuals, such as
a shared employer, that is capable of overriding their free will as
individuals, directly or indirectly."

- http://marc.info/?l=incubator-cvs&m=106976845317594&w=2

   ...ant

Re: [VOTE] Please approve Tuscany SCA Java 1.0.1-incubating release

[ant elder]

On Nov 16, 2007 2:10 PM, Kevan Miller <[EMAIL PROTECTED]> wrote:

>
> On Nov 16, 2007, at 2:09 AM, Raymond Feng wrote:
>
> > Hi, Kevan.
> >
> > Thank you for the review. We have fixed the issue and republished a
> > RC5a at:
> >
> > SVN Tag:
> >
> http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.0.1-RC5a/
> >
> > Stage maven repo:
> http://people.apache.org/~rfeng/tuscany/maven/1.0.1-RC5a
> >
> > RAT report:
> > http://people.apache.org/~rfeng/tuscany/1.0.1-RC5a/1.0.1-RC5a.rat.txt
> >
> > Binary and source distros (zip/gz/asc/md5) :
> > http://people.apache.org/~rfeng/tuscany/1.0.1-RC5a/
> >
> > Since the fix doesn't involve any 'code' changes, can we skip the
> > tuscany-dev vote and continue the IPMC vote here? Please advise.
>
> Well, I've certainly seen incubator votes continue with similar
> issues, in the past. I'm fine with the vote continuing, as long as the
> problem (and changes) have been communicated to the tuscany community.
>
> The updated binaries look good.
>
> Here's my +1.
>
> One minor note for future releases: some of your jar files contain
> both a LICENSE and a LICENSE.txt file.
>
> --kevan
>
>
I've already voted over on tuscany-dev but I'll also vote +1 here to keep
the thread current...still looking for one more vote if anyone else has any
time to take a look at the release.

   ...ant

Re: [DISCUSS] Community diversity: current concerns and suggestions for improvement

[ant elder]

On Nov 22, 2007 7:09 PM, Niall Pemberton <[EMAIL PROTECTED]> wrote:

> On Nov 20, 2007 9:14 PM, Eelco Hillenius <[EMAIL PROTECTED]>
> wrote:
> > > I would agree with reviewing committers at graduation, but how do we
> > > implement that?
> >
> > I would say that this depends on the judgment of the mentors, and it
> > is probably more important to evaluate the role they would be playing
> > in the project once it is over to Apache, than what happened before
> > entering incubation.
> >
> > > Would you kick out people during graduation, if they don't show
> > > sufficient merit?
> >
> > I don't think you can make rules for that. Imho it's simple. The
> > project has to prove it can behave the Apache way, and the project's
> > members are responsible for this. People not functioning well in a
> > project can be a reason to reject incubation, so the members better
> > make sure that doesn't happen.
> >
> > > Or re-elect all committers before graduation?
> >
> > That might be a good idea actually.
>
> Ask people to self nominate - I imagine often inactive commiters won't
> put themselves forward, removing any issue. Then maybe a review of the
> list by the the mentors and proposed PMC Chair. If there are issues it
> can be discussed in the community and if theres disagreement then
> vote. I imagine most of the time it won't come to voting.
>
> Niall
>

That sounds reasonable but is it ok to do that? Its quite hard to remove a
committer from a real Apache project, are incubating committers different
and its ok to just ask who wants to be included at graduation?

   ...ant

Re: [VOTE] Graduate Woden into the WS PMC

[ant elder]

On Dec 5, 2007 3:57 AM, Niclas Hedhman <[EMAIL PROTECTED]> wrote:

> On Monday 03 December 2007 23:09, Paul Fremantle wrote:
> > Here is my +1. Paul
>
> +1,
>
> With a note that IBM's contribution to the project *seems* to be a
> worryingly
> large proportion. I still vote +1 as I am convinced that the WS PMC will
> be
> able to deal with that if it becomes a problem. If Woden were seeking TLP,
> I
> would probably not vote in favor.
>
> Now, get out of here... ;o)
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
>
>
+1 from me with the same sentiments as Niclas.

   ...ant

Re: [VOTE] Move Project Yoko to Apache Geronimo and Apache CXF

[ant elder]

On Dec 11, 2007 2:15 PM, Alexey Petrenko <[EMAIL PROTECTED]>
wrote:

> 2007/12/11, Carl Trieloff <[EMAIL PROTECTED]>:
> >
> > Just to make sure I understand what is happening here - Yoko is going
> > away/ending and getting
> > merged into Geronimo and CXF?
> Yes.
>
> SY, Alexey
>
>
The proposal mentions continuing to allow for independent releases of the
Yoko code that gets moved to Geronimo so is this going to be a new
sub-project of Geronimo and if so then shouldn't this just be a simple
graduation as a sub-project vote?

   ...ant

Re: [VOTE] Approve release Apache UIMA 2.2.1-incubating

[ant elder]

On Dec 13, 2007 11:50 AM, Michael Baessler <[EMAIL PROTECTED]> wrote:

> The Apache UIMA committers ask the Apache Incubator PMC for
> permission to publish a new bug fix release of Apache UIMA.
> This release contains bug fixes of the Apache UIMA 2.2.0 release published
> in
> August 2007. For details about the fixes, please have a look at the
> release notes.
>
> We had a vote on uima-dev that resulted in 6 binding +1s
> (all the committers) and no 0s or -1s.  The vote thread
> is here:
>
> http://mail-archives.apache.org/mod_mbox/incubator-uima-dev/200712.mbox/[EMAIL
>  PROTECTED]
>
> Please review the release candidate here:
> http://people.apache.org/~mbaessler/uimaj-2.2.1/06/
>
> There are subdirectories like:
> /bin - that contains the binary distribution files
> /src - that contains the source distribution files
> /rat - that contains the RAT reports (using RAT 0.5.1) with some comments
> /eclipseUpdateSite - that contains the eclipse update site artifacts
> /maven - that contains the Maven artifacts we would like to release to the
> incubator repository
>
> The SVN tag for this release candidate is:
>
> https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-2.2.1/uimaj-2.2.1-06
>
> Please vote:
> [ ] +1  Accept to release Apache UIMA 2.2.1
> [ ] -1  No, because
>
> Thanks!
>
> -- Michael
>

+1  this looks all fine to me.

i did wonder why the jVinci jar doesn't have a uima- prefix or use the
org.apache.uima package name but it looks fine in the maven repository so i
guess that doesn't matter.

   ...ant

Re: [VOTE] Approve release Apache UIMA 2.2.1-incubating

[ant elder]

On Dec 15, 2007 9:21 PM, Kevan Miller <[EMAIL PROTECTED]> wrote:

>
> On Dec 15, 2007, at 1:43 PM, sebb wrote:
>
> > [Eventually found the KEYS file in SVN, but it might be helpful to
> > provide a pointer in the vote mails]
> >
> > The NOTICE file in uimaj-2.2.1-incubating-bin.zip refers to the
> > contributions from IBM:
> >
> > "Software Grant License Agreement", informally known as the
> > "IBM UIMA License Agreement".
> >
> > however, that license is not in LICENSE, nor is it linked from there.
>
> The code covered by that software grant would now be covered by the
> Apache License. I would not expect to find the software grant
> agreement in the license text/files. Haven't looked into the hash/
> checksum issues...
>
> On further review, I am changing my vote to a -1.
>
> The source code in svn (
> https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-2.2.1/uimaj-2.2.1-06
> ) does not contain a LICENSE, NOTICE, and DISCLAIMER file in the top
> directory. Refer to http://apache.org/dev/apply-license.html if you
> have any questions.
>
> --kevan


That seems a little harsh to me and with some build setups its easier to
keep the legal files in a different location. AIUI its only that actual
distribution archives which MUST have the legal files in the top level
folder.

   ...ant

Account Request - Mark Combellack - Tuscany (incubating)

[ant elder]

Dear root,

Please create an id for Mark Combellack  on the Tuscany project under
Incubation.

Preferred userid:mcombellack
Full name:   Mark Combellack
Forwarding email address:[EMAIL PROTECTED]
Requested Karma for: ws-tuscany

ICLA is on file.

Votes:

tuscany-private, Oct 29, Message-ID: <
[EMAIL PROTECTED]>

incubator-private, Nov 1, Message-ID: <
[EMAIL PROTECTED]>

Many thanks,

   ...ant

Re: [VOTE] Approve release Apache UIMA 2.2.1-incubating

[ant elder]

On Dec 17, 2007 5:44 PM, Thilo Goetz <[EMAIL PROTECTED]> wrote:

> Kevan Miller wrote:
> >
> > On Dec 17, 2007, at 4:09 AM, Thilo Goetz wrote:
> >
> >> William A. Rowe, Jr. wrote:
> >>> Marshall Schor wrote:
>  We've put the LICENSE, NOTICES, and DISCLAIMERs into the top
> directory
>  of the source (and binary) distribution(s), but didn't realize this
>  also
>  needs to be in the top level of the SVN tag, because we didn't know
>  that
>  was considered part of the "distribution".
> 
>  Can you please confirm this is the case?  In which case, we'll of
>  course
>  comply.
> >>>
> >>> Your distribution must correspond to subversion, otherwise it's very
> >>> hard
> >>> to track the artifacts in the tarball, where they came from, how they
> >>> got there, and if they underwent the proper oversight prior to
> >>> packaging.
> >>> (Yes, we vote on the prepared tarball, but you can see how
> discrepancies
> >>> do create questions.)
> >>
> >> That's not how I interpret the policy document.  It says:
> >>
> >> "To apply the ALv2 to a new software distribution, include one copy of
> >> the license text by copying
> >> the file:
> >>
> >> http://www.apache.org/licenses/LICENSE-2.0.txt
> >>
> >> into a file called LICENSE in the top directory of your distribution.
> >> If the distribution is a jar
> >> or tar file, try to add the LICENSE file first in order to place it at
> >> the top of the archive."
> >>
> >> That's what we do.  Of course we'll make every effort to make
> >> our distribution easy to review.  However, it does seem that
> >> we're ok wrt current policy, and view this as a suggestion
> >> for next time.  Ok?
> >
> > Your interpretation works if your subversion repository is not a
> > "distribution". IMO, it is and should contain appropriate
> > license/notice/disclaimer.
>
> If that is the consensus opinion here, that's what we'll
> do.  But please put yourself in our shoes.  We can only go
> by the information that is available to us.  If this is a
> rule, it would be great if it could be written down so the
> next incubator project doesn't have to go through this.  I'd
> be happy to help with the docs.
>
> Out of curiosity, I started going through the Apache SVN repo
> to see what Apache projects complied with this requirement.  I
> stopped after C because I'd already found 4 that didn't
> comply: Avalon, Cayenne, Cocoon and Commons.  Compliant
> were Activemq, Ant, APR and Beehive.
>
> --Thilo
>

I've never considered that the SVN tag for a release is a "distribution"
before, but its an interesting idea. There clearly is not yet consensus
among the IPMC on this though or if that tag MUST have LICENSE and NOTICE
files in the the top-level directory. As pointed out above many Apache
projects don't do this, and looking back at all the recent Incubator
poddling releases many of those have not done this either but never the less
their vote has passed.

So it is a new requirement and I don't think we should be making up policy
during a release vote like this as it makes it very frustrating for
poddling. How about letting this UIMA release out as-is for now while we
work this out? Kevan, would you withdraw your -1 for this release while we
resolve this?

   ...ant

Re: [VOTE] publish Tika 0.1-incubating

[ant elder]

Looks ok to me so +1. Was going to say the Incubator disclaimer is missing
in the artifacts but then found it in the README file, should probably move
that to a separate DISCLAIMER file for later releases.

   ...ant

On Dec 31, 2007 7:20 PM, Chris Mattmann <[EMAIL PROTECTED]> wrote:

> Hi Incubator PMC:
>
> The Tika community voted on and has approved a proposal to release
> Tika 0-1 incubating. Pursuant to the Releases section of the Incubation
> Policy and with the endorsement of Jukka Zitting, one of our mentors we
> would now like to request the permission of the Incubator PMC to publish
> the
> tarball on the Tika Download page.
>
> I'd also like to request on behalf of the Tika community that
> /www/www.apache.org/dist/incubator/tika, be used as the warehouse for Tika
> releases. I apologize for creating this directory ahead of time, without
> asking the PMC: it's simply due to this being my first time as an
> incubator
> release manager, and I assure you, it will not happen again.
>
> Please vote by 6 PM PST Wednesday, 1/3/2008.
>
> Thanks!
>
> Proposal:
> http://www.nabble.com/Tika-0.1-update-to14452777.html
>
> Vote result:
>
> http://www.nabble.com/-VOTE--Tika-0.1-incubating-Release-Candidate-2-to14522
> 857.html
>
> Download page:
> http://www.apache.org/dyn/closer.cgi/incubator/tika
>
> (will update http://incubator.apache.org/tika/ to have link to above on
> left
> hand navigation bar)
>
> Releases section of the Incubation Policy:
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
>
>
> Thanks!
>
> Cheers,
>  Chris
>
> __
> Chris Mattmann, Ph.D.
> [EMAIL PROTECTED]
> Cognizant Development Engineer
> Early Detection Research Network Project
> _
> Jet Propulsion LaboratoryPasadena, CA
> Office: 171-266B Mailstop:  171-246
> ___
>
> Disclaimer:  The opinions presented within are my own and do not reflect
> those of either NASA, JPL, or the California Institute of Technology.
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Account Request - Rajini Sivaram - Tuscany (incubating)

[ant elder]

Dear root,

Please create an id for Rajini Sivaram on the Tuscany project under
Incubation.

Preferred userid:  rsivaram
Full name:  Rajini Sivaram
Forwarding email address:[EMAIL PROTECTED]
Requested Karma for:  ws-tuscany

ICLA is on file.

Votes:

tuscany-private, Nov 8, Message-ID: <
[EMAIL PROTECTED]>

incubator-private, Nov 19, Message-ID: <
[EMAIL PROTECTED]>

Many thanks,

   ...ant

Re: Policy re importing non-APL source into apache svn

[ant elder]

On Jan 14, 2008 3:29 PM, Noel J. Bergman <[EMAIL PROTECTED]> wrote:

> Simon Kitching wrote:
>
> > Is a project under incubation allowed to import its existing sources
> > (not under the Apache license) into the Apache svn?  And after
> > graduation from the incubator, is it ok for the svn history to
> > still show those old non-apl files in the history?
>
> > I hope the answer is simply "yes". It is nice to be able to see the
> > complete history of any file, even before its move to Apache. However
> > this does mean that non-apl source can be downloaded via the apache
> > svn server which seems a little odd.
>
> I honestly don't remember, and seem to recall that we've had both things
> happen in the past, with discussion about it.  There have definitely been
> statements to the effect that projects can clean up their licensing while
> in
> the Incubator.  That also seems to be implied by the presence of the
> Copyright and Distribution Rights questions in the STATUS file.
>
> On the other hand, I also believe that the ASF should have the code grants
> prior to importing the code into SVN.
>
> Discussion?
>
>--- Noel
>

The current draft of the proposed third party licensing policy mentions this
and seems to allow it, see:
http://people.apache.org/~rubys/3party.html#transition-incubator

   ...ant

Re: [VOTE] Please approve Tuscany SCA Java 1.1-incubating release

[ant elder]

I think the NOTICE files in the artifacts that are actually being
distributed are OK. The ${pom.name} is changed by the build process so the
generated artifact has the proper name, for example, the jar built for
wsdl2java ends up with a NOTICE file containing "Apache Tuscany SCA
WSDL2Java Tool", see inside:
http://people.apache.org/~slaws/tuscany/1.1-RC3/maven/org/apache/tuscany/sca/tuscany-wsdl2java/1.1-incubating/tuscany-wsdl2java-1.1-incubating.jar
.

The mortgage-loanapproval is only distributed within the src and bin
distributions and the NOTICE file in those distributions does include all
the necessary references so that also looks ok to me.

Including the Derby.log is a mistake, but I don't think its a blocker :)

+1 to release.

   ...ant

On Jan 23, 2008 10:55 PM, sebb <[EMAIL PROTECTED]> wrote:

> Some of the NOTICE files start with the text:
>
> ${pom.name}
>
> e.g.
>
> tools/wsdl2java
> and
> modules/policy
>
> This does not seem right.
>
> The top-level NOTICE and LICENSE files in demos/mortgage-loanapproval
> are the standard ASF ones - however NOTICE and LICENSE.txt in the
> demos/mortgage-loanapproval/src/main/resources/META-INF directory
> include additional references to Eclipse licenses.
>
> Again, I would expect the top-level L&N files for a directory tree to
> agree with the lower level ones.
>
> The file apache-tuscany-sca-1.1-incubating-src.tar.gz contains the
> file derby.log which perhaps should not be there.
>
> On 23/01/2008, Simon Laws <[EMAIL PROTECTED]> wrote:
> > Hi,
> >
> > The Tuscany project had a vote on [EMAIL PROTECTED] to publish
> the
> > Tuscany SCA Java 1.1-incubating release. The vote thread on tuscany-dev
> has
> > 7 +1s and an archive can be found at:
> >
> > http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg27321.html
> >
> > The release includes new function and bug fixes. You can see a list of
> > changes at:
> >
> >
> http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3/distribution/src/main/release/CHANGES
> >
> >
> > The signed binary and source distributions, the RAT reports, and the
> Maven
> > staging repository are listed at the following links.
> >
> > SVN Tag:
> > http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3/
> >
> > Stage maven repo:
> > http://people.apache.org/~slaws/tuscany/1.1-RC3/maven/
> > 
> >
> > RAT report:
> > http://people.apache.org/~slaws/tuscany/1.1-RC3/rat-1.1-RC3.txt
> 
> >
> > Binary and source distros (zip/gz/asc/md5) :
> > http://people.apache.org/~slaws/tuscany/1.1-RC3/
> 
> >
> > Please review and approve the release. This vote will remain open for at
> > least 72 hours.
> >
> > Thanks,
> >
> > Simon
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE] Please approve Tuscany SCA Java 1.1-incubating release

[ant elder]

On Jan 24, 2008 9:39 PM, sebb <[EMAIL PROTECTED]> wrote:

> On 24/01/2008, Simon Laws <[EMAIL PROTECTED]> wrote:
> > Hi sebb
> >
> > Thank you for the detailed review.
> >
> > Can you tell me what you mean by
> >
> > On Jan 24, 2008 4:57 PM, sebb <[EMAIL PROTECTED]> wrote:
> >
> > > On 24/01/2008, ant elder <[EMAIL PROTECTED]> wrote:
> > > > I think the NOTICE files in the artifacts that are actually being
> > > > distributed are OK.
> > >
> > > Surely the archive bundles are also distributed?
>
> I meant that the files in the
>
> 
> Binary and source distros (zip/gz/asc/md5) :
> http://people.apache.org/~slaws/tuscany/1.1-RC3/<http://people.apache.org/%7Eslaws/tuscany/1.1-RC3/>
> 
> are actually being distributed.
>
> I took Ant Elder's comment to mean that these were not being distributed.
>
> > >
> > >
> > snip..
> >
> > Also can you tell me if you consider that the issues you have found to
> be
> > blocking issues?
> >
>
> Yes, I think the discrepancies in the LICENSE file need to be addressed.
>
> Also, comparing the SVN tag with the source archive shows that there
> are quite a few files and directories that are missing from the source
> archive.
>
> There are several files in the source archive that are not in SVN,
> which probably should be in SVN, for example:
>
> BUILDING
> CHANGES
> DISCLAIMER
> LICENSE
> NOTICE
> README
> RELEASE_NOTES
> demos/alert-aggregator-webapp/build-dependency.xml
> demos/xml-bigbank/build-dependency.xml
>
> itest/databindings/interop/src/test/java/org/apache/tuscany/sca/itest/sdodatabinding/InteropDatabindingTestCase.java
>
> itest/databindings/jaxbgen/src/main/java/org/apache/tuscany/sca/itest/jaxbdatabinding/GreeterService.java
>
> itest/databindings/jaxbgen/src/main/java/org/apache/tuscany/sca/itest/jaxbdatabinding/GreeterServiceClient.java
>
> itest/databindings/jaxbgen/src/main/java/org/apache/tuscany/sca/itest/jaxbdatabinding/GreeterServiceClientImpl.java
>
> itest/databindings/jaxbgen/src/main/java/org/apache/tuscany/sca/itest/jaxbdatabinding/GreeterServiceImpl.java
>
> itest/databindings/jaxbgen/src/test/java/org/apache/tuscany/sca/itest/jaxbdatabinding/DatabindingTestCase.java
>
> itest/databindings/sdogen/src/main/java/org/apache/tuscany/sca/itest/sdodatabinding/GreeterService.java
>
> itest/databindings/sdogen/src/main/java/org/apache/tuscany/sca/itest/sdodatabinding/GreeterServiceClientImpl.java
>
> itest/databindings/sdogen/src/main/java/org/apache/tuscany/sca/itest/sdodatabinding/GreeterServiceImpl.java
>
> itest/databindings/sdogen/src/test/java/org/apache/tuscany/sca/itest/sdodatabinding/DatabindingTestCase.java
> samples/calculator-webapp/build.xml
> samples/calculator-ws-webapp/build.xml
> samples/chat-webapp/build.xml
> samples/feed-aggregator-webapp/build.xml
> samples/helloworld-dojo-webapp/build-dependency.xml
> samples/helloworld-jsonrpc-webapp/build.xml
> samples/helloworld-ws-sdo-webapp/build-dependency.xml
>
> There are also a lot of files in SVN, which are not in the source archive:
>
> demos/alert-aggregator-webapp/alert-aggregator.svg
> demos/bigbank-account/bigbank.svg
> demos/bigbank-calculator/src/test
> demos/secure-bigbank/secure-bigbank-account/bigbank.svg
> demos/secure-bigbank/secure-bigbank-calculator/src/test
> demos/xml-bigbank/xml-bigbank.svg
> distribution/standalone/src/main/resources
> distribution/tomcat/src/test
> distribution/webapp/src/test
> distribution/webapp/src/main/resources
> itest/admin/src/test/java/test
> itest/contribution-import-export/export-java/src/test
> itest/contribution-import-export/export-wsdl/src/test
> itest/contribution-import-export/export-wsdl/src/main/java
> itest/contribution-multiple/src/main
> itest/databindings/config.svg
> itest/databindings/databinding.svg
> itest/databindings/interop.svg
> itest/domain/src/main/java/org
> itest/interop-soap-client/src/test/resources
> itest/osgi-contribution/contribution-classes-v2/src/test
> itest/osgi-contribution/contribution-classes/src/test
> itest/transaction/src/test/resources
> itest/wsdl2java/src/main
> itest/wsdl2java/src/test/java
> modules/implementation-das
> modules/binding-dwr/src/test
> modules/binding-ws-axis2/src/main/assembly
> modules/binding-ws/src/test
> modules/contribution-java/src/test/resources
> modules/contribution-namespace/src/test/resources
> modules/contribution-osgi/src/test
> modules/contribution/src/test
> modules/core-databinding/src/test/java/org/apache/tuscany/core
> modules/core-spi/src/test
> modules/data-engine-helper/src/test
> modules/data-e

Re: [VOTE] Approve release CXF 2.0.4-incubator

[ant elder]

I'm not sure those votes on cxf-dev count in this vote unless they vote in
this thread, no mater though as there are enough votes here now.

   ...ant

On Jan 26, 2008 5:56 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:

>
>
> Just a quick update while the vote is open.
>
> Jim Jagielski and Jeff Genender both voted +1 on the thread on cxf-dev.
> Thus, that's two additional binding IPMC votes.   Vote is still
> open :-)
>
> Dan
>
>
> On Friday 25 January 2008, Daniel Kulp wrote:
> > We held a vote on cxf-dev to release a new version of CXF. This
> > version is pretty much just a big "bug fix rollup" compared to 2.0.3
> > fixing over 50 JIRA issues reported by users and bugs encountered
> > during some interop testing.
> >
> > For a full list of the issues, see:
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=1231285
> >5&styleName=Html&projectId=12310511&Create=Create
> >
> > The vote thread is at:
> > http://www.nabble.com/-VOTE--Release-CXF-2.0.4-incubator-to15025947.ht
> >ml
> >
> > In summary, we have 11 +1 votes,  no 0 or -1 votes.  Two of the votes
> > are from ASF members (bsnyder and gnodet).   I'm not sure if they are
> > binding yet or not.  (I think they both sent in requests to join the
> > IPMC, just not sure if that is finished yet).
> >
> >
> > The staging area is at:
> > http://people.apache.org/~dkulp/stage_cxf/2.0.4-incubator
> >
> >
> > The distributions are in the "dist" directory. The "m2repo" directory
> > contains the stuff that will by pushed to the
> > m2-incubating-repository.
> >
> > This release is tagged at:
> > http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.0.4-incubator
> >/
> >
> > We and our users appreciate you taking the time to look over this
> > release!
>
>
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE] Approve release CXF 2.0.4-incubator

[ant elder]

Looks ok to me, +1.

   ...ant

On Jan 25, 2008 9:42 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:

>
>
> We held a vote on cxf-dev to release a new version of CXF. This version
> is pretty much just a big "bug fix rollup" compared to 2.0.3 fixing over
> 50 JIRA issues reported by users and bugs encountered during some
> interop testing.
>
> For a full list of the issues, see:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12312855&styleName=Html&projectId=12310511&Create=Create
>
> The vote thread is at:
> http://www.nabble.com/-VOTE--Release-CXF-2.0.4-incubator-to15025947.html
>
> In summary, we have 11 +1 votes,  no 0 or -1 votes.  Two of the votes are
> from ASF members (bsnyder and gnodet).   I'm not sure if they are
> binding yet or not.  (I think they both sent in requests to join the
> IPMC, just not sure if that is finished yet).
>
>
> The staging area is at:
> http://people.apache.org/~dkulp/stage_cxf/2.0.4-incubator
>
>
> The distributions are in the "dist" directory. The "m2repo" directory
> contains the stuff that will by pushed to the m2-incubating-repository.
>
> This release is tagged at:
> http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.0.4-incubator/
>
> We and our users appreciate you taking the time to look over this
> release!
>
> --
> J. Daniel Kulp
> Principal Engineer, IONA
> [EMAIL PROTECTED]
> http://www.dankulp.com/blog
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE] Approve release CXF 2.0.4-incubator

[ant elder]

The policy page says:

"Therefore, should a Podling decide it wishes to perform a release, the
Podling SHALL hold a vote on the Podling's public -dev list. At least three
+1 votes are required (see the Apache Voting Process page), and only the
PPMC member votes are binding. If the majority of all votes is positive,
then the Podling SHALL send a summary of that vote to the Incubator's
general list and formally request the Incubator PMC approve such a release.
Three +1 Incubator PMC votes are required." -
http://incubator.apache.org/incubation/Incubation_Policy.html#Releases

Its a separate approval vote so wouldn't that require an explicit vote? Is
it so hard to vote over here as well?

   ...ant

On Jan 29, 2008 6:10 PM, Craig L Russell <[EMAIL PROTECTED]> wrote:

> As long as the vote was for the *same artifact*, I don't see what
> difference it makes *where* the vote was posted.
>
> Craig
>
> On Jan 28, 2008, at 11:20 PM, ant elder wrote:
>
> > I'm not sure those votes on cxf-dev count in this vote unless they
> > vote in
> > this thread, no mater though as there are enough votes here now.
> >
> >   ...ant
> >
> > On Jan 26, 2008 5:56 PM, Daniel Kulp <[EMAIL PROTECTED]> wrote:
> >
> >>
> >>
> >> Just a quick update while the vote is open.
> >>
> >> Jim Jagielski and Jeff Genender both voted +1 on the thread on cxf-
> >> dev.
> >> Thus, that's two additional binding IPMC votes.   Vote is still
> >> open :-)
> >>
> >> Dan
> >>
> >>
> >> On Friday 25 January 2008, Daniel Kulp wrote:
> >>> We held a vote on cxf-dev to release a new version of CXF. This
> >>> version is pretty much just a big "bug fix rollup" compared to 2.0.3
> >>> fixing over 50 JIRA issues reported by users and bugs encountered
> >>> during some interop testing.
> >>>
> >>> For a full list of the issues, see:
> >>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=1231285
> >>> 5&styleName=Html&projectId=12310511&Create=Create
> >>>
> >>> The vote thread is at:
> >>> http://www.nabble.com/-VOTE--Release-CXF-2.0.4-incubator-to15025947.ht
> >>> ml
> >>>
> >>> In summary, we have 11 +1 votes,  no 0 or -1 votes.  Two of the
> >>> votes
> >>> are from ASF members (bsnyder and gnodet).   I'm not sure if they
> >>> are
> >>> binding yet or not.  (I think they both sent in requests to join the
> >>> IPMC, just not sure if that is finished yet).
> >>>
> >>>
> >>> The staging area is at:
> >>> http://people.apache.org/~dkulp/stage_cxf/2.0.4-incubator<http://people.apache.org/%7Edkulp/stage_cxf/2.0.4-incubator>
> <http://people.apache.org/%7Edkulp/stage_cxf/2.0.4-incubator
> >>> >
> >>>
> >>>
> >>> The distributions are in the "dist" directory. The "m2repo"
> >>> directory
> >>> contains the stuff that will by pushed to the
> >>> m2-incubating-repository.
> >>>
> >>> This release is tagged at:
> >>> http://svn.apache.org/repos/asf/incubator/cxf/tags/cxf-2.0.4-incubator
> >>> /
> >>>
> >>> We and our users appreciate you taking the time to look over this
> >>> release!
> >>
> >>
> >>
> >> --
> >> J. Daniel Kulp
> >> Principal Engineer, IONA
> >> [EMAIL PROTECTED]
> >> http://www.dankulp.com/blog
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
>
> Craig Russell
> Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
> 408 276-5638 mailto:[EMAIL PROTECTED]
> P.S. A good JDO? O, Gasp!
>
>

Re: [VOTE] Please approve Tuscany SCA Java 1.1-incubating release (RC3a)

[ant elder]

+1

   ...ant

On Jan 28, 2008 5:31 PM, Simon Laws <[EMAIL PROTECTED]> wrote:

>  Hi,
>
> The previous VOTE thread here for SCA Java 1.1-incubating identified some
> issues.
>
> http://www.mail-archive.com/general@incubator.apache.org/msg16483.html
>
> A new release candidate (RC3a) has been created addressing the issues as
> discussed in the previous thread. I'm starting this IPMC VOTE thread in
> parallel with the project vote thread as the material content of the
> release
> hasn't changed significantly and I don't want to delay before getting IPMC
> eyeballs on it.
>
> The ongoing thread in the Tuscany community can be found here
>
> http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg27401.html
>
> The release includes a set of bug-fixes and new function such as the
> implementation of binding.jms. You can see a list of changes at:
>
>
> http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3a/distribution/src/main/release/CHANGES
>
> The signed binary and source distributions, the RAT reports, and the Maven
> staging repository are listed at the following links.
>
> SVN Tag:
> http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.1-RC3a/
>
> Stage maven repo:
> http://people.apache.org/~slaws/tuscany/1.1-RC3a/maven/
> 
>
> RAT report:
> http://people.apache.org/~slaws/tuscany/1.1-RC3a/rat-1.1-RC3a.txt
> 
>
> Binary and source distros (zip/gz/asc/md5) :
> http://people.apache.org/~slaws/tuscany/1.1-RC3a/
> 
>
> Please review and approve the release. This vote will remain open for at
> least 72 hours.
>
> Thank you for your attention,
>
> Simon
>

Re: "Binding" term

[ant elder]

On Jan 31, 2008 5:40 AM, Noel J. Bergman <[EMAIL PROTECTED]> wrote:

> > and only the PPMC member votes are binding.
>
> The error is the use of PPMC.  It should say that only PMC member votes
> are binding.
>
>--- Noel
>

Now I'm confused. If it says "only PMC member votes are binding" does that
mean Incubator PMC? Wouldn't that mean the vote on the dev list needs three
Incubator PMC +1s before the Incubator general list vote can be started? If
thats what we want would it be easier to just forget about the dev list vote
and have a single vote on the Incubator general list?

   ...ant

Account Request - Giorgio Zoppi - Tuscany (incubating)

[ant elder]

Dear root,

Please create an id for Giorgio Zoppi on the Tuscany project under
Incubation.

Preferred userid:  giorgio or 2nd choice gzoppi
Full name:   Giorgio Zoppi
Forwarding email address:[EMAIL PROTECTED]
Requested Karma for:  ws-tuscany

ICLA is on file.

Votes:

tuscany-private, March 17, Message-ID: <
[EMAIL PROTECTED]>

incubator-private, March 26, Message-ID: <
[EMAIL PROTECTED]>

Many thanks,

   ...ant

[VOTE] Approve the 1.1 release of Tuscany SDO

[ant elder]

Please vote to approve the 1.1 release of Tuscany SDO.

This is RC4 fixing the issues found in the previous RC2. The release
artifacts including source and binary distributions, maven staging
repository, and RAT report are at:
http://people.apache.org/~antelder/tuscany/sdo/1.1-rc4a

The tag for the release is at:
https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.1/

KEYS file is at: https://svn.apache.org/repos/asf/incubator/tuscany/KEYS

The tuscany-dev list vote thread is at:
http://apache.markmail.org/message/xgaeb7klnsfdkrmx

Many thanks,

   ...ant

Re: [VOTE] Approve the 1.1 release of Tuscany SDO

[ant elder]

Should have voted myself, so +1.

Anyone else able to review and vote on this?

   ...ant

On Mon, Apr 7, 2008 at 12:10 AM, ant elder <[EMAIL PROTECTED]> wrote:

> Please vote to approve the 1.1 release of Tuscany SDO.
>
> This is RC4 fixing the issues found in the previous RC2. The release
> artifacts including source and binary distributions, maven staging
> repository, and RAT report are at:
> http://people.apache.org/~antelder/tuscany/sdo/1.1-rc4a<http://people.apache.org/%7Eantelder/tuscany/sdo/1.1-rc4a>
>
> The tag for the release is at:
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.1/
>
> KEYS file is at: https://svn.apache.org/repos/asf/incubator/tuscany/KEYS
>
> The tuscany-dev list vote thread is at:
> http://apache.markmail.org/message/xgaeb7klnsfdkrmx
>
> Many thanks,
>
>...ant
>
>

Re: Graduate Tuscany as a top level project

[ant elder]

On Thu, Apr 10, 2008 at 4:31 PM, William A. Rowe, Jr. <[EMAIL PROTECTED]>
wrote:

> Robert Burrell Donkin wrote:
>
> >
> > i've been a passive subscriber to the tuscany list for quite a while
> > now and to me, from the lists, it feels like an open community
> >
>
> It's been a while since we discussed this.
>
> I'm very curious where Tuscany stands - in terms of viably graduating
> at this point.  The one apparent issue is diversity - but I don't think
> we want to continue using that as a cudgel - in fact I think we are
> going to get very 'full' here at the Incubator if we have unrealistic
> expectations.
>
>
> Can someone fill me in on how many non-IBM PPMC members now participate?
>
> Bill
>

The complete PPMC list is being maintained on the graduation proposal wiki
page -
http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Draft+TLP+Resolution

So thats 15 members, currently 3 non-IBMers. However there have been
regularly new committers added so I expect there may be other non-IBMer
committers we will add to that PPMC list before our next graduation attempt
(which i expect wont be so long away, we are actively thinking about it...).

   ...ant

Re: Graduate Tuscany as a top level project

[ant elder]

On Thu, Apr 10, 2008 at 7:07 PM, Matthieu Riou <[EMAIL PROTECTED]>
wrote:

> On 4/10/08, ant elder <[EMAIL PROTECTED]> wrote:
> >
> > On Thu, Apr 10, 2008 at 4:31 PM, William A. Rowe, Jr. <
> [EMAIL PROTECTED]
> > >
> > wrote:
> >
> >
> > > Robert Burrell Donkin wrote:
> > >
> > > >
> > > > i've been a passive subscriber to the tuscany list for quite a while
> > > > now and to me, from the lists, it feels like an open community
> > > >
> > >
> > > It's been a while since we discussed this.
> > >
> > > I'm very curious where Tuscany stands - in terms of viably graduating
> > > at this point.  The one apparent issue is diversity - but I don't
> think
> > > we want to continue using that as a cudgel - in fact I think we are
> > > going to get very 'full' here at the Incubator if we have unrealistic
> > > expectations.
> > >
> > >
> > > Can someone fill me in on how many non-IBM PPMC members now
> participate?
> > >
> > > Bill
> > >
> >
> >
> > The complete PPMC list is being maintained on the graduation proposal
> wiki
> > page -
> >
> >
> http://cwiki.apache.org/confluence/display/TUSCANYWIKI/Draft+TLP+Resolution
> >
> > So thats 15 members, currently 3 non-IBMers. However there have been
> > regularly new committers added so I expect there may be other non-IBMer
> > committers we will add to that PPMC list before our next graduation
> > attempt
> > (which i expect wont be so long away, we are actively thinking about
> > it...).
>
>
> You should also mention people who happen to work for IBM but are not
> working on Tuscany as part of their daily job.
>
> Cheers,
> Matthieu
>
>   ...ant
> >


That would make the PPMC be about 50%  IBM day job  and 50% (non IBMers or
IBM non-day jobers). Can we take it to a private list if anyone wants a
detailed breakdown?

   ...ant

Re: [VOTE] Approve the 1.1 release of Tuscany SDO

[ant elder]

On Fri, Apr 11, 2008 at 2:08 AM, Kevan Miller <[EMAIL PROTECTED]>
wrote:



For files without src license headers, I was referring to files like:
>
>
>  
> ==C:/Tuscany/Distros/SDO/1.1-rc4a/tuscany-sdo-1.1-incubating-src/impl/model/SDO.mdl
>
>  
> ==C:/Tuscany/Distros/SDO/1.1-rc4a/tuscany-sdo-1.1-incubating-src/impl/src/test/resources/customer1.xml
> ...
>
> Looks like most are test files. I won't quibble much about the test files.
> Easiest (in the long run) to add license headers, IMO. Not sure what to make
> of the SDO.mdl file.
>

For the .mdl one I believe it has not yet been found how to generate it
including the header, the few test files that don't include it i think may
need the files without header for the tests, either way, I don't think its a
blocking problem for those test files and they're covered by the top level
LICENSE and don't contain much much IP, eg:
https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.1/impl/src/test/resources/customer1.xml

   ...ant

Re: [VOTE] Approve the 1.1 release of Tuscany SDO

[ant elder]

On Fri, Apr 11, 2008 at 2:35 AM, sebb <[EMAIL PROTECTED]> wrote:

> On 11/04/2008, Kevan Miller <[EMAIL PROTECTED]> wrote:
> >
> >  On Apr 10, 2008, at 8:42 PM, Luciano Resende wrote:
> >
> >
> > > The files that have this license are listed in the LICENSE [1] file
> > > (search for "Apache Tuscany SDO for Java Subcomponents") and I also
> > > see a mention of osoa.org in the NOTICE [2].
> > >
> > > Is this what you were looking for ?
> > >
> >
> >  For files without src license headers, I was referring to files like:
> >
> >
> >
> ==C:/Tuscany/Distros/SDO/1.1-rc4a/tuscany-sdo-1.1-incubating-src/impl/model/SDO.mdl
> >
> >
> ==C:/Tuscany/Distros/SDO/1.1-rc4a/tuscany-sdo-1.1-incubating-src/impl/src/test/resources/customer1.xml
> >  ...
> >
> >  Looks like most are test files. I won't quibble much about the test
> files.
> > Easiest (in the long run) to add license headers, IMO. Not sure what to
> make
> > of the SDO.mdl file.
> >
> >  Yes, I saw the simple osoa.org attribution in the notice file. However,
> IMO
> > that is not sufficient. I think the NOTICE should contain the copyright
> info
> > and I believe the OSOA license requires it. From the OSOA license:
> >
> >  1.A link or URL to the Artifacts at this location:
> > http://www.osoa.org/display/Main/Service+Data+Objects+Specifications
> >
> >  2.The full text of this copyright notice as shown in the Artifacts.
> >
> >  I would add both of those to the NOTICE file.
> >
>
> The NOTICE file is for attributions only.
>
> The rest goes in the LICENSE file, as has already been done


This was our understanding too which is why its been changed to be this way.

Have these replies clarified things enough, any further comments...or votes?

   ...ant

[RESULT][VOTE] Approve the 1.1 release of Tuscany SDO

[ant elder]

Passed with +1s from Matthieu, Paul, and me.

Thanks for the reviews everyone.

   ...ant

On Mon, Apr 7, 2008 at 12:10 AM, ant elder <[EMAIL PROTECTED]> wrote:

> Please vote to approve the 1.1 release of Tuscany SDO.
>
> This is RC4 fixing the issues found in the previous RC2. The release
> artifacts including source and binary distributions, maven staging
> repository, and RAT report are at:
> http://people.apache.org/~antelder/tuscany/sdo/1.1-rc4a<http://people.apache.org/%7Eantelder/tuscany/sdo/1.1-rc4a>
>
> The tag for the release is at:
> https://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sdo/1.1/
>
> KEYS file is at: https://svn.apache.org/repos/asf/incubator/tuscany/KEYS
>
> The tuscany-dev list vote thread is at:
> http://apache.markmail.org/message/xgaeb7klnsfdkrmx
>
> Many thanks,
>
>...ant
>
>

Re: [Proposal] NoNameYet aka Davos

[ant elder]

On Mon, Apr 14, 2008 at 5:10 PM, Noel J. Bergman <[EMAIL PROTECTED]> wrote:
> > There is a discussion going on Tuscany dev list whether the SDO part of
>  > the community would like to join the new project in the event it will
>  > get approved in incubation. Once there is a consensus, Kelvin will
>  > update the proposal.
>
>  > Also, we think we found a name for the project: Davos. It contains the
>  > sdo letters; it's simple, easy to remember and we hope everyone will
>  > like it.
>
>  Status?
>
> --- Noel
>

I gather its not going to be taken any further.

  ...ant

[ANNOUNCE] Apache Tuscany Java SDO 1.1 released

[ant elder]

The Apache Tuscany team are pleased to announce the 1.1-incubating
release of the Java SDO project.

Service Data Objects (SDO) are designed to simplify and unify the way
in which applications handle data. Using SDO, application programmers
can uniformly access and manipulate data from heterogeneous data
sources, including relational databases, XML data sources, Web
services, and enterprise information systems. Tuscany SDO provides an
implementation of the SDO 2.1 specification, this 1.1 release includes
several new features and improvements over the 1.0 release such as:

- the ability to generate SDO test classes using the maven-sdo-plugin
- support for custom data binding of DataObjects in a Swing UI
- Using the HelperContext for scope in the Tuscany API
- improved diagnostics

along with many bug fixes. See the RELEASE_NOTES for full details.

For more information and to download the SDO 1.1 release please go to:
http://incubator.apache.org/tuscany/sdo-java-releases.html

Apache Tuscany welcomes your help. Any contribution, including code,
testing, improving the documentation, or bug reporting is always
appreciated. For more information on how to get involved in Apache
Tuscany visit the website at: http://incubator.apache.org/tuscany.

Thank you for your interest in Apache Tuscany!
The Apache Tuscany Team.
---

Tuscany is an effort undergoing incubation at the Apache Software Foundation
(ASF), sponsored by the Apache Web services PMC. Incubation is required of
all newly accepted projects until a further review indicates that the
infrastructure, communications, and decision making process have stabilized
in a manner consistent with other successful ASF projects. While incubation
status is not necessarily a reflection of the completeness or stability of
the code, it does indicate that the project has yet to be fully endorsed by
the ASF.

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

Re: [Proposal] NoNameYet aka Davos

[ant elder]

On Mon, Apr 14, 2008 at 7:54 PM, Noel J. Bergman <[EMAIL PROTECTED]> wrote:

> ant elder wrote:
>
> > Noel J. Bergman wrote:
> > > > There is a discussion going on Tuscany dev list whether the SDO part
> of
> > > > the community would like to join the new project in the event it
> will
> > > > get approved in incubation. Once there is a consensus, Kelvin will
> > > > update the proposal.
> > >
> > > Status?
> >
> > I gather its not going to be taken any further.
>
> Oh?  That's a surprise.  We'd been given the impression that all was well,
> and that the Tuscany SDO folks were looking forward to joining the new
> project.  Is there explanation on the Tuscany list?
>

I think there was consensus with the Tuscany folks to join the new project
if it went ahead, but after assessing all the discussions and feedback from
the Incubator it was decided to not to go ahead with the proposal. The
others involved may have more detailed comments but thats about the sum of
it.

   ...ant

Re: Graduate Tuscany as a top level project

[ant elder]

On Sun, Apr 13, 2008 at 12:30 PM, Robert Burrell Donkin <
[EMAIL PROTECTED]> wrote:

> On Thu, Apr 10, 2008 at 9:27 PM, ant elder <[EMAIL PROTECTED]> wrote:
>
> 
>
> >  That would make the PPMC be about 50%  IBM day job  and 50% (non IBMers
> or
> >  IBM non-day jobers). Can we take it to a private list if anyone wants a
> >  detailed breakdown?
>
> +1
>
> IMO the IPMC is wrong to ask for named affiliations in public.
> contractual information is potentially confidential and should be
> discussed only in private. all that should be needed in public are
> aggregate statistics.
>
> IMHO the emphasis on committer affiliation is misguided. overloading
> the word diversity was also probably a mistake. maybe we need to focus
> on narrower concepts with alternative names.
>
> 1. the incubator should be concerned about the composition of the
> proposed PMC. PMC conveys voting rights and control of the project
> going forward. independent committers are fine but if these are not
> being enfranchised then this should be a concern. so the aggregation
> distribution of affiliations of PPMC members should be of interest. i
> don't care what the affliation is, just the aggregate stats.
>
> 2. for a top level project to succeed, it needs to be able to
> encrourage, recruit and mentor new independent developers. unless a
> project demonstrates the ability to recruit new independent
> developers, it is not ready to graduate. so, i would like to know how
> many new independent committers the project has developed, am
> interested in the quantity of code they've contributed and whether
> they are on the PPMC. again, i don't care about their affiliations.
>

Some answers to these:

Here is the timeline of new committers additions to Tuscany:

2008-04-16 Vote to add Wang Feng as Tuscany committer
2008-03-26 Vote to add Giorgio Zoppi as Tuscany committer
2007-11-19 Vote to add Rajini Sivaram as Tuscany committer
2007-11-01 Vote to add Mark Combellack as Tuscany committer
2007-10-21 Vote to add Michael Yoder as Tuscany committer
2007-10-08 Vote to add Amita Vadhavkar as a new committer
2007-09-19 Vote to add Simon Nash as a new committer
2007-08-21 Vote to add Brady Johnson as a new committer
2007-07-12 Vote to add Fuhwei Lwo as a new committer
2007-05-01 Vote to add Andy Grove as a new committer
2007-04-03 Vote to add Adriano Crestani as a new committer
2007-01-22 Vote to add Simon Laws as a new committer
2006-11-15 Vote to add Geoffrey Winn as a new committer
2006-11-10 Vote to add Luciano Resende as a new commiter
2006-11-07 Vote to add Rajith Attapattu
2006-09-29 Vote to add Ignacio Silva-Lepe as a new committer
2006-09-18 Vote to add Venkata Krishnan as a new committer
2006-08-10 Vote to add Andrew Borley as a new committer
2006-08-07 Vote to add Meeraj Kunnumpurath as a new committer
2006-08-07 Vote to add Kelvin Goodson as a new committer
2006-08-06 Vote to add Brent Daniel as a new committer
2006-08-04 Vote to add Raymond Feng as a new committer
2006-05-02 Vote to add Dan Kulp as a new committer
2006-03-01 Vote to add Ant Elder as a new committer

So thats 24 new committers over the two and a bit years of incubation, about
one new committer every month or two. Of those, 12 were IBMers, 12 were
independents or non-paid job IBMers. The actual quantity of code each of
those have done is harder to say but using the dates on that list if you
trawl around in the tuscany-private archives you can see the discussion
around each nomination and I think be satisfied each was justified. Not all
those have become PPMC members (yet), some committers don't stay active and
we've had PPMC membership take a little longer and require a bit more
commitment to the project, but as mentioned earlier on this thread the
Tuscany PPMC currently has 15 members, about 50%  IBM day job and 50% (non
IBMers or IBM non-day jobers).

   ...ant

Re: Graduate Tuscany as a top level project

[ant elder]

On Wed, Apr 16, 2008 at 10:47 AM, William A. Rowe, Jr. <[EMAIL PROTECTED]>
wrote:

> On Sunday 13 April 2008 19:30, Robert Burrell Donkin wrote:
> >
> > > IMHO the emphasis on committer affiliation is misguided. overloading
> > > the word diversity was also probably a mistake. maybe we need to focus
> > > on narrower concepts with alternative names.
> > >
> > > 1. the incubator should be concerned about the composition of the
> > > proposed PMC.
> > >
> >
> Only that the community will be welcoming to newcomers and not treat the
> ASF community-project as the "company's private project"; e.g. stdcxx is
> largely one company, yet and still they brought across 2 mentors (Justin
> and myself) to ensure we continue to foster community with the stdcxx
> user community.  A good c++ programmer/open source library user is always
> a potential patch contributor, more akin to apr, and very unlike httpd,
> and we see those users to become potential contributors.
>
> Niclas Hedhman wrote:
> >
>
> > Also, my personal and highly subjective interpretation of the (if
> > present) intent around diversity boils down to one scenario;
> >
> > * A company pulls the plug for paid developers - will the project
> > survive?
> >
>
> Actually I think we are far too obsessed with the prospects of letting
> a given project or podling die.  So the project passes into lethargy
> and it's time ends, what's really so "negative" about that?  We don't
> hold committers to the grindstone, why should we treat employer sponsored
> committers any differently?
>
>  So, for the case of Tuscany; I am satisfied with the diversity goal, and
> > encourage Tuscany community with the aid of Mentors to move for graduation.
> >
>
> ++1
>

So it seems like there is better support for Tuscany graduation now, are
there any other issues or concerns anyone would like to bring up before we
do make another attempt?

   ...ant

Re: [VOTE] Approve release Apache UIMA 2.2.2-incubating

[ant elder]

Looks ok to me, +1

   ...ant

On Thu, Apr 17, 2008 at 9:50 AM, Thilo Goetz <[EMAIL PROTECTED]> wrote:

> Folks, just a quick reminder that this vote is still
> open.  Please vote if you can find the time to look
> at our release.  Thanks.
>
> --Thilo
>
>
> Michael Baessler wrote:
>
> > The Apache UIMA committers ask the Apache Incubator PMC for permission
> > to publish a new bug fix
> > release of Apache UIMA version 2.2.2. This release contains bug fixes of
> > for release version 2.2.1
> > that was published in December 2007. For details about the fixes, please
> > have a look at the release
> > notes.
> >
> > We had a vote on uima-dev that resulted in 6 binding +1s
> > (all the committers) and no 0s or -1s.  The vote thread
> > is here:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-uima-dev/200804.mbox/[EMAIL
> >  PROTECTED]
> >
> > Please review the release candidate here:
> > http://people.apache.org/~mbaessler/uimaj-2.2.2/05/
> >
> > There are subdirectories like:
> > /bin - contains the binary distribution files
> > /src - contains the source distribution files
> > /rat - contains the RAT reports (using RAT 0.5.1) with some comments
> >
> > The SVN tag for this release candidate is:
> >
> > https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-2.2.2/uimaj-2.2.2-05
> >
> > The KEYS file can be found in the SVN at:
> >
> > http://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk/uimaj-distr/src/main/readme/KEYS
> >
> > Please vote:
> > [ ] +1  Accept to release Apache UIMA 2.2.2
> > [ ] -1  No, because
> >
> > Thanks!
> >
> > -- Michael
> >
> >
> > -
> > 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]
>
>

More timely release reviews? (was: Re: [VOTE] Approve release Apache UIMA 2.2.2-incubating

[ant elder]

The poor UIMA guys have been trying to get this release approved for nearly
two weeks now and it still has just a single vote. Could a couple of other
IPMCers take a look and vote?

   ...ant

On Fri, Apr 18, 2008 at 2:22 PM, Marshall Schor <[EMAIL PROTECTED]> wrote:

> Hello Incubator PMC -
>
> Thank you for your reviews of this; please do not confuse this with
> another release vote just posted for the UIMA Add-on package, which is
> another piece of the project, moving forward under a separate packaging and
> vote.
>
> For this vote, so far we have 1 +1 vote (only).  Could some others please
> review and cast their votes?
>
> Thanks again. -Marshall Schor
>
>
> Michael Baessler wrote:
>
> > The Apache UIMA committers ask the Apache Incubator PMC for permission
> > to publish a new bug fix
> > release of Apache UIMA version 2.2.2. This release contains bug fixes of
> > for release version 2.2.1
> > that was published in December 2007. For details about the fixes, please
> > have a look at the release
> > notes.
> >
> > We had a vote on uima-dev that resulted in 6 binding +1s
> > (all the committers) and no 0s or -1s.  The vote thread
> > is here:
> >
> > http://mail-archives.apache.org/mod_mbox/incubator-uima-dev/200804.mbox/[EMAIL
> >  PROTECTED]
> >
> > Please review the release candidate here:
> > http://people.apache.org/~mbaessler/uimaj-2.2.2/05/
> >
> > There are subdirectories like:
> > /bin - contains the binary distribution files
> > /src - contains the source distribution files
> > /rat - contains the RAT reports (using RAT 0.5.1) with some comments
> >
> > The SVN tag for this release candidate is:
> >
> > https://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-2.2.2/uimaj-2.2.2-05
> >
> > The KEYS file can be found in the SVN at:
> >
> > http://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk/uimaj-distr/src/main/readme/KEYS
> >
> > Please vote:
> > [ ] +1  Accept to release Apache UIMA 2.2.2
> > [ ] -1  No, because
> >
> > Thanks!
> >
> > -- Michael
> >
> >
> > -
> > 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: [VOTE] Approve the release of Tuscany Java SCA 1.2-incubating

[ant elder]

+1

   ...ant

On Thu, Apr 17, 2008 at 4:07 PM, Luciano Resende <[EMAIL PROTECTED]>
wrote:

> The Apache Tuscany project request IPMC permission to release the Java
> SCA 1.2-incubating. The vote thread is here ...
>
> http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg30405.html
>
> The artifacts are available for review at:
> http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/
>
> This includes the signed binary and source distributions, the RAT report,
> and the Maven staging repository.
>
> The eclipse updatesite for the Tuscany Eclipse plugins is available at:
> http://people.apache.org/~lresende/tuscany/sca-1.2-RC4/updatesite/
>
> The release tag is available at :
> http://svn.apache.org/repos/asf/incubator/tuscany/tags/java/sca/1.2-RC4/
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende 
> http://lresende.blogspot.com/
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: Graduate Tuscany as a top level project

[ant elder]

On Wed, Apr 16, 2008 at 11:24 AM, ant elder <[EMAIL PROTECTED]> wrote:

>
>
> On Wed, Apr 16, 2008 at 10:47 AM, William A. Rowe, Jr. <
> [EMAIL PROTECTED]> wrote:
>
> >  On Sunday 13 April 2008 19:30, Robert Burrell Donkin wrote:
> > >
> > > > IMHO the emphasis on committer affiliation is misguided. overloading
> > > > the word diversity was also probably a mistake. maybe we need to
> > > > focus
> > > > on narrower concepts with alternative names.
> > > >
> > > > 1. the incubator should be concerned about the composition of the
> > > > proposed PMC.
> > > >
> > >
> > Only that the community will be welcoming to newcomers and not treat the
> > ASF community-project as the "company's private project"; e.g. stdcxx is
> > largely one company, yet and still they brought across 2 mentors (Justin
> > and myself) to ensure we continue to foster community with the stdcxx
> > user community.  A good c++ programmer/open source library user is
> > always
> > a potential patch contributor, more akin to apr, and very unlike httpd,
> > and we see those users to become potential contributors.
> >
> > Niclas Hedhman wrote:
> > >
> >
> > > Also, my personal and highly subjective interpretation of the (if
> > > present) intent around diversity boils down to one scenario;
> > >
> > > * A company pulls the plug for paid developers - will the project
> > > survive?
> > >
> >
> > Actually I think we are far too obsessed with the prospects of letting
> > a given project or podling die.  So the project passes into lethargy
> > and it's time ends, what's really so "negative" about that?  We don't
> > hold committers to the grindstone, why should we treat employer
> > sponsored
> > committers any differently?
> >
> >  So, for the case of Tuscany; I am satisfied with the diversity goal,
> > > and encourage Tuscany community with the aid of Mentors to move for
> > > graduation.
> > >
> >
> > ++1
> >
>
> So it seems like there is better support for Tuscany graduation now, are
> there any other issues or concerns anyone would like to bring up before we
> do make another attempt?
>
>...ant
>
>
FYI, we've now started the tuscany-dev vote for doing this:
http://apache.markmail.org/message/6bduwmwuhntbjafu

   ...ant

Re: [VOTE] Approve release Apache UIMA Annotator Add-on package version 2.2.2-incubating

[ant elder]

+1 from me too. Had reviewed this last week but must have forgotten to post
the vote.

   ...ant

On Wed, Apr 30, 2008 at 4:12 PM, Sam Ruby <[EMAIL PROTECTED]> wrote:

> On Thu, Apr 17, 2008 at 11:58 AM, Michael Baessler
> <[EMAIL PROTECTED]> wrote:
> > The Apache UIMA project ask the Apache Incubator PMC for permission to
> publish the
> >  first UIMA Sandbox annotator release. The UIMA Sandbox is place for
> contributions from the community
> >  and hosts components like annotators (UIMA analysis components) and
> tooling around UIMA.
> >
> >  We now want to ship the first version of the UIMA Annotator Add-on
> package, version 2.2.2, that is
> >  based to UIMA core release version 2.2.2.
> >
> >  We had a vote on uima-dev that resulted in 5 binding +1s
> >  (all the committers), one 0s and no -1s.  The vote thread
> >  is here:
> >
> http://mail-archives.apache.org/mod_mbox/incubator-uima-dev/200804.mbox/[EMAIL
>  PROTECTED]
>
> +1 for release
>
> - Sam Ruby
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Account Request - Feng Wang - Tuscany (incubating)

[ant elder]

Dear root,

Please create an id for  Feng Wang on the Tuscany project under Incubation.

Preferred userid:   fwang
Full name:   Feng Wang
Forwarding email address:[EMAIL PROTECTED]
Requested Karma for:  ws-tuscany

ICLA is on file.

Votes:

tuscany-private, April 12, Message-ID: <[EMAIL PROTECTED]>

incubator-private, April 16, Message-ID: <
[EMAIL PROTECTED]>

Many thanks,

   ...ant

[VOTE] Apache Tuscany Graduation as TLP

[ant elder]

After 29 months in the incubator, 19 releases, 25 new committers, and
tons of emails the Apache Tuscany community (with support from our
mentors) again feels that we are ready to graduate to an official top
level project at Apache as indicated by the community vote recorded
at: http://apache.markmail.org/message/lss5jhjxail7m67r

We would like the resolution below to be presented to the board for
consideration at the next possible board meeting.

For additional information, the Tuscany status file is here:
https://svn.apache.org/repos/asf/incubator/tuscany/STATUS

Thanks in advance for your time and consideration.

   ...ant

X. Establish the Apache Tuscany Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the Foundation's
purpose to establish a Project Management Committee charged with
the creation and maintenance of open-source software for
distribution at no charge to the public, that simplifies the
development, deployment and management of distributed applications
built as compositions of service components. These components
may be implemented with a range of technologies and connected
using a variety of communication protocols. This software will
implement relevant open standards including, but not limited to,
the Service Component Architecture standard defined by the OASIS
OpenCSA member section, and related technologies.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the "Apache Tuscany Project",
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache Tuscany Project be and hereby is
responsible for the creation and maintenance of software
related to Apache Tuscany;
and be it further

RESOLVED, that the office of "Vice President, Apache Tuscany" be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache Tuscany Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache Tuscany Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache Tuscany Project:

* Adriano Crestani 
* ant elder 
* Brady Johnson 
* Frank Budinsky 
* Ignacio Silva-Lepe 
* Jean-Sebastien Delfino 
* kelvin goodson 
* Luciano Resende 
* Mark Combellack 
* Matthieu Riou 
* Mike Edwards 
* Paul Fremantle 
* Pete Robbins 
* Raymond Feng 
* Simon Laws 
* Simon Nash 
* Venkata Krishnan 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder
be appointed to the office of Vice President, Apache Tuscany, to
serve in accordance with and subject to the direction of the
Board of Directors and the Bylaws of the Foundation until
death, resignation, retirement, removal or disqualification,
or until a successor is appointed; and be it further

RESOLVED, that the Apache Tuscany Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator Tuscany podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator Tuscany podling encumbered upon the Apache Incubator
Project are hereafter discharged.

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

Account Request - Mario Antollini- Tuscany (incubating)

[ant elder]

Dear root,

Please create an id for Mario Antollini on the Tuscany project under Incubation.

Preferred userid:  antollinim
Full name:  Mario Antollini
Forwarding email address:[EMAIL PROTECTED]
Requested Karma for:  ws-tuscany

ICLA is on file.

Votes:

tuscany-private, April 21, Message-ID:
<[EMAIL PROTECTED]>

incubator-private, April 25, Message-ID:
<[EMAIL PROTECTED]>

Many thanks,

   ...ant

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

[RESULT][VOTE] Apache Tuscany Graduation as TLP

[ant elder]

Its been 5 days now so I'm going to call this...passed with 19 +1s from:

Noel J. Bergman, Carl Trieloff, Niklas Gustavsson, Robert Burrell Donkin,
Niall Pemberton, Jean T. Anderson, Craig L Russell, Paul Fremantle, Kevan
Miller, Guillaume Nodet, Vamsavardhana Reddy, Sam Ruby, Martijn Dashorst,
Matthieu Riou, Davanum Srinivas, William A. Rowe, Jr., Bertrand Delacretaz

Many many thanks to everyone for all the help during the incubation.

   ...ant

On Wed, May 14, 2008 at 7:51 PM, ant elder <[EMAIL PROTECTED]> wrote:

> After 29 months in the incubator, 19 releases, 25 new committers, and
> tons of emails the Apache Tuscany community (with support from our
> mentors) again feels that we are ready to graduate to an official top
> level project at Apache as indicated by the community vote recorded
> at: http://apache.markmail.org/message/lss5jhjxail7m67r
>
> We would like the resolution below to be presented to the board for
> consideration at the next possible board meeting.
>
> For additional information, the Tuscany status file is here:
> https://svn.apache.org/repos/asf/incubator/tuscany/STATUS
>
> Thanks in advance for your time and consideration.
>
>   ...ant
>
> X. Establish the Apache Tuscany Project
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the Foundation's
> purpose to establish a Project Management Committee charged with
> the creation and maintenance of open-source software for
> distribution at no charge to the public, that simplifies the
> development, deployment and management of distributed applications
> built as compositions of service components. These components
> may be implemented with a range of technologies and connected
> using a variety of communication protocols. This software will
> implement relevant open standards including, but not limited to,
> the Service Component Architecture standard defined by the OASIS
> OpenCSA member section, and related technologies.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Tuscany Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Tuscany Project be and hereby is
> responsible for the creation and maintenance of software
> related to Apache Tuscany;
> and be it further
>
> RESOLVED, that the office of "Vice President, Apache Tuscany" be
> and hereby is created, the person holding such office to
> serve at the direction of the Board of Directors as the chair
> of the Apache Tuscany Project, and to have primary responsibility
> for management of the projects within the scope of
> responsibility of the Apache Tuscany Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Tuscany Project:
>
>* Adriano Crestani 
>* ant elder 
>* Brady Johnson 
>* Frank Budinsky 
>* Ignacio Silva-Lepe 
>* Jean-Sebastien Delfino 
>* kelvin goodson 
>* Luciano Resende 
>* Mark Combellack 
>    * Matthieu Riou 
>* Mike Edwards 
>* Paul Fremantle 
>* Pete Robbins 
>* Raymond Feng 
>* Simon Laws 
>* Simon Nash 
>* Venkata Krishnan 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ant Elder
> be appointed to the office of Vice President, Apache Tuscany, to
> serve in accordance with and subject to the direction of the
> Board of Directors and the Bylaws of the Foundation until
> death, resignation, retirement, removal or disqualification,
> or until a successor is appointed; and be it further
>
> RESOLVED, that the Apache Tuscany Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Tuscany podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache
> Incubator Tuscany podling encumbered upon the Apache Incubator
> Project are hereafter discharged.
>

Fwd: Graduation

[ant elder]

Forwarding for those not on tuscany-dev...

Congratulations everyone and a very big thank you to our mentors and all the
incubator folks for their help and guidance during the incubation, wouldn't
have made it without you.

   ...ant

-- Forwarded message --
From: Matthieu Riou <[EMAIL PROTECTED]>
Date: Wed, May 21, 2008 at 10:14 PM
Subject: Graduation
To: tuscany-dev <[EMAIL PROTECTED]>


"Special order 7B, Establish the Apache Tuscany Project, was approved by
Unanimous Vote of the directors present."

Congratulations guys!

Matthieu

Re: [VOTE]: Buildr 1.3.1 release

[ant elder]

The NOTICE file in the distribution is missing the line "Copyright
[] The Apache Software Foundation" at the top of the file. Was
going to say thats a blocker but the doc at
http://www.apache.org/legal/src-headers.html only says "should" not
MUST so I guess its ok to just fix this for next time. Also the text
on the top four lines in the "=" box is a comment from the example
NOTICE file you shouldn't include that in your NOTICE file so the
lines should be deleted when the copyright line is added.

Otherwise all looks good to me so +1.

   ...ant

On Fri, May 23, 2008 at 3:29 AM, Assaf Arkin <[EMAIL PROTECTED]> wrote:
>
> This release is primarily to solve the installation problem on Windows
> due to unspecific dependency on RJB.  Other changes and solved issues
> in this release are listed below.
>
> The release vote passed within the PPMC with 3 +1:
> http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200805.mbox/[EMAIL
>  PROTECTED]
>
> We're voting on the source distributions available here:
> http://people.apache.org/~assaf/buildr/1.3.1/distro/
>
> Specifically:
> http://people.apache.org/~assaf/buildr/1.3.1/distro/buildr-1.3.1-incubating.tgz
> http://people.apache.org/~assaf/buildr/1.3.1/distro/buildr-1.3.1-incubating.zip
>
> The documentation generated for this release is available here:
> http://people.apache.org/~assaf/buildr/1.3.1/site/
> http://people.apache.org/~assaf/buildr/1.3.1/site/buildr.pdf
>
> The official specification against which this release was tested:
> http://people.apache.org/~assaf/buildr/1.3.1/site/specs.html
>
>
> Changes since 1.3.0:
> * Added: Downloading files from SFTP server, uploading to HTTP.
> * Added: jibx_bind method to use JiBX for Java<=>XML binding (by David
> Peterson).
> * Changed: Upgraded to Net::SSH 2.0 and Net::SFTP 2.0.
> * Fixed: BUILDR-67 HTTP GET now works with query parameters (Tommy Knowlton).
> * Fixed: BUILDR-68 Now accepting JAVA_HOME setting on OS X (Nathan Hamblen).
> * Fixed: JUnit now accepts java_args and passes these arguments to the JVM
> (only applicable when forking).
> * Fixed: BUILDR-70 JUnit not passing environment variables from the
> :environment option.
> * Fixed: BUILDR-75 Filter now runs if there's a target directory, even if
> there are no source files to copy over, since everyone else just checks
> resources.target for existence before depending on it.
> * Fixed: BUILDR-63 Possible fix.
>
> Assaf
>
> -
> 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: [VOTE] Approve hotfix 1 for Apache UIMA v2.2.2-incubating

[ant elder]

Looks ok to me, jar has good license/notice/disclaimer, signatures verify
etc.

+1

   ...ant

On Thu, Jul 10, 2008 at 9:07 AM, Thilo Goetz <[EMAIL PROTECTED]> wrote:

> Folks,
>
> this is just a small hotfix.  Could some kind
> IPMC souls please take a look?  Thanks!
>
> --Thilo
>
>
> Michael Baessler wrote:
>
>> The Apache UIMA committers ask the Apache Incubator PMC for permission to
>> publish a
>> hotfix for the UIMA core release v2.2.2-incubating.
>>
>> The hotfix release fp1 contains fixes for two UIMA memory issues of
>> release version
>> 2.2.2-incubating. The release just ships the jar that has been modified
>> and a readme that contains
>> the hotfix information. LICENSE, NOTICE, and DISCLAIMER files are inside
>> the Jar.
>>
>> The fixes made for this hotfix are based on a UIMA v2.2.2 branch with a
>> separate tag in SVN.
>> Release tag:
>>
>> http://svn.apache.org/repos/asf/incubator/uima/uimaj/tags/uimaj-2.2.2/uimaj-2.2.2-fp1-02
>> Hotfix source:
>>
>> http://svn.apache.org/repos/asf/incubator/uima/uimaj/branches/uimaj-2.2.2-01
>>
>> We had a vote on uima-dev that resulted in 6 binding +1s
>> (all the committers) and no 0s or -1s.  The vote thread is here:
>> http://www.mail-archive.com/[EMAIL PROTECTED]/msg07527.html
>>
>> Please review the release candidate at:
>> people.a.o/~mbaessler/uima-2.2.2-fp1/02
>> The package is just provided as zip since all the content (one jar) is
>> platform independent.
>>
>> The KEYS file can be found in the SVN at:
>>
>> http://svn.apache.org/repos/asf/incubator/uima/uimaj/trunk/uimaj-distr/src/main/readme/KEYS
>>
>> Please vote:
>> [ ] +1  Accept to release Apache UIMA 2.2.2-fp1-incubating
>> [ ] -1  No, because
>>
>> Thanks!
>>
>> -- Michael
>>
>> -
>> 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: [VOTE] Release Apache UIMA-AS 2.2.2-incubating

[ant elder]

+1

   ...ant

On Mon, Jun 30, 2008 at 8:57 PM, Marshall Schor <[EMAIL PROTECTED]> wrote:

> Hi Everyone,
>
> Please review and vote on approving the 1st release of Apache UIMA-AS, an
> add-on to base UIMA.  The release artifacts and the annotated RAT reports
> can be found here:
> http://people.apache.org/~schor/uima-release-candidates/uima-as/08
>
> UIMA-AS originally came to Apache under a software grant, and has an IP
> Clearance form recorded:
> http://incubator.apache.org/ip-clearance/uima-as.html and linked from
> http://incubator.apache.org/ip-clearance/index.html
>
> The UIMA project dev-list vote to release was 6 +1's, and no other votes;
> see the vote here: http://markmail.org/message/t6l2ineufbr3qo4g
>
> UIMA-AS adds a scaleout capability to base UIMA based on asynchronous
> messaging; it makes use of the recently released UIMA base 2.2.2-incubating
> level, as well as  Apache ActiveMQ and the Spring middleware framework (also
> licensed under the Apache v.2 license), internally.
>
> Because this release includes a distribution of parts of ActiveMQ, which in
> turn is classified as a 5D002 export, we submitted classification for
> UIMA-AS also as a 5D002 category.  The 
> http://apache.org/licenses/exports/page has been updated to reflect this.
>
> Thanks.  -Marshall
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE] Release Apache UIMA CasEditor-2.2.2-incubating

[ant elder]

+1

   ...ant

On Thu, Jul 3, 2008 at 10:52 AM, Jörn Kottmann <[EMAIL PROTECTED]> wrote:

> Hello,
>
> the Cas Editor is a text annotation tool which supports manual and
> automatic
> annotation of CAS files. It is now ready for its first release.
> Please review and vote for releasing the Apache Uima Cas Editor-2.2.2-02.
>
> The release artifacts and the rat reports can be found at:
> http://people.apache.org/~joern/CasEditor-2.2.2-02/
>
> On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to release
> it.
>
> The Cas Editor originally came to Apache under a software grant.
>
> Thanks,
> Jörn

Re: [VOTE]: Buildr 1.3.2 release

[ant elder]

Looks ok to me so +1.

Would be helpful to include a RAT report with the request, but I ran it
myself and it didn't highlight any issues.

If the doc pdf is going to be distributed separately it should probably
include the Incubator disclaimer text, maybe on the page which already has
the Apache License text.

   ...ant

On Mon, Jul 21, 2008 at 9:36 PM, Assaf Arkin <[EMAIL PROTECTED]> wrote:

> Up for vote, the Buildr 1.3.2 release.  The release vote passed within
> the PPMC with +3 (+5 including non-binding votes) and no -1:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-buildr-dev/200807.mbox/[EMAIL
>  PROTECTED]
>
>
> We're voting on the source distributions available here:
> http://people.apache.org/~assaf/buildr/1.3.2/distro/
>
> Specifically:
>
> http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.tgz
>
> http://people.apache.org/~assaf/buildr/1.3.2/distro/buildr-1.3.2-incubating.zip
>
> The documentation generated for this release is available here:
> http://people.apache.org/~assaf/buildr/1.3.2/site/
> http://people.apache.org/~assaf/buildr/1.3.2/site/buildr.pdf
>
> The official specification against which this release was tested:
> http://people.apache.org/~assaf/buildr/1.3.2/site/specs.html
>
>
> Changes since 1.3.1:
> * Added: --prereqs command line argument to show all tasks and their
> dependencies. You can also follow with regular expression to narrow down
> the
> list of tasks.
> * Changed: Upgraded to Rubyforge 1.0.0.
> * Changed: BUILDR-86 Use newest versions of net-ssh and net-sftp gems.
> * Changed: BUILDR-88 Test classes/resources should come before compile
> classes/resources so they load up earlier in java classpath.
> * Changed: BUILDR-102 Update JUnit Version to 4.4.
> * Fixed: BUILDR-73 idea7x task incorrect adds target/resources to the
> sources
> paths.
> * Fixed: BUILDR-76 Added more specs and fixes to compile task.
> * Fixed: BUILDR-77 Layout feature not working.
> * Fixed: BUILDR-79 Remove :source option for Scala compiler
> * Fixed: BUILDR-80 Fix reference to Util#timestamp method on nailgun addon.
> * Fixed: BUILDR-82 Temporary work around for Net::SSH 2.0.2 attempting to
> load Pageant DLLs when running on JRuby/Windows.
> * Fixed: BUILDR-89 JUnit (and all other Java frameworks) no longer include
> abstract classes.
> * Fixed: BUILDR-90 Installing from source doesn't work with JRuby.
> * Fixed: BUILDR-91 When doing a release, buildr should spawn the same
> version of buildr
> * Fixed: BUILDR-92 IDEA 7x: add resources directories to classpath.
> * Fixed: BUILDR-95: Only download Scala test framework artifacts when
> required
> * Fixed: BUILDR-100 Directory structure documentation needs updating.
> * Fixed: Installation instructions updated for RubyGems 1.2.0.
>
> Assaf
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE]: Buildr 1.3.2 release

[ant elder]

On Wed, Jul 23, 2008 at 8:14 AM, Assaf Arkin <[EMAIL PROTECTED]> wrote:

> On Tue, Jul 22, 2008 at 6:18 AM, ant elder <[EMAIL PROTECTED]> wrote:
> > Looks ok to me so +1.
> >
> > Would be helpful to include a RAT report with the request, but I ran it
> > myself and it didn't highlight any issues.
> >
> > If the doc pdf is going to be distributed separately it should probably
> > include the Incubator disclaimer text, maybe on the page which already
> has
> > the Apache License text.
>
> Welcome/Notices, on page 7.
>
> It's generated from the same source as the web site, so we only have
> to edit one file to include all the proper notices.
>
> Assaf
>
>
Ah ha so it is. All looks fine to me then.

   ...ant

Re: [VOTE] Release Apache UIMA CasEditor-2.2.2-incubating

[ant elder]

+1,

but i've noticed another potential issue in
CasEditor-linux.gtk.x86-2.2.2-incubating.zip which i'll mention in case
others object - there are some licenses in the top level LICENSE file and
some other licenses in the about_files folder that are not mentioned in the
top LICENSE file. I guess thats ok as all the legal text is included in the
distro and other projects are now also including licenses outside of the top
level LICENSE file but its easy to miss with then being in multiple places
so i think it would be better to move all the legal files to the top level
LICENSE and NOTICE files for the next release.

The other distro's look fine to me now.

   ...ant

On Tue, Jul 22, 2008 at 8:55 PM, Jörn Kottmann <[EMAIL PROTECTED]> wrote:

> Hello,
>
> please vote again to release the Cas Editor. The first vote was
> rejected, because the ICU license and notice was
> missing, this is now fixed, see UIMA-1115.
>
> On the uima-dev list there were 5 +1 votes and no 0 or -1 votes to release
> it.
> The vote thread can be found here:
>
> http://www.mail-archive.com/uima-dev%40incubator.apache.org/msg07741.html
>
> The release artifacts and the rat reports can be found at:
> http://people.apache.org/~joern/CasEditor-2.2.2-04/
>
> The Cas Editor originally came to Apache under a software grant.
>
> Thanks,
> Jörn

Re: [VOTE] Release Apache Sanselan 0.94

[ant elder]

+1

A few comments for next time:

- Would be good to have a RELEASE_NOTES file in the distributions as there
is nothing included which says what Sanselan does or whats new in this
release

- The Apache licence header is missing from the assembly bin.xml and src.xml
in the src distribution

- Its preferred that the NOTICE files has nothing but what must be included
so the bit about the 3rd party license policy should be removed

- Might be worth mentioning in the src distro LICENSE file about all the
test images being in the public domain

   ...ant

On Sat, Jul 26, 2008 at 7:21 PM, Charles Matthew Chen <
[EMAIL PROTECTED]> wrote:

>  Apache Sanselan is a pure-Java image library which supports reading
> and writing image data and metadata from a variety of file formats.
> The first proposed incubator release is now ready.
>
>  The proposed release can be found here:
>
> http://people.apache.org/~cmchen/dist/incubator/sanselan/0.94/
>
>  The RAT output for the bin and src distributions can be found here:
>
> http://people.apache.org/~cmchen/rat-src-0.94.txt
> http://people.apache.org/~cmchen/rat-bin-0.94.txt
>
>   The release vote on the sanselan-dev mailing list resulted in 4 +1
> votes and no 0 or -1 votes from podling PMC members.
>
>   More information about the project can be found here:
>
>  * Wiki: http://cwiki.apache.org/SANSELAN/
>  * Incubation Status: http://incubator.apache.org/projects/sanselan.html
>  * Mailing list archive: http://incubator.apache.org/mail/sanselan-dev/
>
> Thanks,
>   Charles.
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE][POLICY] fix table of contents

[ant elder]

+1 to apply the patch.

   ...ant

On Mon, Jul 28, 2008 at 9:38 AM, Roland Weber <[EMAIL PROTECTED]> wrote:

> As explained in INCUBATOR-80, the Table of Contents
> of the policy document is inconsistent and contains
> broken links.
> https://issues.apache.org/jira/browse/INCUBATOR-80
>
> Please vote on applying the patch provided there.
>
> Votes of IPMC members are binding. The vote passes
> with at least three binding +1 and no binding -1.
> The voting period ends Sunday 2008-08-03 06:00 GMT.
> (because I'm away until Saturday anyway :-)
>
> cheers,
>  Roland
>
> --8<
> [ ] +1 apply the patch
> [ ] +0
> [ ] -0
> [ ] -1 don't apply the patch (reasons appreciated)
> 
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [VOTE] Release Apache UIMA CasEditor-2.2.2-incubating

[ant elder]

On Mon, Jul 28, 2008 at 4:17 PM, Jörn Kottmann <[EMAIL PROTECTED]> wrote:

> but i've noticed another potential issue in
>> CasEditor-linux.gtk.x86-2.2.2-incubating.zip which i'll mention in case
>> others object - there are some licenses in the top level LICENSE file and
>> some other licenses in the about_files folder that are not mentioned in
>> the
>> top LICENSE file. I guess thats ok as all the legal text is included in
>> the
>> distro and other projects are now also including licenses outside of the
>> top
>> level LICENSE file but its easy to miss with then being in multiple places
>> so i think it would be better to move all the legal files to the top level
>> LICENSE and NOTICE files for the next release.
>>
>> The other distro's look fine to me now.
>>
>
> Thanks, the about_files folder is generated during the RCP build
> and contains licenses for plugins which are contained in the bundle.
> If this it not a blocking the release we would fix this for the next
> version.
>
> Jörn
>
>
Yes i agree so just to reiterate,  +1 from me for the release.

   ...ant

Re: [VOTE] Accept project PicaGalley into the Incubator

[ant elder]

+1

   ...ant

On Sun, Aug 3, 2008 at 7:02 PM, Roland Weber <[EMAIL PROTECTED]> wrote:

> Hi all,
>
> please vote on accepting project PicaGalley
> (originally proposed under the name of Caitrin)
> for incubation, with the Incubator PMC as the Sponsor.
>
> This vote runs until Sun 2008-08-10 24:00 GMT,
> unless major discussions ensue. Votes of IPMC
> members are binding, a minimum of three +1 is
> required. I don't know whether a majority is
> sufficient or whether consensus is required,
> so I hope for the latter :-)
>
> thanks and cheers,
>  Roland
>
> --8<
> [ ] +1 Accept PicaGalley for incubation
> [ ]  0 Don't care
> [ ] -1 Reject for the following reason :
> 
>
> (The text below contains minor edits compared to the draft at
> http://wiki.apache.org/incubator/CaitrinProposal
> I removed the section "Help Wanted", improved formatting for
> direct reading, and removed the ! prefix from "!PicaGalley".)
>
>
> == Abstract ==
>
> PicaGalley will be a photo gallery application with web access.
>
> == Proposal ==
>
> PicaGalley will be a complete open source photo gallery application
> including a content repository for the images, a display piece, an access
> control layer, and upload capabilities. The idea is to have a rigid design
> for the content repository with a very flexible display piece. The images in
> the content repository will be protected with granular access control.
>
> == Background ==
>
> Photo gallery software provides users with the means to store, manage, and
> publish photographies and other digital images. A user creates one or more
> photo albums and puts images into them. Metadata stored with the images
> allows for searching. The primary means to access the photo gallery will be
> web interfaces, for human interaction through a browser as well as for
> machine retrieval. Images are published by granting read access to everybody
> or to a group of invites.
>
> Initially the proposal idea for a photo gallery was brought forth due to a
> project that had been started at Nechtan Design.  While discussing the
> possibility of forming a community around that project (called Caitrin) a
> community started to form.  Others with interest in the subject and problem
> space started putting in their ideas and offered to donate code that could
> help. It was decided that the project should start from scratch with a new
> architecture. This proposal is based on a high level design that evolved
> from the subsequent discussions.
>
> We are aware that we have significant work ahead of us, not only in the
> code to be written but in finding a community to support the project.
>
> == Rationale ==
> "A picture tells a thousand words..."
>
> If a picture tells a thousand words then a gallery of pictures tells an
> amazing story.  It could tell this story as part of a larger web site, in a
> blog or on its own.  Unfortunately, there exists no Java open source
> application to assist the community to tell this story.  PicaGalley will
> change that.
>
> There are many photo galleries that are written in PHP.  Each of these
> addresses a particular need and many work well for their intended purpose.
> However, there is not a photo gallery that is written in Java.  As Web 2.0
> continues to grow it only makes sense that the community provide not only
> PHP but also Java applications to allow everyone the ability to publish
> their own content.  Apache started down this road with Roller and can
> continue with PicaGalley.
>
>
> == Initial Goals ==
>
>  * Create a prototype by drawing pieces from existing efforts
>  * Recruit additional community members
>
>  * Finalize the Content Repository
>   * Use cases - capture ideas such as access control that might not make
> first drop
>   * Layout
>   * Unit tests (simple drivers for loading, accessing, searching, etc.)
>
>  * ReST structure
>   * Use cases
>   * URI format
>   * semantics
>   * prototype implementation
>
>  * Web service
>   * Use cases - want to capture ideas for process (Ode) integration
>   * WSDL Description
>   * prototype
>
>
> == Current Status ==
>
> Responses to the initial proposal uncovered several existing efforts at
> implementing photo gallery software in Java. Instead of picking one codebase
> over the others, we started from scratch with a high-level design. Pieces
> will be taken from the existing efforts as appropriate. These efforts are:
>
>  * Caitrin: Originally developed for a fee at Nechtan Design then
> voluntarily updated. The code is in use on a test site and ready to be moved
> to production. It runs on Tomcat and uses a relational DB for
>  storing metadata as well as the filesystem for storing images. This
> codebase was at the core of the initial proposal for this podling.
>
>  * Noel Bergman developed a photo gallery software he is willing to donate.
> The software is in production use, technical details remain to be

Re: [VOTE] Release Apache Pig 0.1.0-incubating

[ant elder]

On Mon, Aug 11, 2008 at 7:26 PM, Olga Natkovich <[EMAIL PROTECTED]> wrote:

> Hi Everyone,
>
> Apache Pig dev community voted to release Pig 0.1.0-incubating. We had 4
> +1 votes from committers and mentors and no 0 or -1 votes. (Message-ID:
> <[EMAIL PROTECTED]>)
> .
>
> The artifacts are available at
> http://people.apache.org/~olga/pig-0.1.0-candidate-4/
> 
> >
>
> Please vote by 6 pm on Thursday, 8/14.
>
> Olga
>
>

The main issue is the NOTICE file is missing some copyrights for the 3rd
party products that are included such as javacc, jsch, and jetty (jetty is
embedded within the pig-0.1.0-incubating-core.jar). I think this should be
fixed for this release.

Some other comments:

If the pig-0.1.0-incubating-core.jar is to be distributed separately (eg
maven repo) then it needs to include LICENSE/NOTICE/DISCLAIMER files.

The signature used to sign the distribution isn't available online from a
public key server, eg pgp.surfnet.nl

The release should be built from an svn tag but there doesn't seem to be
one.

Would be helpful to include a RAT report in the VOTE email

Other than that it looks good, if the NOTICE file is updated it would get my
+1.

   ...ant

Re: [VOTE] Release Apache Pig 0.1.0-incubating

[ant elder]

Replies inline.

   ...ant

On Wed, Aug 13, 2008 at 1:43 AM, Olga Natkovich <[EMAIL PROTECTED]> wrote:

> Hi,
>
> Thanks for quick feedback! A couple of follow up questions inline.
>
> > -Original Message-
> > From: ant elder [mailto:[EMAIL PROTECTED]
> > Sent: Tuesday, August 12, 2008 12:07 AM
> > To: general@incubator.apache.org
> > Subject: Re: [VOTE] Release Apache Pig 0.1.0-incubating
> >
> > On Mon, Aug 11, 2008 at 7:26 PM, Olga Natkovich
> > <[EMAIL PROTECTED]> wrote:
> >
> > > Hi Everyone,
> > >
> > > Apache Pig dev community voted to release Pig
> > 0.1.0-incubating. We had
> > > 4
> > > +1 votes from committers and mentors and no 0 or -1 votes.
> > (Message-ID:
> > >
> > <[EMAIL PROTECTED]
> > > >)
> > > .
> > >
> > > The artifacts are available at
> > >
> > http://people.apache.org/~olga/pig-0.1.0-candidate-4/<http://people.apache.org/%7Eolga/pig-0.1.0-candidate-4/>
> <http://people.ap
> > > ache.org/%7Eolga/pig-0.1.0-candidate-4/>
> > >
> > <http://people.apache.org/~olga/pig-0.1.0-candidate-4/<http://people.apache.org/%7Eolga/pig-0.1.0-candidate-4/>
> <http://people.a
> > > pache.org/%7Eolga/pig-0.1.0-candidate-4/>
> > > >
> > >
> > > Please vote by 6 pm on Thursday, 8/14.
> > >
> > > Olga
> > >
> > >
> >
> > The main issue is the NOTICE file is missing some copyrights
> > for the 3rd party products that are included such as javacc,
> > jsch, and jetty (jetty is embedded within the
> > pig-0.1.0-incubating-core.jar). I think this should be fixed
> > for this release.
>
> I put the licenses in separate files in the lib directory where all the
> 3rd party libraries are following Hadoop model. I did not realize that
> they had to go to the notice file. I can move them if needed. Also jetty
> is part of Hadoop distribution; is it sufficient just to have Hadoop
> license present?
>

Having the licenses in the separate lib directory is fine but the top NOTICE
file still needs to include any attributions. For example, pig includes
javacc and the javacc license says "Copyright (c) 2003 Sun Microsystems,
Inc." and the JavaCC license says "Redistribution in binary form must
reproduce the above copyright notice", so add the pig NOTICE file something
like:

This product includes/uses the JavaCC (https://javacc.dev.java.net/),
   Copyright (c) 2003 Sun Microsystems, Inc.

You need that for javacc, jsch, and jetty.


>
> >
> > Some other comments:
> >
> > If the pig-0.1.0-incubating-core.jar is to be distributed
> > separately (eg maven repo) then it needs to include
> > LICENSE/NOTICE/DISCLAIMER files.
>
> What is the DISCLAIMER file?
>

Its the text at the bottom of the pig README, or that text can be in a file
on its own. The pig distro is fine as-is, i was just pointing out that _if_
the pig-0.1.0-incubating-core.jar is going to be distributed seperately then
it would also need to include its own legal files.


>
> > The signature used to sign the distribution isn't available
> > online from a public key server, eg pgp.surfnet.nl
>
> Keys are at /www/www.apache.org/dist/incubator/pig on people.apache.org.
> Is this not the right location?
>

Yes thats the right place, but you can also publish them to a public key
server and then if peoples clients are configured correctly the keys will be
downloaded automatically. See
http://www.apache.org/dev/release-signing.html#keyserver


>
> > The release should be built from an svn tag but there doesn't
> > seem to be one.
>
> I created a branch for it. Will add a tag as well.
>
> > Would be helpful to include a RAT report in the VOTE email
>
> Attached now
>
> >
> > Other than that it looks good, if the NOTICE file is updated
> > it would get my
> > +1.
> >
> >...ant
> >
>

Re: [VOTE] Apache CouchDB 0.8.1-incubating release

[ant elder]

On Wed, Aug 13, 2008 at 7:20 PM, Niklas Gustavsson <[EMAIL PROTECTED]>wrote:

> On Wed, Aug 13, 2008 at 7:12 PM, Noah Slater <[EMAIL PROTECTED]> wrote:
> > Pursuant to the Releases section of the Incubation Policy we would now
> like to
> > request the approval of the Incubator PMC to make the release.
>
> +1 (non-binding).
>
> An issue that should be fixed, but I don't believe is blocking for the
> release is that the license for the autoconf macro reads:
>
> "Copyright (c) 2008 Akos Maroy <[EMAIL PROTECTED]>
>
> Copying and distribution of this file, with or without modification,
> are permitted in any medium without royalty provided the copyright
> notice and this notice are preserved."
>
> However, the NOTICE file does not contain the second line and I can't
> seem to find it elsewhere.
>
> /niklas
>
>
That looks ok to me, the 2nd line is the license so should go in the CouchDB
LICENSE file - and it is included there along with the licenses for all the
other third party components.

The rest of the release looks fine to me too, so +1.

   ...ant

Re: [VOTE] Release Apache Pig 0.1.0-incubating

[ant elder]

The attached NOTICE file looks ok to me, it should also have the following
two lines at the top:

Apache Pig
Copyright 2008 The Apache Software Foundation

See http://www.apache.org/legal/src-headers.html#notice.

I think you will need to restart as to fix the NOTICE file you'll need to
build a new distribution. It has been done in the past that the dev list and
general@ votes on the respin are done in parallel though.

   ...ant

On Wed, Aug 13, 2008 at 10:15 PM, Olga Natkovich <[EMAIL PROTECTED]>wrote:

>  Does the attached notice file look correct?
>
> Also, does this mean we need to restart the entire process?
>
> Thanks,
>
> Olga
>
>  --
> *From:* [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] *On Behalf Of *ant
> elder
> *Sent:* Tuesday, August 12, 2008 11:32 PM
> *To:* Olga Natkovich
> *Cc:* general@incubator.apache.org
>
> *Subject:* Re: [VOTE] Release Apache Pig 0.1.0-incubating
>
>  Replies inline.
>
>...ant
>
> On Wed, Aug 13, 2008 at 1:43 AM, Olga Natkovich <[EMAIL PROTECTED]>wrote:
>
>> Hi,
>>
>> Thanks for quick feedback! A couple of follow up questions inline.
>>
>> > -Original Message-
>> > From: ant elder [mailto:[EMAIL PROTECTED]
>> > Sent: Tuesday, August 12, 2008 12:07 AM
>> > To: general@incubator.apache.org
>> > Subject: Re: [VOTE] Release Apache Pig 0.1.0-incubating
>> >
>> > On Mon, Aug 11, 2008 at 7:26 PM, Olga Natkovich
>> > <[EMAIL PROTECTED]> wrote:
>> >
>> > > Hi Everyone,
>> > >
>> > > Apache Pig dev community voted to release Pig
>> > 0.1.0-incubating. We had
>> > > 4
>> > > +1 votes from committers and mentors and no 0 or -1 votes.
>> > (Message-ID:
>> > >
>> > <[EMAIL PROTECTED]
>> > > >)
>> > > .
>> > >
>> > > The artifacts are available at
>> > >
>> > http://people.apache.org/~olga/pig-0.1.0-candidate-4/<http://people.apache.org/%7Eolga/pig-0.1.0-candidate-4/>
>> <http://people.ap
>> > > ache.org/%7Eolga/pig-0.1.0-candidate-4/>
>> > >
>> > <http://people.apache.org/~olga/pig-0.1.0-candidate-4/<http://people.apache.org/%7Eolga/pig-0.1.0-candidate-4/>
>> <http://people.a
>> > > pache.org/%7Eolga/pig-0.1.0-candidate-4/>
>> > > >
>> > >
>> > > Please vote by 6 pm on Thursday, 8/14.
>> > >
>> > > Olga
>> > >
>> > >
>> >
>> > The main issue is the NOTICE file is missing some copyrights
>> > for the 3rd party products that are included such as javacc,
>> > jsch, and jetty (jetty is embedded within the
>> > pig-0.1.0-incubating-core.jar). I think this should be fixed
>> > for this release.
>>
>> I put the licenses in separate files in the lib directory where all the
>> 3rd party libraries are following Hadoop model. I did not realize that
>> they had to go to the notice file. I can move them if needed. Also jetty
>> is part of Hadoop distribution; is it sufficient just to have Hadoop
>> license present?
>>
>
> Having the licenses in the separate lib directory is fine but the top
> NOTICE file still needs to include any attributions. For example, pig
> includes javacc and the javacc license says "Copyright (c) 2003 Sun
> Microsystems, Inc." and the JavaCC license says "Redistribution in binary
> form must reproduce the above copyright notice", so add the pig NOTICE file
> something like:
>
> This product includes/uses the JavaCC (https://javacc.dev.java.net/),
>Copyright (c) 2003 Sun Microsystems, Inc.
>
> You need that for javacc, jsch, and jetty.
>
>
>>
>> >
>> > Some other comments:
>> >
>> > If the pig-0.1.0-incubating-core.jar is to be distributed
>> > separately (eg maven repo) then it needs to include
>> > LICENSE/NOTICE/DISCLAIMER files.
>>
>> What is the DISCLAIMER file?
>>
>
> Its the text at the bottom of the pig README, or that text can be in a file
> on its own. The pig distro is fine as-is, i was just pointing out that _if_
> the pig-0.1.0-incubating-core.jar is going to be distributed seperately then
> it would also need to include its own legal files.
>
>
>>
>> > The signature used to sign the distribution isn't available
>> > online from a public key server, eg pgp.surfnet.nl
>>
>> Keys are at /www/www.apache.org/dist/incubator/pig on people.apache.org.
>> Is this not the right location?
>>
>
> Yes thats the right place, but you can also publish them to a public key
> server and then if peoples clients are configured correctly the keys will be
> downloaded automatically. See
> http://www.apache.org/dev/release-signing.html#keyserver
>
>
>>
>> > The release should be built from an svn tag but there doesn't
>> > seem to be one.
>>
>> I created a branch for it. Will add a tag as well.
>>
>> > Would be helpful to include a RAT report in the VOTE email
>>
>> Attached now
>>
>> >
>> > Other than that it looks good, if the NOTICE file is updated
>> > it would get my
>> > +1.
>> >
>> >...ant
>> >
>>
>
>

Re: [VOTE] Apache CouchDB 0.8.1-incubating release

[ant elder]

Yes.

   ...ant

On Thu, Aug 14, 2008 at 1:31 PM, Noah Slater <[EMAIL PROTECTED]> wrote:

> On Thu, Aug 14, 2008 at 06:25:55AM +0100, ant elder wrote:
> > The rest of the release looks fine to me too, so +1.
>
> Binding?
>
> --
> Noah Slater, 
> http://people.apache.org/~nslater/<http://people.apache.org/%7Enslater/>
>

Re: [VOTE] Release Apache Pig 0.1.0-incubating

[ant elder]

Looks good to me now, +1.

One more suggestion for next time is it would be nice to add a sentence to
the top of the release notes saying what Pig does and to include the release
notes within the distribution.

   ...ant

On Fri, Aug 15, 2008 at 8:13 PM, Olga Natkovich <[EMAIL PROTECTED]> wrote:

> Hi Everyone,
>
> Apache Pig would like to release Pig 0.1.0-incubating. This is a second
> try. We have changed the NOTICE file to contain copyright statements
> from libraries Pig depends on.
>
> Since the change is very small, I am starting this thread in parallel
> with the vote on pig-dev mailing list. The MessageId for that thread is
> <[EMAIL PROTECTED]>
>
> The new artifacts are available at
> http://people.apache.org/~olga/pig-0.1.0-candidate-5/
> 
> >
>
> The keys used to sign the release are available at
> /www/www.apache.org/dist/incubator/pig/KEYS on people.apache.org
>
> Please vote by 6 pm on Wednesday, 8/20.
>
> Thanks,
>
> Olga
>
>

Re: aesthetic changes to the NOTICE file

[ant elder]

On Mon, Aug 18, 2008 at 12:08 PM, Noah Slater <[EMAIL PROTECTED]> wrote:

> Hello,
>
> CouchDB's current notice file looks like:
>
>  http://svn.apache.org/repos/asf/incubator/couchdb/trunk/NOTICE
>
> This matches Apache httpd's NOTICE file:
>
>  http://svn.apache.org/repos/asf/httpd/httpd/trunk/NOTICE
>
> So that our NOTICE file matches our other source documentation:
>
>  http://svn.apache.org/repos/asf/incubator/couchdb/trunk/README
>  http://svn.apache.org/repos/asf/incubator/couchdb/trunk/AUTHORS
>  http://svn.apache.org/repos/asf/incubator/couchdb/trunk/THANKS
>
> Would it be okay if I reformulated the NOTICE like this:
>
>  
> http://people.apache.org/~nslater/ephemera/NOTICE
>
> Trivial I know, but I'm a stickler for aesthetics.
>
> Best,
>
> --
> Noah Slater, 
> http://people.apache.org/~nslater/
>
>
I'd be wary of doing that if i was you. Whether or not it means the same
thing legally this is clearly specified in ASF policy at
http://www.apache.org/legal/src-headers.html#notice and if you change from
that you may find some other stickler delaying or blocking one of you
release votes due to any differences.

   ...ant

Re: [VOTE] accept Etch into the Incubator

[ant elder]

+1

   ...ant

On Mon, Aug 25, 2008 at 7:09 PM, Yonik Seeley <[EMAIL PROTECTED]> wrote:

> Since wiki pages can change, the full text of the proposal needs to be
> in the vote thread.
> Here is the text of the proposal:
>
> == Abstract ==
>
> Etch is a cross-platform, language- and transport-independent
> framework for building and consuming network services.
>
> == Proposal ==
>
> Etch is a cross-platform, language- and transport-independent
> framework for building and consuming network services. The Etch
> toolset includes a network service description language, a compiler,
> and binding libraries for a variety of programming languages. Etch is
> also transport-independent, allowing for a variety of different
> transports to used based on need and circumstance. The goal of Etch is
> to make it simple to define small, focused services that can be easily
> accessed, combined, and deployed in a similar manner. Ultimately with
> Etch, service development and consumption becomes no more difficult
> than library development and consumption.
>
> == Background ==
>
> Etch was started because we wanted to have a way to write a concise,
> formal description of the message exchange between a client and a
> server, with that message exchange supporting a hefty set of
> requirements. The messaging technology should support one-way and
> two-way, real-time communication. It should have high performance and
> scalability. I should support clients and servers written in different
> languages. It should also support clients/servers running in a wide
> range of contexts (such as thin web client, embedded device, PC
> application, or server). It must support anyone adding new language
> bindings and new transports. It should also be fast and small, while
> still being flexible enough to satisfy requirements. Finally, it must
> be easy to use for developers both implementing and/or consuming the
> service.
>
> == Rationale ==
>
> Existing systems were either too slow, hard to use, bloated and/or
> proprietary. In any case, none fit our matrix of requirements
> perfectly.
>
> Developers of applications that must leverage the capabilities of
> network-hosted services have a daunting challenge. They must cobble
> together a heterogeneous collection of services that expose different
> APIs with different communications technologies just to integrate with
> the services, essentially spending a great deal of energy and effort
> on just the basics of inter-service communication rather than core
> business logic.
>
> So the desired state then is when developing applications that
> leverage the capabilities of dispersed and heterogeneous network
> services, APIs must be simple, cohesive, and coherent across network
> services. APIs should be easy to consume by developers regardless of
> the implementation technology of the service used or the domain a
> service is being built within- from client-side web applications to
> complex real-time server systems. Put simply, developers ideally
> should feel that they are developing to a platform.
>
> API development is a much better understood and simpler subject if you
> are building those APIs to be run _locally_ on a single machine or
> service. Microsoft and Linux centric API developers have the luxury of
> the massive assumption that a standard OS is available with a certain
> set of features, and the API libraries do not have to take into
> account the complexities of APIs that cross machine or OS boundaries.
>
> Developers of network-centered services, rather than OS-centered
> services, do not have this luxury; we have a significant set of issues
> facing us today because of the fundamental fact that "the network" is
> not a single machine, or a homogeneous set of machines, but a
> heterogeneous and widely distributed set of services.
>
> The conventional method for developers of network services today is to
> use either a technology specific to the language of preference, RMI
> for Java, .NET Remoting for .NET for C#, etc., or if trying to be
> "language neutral" picking a CORBA ORB or a Web Service technology
> like SOAP or REST. These choices are fine until the requirements of
> the application cannot accept the limitations of the remoting
> technology. If the application needs to work on non-Microsoft
> platforms, .NET Remoting is out (unless, of course, you can use the
> Mono implementation of .NET, but that brings with it other
> challenges). If the need is to support access from languages other
> than Java, then RMI is out. If the need includes support for
> real-time, asynchronous communication, or symmetric two-way
> communications, the Web services technologies must also be rejected.
>
> For other classes of applications, there are simply no "standard"
> choices left. The developer is forced to drop down to a network
> protocol level and invent a new messaging system for their needs.
> Building a protocol by hand is hard; building a messaging system is
> also hard. This d

Re: [VOTE] Release Apache Qpid Incubating M3 (RC3)

[ant elder]

On Fri, Aug 29, 2008 at 1:32 AM, Aidan Skinner <[EMAIL PROTECTED]> wrote:

> On Fri, Aug 29, 2008 at 12:44 AM, Craig L Russell <[EMAIL PROTECTED]>
> wrote:
>
> Thanks for checking these.
>
> > There should be a KEYS file high up in your directory structure. I didn't
> > look too hard for it elsewhere, but just downloaded your key from the
> public
> > keyserv. I later found a KEYS in the java directory, but it's clearly
> > misplaced here and doesn't appear to contain your key.
> >
> > There is still no LICENSE file high in your distribution. If you go to
> many
> > of the project directories at the top level you don't find the LICENSE
> > either.
>
> Urrr. Looks like a commit failed and I didn't check when I tagged it
> again, gah.  I've added KEYS, NOTICE, DISCLAIMER, LICENSE to the top
> level but..
>
> > But qpid-incubating-M3/java has no LICENSE or NOTICE. Not ok. If your
> intent
> > is that the files in java/resources are supposed to cover the entire java
> > directory, they need to be popped up a level when you package the
> release,
> > because there's no indication that this is the intent. We don't want
> people
> > to guess where LICENSE and NOTICE files apply.
>
> The top level notice will point to these.
>
> > The qpid-incubating-M3/gentools has no LICENSE or NOTICE.
> >
> > The qpid-incubating-M3/specs have licenses and notices in the files but
> > again, you need LICENSE and NOTICE files popped up at least one level.
> >
> > The qpid-incubating-M3/cc has no LICENSE or NOTICE.
> >
> > The qpid-incubating-M3/bin has no LICENSE or NOTICE.
> >
> > The qpid-incubating-M3/review has no LICENSE or NOTICE.
> >
> > The qpid-incubating-M3/buildtools has no LICENSE or NOTICE.
>
> Can somebody else from qpid take care of these for me please? I'm
> going to be without internet access until Tuesday. I've attached the
> shell script I use to do all this, it should Just Work. (it does the
> tagging for you, so make sure you have $EDITOR or $VISUAL set so you
> can enter the commit message for the svn commands)
>
> - Aidan
>
> --
> Apache Qpid - World Domination through Advanced Message Queueing
> http://cwiki.apache.org/qpid
> "Nine-tenths of wisdom consists in being wise in time." - Theodore
> Roosevelt
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>

While those are being fixed there's one more thing as well,
qpid-incubating-M3-java.tar.gz  is missing the license text for the third
party licenses it uses, eg BSD, MIT, MPL, EPL. The text of those licenses
needs to be included somewhere probably in the top level LICENSE file.

   ...ant

Re: [VOTE] [POLICY] Allow extra release distribution channels like the central Maven repository

[ant elder]

On Thu, Sep 18, 2008 at 4:57 AM, Noel J. Bergman <[EMAIL PROTECTED]> wrote:

> William A. Rowe, Jr. wrote:
>
> > Noel J. Bergman wrote:
> >>> The current tally is extremely close (9 +1 vs. 8 -1 binding)
> >>> I don't want to close an issue with such a small margin.
> >> I suggest that we should not change policy on anything like this lack of
> >> concensus.  I do, however, suggest that pressure be put on Maven to
> >> enforce signing.
> > As no-maven still hasn't been justified, and when we authorized releases
> > we had not explicitly called out specific channels, so I'm wondering what
> > the "change" you refer to actually is :)
>
> Right now, the policy has been an Incubator-specific repository, not the
> main one.
>
> And the general statement is that when we have an issue with no clear
> consensus, we should take care about making changes on slim margins.
>
>
>
I'd not been able to decide how to vote on this but it doesn't feel right to
have it decided by a 9 to 8 vote. There clearly isn't consensus and there's
still lots of discussion going on about it in this and other threads so for
now my vote is -1.

   ...ant

Re: [Vote] accept Droids into incubation

[ant elder]

+1

   ...ant

On Thu, Oct 2, 2008 at 9:00 PM, Thorsten Scherler <[EMAIL PROTECTED]>wrote:

> Please vote on accepting Droids into incubation.
>
> The proposal can be found at:
> http://wiki.apache.org/incubator/DroidsProposal
>
> The text of the proposal
>
> = Droids, an intelligent standalone robot framework =
>
> === Abstract ===
>
> Droids aims to be an intelligent standalone robot framework that allows
> to create and extend existing droids (robots).
>
> === Proposal ===
>
> As a standalone robot framework Droids will offer infrastructure code to
> create and extend existing robots. In the future it will offer as well a
> web based administration application to manage and controll the
> different droids which will communicate with this app.
>
> Droids makes it very easy to extend existing robots or write a new one
> from scratch, which can automatically seek out relevant online
> information based on the user's specifications. Since the flexible
> design it can reuse directly all custom business logic that are written
> in java.
>
> In the long run it should become umbrella for specialized droids that
> are hosted as sub-projects. Where an ultimate goal is to integrate an
> artificial intelligence that can control a swarm of droids and actively
> plan/react on different tasks.
>
> === Background ===
>
> The initial idea for the Droids project was voiced in February 2007 from
> Thorsten Scherler mainly because of personal curiosity and developed as
> a labs project. The background of his work was that Cocoon trunk (2.2)
> did not provide a crawler anymore and Forrest was based on it, meaning
> we could not update anymore till we found a crawler replacement. Getting
> more involved in Solr and Nutch he saw the request for a generic
> standalone crawler.
>
> For the first version he took nutch, ripped out and modified the
> plugin/extension framework. However the second version were not based on
> it anymore but was using Spring instead. The main reason was that Spring
> has become a standard and helped to make Droids as extensible as
> possible.
>
> Soon the first plugins and sample droids had been added to the code
> based.
>
> === Rationale ===
>
> There is ever more demand for tools that automatically do determinate
> tasks. Search engines such as Nuts are normally very focused on a
> specific functionality and are not focused on extensibility. Furthermore
> there are manly focused on crawling, requesting certain pages and
> extract links to other pages, which in our opinion is only one small
> area for automated robots. While there are a number of existing crawler
> libraries for various task, each of them comes with a custom API and
> there are no generic interface for automatically determining which
> crawler (droids) to use for a specific task.
>
> The Droids project attempts to remove this duplication of efforts. We
> believe that by pooling the efforts of multiple projects we will be able
> to create a generic robot framework that exceeds the capabilities and
> quality of the custom solutions of any single project. The focus of
> Droids is not a single crawler but more to offer different reusable
> components that custom droids (robots) can use to automate certain
> tasks. An intelligent standalone robot framework project will not only
> provide common ground for the developers of crawler but as well for any
> other automated application (robots) libraries.
>
> === Initial Goals ===
>
> The initial goals of the proposed project are:
>
>  * Viable community around the Droids codebase
>  * Active relationships and possible cooperation with related projects
> and communities (e.g. reusing Tika for text extraction)
>  * Generic robot API for crawling, extracting structured text content
> and/or new task, filtering task and handle the content
>  * Flexible extension and plugin development to create a wide range of
> functionality
>  * Fuel develop of various droids and bring the current wget style
> crawler to state-of-the-art level
>
> == Current Status ==
>
> === Meritocracy ===
>
> All the initial committers are familiar with the meritocracy principles
> of Apache, and have already worked on the various source codebases. We
> will follow the normal meritocracy rules also with other potential
> contributors.
>
> === Community ===
>
> There is not yet a clear Droids community. Instead we have a number of
> people and related projects with an understanding that an intelligent
> standalone robot framework project would best serve everyone's
> interests. The primary goal of the incubating project is to build a
> self-sustaining community around this shared vision.
>
> === Core Developers ===
>
> The initial set of developers comes from various backgrounds, with
> different but compatible needs for the proposed project.
>
> === Alignment ===
>
> As a generic robot framework Droids will likely be widely used by
> various open source and commercial projects both together with and
> independent of other A

Re: [VOTE] apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating release, 2nd round

[ant elder]

On Thu, Oct 2, 2008 at 8:39 AM, Jörg Reiher <[EMAIL PROTECTED]> wrote:

> Hello,
>
> the community has approved a release of apache-empire-db-2.0.4-incubating
> and apache-empire-struts2-ext-1.0.4-incubating.
>
>
>
> Pursuant to the Releases section of the Incubation Policy we would now like
> to request the approval of the Incubator PMC to make the release.
>
>
>
> Release proposal apache-empire-db-2.0.4-incubating:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL
>  PROTECTED]<
> http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL
>  PROTECTED]
> >
>
>
>
> Vote result apache-empire-db-2.0.4-incubating:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL
>  PROTECTED]<
> http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL
>  PROTECTED]
> >
>
>
>
>
>
> Release proposal apache-empire-struts2-ext-1.0.4-incubating:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200809.mbox/[EMAIL
>  PROTECTED]
>
>
>
> Vote result apache-empire-struts2-ext-1.0.4-incubating:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-empire-db-dev/200810.mbox/[EMAIL
>  PROTECTED]
>
>
>
> My vote is
>
>
>
> +1 (non binding)
>
>
>
>
>
>
>
> Joerg
>
>

+1

though i do think for the next release all those separate licenses in the
top level folder should be merged into the single LICENSE and NOTICE files.

   ...ant

Re: [VOTE] apache-empire-db-2.0.4-incubating and apache-empire-struts2-ext-1.0.4-incubating release, 2nd round

[ant elder]

On Fri, Oct 3, 2008 at 8:42 AM, Martijn Dashorst <[EMAIL PROTECTED]
> wrote:

> On Fri, Oct 3, 2008 at 8:23 AM, ant elder <[EMAIL PROTECTED]> wrote:
> > +1
>
> +1
>
> > though i do think for the next release all those separate licenses in the
> > top level folder should be merged into the single LICENSE and NOTICE
> files.
>
> And this is where I disagree strongly. Licenses for 3rd party
> libraries should be separate from licenses covering the source code.
> It is not like these licenses are not easy to find, nor easy to
> overlook. In fact: putting them all in one file makes it impossible to
> ascertain which license covers which product. A 64 page license file
> is never read.
>
> Martijn
>

Sure, and we seem to be accepting either approach as ok these days in the
poddling reviews, though if lots of separate files are being used i think
its probably better to put them somewhere other than the top level folder.
What i was hinting at in the previous email is that the copyright statements
are also in the seperate license files and I think they should be really be
copied to or at least pointed to from the top NOTICE file.

   ...ant

Re: [Proposal] Kato - mentors needed etc

[ant elder]

On Wed, Oct 1, 2008 at 9:53 AM, Steve Poole <[EMAIL PROTECTED]>wrote:

> A couple of weeks ago I posted the existence of a draft proposal for a new
> project.
> (For those of you who missed it it's here ->
> http://wiki.apache.org/incubator/KatoProposal)
>
> I've only had one comment so far,  so I'm assuming that either I'm missing
> something, the proposal is not clear, or (most likely) its not greatly
> interesting :-)
>
> Anyone like to give a novice a helping hand and explain what it is I need
> to do to stimulate some discussion?
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
Hi Steve, I've added myself as a mentor on the Kato proposal wiki page.

I've also set the "Proposed Apache Sponsor" section on the proposal to be
the Incubator PMC, but as this sounds relevant to Apache Harmony I wondered
if it had been mentioned to them?

   ...ant

Re: [VOTE] Graduate Tika to a Lucene subproject (Graduation Approval Vote)

[ant elder]

+1

   ...ant

On Fri, Oct 24, 2008 at 3:07 PM, Jukka Zitting <[EMAIL PROTECTED]>wrote:

> Hi,
>
> The Tika community has voted [1] to request and the Lucene PMC has
> accepted [2] graduating Apache Tika to a Lucene subproject. As
> described in in the graduation guide [3], I now ask the Incubator PMC
> to approve this graduation. For background, see the Tika status page
> [4] and the recent graduation discussion at tika-dev@ [5].
>
> Please vote on approving the graduation of Tika. This vote is open for
> the next 72 hours and only votes from Incubator PMC members are
> binding.
>
>[ ] +1 Approve graduation of Tika to a Lucene subproject
>[ ] -1 Tika is not ready to graduate
>
> The following Incubator PMC members already participated in the
> community vote and indicated that their votes should also be counted
> in this approval vote. I will be counting these votes when tallying
> the results.
>
>+1 Bertrand Delacretaz (mentor)
>+1 Grant Ingersoll
>+1 Jukka Zitting (mentor)
>+1 Niall Pemberton
>
> [1] http://markmail.org/message/rsm5mk3rybhxcp3i
> [2] http://markmail.org/message/j43alqu2y4hikpui
> [3] http://incubator.apache.org/guides/graduation.html#subproject
> [4] http://incubator.apache.org/projects/tika.html
> [5] http://markmail.org/message/d3ydcybnutt7o2uf
>
> BR,
>
> Jukka Zitting
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Re: [Proposal] Kato - mentors needed etc

[ant elder]

On Wed, Oct 1, 2008 at 8:53 AM, Steve Poole <[EMAIL PROTECTED]>wrote:

> A couple of weeks ago I posted the existence of a draft proposal for a new
> project.
> (For those of you who missed it it's here ->
> http://wiki.apache.org/incubator/KatoProposal)
>
> I've only had one comment so far,  so I'm assuming that either I'm missing
> something, the proposal is not clear, or (most likely) its not greatly
> interesting :-)
>
> Anyone like to give a novice a helping hand and explain what it is I need
> to do to stimulate some discussion?
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
This has been proposed for a few weeks now, there was some additional
generally positive discussion over on jcp-open -
http://apache.markmail.org/message/ok6rtygeptzzx3fu - as discussion here has
died down in a day or two I'd like to start a vote on accepting this
proposal.

   ...ant

[VOTE] Accepting Kato into the Incubator

[ant elder]

ework for Java (DTFJ)
technology as a seed for development. This codebase consists of
diagnostic dump readers and the data access API. There are data
providers for DTFJ that are specific and proprietary to IBM JVMs;
these providers will not be open-sourced. DTFJ is being donated to
kick start the project and as a foundation on which to build and
develop our ideas. There is no expectation that the final output must
resemble this seed offering.
Source and Intellectual Property Submission Plan

Apache would receive all source and documentation under the Apache
Corporate Contributor agreement. IBM is the only license holder.
External Dependencies

Ant and JUnit are the only external dependencies.
Cryptography
Required Resources
Mailing Lists

*

  kato-private
*

  kato-dev
*

  kato-spec

Subversion Directory

*

  [WWW] https://svn.apache.org/repos/asf/incubator/kato

Issue Tracking

*

  JIRA : Kato (KATO)

Other Resources
Initial Committers

Steve Poole spoole at uk dot ibm dot com

Stuart Monteith monteith at uk dot ibm dot com

Carmine Cristello cristallo at uk dot ibm dot com

Richard Cole rich dot cole at uk dot ibm dot com

Christian Glatschke christian at glatschke dot com

Sonal Goyal sonalgoyal4 at gmail dot com
Affiliations

The initial committers listed are affiliated with IBM and self.
Champion

Geir Magnusson Jr has agreed to be Champion
Proposed Apache Sponsor

Incubator PMC

Nominated Mentors
Geir has volunteered to be a mentor.
Ant Elder

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

Re: [VOTE] Accepting Kato into the Incubator

[ant elder]

On Sun, Nov 2, 2008 at 12:13 PM, Robert Burrell Donkin <
[EMAIL PROTECTED]> wrote:

> On Sun, Nov 2, 2008 at 10:45 AM, Roland Weber <[EMAIL PROTECTED]> wrote:
> > ant elder wrote:
> >> The Kato proposal has been out for discussion for a few weeks now,
> >> please vote on accepting the Kato project for incubation.
> >>
> >> [...]
> >> = Kato - Post-mortem JVM Diagnostics API and RI/TCK for JSR 326 =
> >> [...]
> >>
> >> Nominated Mentors
> >> Geir has volunteered to be a mentor.
> >> Ant Elder
> >
> > That list looks a bit short, but +1 anyway. (binding)
>
> i'm willing to be added as a mentor if this is a problem and kato are
> happy to have me
>
> - robert
>
>
Wonderful. I've taken the liberty of adding you as a mentor on the wiki
page.

  ...ant

[RESULT][VOTE] Accepting Kato into the Incubator

[ant elder]

This vote has been open for a week now so I'm going to call it PASSED with
19 +1s and no other votes.

Votes from the following, binding ones marked with a *:

 Carmine Cristallo
 Konstantin Bobrovsky
*Ant Elder
*Geir Magnusson Jr.
*Niclas Hedhman
 Niklas Gustavsson
*Matthias Wessendorf
 Christian Glatschke
*Craig L Russell
 Tim Ellison
*Alan D. Cabrera
 Steve Poole
 Sonal Goyal
 Stuart Monteith
 Edward J. Yoon
*Roland Weber
*Robert Burrell Donkin
*Niall Pemberton
 Richard Cole

Congratulations Kato and best wishes for the Incubation.

   ...ant

On Thu, Oct 30, 2008 at 9:14 AM, ant elder <[EMAIL PROTECTED]> wrote:

> The Kato proposal has been out for discussion for a few weeks now,
> please vote on accepting the Kato project for incubation.
>
> The full Kato proposal is available at the end of this message and as
> a wiki page at http://wiki.apache.org/incubator/KatoProposal.
>
> Here is my +1
>
>   ...ant
>
> = Kato - Post-mortem JVM Diagnostics API and RI/TCK for JSR 326 =
>
> Abstract
>
> Kato is a project to develop the Specification, Reference
> Implementation and Technology Compatibility Kit for JSR 326:
> Post-mortem JVM Diagnostics API
> Proposal
>
> JSR 326 is intended to be a Java API specification for standardising
> how and what can be retrieved from the contents of post-mortem
> artefacts -- typically process and JVM dumps. Project Kato is intended
> to be the place where the Specification, Reference implementation (RI)
> and Technology Compatibility Kit (TCK) are openly created. The
> intention is that the Specification and RI will be developed in tight
> unison, guided by a user-story-focused approach to ensure that
> real-world problems drive the project from the beginning.
>
> Unusually for new APIs, this project will endeavour to encompass the
> old and the new. A diagnostic solution that only works when users move
> to the latest release does little to improve diagnosability in the
> short term. This project will consume existing dump artefacts as well
> as possible while developing an API that can address the emerging
> trends in JVM and application directions. The most obvious of these
> trends are the exploitation of very large heaps, alternative languages
> and, paradoxically for Java, the increased use of native memory
> through vehicles such as NIO.
> Background
>
> Post-mortem versus Live Monitoring: It's worth noting that the term
> "post mortem" is used loosely. It does not just imply dead JVMs and
> applications; JSR 326 also covers living, breathing applications where
> the dump artefacts are deliberately produced as part of live
> monitoring activity. Live monitoring generally means tracing,
> profiling, debugging, or even bytecode monitoring and diagnosis by
> agents via the java.lang.instrument API . It can also mean analysis of
> dumps to look for trends and gather statistics. The live-monitoring
> diagnostic space is well served except for this last area, which is
> where JSR 326 can help.
>
> IBM developed an API called DTFJ ("Diagnostic Tooling and Framework
> for Java") as a means of providing its support teams a basis on which
> to write tools to diagnose Java SDK and Java application faults. It
> consists of a native JVM-specific component and the DTFJ API, which
> was written in pure Java.
> Rationale
>
> JSR 326 exists because of the widely acknowledged limitations in
> diagnosing Java application problems after the fact. There are many
> good ways to understand and diagnose problems while they happen, but
> few credible or pervasive tools exist for helping resolve problems
> when all has gone suddenly and horribly wrong. Outside of "live
> monitoring" there is no standard way to provide diagnostics
> information, and hence no standard tools. Each tool writer has to
> figure out how to access the data individually and specifically for
> each JVM vendor and operating system. This sparsity of tools has meant
> that users have limited options in diagnosing their own problems,
> especially unexpected or intermittent failures. Consequently these
> users turn to the providers of their software to work out what is
> happening. Application, middleware, and JVM vendors are spending
> increasing time supporting customers in problem diagnosis. Emerging
> trends indicate that this is going to get worse.
>
> Today JVM heap sizes are measured in small numbers of gigabytes,
> processors on desktops come in twos or fours, and most applications
> running on a JVM are written in Java. To help analyse problems in
> these configurations, we use a disparate set of diagnostic tools and
> artefacts. If the problem can't be reproduced in a debugger, then
> things quickly get complicated. There are p

Re: [PROPOSAL] Stonehenge

[ant elder]

On Tue, Nov 4, 2008 at 4:34 PM, Paul Fremantle <[EMAIL PROTECTED]> wrote:
> I'd like to propose Stonehenge as an incubator proposal.
>
> Stonehenge is a set of example applications for Service Oriented
> Architecture that spans languages and platforms and demonstrates best
> practise and interoperability.
>
> The full proposal is here: http://wiki.apache.org/incubator/StonehengeProposal
>
> As ever, all feedback, positive or negative is welcome. Also, any
> further mentors are more than welcome!
>

This sounds like it has a lot of potential. Looks like you've plenty
of mentors now but I'll forward it to the Tuscany mailing lists to see
if we can get some Tuscany folks to help with showing Tuscany/SCA in
the Stonehenge apps.

   ..ant

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

Re: [VOTE] Qpid Graduation - for top level

[ant elder]

+1

   ...ant

On Wed, Nov 12, 2008 at 8:51 PM, Carl Trieloff <[EMAIL PROTECTED]> wrote:
>
> It is with the support of our mentors and a community vote on our dev list
> that Qpid
> would like to graduate. In our last graduation vote the incubator PMC felt
> that the
> Qpid project should increase its diversity. Over the intervening months Qpid
> has
> added more independents to the project & PPMC, bringing the diversity to 7
> legally
> independent parties (not counting those mentors who will stay on to help
> advise), with
> the PPMC diversity at 5 legally independent parties (also not counting
> mentors).
>
> Qpid also continues to attract more contributors (both independents and
> large corporates),
> so the committer pool and diversity should continue to expand as
> contributors are voted
> in as committers.
>
> Qpid has also made an additional release since the last graduation attempt
> and is currently
> working through close down of the next release. Qpid was accepted into the
> incubator
> August 2006.
>
> Attached is the graduation resolution, Please consider your vote for our
> graduation.
>
> many thanks.
> Carl.
>
>
> ---
>
> WHEREAS, the Board of Directors deems it to be in the best
> interests of the Foundation and consistent with the
> Foundation's purpose to establish a Project Management
> Committee charged with the creation and maintenance
> of open-source software related to distributed messaging,
> for distribution at no charge to the public.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "Apache Qpid Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that the Apache Qpid Project be and hereby is
> responsible for the creation and maintenance of software
> related to distributed messaging; a multiple language
> implementation providing daemons and APIs for publish &
> subscribe, eventing and a wide range of message distribution patterns
> based on the Advanced Message Queuing Protocol (AMQP) and
> related technologies such as (transaction management, federation,
> security, management); and be it further
>
> RESOLVED, that the office of "Vice President, Qpid" be and
> hereby is created, the person holding such office to serve at
> the direction of the Board of Directors as the chair of the
> Apache Qpid Project, and to have primary responsibility for
> management of the projects within the scope of responsibility
> of the Apache Qpid Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and
> hereby are appointed to serve as the initial members of the
> Apache Qpid Project:
>
>   * Aidan Skinner
>   * Alan Conway
>   * Arnaud Simon
>   * Carl Trieloff
>   * Craig Russell
>   * Gordon Sim
>   * Jonathan Robie
>   * John O'Hara
>   * Kim van der Riet
>   * Marnie McCormack
>   * Martin Ritchie
>   * Manuel Teira
>   * Paul Fremantle
>   * Nuno Santos
>   * Rafael Schloming
>   * Rajith Attapattu
>   * Robert Greig
>   * Robert Godfrey
>   * Steve Huston
>   * Ted Ross
>   * Yoav Shapira
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that
> Carl Trieloff be appointed to the office of Vice President,
> Qpid, to serve in accordance with and subject to the
> direction of the Board of Directors and the Bylaws of the
> Foundation until death, resignation, retirement, removal or
> disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that all responsibility pertaining to the Qpid
> encumbered upon the Apache Incubator be hereafter discharged.
>
>
>

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

Re: Outstanding INFRA Issues for KATO Project

[ant elder]

On Mon, Feb 2, 2009 at 7:21 AM, Steve Poole wrote:

> On Mon, Feb 2, 2009 at 2:38 AM, Gavin  wrote:
>
> > Hi All,
> >
> > Since KATO was accepted into Incubator in November, there were some of
> the
> > usual requests for stuff to be set up by INFRA.
> >
> > On 3rd December I set up the KATO Jira Project. It is ready to be used.
> One
> > remaining item for that Issue -
> > (https://issues.apache.org/jira/browse/INFRA-1784)is
> for the creation of
> a
> > Jira account for S Goyal; so I can then put SGoyal into the correct
> > groups/permissions etc.
> >
> > Another issue (https://issues.apache.org/jira/browse/INFRA-1783) shows
> > that
> > we are still waiting for CLAs from a couple of folk.
> >
>
> Hi Gav -  I think this is a all done -  but I'll defer to Ant who did all
> the work.
>
> >
> > If this is all in hand then sorry for the noise, I'm just trying to have
> a
> > tidy up of some Infra Issues and these have been hanging around for a
> > couple
> > of months. I'd have thought new podlings would be eager to get on.
> >
>
> > Cheers
> >
> > Gav...
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Just got the last CLA in last Friday, I'll ping Sonal about the JIRA
account, other than those i think its almost there :)

   ...ant

Re: [VOTE] Suspending Projects -- XAP

[ant elder]

On Mon, Feb 16, 2009 at 6:56 PM, Noel J. Bergman  wrote:

> In August 2008, it was discussed that XAP had been inactive for at least 4
> months.  In November 2008, we again saw issues with XAP and discussed
> suspension.  Having reached, now, February 2009, and still nothing with
> XAP,
> I am raising this as a vote.
>
>--- Noel
>

+1

   ...ant

Re: [VOTE] Release Apache Etch 1.0.2-incubating

[ant elder]

On Wed, Mar 4, 2009 at 1:54 AM, James Dixson  wrote:

>
> Ok folks I believe we have our first Apache release candidate for Etch:
> apache-etch-1.0.2-incubating.
>
> With this release we have updated all of the licensing/headers for the
> project to meet Apache standards, fixed a few bugs and validated under
> Windows, OS X and Linux (Ubuntu).
>
> Complete listing of what was fixed is here:
> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310835&fixfor=12313456
>
>
> We *have not* in 1.0.2 changed the package names from "etch" to
> "org.apache.etch", that change will be in our next release,
> apache-etch-1.1-incubating, which will be ready for release in another 2-3
> weeks. We did not change the package names to maintain compatibility for
> folks running the pre-apache 1.0.x releases who are only interested in
> bug-fixes.
>
> We have met the threshold for committer votes in the following threads:
>
>  http://n2.nabble.com/-vote--Release-1.0.2-td2294748.html
>  
> http://n2.nabble.com/-vote--Release-1.0.2-(second-attempt)-td2360187.html
>
>
> The candidate files can be found here:
>   
> http://people.apache.org/~dixson/apache-etch/1.0.2-incubating/
>
> Each file has a MD5, SHA1 and a Signature.
>
> Finally, the output from RAT is also included in the "*-rat-output.txt"
> file.
>
>
> --
> james
>
>
I can't find a DISCLAIMER file or the Incubator disclaimer text anywhere in
the release artifacts. If it is there and I've just missed it then +1 as the
rest of it looks good, but if the disclaimer is missing then that probably
needs to be fixed.

A couple of other non-blocking comments:

Nothing in the readme or releases notes says what Etch does, might be nice
to have a brief sentence or two saying what the project is about.

There's a Cisco copyright at the top of all the source files, can that be
moved to the NOTICE file as described at:
http://www.apache.org/legal/src-headers.html#headers

   ...ant

Re: [VOTE] Release Apache Etch 1.0.2-incubating

[ant elder]

There needs to be this text included:

"Apache Etch is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by the Apache Incubator PMC. Incubation is
required of all newly accepted projects until a further review indicates
that
the infrastructure, communications, and decision making process have
stabilized
in a manner consistent with other successful ASF projects. While incubation
status is not necessarily a reflection of the completeness or stability of
the
code, it does indicate that the project has yet to be fully endorsed by the
ASF."

The Incubator policy page mentions that this is required:

"the release archive MUST contain an Incubation disclaimer (as described in
the previous section)"
  - http://incubator.apache.org/incubation/Incubation_Policy.html#Releases

but that previous section mentioned appears to be missing. The release
management guide also mentions it but has a TODO to finish the section:

"TODO: the incubator requires that users are informed that the by including
a standard disclaimer. may be include in README, RELEASE_NOTES DISCLAIMER."
 -
http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer

That guide recommends that the disclaimer is included in the NOTICE but I'm
not sure that is correct these days and I thought now either a separate
DISCLAIMER file or including the disclaimer text in the top README was
preferred.

   ...ant

On Wed, Mar 4, 2009 at 2:20 PM, James Dixson  wrote:
>
> I probably missed the disclaimer text completely. Is there a
> web-page/reference that describes what should be in it?
>
> As for the headers, this is a known inconsistency in some of the
> source files. We have already corrected it in trunk and it will be
> part of the 1.1 release.
>
> --
> james
>
>
> On Wed, Mar 4, 2009 at 4:06 AM, ant elder  wrote:
> > On Wed, Mar 4, 2009 at 1:54 AM, James Dixson  wrote:
> >
> >>
> >> Ok folks I believe we have our first Apache release candidate for Etch:
> >> apache-etch-1.0.2-incubating.
> >>
> >> With this release we have updated all of the licensing/headers for the
> >> project to meet Apache standards, fixed a few bugs and validated under
> >> Windows, OS X and Linux (Ubuntu).
> >>
> >> Complete listing of what was fixed is here:
> >>
https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310835&fixfor=12313456
> >>
> >>
> >> We *have not* in 1.0.2 changed the package names from "etch" to
> >> "org.apache.etch", that change will be in our next release,
> >> apache-etch-1.1-incubating, which will be ready for release in another
2-3
> >> weeks. We did not change the package names to maintain compatibility
for
> >> folks running the pre-apache 1.0.x releases who are only interested in
> >> bug-fixes.
> >>
> >> We have met the threshold for committer votes in the following threads:
> >>
> >>  http://n2.nabble.com/-vote--Release-1.0.2-td2294748.html
> >>
http://n2.nabble.com/-vote--Release-1.0.2-(second-attempt)-td2360187.html<http://n2.nabble.com/-vote--Release-1.0.2-%28second-attempt%29-td2360187.html>
<
http://n2.nabble.com/-vote--Release-1.0.2-%28second-attempt%29-td2360187.html
>
> >>
> >>
> >> The candidate files can be found here:
> >>   
> >> http://people.apache.org/~dixson/apache-etch/1.0.2-incubating/<http://people.apache.org/%7Edixson/apache-etch/1.0.2-incubating/>
<http://people.apache.org/%7Edixson/apache-etch/1.0.2-incubating/>
> >>
> >> Each file has a MD5, SHA1 and a Signature.
> >>
> >> Finally, the output from RAT is also included in the "*-rat-output.txt"
> >> file.
> >>
> >>
> >> --
> >> james
> >>
> >>
> > I can't find a DISCLAIMER file or the Incubator disclaimer text anywhere
in
> > the release artifacts. If it is there and I've just missed it then +1 as
the
> > rest of it looks good, but if the disclaimer is missing then that
probably
> > needs to be fixed.
> >
> > A couple of other non-blocking comments:
> >
> > Nothing in the readme or releases notes says what Etch does, might be
nice
> > to have a brief sentence or two saying what the project is about.
> >
> > There's a Cisco copyright at the top of all the source files, can that
be
> > moved to the NOTICE file as described at:
> > http://www.apache.org/legal/src-headers.html#headers
> >
> >   ...ant
> >

Re: [vote] Apache Etch 1.0.2-incubating (second attempt)

[ant elder]

+1

   ...ant

On Thu, Mar 12, 2009 at 1:54 PM, James Dixson  wrote:
> Here are new package versions for apache-etch-1.0.2-incubating. A
> DISCLAIMER.txt is now included...
>
> From the original vote request...
>
>>  Ok folks I believe we have our first Apache release candidate for Etch: 
>> apache-etch-1.0.2-incubating.
>>
>> With this release we have updated all of the licensing/headers for the 
>> project to meet Apache standards, fixed a few bugs and validated under 
>> Windows, OS X and Linux (Ubuntu).
>>
>>  Complete listing of what was fixed is here: 
>> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12310835&fixfor=12313456
>>
>>  We *have not* in 1.0.2 changed the package names from "etch" to 
>> "org.apache.etch", that change will be in our next release, 
>> apache-etch-1.1-incubating, which will be ready for
>>  release in another 2-3 weeks. We did not change the package names to 
>> maintain compatibility for folks running the pre-apache 1.0.x releases who 
>> are only interested in bug-fixes.
>>
>>  We have met the threshold for committer votes in the following threads:
>>
>>    http://n2.nabble.com/-vote--Release-1.0.2-td2294748.html
>>    http://n2.nabble.com/-vote--Release-1.0.2-(second-attempt)-td2360187.html
>>
>>
>>  The candidate files can be found here:
>>     http://people.apache.org/~dixson/apache-etch/1.0.2-incubating/
>>
>>  Each file has a MD5, SHA1 and a Signature.
>>
>>  Finally, the output from RAT is also included in the "*-rat-output.txt" 
>> file.
>
> ---
> james
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Missing board reports, due today!

[ant elder]

On Tue, Apr 7, 2009 at 10:16 AM, Martijn Dashorst
 wrote:
> The following podlings should report today on their status, but have
> yet to write up their report [1]:
>
> Bluesky
> Cassandra
> Empire-db
> Imperius
> JSPWiki
> Kato
> Ki
> Lucene.Net
> Olio
> RCF
> Stonehenge
> Tashi
> Thrift
> UIMA
>
> Please submit your report today! Remember to include:
>
> The "incubating since" info
> The project's top 2 or 3 things to resolve prior to graduation
> A short description of what your project's software does
>
> Martijn
>
> [1] http://wiki.apache.org/incubator/April2009

I don't think Kato is reporting this month, they've done the 3 monthly
reports when first starting incubation (dec/jan/feb) and are now on
quarterly reporting (mar/jun/sept/dec). So i've removed the Kato
heading from the April report page.

   ...ant

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Pivot 1.1 (second try)

[ant elder]

On Thu, Apr 16, 2009 at 4:34 PM, Todd Volkert  wrote:

> Actually, it occurs to me that since the distribution archives don't
> have the offending code, we should be able to release 1.1 as packaged
> (pending the vote), and if legal-discuss says that we need to remove
> that stuff from SVN, that can be done after the fact.
>
> -T
>
>
I agree.

These artifacts look ok to me now. Would be helpful to include RAT reports
for both the src and binary distributions next time.

+1

   ...ant

Re: [VOTE] Release Apache Pivot 1.1 (second try)

[ant elder]

On Fri, Apr 17, 2009 at 3:48 AM, Niclas Hedhman  wrote:

> On Thu, Apr 16, 2009 at 11:07 PM, sebb  wrote:
>
> > As far as I know, putting a file in a publicly accessible SVN
> > repository is considered as distribution too.
>
> No, I am very positive that this is not the case. Legal dilligence is
> done on the release artifacts separately from SVN issues. Unlike
> release artifacts, SVN are at times incomplete, incorrect and
> inaccurate. "Tags" have no legal meaning whatsoever, and should not
> even be part of the discussion.
>
>
And that matches "What is a release?" in the ASF Releases FAQ (although SVN
its not explicitly mentioned): http://www.apache.org/dev/release.html#what

   ...ant

Re: [VOTE] Release Apache Pivot 1.1 (second try)

[ant elder]

On Fri, Apr 17, 2009 at 9:05 AM, Niclas Hedhman  wrote:
> On Fri, Apr 17, 2009 at 2:59 PM, ant elder  wrote:
>> On Fri, Apr 17, 2009 at 3:48 AM, Niclas Hedhman  wrote:
>>
>>> On Thu, Apr 16, 2009 at 11:07 PM, sebb  wrote:
>>>
>>> > As far as I know, putting a file in a publicly accessible SVN
>>> > repository is considered as distribution too.
>>>
>>> No, I am very positive that this is not the case. Legal dilligence is
>>> done on the release artifacts separately from SVN issues. Unlike
>>> release artifacts, SVN are at times incomplete, incorrect and
>>> inaccurate. "Tags" have no legal meaning whatsoever, and should not
>>> even be part of the discussion.
>>>
>>>
>> And that matches "What is a release?" in the ASF Releases FAQ (although SVN
>> its not explicitly mentioned): http://www.apache.org/dev/release.html#what
>
> Uhhh, sorry, are you agreeing or disagreeing with me?
>

Agreeing with you, sorry if that wasn't clear.

   ...ant

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] Apache Click graduation

[ant elder]

On Fri, Apr 24, 2009 at 7:06 AM, Andrus Adamchik  wrote:
>> Additional concern, it does not appear that the mentors are planning to
>> be on the PMC. Why not?
>
> Why is this a concern? Mentors volunteer to do mentoring to ensure the
> project is viable and understands the Apache way, not necessarily to develop
> code. If you trace the existing Apache projects back to the incubator, I'd
> suspect 70% of them will not have their original mentors on the PMC.
>
> Andrus
> Apache Click Mentor
>

The incubator projects i've been involved in have all had at least
some of mentors stay on the PMC when graduating. It certainly wont
hurt having some extra people around who are familiar with both the
project and the ASF. In this case when the proposed PMC is so small i
can't see why you wouldn't want to add them, to avoid the problem of
needing 3 binding votes when someone is out on holiday, or even if
just to save getting bogged down in general@ debate on whether the PMC
is big enough to graduate.

It does look at little odd to enter incubation with 4 committers and
leave with only 3 on the PMC but still the original 4 are all active
enough to have just voted for graduation on the click dev list. Also,
about 10 people voted on click-dev for graduation, are any more of
those active enough to be made committers and pmc members?

What is the diversity of the three, do you all work for different companies?

   ...ant

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org