axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rich Bowen <rbo...@rcbowen.com>
Subject Re: Axis move to the Attic (was: Board concerns over Axis project reports - README)
Date Thu, 12 Oct 2017 12:21:41 GMT
On 10/11/2017 10:23 PM, Deepal jayasinghe wrote:
> I agree with Robert, Andreas is really active and he was able to push 
> forward a release few weeks back as well.
> 
> I really like him to be the PMC chair and we can give required support 
> to him

This is clearly the preferred outcome. Please make it happen.

Thanks.

--Rich

> 
> Deepal
>> I was waiting for Andreas Veithen to reply since he is by far the most 
>> active contributor to Axis2 currently.
>>
>> I have a vested interest in Axis2 going forward as its used 
>> extensively by the company I work for. The CVE questions that come up 
>> periodically with Axis2 and its dependencies are essential for the 
>> project to continue, and I don't expect being in the attic will allow 
>> Axis2 to be used in production projects.
>>
>> I have been a committer to Axis2 since 2006. I contributed the Spring 
>> Framework support to Axis2, ported the SOAP Monitor from Axis1 to 
>> Axis2, and wrote some docs explaining both of these and also the Ant 
>> commands. This was all years go.
>>
>> Since then I did respond to some recent security questions regarding 
>> the SOAP Monitor, and I do help on the user list around once a month.
>>
>> From my perspective, we have at least 3 active members as we have had 
>> several releases this year already. No problems voting. Because of any 
>> CVE's I always run the latest version and dependencies, so I do test 
>> the releases.
>>
>> The main problem as I see it, is no one has stepped up to take over 
>> the monthly Apache board reports as required for the Axis2 project. I 
>> am not sure I am the right person for it, though it doesn't seem hard.
>>
>> As stated, I am hoping Andreas Veithen can share his thoughts.
>>
>> Kind regards,
>> Robert
>>
>>
>> On Wed, Oct 11, 2017 at 6:03 PM, Davanum Srinivas <davanum@gmail.com 
>> <mailto:davanum@gmail.com>> wrote:
>>
>>     +1 from me (Axis->Attic). Lot's of good memories :) Thanks Shane.
>>
>>     -- Dims
>>
>>     On Wed, Oct 11, 2017 at 4:50 PM, Shane Curcuru
>>     <asf@shanecurcuru.org <mailto:asf@shanecurcuru.org>> wrote:
>>     > (bcc: general@, c-dev@, board@ for FYI)
>>     >
>>     > Since there hasn't been any response to the below email by any PMC
>>     > members (or indeed any community members), it may be time Axis
>>     to go to
>>     > the Apache Attic, and turn the entire project read-only.
>>     >
>>     > To be blunt: if there are not three active PMC members to ensure
>>     that
>>     > the board has quarterly reports and the project could vote on a
>>     > potential security release, my estimate is that the board will
>>     move the
>>     > entire Axis project to the Attic no later than the November board
>>     > meeting, possibly earlier.
>>     >
>>     > I strongly urge any PMC members or even committers on the project to
>>     > step up, propose a new PMC chair, and work on a report for the
>>     board ASAP.
>>     >
>>     > ---- Some perspective on why board reports are important ----
>>     >
>>     > In the governance model at the ASF the board delegates
>>     responsibility
>>     > for managing projects to PMCs. To enable to board to provide
>>     oversight
>>     > across the foundation, the the PMCs aretasked with providing the
>>     board
>>     > with a quarterly report on the health of the project. The board has
>>     > noticed that the reports for XXX have been missed for a number
>>     > of months.
>>     >
>>     > The reports to the board are normally written by the PMC chair
>>     but all
>>     > PMC members have an individual responsibility to ensure that a
>>     report is
>>     > submitted. If the PMC chair is not available then any PMC member can
>>     > submit the report. If you need help with this process, please
>>     reach out
>>     > to board@apache.org <mailto:board@apache.org>
>>     >
>>     > Please ensure that a report for XXX is submitted to the board
>>     for the
>>     > next meeting.
>>     >
>>     > If the PMC chair is not going to be available for an extended
>>     period of
>>     > time it may make sense to rotate the PMC chair. Rotating the PMC
>>     chair
>>     > does not mean the current chair has failed. People's situations and
>>     > interests change, and rotation is good as it allows more people to
>>     > become familiar with that role. Again, if assistance is required
>>     with
>>     > this process, please feel free to reach out to board@apache.org
>>     <mailto:board@apache.org>
>>     >
>>     > As projects mature, they will naturally reach a point where activity
>>     > reduces to a level that the project is no longer sustainable. At
>>     Apache,
>>     > projects reach this stage when there are no longer 3 active PMC
>>     members
>>     > providing oversight. Projects that reach this stage are placed
>>     in the
>>     > attic [1].  If XXX has reached this point, please reach out to
>>     the Attic
>>     > project to arrange transfer. On the other hand, if your project is
>>     > mostly dormant but still has at least three active PMC members
>>     it can
>>     > stay in that state for as long as needed. If your project is in
>>     such a
>>     > state, please mention that in your report and verify the PMC's
>>     state at
>>     > regular intervals.
>>     >
>>     > Finally, if you have any questions please feel free to reach out to
>>     > board@apache.org <mailto:board@apache.org>
>>     >
>>     > ----
>>     >
>>     > On 2017-09-20 10:31, Shane Curcuru <asf@shanecurcuru.org
>>     <mailto:asf@shanecurcuru.org>> wrote: > (Note
>>     > mixed private/public lists)
>>     >>
>>     >> The ASF requires that any Apache project have at least three
>>     somewhat
>>     >> active PMC members - such that they can do things like review
>>     patches,
>>     >> and in particular vote to release a software update in case of
>>     security
>>     >> issues.  To verify that Apache projects are still operating by ASF
>>     >> policies, the board requires that each PMC provides a report of
>>     activity
>>     >> and project health each quarter.
>>     >>
>>     >> It's clear there's still some contributors wanting to work on
>>     Axis, but
>>     >> lately, it's equally clear from watching the lack of acceptable
>>     reports
>>     >> to the board that the PMC as a whole is not working out.
>>     >>
>>     >> I strongly urge all PMC members still listening here to work
>>     out among
>>     >> yourselves a plan to 1) choose a new project chair and
>>     recommend them to
>>     >> the board ASAP and 2) engage with the contributors still here
>>     to review
>>     >> their work and keep the project moving forward.
>>     >>
>>     >> If the PMC (and/or committers on the project) can't show some
>>     obviously
>>     >> organized energy at project management, then perhaps it's time
>>     for the
>>     >> project as a whole to consider moving to the Attic soon.
>>     >
>>     > --
>>     >
>>     > - Shane
>>     > https://www.apache.org/foundation/marks/resources
>>     <https://www.apache.org/foundation/marks/resources>
>>
>>
>>
>>     --
>>     Davanum Srinivas :: https://twitter.com/dims
>>
>>     ---------------------------------------------------------------------
>>     To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
>>     <mailto:java-dev-unsubscribe@axis.apache.org>
>>     For additional commands, e-mail: java-dev-help@axis.apache.org
>>     <mailto:java-dev-help@axis.apache.org>
>>
>>
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: java-dev-unsubscribe@axis.apache.org
For additional commands, e-mail: java-dev-help@axis.apache.org


Mime
View raw message