Mailman 3 September 2023 - moin-devel

Re: [moin-devel] moin-devel Digest, Vol 23, Issue 8
by Reimar Bauer Sept. 28, 2023

Sept. 28, 2023

On Fri, Sep 22, 2023 at 6:00 PM <moin-devel-request(a)python.org> wrote: > Send moin-devel mailing list submissions to > moin-devel(a)python.org > > To subscribe or unsubscribe via the World Wide Web, visit > https://mail.python.org/mailman/listinfo/moin-devel > or, via email, send a message with subject or body 'help' to > moin-devel-request(a)python.org > > You can reach the person managing the list at > moin-devel-owner(a)python.org > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of moin-devel digest..." > > > Today's Topics: > > 1. Re: Moin2 - Create new theme (Paul Boddie) > 2. Re: Moin2 - Create new theme (Ulrich B.) > 3. Re: Moin2 - Create new theme (Christoph Klassen) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Thu, 21 Sep 2023 18:03:39 +0200 > From: Paul Boddie <paul(a)boddie.org.uk> > To: moin-devel(a)python.org > Subject: Re: [moin-devel] Moin2 - Create new theme > Message-ID: <2111020.dz6aNmVp7Z@jason> > Content-Type: text/plain; charset="us-ascii" > > On Thursday, 21 September 2023 16:16:00 CEST Christoph Klassen wrote: > > > > And which icons are you using? Are they from Font Awesome? > > They appear to be, yes. In the Debian package, the python3-xstatic-font- > awesome package is a dependency which depends on fonts-font-awesome. > > I think the Debian package may need to incorporate a patch to upstream > Moin > sources because a stylesheet file in src/moin/templates/base.html called > all.css is specified, whereas the Debian fonts-font-awesome package > doesn't > have such a file. Instead, it seems that font-awesome.css might be the > appropriate file. > > Although Debian unstable provides Font Awesome 5.x, which has the all.css > file > upstream, Debian appears to have maintained compatibility with 4.x. > Indeed, > the version of this package is given as... > > 5.0.10+really4.7.0~dfsg-4.1 > > So maybe there will be an upgrade to this package at some point. > > Paul > > > > I had builded last year the V6.2.1 on Pypi, compared to the old 4.1.0, this was a big change https://github.com/xstatic-py/xstatic-font-awesome/pull/1/files Likly in november I will update this to 6.4.0 or newer Reimar

1 0

Re: [moin-devel] Debian packages (Re: moin2 release with core functionality)
by Paul Boddie Sept. 22, 2023

Sept. 22, 2023

On Tuesday, 12 September 2023 22:56:26 CEST Nicholas D Steeves wrote: > > Paul, you're already forwarding patches, maintaining a package, and > deploying it using a not-particularly-well-known apt_repo-in-Salsa > method, so I think a Debian team context would be an asset for those > times when--for example--you want to take a holiday :) Also would mean > that sysadmins who use downstreams like Ubuntu would also be able to > benefit from your work, and this seems like it would reinvigorate Moin > usage in the wild. The moin-team group was Steve McIntyre's initiative, and publishing out of Salsa is just a workaround at present, but I agree that something more substantial is probably needed. [...] > sbuild-debian-developer-setup is the easiest way that I know to get a > clean chroot: > > https://manpages.debian.org/bookworm/sbuild-debian-developer-setup/sbuild-d > ebian-developer-setup.1.en.html > > Using sbuild will also do some minor fuzzing (eg: packages must declare > all needed dependencies and must only write to safe locations during the > package build) Yes, I currently use gbp as follows: gbp buildpackage --git-debian-branch=debian/master \ --git-upstream-tag='upstream/%(version)s' \ --git-builder=sbuild I overlooked that sbuild might provide tools that are usable enough for more general activities, and I might even try this out myself! Thanks once again for the suggestions! Paul

2 2

Moin2 - Create new theme
by Christoph Klassen Sept. 22, 2023

Sept. 22, 2023

Hello everyone, I'm working at Intevation GmbH and we were and are using the Moin wiki engine and would like to continue to do so with Moin 2 so thanks for your work! My other colleagues were already contributing to the new version and now I also want to do something to improve Moin 2. More precisely, I want to create a new theme. To do so I first want to prepare myself with some documentation. I found the section on https://moin-20.readthedocs.io/en/latest/devel/development.html#templates-a… but are they any other places with documentation about themes? And which icons are you using? Are they from Font Awesome? Many greetings, Christoph -- Christoph Klassen | https://intevation.de Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998 Geschäftsführer: Frank Koormann, Bernhard Reiter

4 4

moin2 release with core functionality
by Ulrich B. Sept. 18, 2023

Sept. 18, 2023

