Re: Migrating to GitHub

On Mon, May 25, 2020 at 9:43 AM Jeff Allen <[email protected]> wrote:

> We've wanted to do this for ages. If you go back far enough, you can
> find Jim confidently asserting we'd use GitHub for 2.7.2
> (
> https://sourceforge.net/p/jython/mailman/jython-dev/thread/CAOhO%3DaO_4GruQXQqmZk39a0C%3DXUnKyj%3DG6OcQtBkhtoQm9BCjw%40mail.gmail.com/#msg35054683
> ).
>

Hah, yes, I had much more confidence back before we got stuck on some
critical bugs finally resolved with the actual 2.7.2.


>
> Building with Gradle and accessing dependencies remotely (no JARs
> checked in) were identified as prerequisites at the time. In turn, I
> think building with Gradle requires re-organising the code to fit with
> its /convention over configuration/ idea
> (
> https://docs.gradle.org/current/userguide/organizing_gradle_projects.html#sec:use_standard_conventions).
>
> At least, doing otherwise in 2.7.2 got too difficult for me, somewhere
> around exposed classes ISTR.
>

+100


>
> These don't seem to be prerequisites for the move. I would do Jython 3
> that way, but leave 2.7.3 as it is.
>

For sure, we need to do this, under https://github.com/jython/jython
Ideally we would replace the Jython 3 sandbox t
https://github.com/jython/jython3 with just a README that that points to
this historical work, but otherwise is empty. (If this were a sandbox under
someone's name I would keep as is, but under this name we have to do this
cleanup to avoid confusion.)

One other thing we should consider in this move to GitHub is the overall
workflow. I suggest we switch over to GitHub issues, and anything else
accommodated by the GitHub ecosystem (eg https://github.com/features/actions).
So I wouldn't want to spend time investing in implementing the full CPython
workflow here like Discourse - standard GitHub is more than adequate for
our needs. Given that Jython 3 will have effectively its own bugs, this can
be a good clean break with bugs.jython.org as it is - I would keep around
historically, but I wouldn't bother porting over these possibly irrelevant
issues into GitHub. However, we would need to do something to ensure that
bugs are not inadvertently reported there - an advisory notice somewhere on
that site should suffice.


> https://bugs.jython.org/issue2892 opened to cover this. I'll try,
> starting withthe obvious way
> (
> https://help.github.com/en/github/importing-your-projects-to-github/importing-a-repository-with-github-importer)
>
> and reading what CPython did. I'd be happy to take input from anyone
> with a sure-fire answer.
>
> --
> Jeff Allen
>

_______________________________________________
Jython-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/jython-dev