Re: Moving to github

--===============0282274280333843331==
Content-Type: multipart/alternative; boundary="000000000000c8bd43060d92aa69"

--000000000000c8bd43060d92aa69
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I think that this is a good suggestion and a good plan.

David


On Thu, Dec 28, 2023 at 3:21=E2=80=AFAM Matti Picus <[email protected]>=
 wrote:

> Now that 7.3.14 has been released, I would like to move the canonical
> repo for pypy and rpython to github. Reasons:
>
> - foss.heptapod.net is not well tracked in google/bing/duckduckgo
> search, so people find it hard to search for issues in the project
>
> - since the site has tightened its spam control, we get reports that
> users create issues only to have them flagged as spam
>
> - open source has become synonymous with github, and we are too small to
> change that
>
> - Much of the current development comes as a reaction to fixing issues.
> Tracking interlocking issues is easier if all the code is on the same
> platform
>
> - The FAQ [2] presents two arguments against the move. Github notes [3]
> solves much of point (1), although not entirely. But the main problem is
> point (2), it turns out that __not__ moving to github is an impediment
> to contribution and issue reporting.
>
> - As development effort winds down, github is a better archive for PyPy
> than foss.heptapod.net. I cannot predict the future, but if there is a
> move to revive the project, or to move to another platform, I believe
> github will provide a better jumping-off point as well. And since the
> repo at foss.heptapod.net will not be deleted, even if I am wrong I
> expect the effort to port the issues and commits from github will be
> manageable.
>
> - People who wish to continue to use mercurial can add a cron job github
> action to pull the changes from foss.heptapod.net across to github
>
> - github is more resource rich than foss.heptapod.net. We can add CI
> jobs to replace some of our aging buildbot infrastructure (still using
> buildbot 0.8 and python2).
>
>
> Technique:
>
>
> These steps will be done in a private repo
>
> - I will convert the repo to git and add a note to most of the commits
> (where I can) which will allow using "git log --notes=3Dbranch" to
> determine which branch a commit came from. More details at [0]
>
> - I will convert the issues and PRs to github via [1]. Using a private
> repo prevents spamming issue authors with emails about the transfer.
>
>
> Then I will make the repo public:
>
> - Move it to github.com/pypy/pypy
>
> - Freeze the issue tracker at
> https://foss.heptapod.net/pypy/pypy/-/issues, and add a message that
> development has moved
>
> - Write a blog post
>
> - Modify the links in the documentation
>
> - Activate the github action in [3] to add a branch note to each git comm=
it
>
>
> Anything else? Any suggestions to make the transition easier?
>
> Matti
>
>
> [0] https://gist.github.com/mattip/b6752c164a075c2aa53f4069e9c30573
>
> [1] https://github.com/piceaTech/node-gitlab-2-github
>
> [2]
>
> https://doc.pypy.org/en/default/faq.html#why-doesn-t-pypy-use-git-and-mov=
e-to-github
>
> [3] https://github.com/Julian/named-branch-action
>
> _______________________________________________
> pypy-dev mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/pypy-dev.python.org/
> Member address: [email protected]
>

