MadGraph5_aMC@NLO

Status of "transition to git" Blueprint given madgraph5 GitHub Organization

Asked by Matthew Feickert

Hi MadGraph5 dev team,

Having recently seen the great work you're all doing over on madgraph4gpu over on the madgraph5 GitHub org (https://github.com/madgraph5/madgraph4gpu) --- very exciting to see by the way, so kudos to the whole team on this --- I was wondering if this might also give some updates on the "transition to git" Blueprint (https://blueprints.launchpad.net/mg5amcnlo/+spec/git). I realize that plans might still be changing and there might not be an answer that the team wants to share publicly at the moment, but are there plans to migrate development of
MadGraph5_aMC@NLO to GitHub under the madgraph5 GitHub org?

Best,
Matthew

Question information

Language:
English Edit question
Status:
Solved
For:
MadGraph5_aMC@NLO Edit question
Assignee:
No assignee Edit question
Solved by:
Olivier Mattelaer
Solved:
Last query:
Last reply:
Revision history for this message
Best Olivier Mattelaer (olivier-mattelaer) said : 		#1

Hi,

For the moment, we are in the middle of two transitions
1) moving from python2 to python3
2) moving to version 2.x to 3.x

We are afraid to move to git in the middle of those two transitions.
So we do not have take any concrete decision on that decision.

Cheers,

Olivier

Revision history for this message
Matthew Feickert (feickert) said : 		#2

Thanks very much for this information!

Revision history for this message
Matthew Feickert (feickert) said : 		#3

Hi. As a follow up to this, given the 2022-05-20 announcement "MG5aMC arrives on github" (https://launchpad.net/mg5amcnlo/+announcement/30657) does this mean that development and Issue tracking is moving to GitHub as well? Or is GitHub going to be used (temporarily) as just a mirror of LaunchPad until development can be moved over? The "also" in "We do now also provides support on github" made it unclear how people should treat the GitHub Issue tracker (https://github.com/mg5amcnlo/mg5amcnlo/issues/).

It is pretty exciting to see https://github.com/mg5amcnlo/mg5amcnlo so congrats and thanks for the work that it took to migrate the source. :+1:

Revision history for this message
Olivier Mattelaer (olivier-mattelaer) said : 		#4

Hi,

If you want to ask a question/submit a bug you can choose to do it here or on github.
So you can use (https://github.com/mg5amcnlo/mg5amcnlo/issues/ <https://github.com/mg5amcnlo/mg5amcnlo/issues/>) --as no one has done it yet we can have glitch obviously at the beginning--.

If you want to contribute to the code by proposing a modification to the code then github is the place to be.
launchpad repo are still used for the moment for all branch that have started their development before 3.4.0.
As soon as they branch will be merged with 3.4.0, I will move them on git/github and they will continue to grow on github.

Cheers,

Olivier

> On 24 May 2022, at 00:15, Matthew Feickert <email address hidden> wrote:
>
> Question #693060 on MadGraph5_aMC@NLO changed:
> https://answers.launchpad.net/mg5amcnlo/+question/693060
>
> Matthew Feickert posted a new comment:
> Hi. As a follow up to this, given the 2022-05-20 announcement "MG5aMC
> arrives on github" (https://launchpad.net/mg5amcnlo/+announcement/30657)
> does this mean that development and Issue tracking is moving to GitHub
> as well? Or is GitHub going to be used (temporarily) as just a mirror of
> LaunchPad until development can be moved over? The "also" in "We do now
> also provides support on github" made it unclear how people should treat
> the GitHub Issue tracker
> (https://github.com/mg5amcnlo/mg5amcnlo/issues/).
>
> It is pretty exciting to see https://github.com/mg5amcnlo/mg5amcnlo so
> congrats and thanks for the work that it took to migrate the source.
> :+1:
>
> --
> You received this question notification because you are an answer
> contact for MadGraph5_aMC@NLO.

Revision history for this message
Matthew Feickert (feickert) said : 		#5

Great! This is all excellent to hear, and thanks for the super fast response as always.

Will you also port over the release tags so that people can get older releases from git tags on GitHub?

Not sure if you're interested in this idea or not, but I would highly recommend enabling GitHub Discussions (https://docs.github.com/en/discussions) on the project and trying to get users to ask use questions there, and then having people use GitHub Issues mainly for development discussions/reporting bugs. GitHub Discussions builds up a very nice community knowledge base this way. You may already be very well aware of this though, so apologies if that's the case.