[
https://issues.apache.org/jira/browse/MNGSITE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604982#comment-17604982
]
ASF GitHub Bot commented on MNGSITE-491:
----------------------------------------
olamy commented on PR #321:
URL: https://github.com/apache/maven-site/pull/321#issuecomment-1247317875
> > > I feel that forcing apache committers to use non-apache (gh)
infrastructure by building a process that requires using github might be
problematic. If I were on the PMC, I would probably ask the board about this.
> >
> >
> > I think this is a valid point. If we are documenting a process that uses
GH PRs then _at the same time_ we should document the process to follow for
those who only want to use ASF owned infra (i.e. what do you do if you are
using gitbox). This second process will also serve as a fallback if the
co-operation with GH ceased (and remember that the ASF is tasked with
developing software for the public good, so it has a corporate responsibility
to ensure continuity... which is why we have gitbox... even if it can seem like
overkill some of the time)
>
> See: [#321
(comment)](https://github.com/apache/maven-site/pull/321#discussion_r967685008)
PR on GH is _one_ way, but not the only one. Patch in JIRA issue or branch with
review request on dev@ is as good as.
correct.
We (Apache) need to be able to accept contributions from everybody without
discrimination as some countries may have no access to GitHub see
(https://docs.github.com/en/site-policy/other-site-policies/github-and-trade-controls)
> Update commit policy related documents to avoid any misunderstanding
> --------------------------------------------------------------------
>
> Key: MNGSITE-491
> URL: https://issues.apache.org/jira/browse/MNGSITE-491
> Project: Maven Project Web Site
> Issue Type: Improvement
> Reporter: Tamás Cservenák
> Priority: Major
>
> Last update related to commit policies happened while project was still
> hosted in Subversion. Since then, a LOT of that changed (migrated to git,
> using Github.com, etc), so refresh the parts that are dated since Svn and are
> related to commit policies.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