--000000000000c8bd43060d92aa69
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I think that this is a good suggestion and a good plan.<di=
v><br></div><div>David</div><div><br></div></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Dec 28, 2023 at 3:21=E2=
=80=AFAM Matti Picus &lt;<a href=3D"mailto:[email protected]">matti.pic=
[email protected]</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">Now that 7.3.14 has been released, I would like to move the can=
onical <br>
repo for pypy and rpython to github. Reasons:<br>
<br>
- <a href=3D"http://foss.heptapod.net" rel=3D"noreferrer" target=3D"_blank"=
>foss.heptapod.net</a> is not well tracked in google/bing/duckduckgo <br>
search, so people find it hard to search for issues in the project<br>
<br>
- since the site has tightened its spam control, we get reports that <br>
users create issues only to have them flagged as spam<br>
<br>
- open source has become synonymous with github, and we are too small to <b=
r>
change that<br>
<br>
- Much of the current development comes as a reaction to fixing issues. <br=
>
Tracking interlocking issues is easier if all the code is on the same <br>
platform<br>
<br>
- The FAQ [2] presents two arguments against the move. Github notes [3] <br=
>
solves much of point (1), although not entirely. But the main problem is <b=
r>
point (2), it turns out that __not__ moving to github is an impediment <br>
to contribution and issue reporting.<br>
<br>
- As development effort winds down, github is a better archive for PyPy <br=
>
than <a href=3D"http://foss.heptapod.net" rel=3D"noreferrer" target=3D"_bla=
nk">foss.heptapod.net</a>. I cannot predict the future, but if there is a <=
br>
move to revive the project, or to move to another platform, I believe <br>
github will provide a better jumping-off point as well. And since the <br>
repo at <a href=3D"http://foss.heptapod.net" rel=3D"noreferrer" target=3D"_=
blank">foss.heptapod.net</a> will not be deleted, even if I am wrong I <br>
expect the effort to port the issues and commits from github will be <br>
manageable.<br>
<br>
- People who wish to continue to use mercurial can add a cron job github <b=
r>
action to pull the changes from <a href=3D"http://foss.heptapod.net" rel=3D=
"noreferrer" target=3D"_blank">foss.heptapod.net</a> across to github<br>
<br>
- github is more resource rich than <a href=3D"http://foss.heptapod.net" re=
l=3D"noreferrer" target=3D"_blank">foss.heptapod.net</a>. We can add CI <br=
>
jobs to replace some of our aging buildbot infrastructure (still using <br>
buildbot 0.8 and python2).<br>
<br>
<br>
Technique:<br>
<br>
<br>
These steps will be done in a private repo<br>
<br>
- I will convert the repo to git and add a note to most of the commits <br>
(where I can) which will allow using &quot;git log --notes=3Dbranch&quot; t=
o <br>
determine which branch a commit came from. More details at [0]<br>
<br>
- I will convert the issues and PRs to github via [1]. Using a private <br>
repo prevents spamming issue authors with emails about the transfer.<br>
<br>
<br>
Then I will make the repo public:<br>
<br>
- Move it to <a href=3D"http://github.com/pypy/pypy" rel=3D"noreferrer" tar=
get=3D"_blank">github.com/pypy/pypy</a><br>
<br>
- Freeze the issue tracker at <br>
<a href=3D"https://foss.heptapod.net/pypy/pypy/-/issues" rel=3D"noreferrer"=
 target=3D"_blank">https://foss.heptapod.net/pypy/pypy/-/issues</a>, and ad=
d a message that <br>
development has moved<br>
<br>
- Write a blog post<br>
<br>
- Modify the links in the documentation<br>
<br>
- Activate the github action in [3] to add a branch note to each git commit=
<br>
<br>
<br>
Anything else? Any suggestions to make the transition easier?<br>
<br>
Matti<br>
<br>
<br>
[0] <a href=3D"https://gist.github.com/mattip/b6752c164a075c2aa53f4069e9c30=
573" rel=3D"noreferrer" target=3D"_blank">https://gist.github.com/mattip/b6=
752c164a075c2aa53f4069e9c30573</a><br>
<br>
[1] <a href=3D"https://github.com/piceaTech/node-gitlab-2-github" rel=3D"no=
referrer" target=3D"_blank">https://github.com/piceaTech/node-gitlab-2-gith=
ub</a><br>
<br>
[2] <br>
<a href=3D"https://doc.pypy.org/en/default/faq.html#why-doesn-t-pypy-use-gi=
t-and-move-to-github" rel=3D"noreferrer" target=3D"_blank">https://doc.pypy=
.org/en/default/faq.html#why-doesn-t-pypy-use-git-and-move-to-github</a><br=
>
<br>
[3] <a href=3D"https://github.com/Julian/named-branch-action" rel=3D"norefe=
rrer" target=3D"_blank">https://github.com/Julian/named-branch-action</a><b=
r>
<br>
_______________________________________________<br>
pypy-dev mailing list -- <a href=3D"mailto:[email protected]" target=3D"_=
blank">[email protected]</a><br>
To unsubscribe send an email to <a href=3D"mailto:[email protected]=
" target=3D"_blank">[email protected]</a><br>
<a href=3D"https://mail.python.org/mailman3/lists/pypy-dev.python.org/" rel=
=3D"noreferrer" target=3D"_blank">https://mail.python.org/mailman3/lists/py=
py-dev.python.org/</a><br>
Member address: <a href=3D"mailto:[email protected]" target=3D"_blank">dje.=
[email protected]</a><br>
</blockquote></div>

--000000000000c8bd43060d92aa69--

--===============0282274280333843331==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
pypy-dev mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/pypy-dev.python.org/
Member address: [email protected]

--===============0282274280333843331==--