Adding package to {GNU,NonGNU} ELPA

[phikal]

Hi, would you be interested in having kmacro-x added to either GNU or NonGNU ELPA? I think it is an interesting package that at least in some parts would be worth merging into Emacs itself, and making the move to an ELPA is usually a good first step in that direction.

If you are interested, I can take care of the rest, and might perhaps send you a patch or two if there is something that would require changing, but it shouldn't require any more effort than that on your part.

[vifon]

Hello and apologies for a late response!

I'd love to contribute back to the community, though I'm not sure if this is the right time. I'm still working on the intended scope of this project and may want to alter it soon-ish. As it stands, the functionality got skewed heavily towards the multiple cursors implementation. The documentation could use some improvement too.

How would that work in general? Do I just keep developing at my own pace etc. here, while I allow GNU to copy some parts as needed, or would it be preferable to move the development somewhere else?

[phikal]

Wojciech Siewierski ***@***.***> writes:

Hello and apologies for a late response! I'd love to contribute back to the community, though I'm not sure if this is the right time. I'm still working on the intended scope of this project and may want to alter it soon-ish. As it stands, the functionality got skewed heavily towards the multiple cursors implementation. The documentation could use some improvement too.

In general this is not an issue. E.g. We can add the package to GNU ELPA or NonGNU ELPA, but you can prevent a release from being made by adding "-dev" to the version number in the "Version" header, then it would be up to you when you want the package to be publicly released.

How would that work in general? Do I just keep developing at my own pace etc. here, while I allow GNU to copy some parts as needed, or would it be preferable to move the development somewhere else?

You don't have to change anything, the GNU ELPA build scripts are configured to periodically mirror your state, and whenever a version bump is made, a new release would be published. Of course if you'd rather contribute your changes to core Emacs, then it would be best to send ***@***.*** a message with your proposals.