lucenenet-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Laimonas Simutis <lai...@gmail.com>
Subject Re: ASF Board Report for Lucene.Net - Repeated Reminder for February 2019
Date Fri, 01 Feb 2019 16:44:20 GMT
Prescott, just saw the report email.   Thank you!

On Thu, Jan 31, 2019 at 8:28 PM Laimonas Simutis <laimis@gmail.com> wrote:

> Arsen,
>
> I am waiting to hear back from Shannon on site and moving his site bits
> from his PR https://github.com/apache/lucenenet/pull/206 to
> https://github.com/apache/lucenenet-site. Once that's done we can ask
> INFRA to sync lucenenet.apache.org from there. Shannon had the latest
> site up here: https://lucenenetsite.azurewebsites.net/.
>
> Laimonas
>
>
> On Thu, Jan 31, 2019 at 7:15 PM Arsen Shnurkov <arsen.shnurkov@gmail.com>
> wrote:
>
>> a bit more details will be usefull.
>>
>> If there is a site - then URL to check will be usefull. If repository -
>> then where it is located, and so on.
>>
>> On 31.01.2019 23:41, Laimonas Simutis wrote:
>> > Anyone from PMC here that could do this for the project? I am not
>> exactly
>> > sure what is usually submit, perhaps this could help:
>> >
>> > Contributions:
>> >
>> > - 1 JIRA ticket fixed
>> > - 1 PR opened, for improving merge stability, it's being reviewed
>> >
>> > General Activity:
>> >
>> > - new website repo provisioned, getting assets ready for the update
>> >
>> > - working on CI servers to bring back the builds to a normal cadence.
>> The
>> > hosts have changed from codebetter to jetbrains and the workflows are
>> > broken as a result. Once complete we will be back to getting feedback on
>> > current open PRs to get final verification if they are ready to be
>> merged
>> > as tests that CI servers run are very informative.
>> >
>> > - major JIRA cleanup with outdated tickets closed. Critical tickets for
>> 4.8
>> > release are being identified. The goal is to make sure we don't have any
>> > outstanding 4.8 issues and we can release 4.8.
>> >
>> >
>> > Nuget downlaod activity for the last six weeks:
>> >
>> > 4.8.0-beta00005 8,848
>> > 4.8.0-beta00004 2,338
>> > 3.0.3 100,300
>> >
>> >
>> > Laimonas
>> >
>> >
>> >
>> > On Thu, Jan 31, 2019 at 1:58 PM Phil Steitz <psteitz@apache.org> wrote:
>> >
>> >> Dear Lucene-Net community,
>> >>
>> >> In the governance model at the ASF the board delegates responsibility
>> for
>> >> managing projects to PMCs. To enable the board to provide oversight
>> across
>> >> the
>> >> foundation, PMCs are tasked with providing the board with a quarterly
>> >> report on the health of the project. The board has noticed that the
>> reports
>> >> for Lucene-Net 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
>> >>
>> >> Please ensure that a report for Lucene-Net 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
>> >>
>> >> 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
>> >> Lucene-Net 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.
>> >>
>> >> Thanks,
>> >> The ASF Board
>> >>
>> >> [1] (http://attic.apache.org/
>> >>
>>
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message