Hello, many owners of a moin 1.9 wiki are waiting for a moin replacement based on Python3. If we limit the functionality of moin2 to the core features of moin1.9, IMO it should be possible to move to beta status or even better create a release candidate. For example, we can allow moinwiki markup and disable all other markup languages in the default configuration. They will then be treated as experimental. Wiki owners can test if they can migrate their wiki data to moin2. This could be an option to get more people interested in the development and to push the release of moin2. What is your opinion about this idea? I look forward to your feedback. With regards, Ulrich

3 13

Re: [moin-devel] Debian packages (Re: moin2 release with core functionality)
by Paul Boddie Sept. 12, 2023

Sept. 12, 2023

Nicholas, > Thank you for already forwarding patches. If you haven't already, and > are interested in Debian metadata for patches, please take a look at > "DEP-3: Patch Tagging Guidelines". I'll try and review how I have formulated these patches. It was all very cumbersome to just get the actual substance of the patches to work, but then I discovered "gbp pq" which makes it somewhat easier. So, I may clean up my patch branch and prepare a cleaner set of patches, reducing them from the 15 or so there are now to probably something closer to half that. There is definitely a distinction between Debian-specific patches, which may always need to be applied, and patches that can be moved upstream. > Thank you very much for you work on this! For feedback about your > Debian packaging project, may I suggest one or more of the following > lists: > > debian-devel (general/main development list) > debian-python (Python Team list) > debian-admin (Debian System Administration list) <- maintain Debian > infrastructure debian-mentors (for packaging-related and Debian Policy > questions). Thank you for the pointers! I have discussed some Salsa-related issues on debian-python already, leading to the availability of packages published from Salsa for broader convenience. I imagine that debian-admin might have some interest in Moin 2, although I noticed a Salsa-based discussion where people were enthusiastic about migrating the Debian Wiki to MediaWiki instead of switching to Moin 2. Still, I think a broader audience would benefit from access to this software. (Obviously, the ejection of Python 2 from Debian has exacerbated the Debian Wiki situation, and I think that more care should have been taken with the deprecation of Python 2. There is also a good argument for keeping a package for Python 2 itself around in the longer term, making sure that it still compiles using contemporary compilers, given that individual users may have scripts that still use it.) > I think that it would be valuable to have your Moin2 package as an > official Debian package in the standard repositories, and I hope you'll > consider reaching out to one of the mailing lists noted above. There > are also IRC channels, and there is not necessarily overlap between the > people who follow the lists vs irc. I will probably stick to mailing lists, beginning with debian-python and debian-admin, I think. > Debconf23 is currently ongoing in Kochi, India, so it's one of the perfect > moments for announcing, discussing, and collaborating on projects. Worst > case scenario, I hope that you will find someone to carry the torch of your > work the last 10%, but I think it's more likely you will find collaboration > :) Thank you for following up and for the encouragement! Regards, Paul

1 0

Re: [moin-devel] moin-devel Digest, Vol 22, Issue 1
by Reimar Bauer Sept. 8, 2023

Sept. 8, 2023

Moin Ulrich, > > Message: 1 > Date: Mon, 14 Aug 2023 20:17:24 +0000 > From: "Ulrich B." <UlrichB(a)posteo.de> > To: moin-devel(a)python.org > Subject: [moin-devel] moin2 release with core functionality > Message-ID: <f81501a5-7aa3-1d96-68c7-030808069de8(a)posteo.de> > Content-Type: text/plain; charset=UTF-8; format=flowed > > Hello, > > many owners of a moin 1.9 wiki are waiting for a moin replacement based > on Python3. If we limit the functionality of moin2 to the core features > of moin1.9, IMO it should be possible to move to beta status or even > better create a release candidate. For example, we can allow moinwiki > markup and disable all other markup languages in the default > configuration. They will then be treated as experimental. > I would prefer a feature freeze, there can still be much improved. But that's always the case. In that freeze a common set of the whole scope may be defined stable and the rest experimental. > Wiki owners can test if they can migrate their wiki data to moin2. This > could be an option to get more people interested in the development and > to push the release of moin2. > That is currently my situation. I am also aware that a lot of my plugins won't work with an update. And the time span where I can upgrade those gets also limited by deleting py 2.7 from LTS distributions. I have also to think about "what comes next after the wiki idea". I assume any old user is in a similar situation. The most important question is. Is it good enough to try for the moment? If it is, please get into a semantic release cycle starting with moin-2.0,0 as soon as possible. With a release instead of working with a repository are also steps of "doings" for others defined. In semantic versioning I would know that I have to verify and refactor something again, with the next major. For my users it would mean as long as we have only minor or patch level releases they can work similiar as they learned with the first change to moin-2.0.0. best regards Reimar > > What is your opinion about this idea? I look forward to your feedback. > > With regards, > > Ulrich > > >

1 0