> On Jun 19, 2026, at 12:57 AM, sebb <[email protected]> wrote:
> 
> On Fri, 19 Jun 2026 at 05:28, tison <[email protected]> wrote:
>> 
>> One thing I'm feeling trouble to work with the reporter is that I'm quite
>> unfamiliar with its deployment and all possible patches in my mind can't be
>> verified.
>> 
>> Not sure if it's possible to move to GitHub and build a well self-hosted
>> test environment so that one can help in maintenance.
> 
> There is already a Docker build, see DOCKER.md here
> 
> https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk/
> 
> Whilst it would be possible to move the code to Git, this would
> involve quite a lot of changes (e.g. Puppet)
> Also the SVN tree incudes data as well as code; there would be more
> changes needed if that was moved to Git.
> 
> AIUI there are plans to merge it with BAT, which would simplify
> authentication between the two.
> So I am sure it is worth the effort for a short-term benefit.
> 
> I don’t know how much work it would be for Infra to create a Git
> mirror of the code.
> That might be. useful stop-gap.

I think we can improve BAT within two months. Tison has made PRs there and it 
would be a reasonable goal to eliminate reporter.

Best,
Dave

> 
> Sebb
>> Best,
>> tison.
>> 
>> 
>> Maxim Solodovnik <[email protected]> 于2026年6月19日周五 11:00写道:
>> 
>>> Hello All,
>>> 
>>> I would like to ask not to remove reporter.a.o completely
>>> It can generate some part of the report like "Recent releases" and
>>> show some community health stats
>>> I would love to see such report helpers in Board Agenda Tool :)
>>> 
>>> On Sat, 13 Jun 2026 at 22:33, Dave Fisher <[email protected]> wrote:
>>>> 
>>>> We do have s test server, I’ll need to dig up the co-ordinates and can
>>> give access next week.
>>>> 
>>>> The tooling team has some work to do on projects.apache.org which
>>> shares its host with the reporter.
>>>> 
>>>> Our work will be in July or so.
>>>> 
>>>> Best,
>>>> Dave
>>>> 
>>>>> On Jun 12, 2026, at 6:38 PM, tison <[email protected]> wrote:
>>>>> 
>>>>> Hi,
>>>>> 
>>>>> We are continuously receiving reports that the Reporter Tool doesn't
>>> work
>>>>> in some scenarios.
>>>>> 
>>>>> Right now, the new Board Agenda Tool (https://agenda.apache.org/)
>>> provides
>>>>> similar tools to PMCs for reporting.
>>>>> 
>>>>> The source code of Reporter can be found here:
>>>>> 
>>>>> svn co
>>> https://svn.apache.org/repos/asf/comdev/reporter.apache.org/trunk/
>>>>> 
>>>>> I have three questions here:
>>>>> 
>>>>> 1. If I'd patch the reporter, is there a workflow like GitHub's PR and
>>>>> GitHub Actions I can ask for review and check the effect of the change
>>> set?
>>>>> I don't even know how the source code gets deployed.
>>>>> 
>>>>> 2. Shall we guide people to use Agenda Tool instead of Reporter? I
>>> don't
>>>>> know if anyone (Sebb?) is maintaining the Reporter.
>>>>> 
>>>>> 3. If (2) is the way to go, I can foresee that we have a notice in
>>>>> https://reporter.apache.org/about.html. But immediately I notice that
>>> I
>>>>> don't find a how-to page of the Agenda Tool to tell the PMC chair on
>>>>> reporting.
>>>>> 
>>>>> From what I knew, it could be done by "Agenda" > (Find Your Project) >
>>>>> “Controls | Post" > "Save" > (Remember to commit the staged change set)
>>>>> 
>>>>> Feedback?
>>>>> 
>>>>> Best,
>>>>> tison.
>>>> 
>>>> 
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: [email protected]
>>>> For additional commands, e-mail: [email protected]
>>>> 
>>> 
>>> 
>>> --
>>> Best regards,
>>> Maxim
>>> 
>>> ---------------------------------------------------------------------
>>> 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]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to