Question: Publishing regular container images or even deb/rpm packages useful / helpful for the project?

[wombelix]

Hey guys,

was wondering if it could be useful for the project to release a moin2 container image on a regular basis, e.g. daily, based on the latest git code? It's a little related to moinwiki/moin-1.9#79, were I created something for moin-1.9.

I want to support moin2, but need to invest some time to get familiar with the code base before I can think about any code contributions.
For me it looks like providing container images or even work an deb / rpm packages could be a starting point to make it easier for someone to get started with moin2?

I understand it's still in development and things might be broken / not finished yet, but a larger user base by making the setup easy would also mean more testing and a greater chance of contributions?

Cheers
Dominik

[ThomasWaldmann]

As moin2 should be primarily used by developers and power users yet, not sure if a container image is needed / useful (especially since we do not have the python2 issue with moin2).

Guess it should be rather used from a git checkout, so that changes can be contributed back in a PR / can be incrementally applied by git pull.

Next step if we get closer to a releasable state is to create pypi releases and these can then be used by package maintainers to create distribution packages.

[Dreamsorcerer]

I'd certainly find it very useful to have a PPA for deb packages. I've upgraded my server recently to the latest Debian release, but the moinmoin package has been removed, so now instead of having a legacy moin wiki, I have no wiki at all.

If a deb release can allow me to view my existing pages again, even with no other features working, that would still be much better than having nothing at all.

[RogerHaase]

moin 2.0.0a13 in available on https://test.pypi.org/project/moin/. Installation instructions at #1197. Do not use for production, new bug reports are welcome.