Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merging the Abella fork of PG #701

Open
phikal opened this issue Jul 22, 2023 · 11 comments
Open

Merging the Abella fork of PG #701

phikal opened this issue Jul 22, 2023 · 11 comments

Comments

@phikal
Copy link
Contributor

phikal commented Jul 22, 2023

The Abella proof assistant has been maintaining a fork of Proof General for a while now, even though looking at the diff, the two don't seem that irreconcilable. Even though the upstream development appears to acknowledge that their fork back into PG would be convenient, the main developer (Kaustuv Chaudhuri) appears to believe that the PG maintainers wouldn't be interested:

I think PG's devs don't want to maintain modes for niche systems, so they will probably not accept Abella's fork.

Could someone say if this is the case, or if given a working pull request, merging support for Abella would be something could conceivably be added to Proof General?

Btw, I have contacted Kaustuv (@chaudhuri on GH), but have yet not received any response from his end.

@chaudhuri
Copy link

If anything, I think the onus is on Abella to provide a suitable PR for PG if indeed Abella thinks it is reasonable to have default support for it in PG.

If possible, I would like the PG devs to recommend a way for a third party to add a PG minor mode without needing to modify PG's proof-site.el or add code to particular subdirectories in PG.

@monnier
Copy link
Contributor

monnier commented Jul 23, 2023 via email

@phikal
Copy link
Contributor Author

phikal commented Jul 29, 2023 via email

@erikmd
Copy link
Member

erikmd commented Jul 29, 2023

Thanks @phikal for opening this issue!

@chaudhuri

If anything, I think the onus is on Abella to provide a suitable PR for PG if indeed Abella thinks it is reasonable to have default support for it in PG.

During the summer, we don't meet up with my fellow colleagues @Matafou and @hendriktews, so I cannot speak from the team.

Still, IMHO I don't believe there would be some objection for merging support for another prover such as Abella.

Anyway, I think it would be much more easy if a member of the Abella community is motivated to help maintaining the Abella flavor in PG after the merge; by this I don't mean maintaining all the layers of PG! but being available to handle Abella-related issues/PRs — given we co-maintain PG essentially as part of our spare time, and we are not necessarily savvy in Abella.

If possible, I would like the PG devs to recommend a way for a third party to add a PG minor mode without needing to modify PG's proof-site.el or add code to particular subdirectories in PG.

I don't think this is required (or urgent) to do this: even if it is a sensible idea from a software engineering POV, we don't add so often support for new provers in PG! so adding a subdirectory and an entry in proof-site.el is fine. The only "boring" step is to update the MELPA and NonGNU ELPA configuration to mention the additional subdirectory.

BTW, feel free to take a look at the PR #636 to get a fairly recent example of proof-assistant addition in PG.

Best wishes

@phikal
Copy link
Contributor Author

phikal commented Jul 29, 2023

The only "boring" step is to update the MELPA and NonGNU ELPA configuration to mention the additional subdirectory.

FWIW there is no need to change anything for NonGNU ELPA, it already bundles everything with the exception of two files.

@phikal
Copy link
Contributor Author

phikal commented Nov 6, 2023

ping?

@Matafou
Copy link
Contributor

Matafou commented Nov 7, 2023

Hi. We welcome such contributions! Of course the maintenance of this code remains yours. We generally proceed by PR.
I would recommend (although this is not a prerequisite) that you write a few tests (see the ci directory) in order to be warned early if something important breaks (scripting basic proofs, goal and error display).

@Matafou
Copy link
Contributor

Matafou commented Nov 7, 2023

But an immediate PR of your current fork would be welcome. Please be patient we will look at it when we have time (we all do this in our spare time).

@chaudhuri
Copy link

Thanks for the encouraging comments. I will see if a suitable PR can be created from my existing Abella-specific fork.

@phikal
Copy link
Contributor Author

phikal commented May 13, 2024

Ping?

@erikmd
Copy link
Member

erikmd commented Jun 18, 2024

Hi @chaudhuri @phikal,

as said earlier, a new PR (that could take inspiration from #636) adding Abella support in PG would be welcome. We'd give you feedback within one such PR.

AFAIAC, my spare time (and thereby PR review time) is very limited currently, but I still support your contribution proposal!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants