AFAIK, we don't have a Jira about that.
For Infra issues, we are requested to pass by
https://issues.apache.org/jira/servicedesk/customer/portal/1/create/3 or for
quick things Hipchat room.
Maybe though for such a long term request (documentation) the infra ML can be
used (but I think Jira is easier for both side)
I fear it could eventually be a karma issue (not enough rights, only infra
have) but we can't know w/o asking and karmas can evolve at the ASF...
Jacques
Le 07/01/2018 à 21:11, Taher Alkhateeb a écrit :
If anyone has information to share that would be great, or at least as
Michael pointed out if you know any documentation anywhere that can
help us identify how mirroring is done so we can resolve the issue
ourselves in the future then we can resolve this more quickly.
Perhaps we should start a new JIRA with infra but I'm not sure. Is
that appropriate or do we have a pending JIRA already?
On Sun, Jan 7, 2018 at 9:17 PM, Pierre Smits <pierresm...@apache.org> wrote:
Similarly to the OFBiz project, INFRA is for the greater part staffed with
volunteers (but I may have outdated insights). More often than not, and due
to the inability to enforce volunteers (with commitments beyond the
project) to take action on something they do not desire) this leads to a
technical debt regarding documentation. Also like our project.
Only one volunteer needs to step up to take the action, either to update
the documentation at INFRA (beyond our control), or in our confluence to
help our volunteers interacting with INFRA.
Best regards,
Pierre Smits
V.P. Apache Trafodion,
PMC Member Apache Directory
On Sun, Jan 7, 2018 at 5:36 PM, Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
So far I simply got to the Infra HipChat room and asked there.
Very successful most of the time, but not documented apart some messages I
sent to this ML and bookmarks I kept on them for myself, like "[FYI] Let's
encrypt certificate renewal failed"
Note that with infra things are moving fast and the documentation, rarely
used, can be deprecated in few years or even months. I did not say we
should not have ;)
Also, for simple things like lagging apps., you can't do much but asking
on Infra HipChat room (not ML , they don't like) or even ask for service
when you must: https://issues.apache.org/jira/servicedesk/customer/portal/
1/create/3
Jacques
Le 07/01/2018 à 16:56, Michael Brohl a écrit :
BTW, do we have documentation somewhere which explains who is responsible
for these services, how they work, where to lokk what's wrong and who to
inform if there are issues?
To me this is not clear for some of the services (like publishing the
website, fisheye, GitHub sync, ...) , but I admit that I did not try very
hard to find information about it.
Thanks,
Michael
Am 07.01.18 um 16:29 schrieb Pierre Smits:
It seems that is not the only service lagging in providing correct
results.
The same applies to fisheye. See
https://fisheye.apache.org/browse/ofbiz/ofbiz-framework/trunk
Best regards,
Pierre Smits
V.P. Apache Trafodion
On Sun, Jan 7, 2018 at 3:47 PM, Taher Alkhateeb <
slidingfilame...@gmail.com>
wrote:
Hey folks, it seems we still have this delay in our git account. Any
idea how to resolve this and why does it keep happening?
