[Moin-user] MoinMoin Development Activity
ajhurst at me.com
Wed Mar 23 21:06:27 EDT 2016
These are very relevant questions from my perspective. I have been running a moin 1.9 site for 6 years or so, and having been promising people who comment on its weaker points that "Moin 2 is coming soon". But I am starting to lose that argument, and there are those who suggest that moving to a more modern wiki would be advantageous.
I have explored how I might help the development of moin 1/2 flavours, but found that I tended to get rather frustrated when I went looking for documentation. For example, I have had trouble in maintaining various home grown flavours of macros, but short of spending my waking hours reverse engineering code, found it difficult to make much progress (yes, what are the entities in a "request"?).
As a (now retired) academic, I spent years exhorting students to document their code, and trying to set a good example for them to follow (http://www.ajhurst.org/~ajh/teaching/fit2070/2014/labs/index.xml). And I understand that the moin development is by volunteers, who receive little thanks and many complaints. But if we can spread the load by encouraging others to join the development, then I would hope emails such as these would no longer be necessary.
So can anyone help me to help you? Where to I find the sort of documentation that would help a newbie to the inner workings of moin become more engaged?
On 20160324, at 09:57, Paul Boddie wrote:
> On Wednesday 23. March 2016 21.50.18 anton wrote:
>> I just looked at moinmoin since a longer time period.
>> The last bitbucket comit is about 9 months ago,
>> so for me it looks thats its silently dead ...
>> as your question has not got an answer since one month...
>> Its sad.
> Indeed. Looking at the Moin 2.0 repository on Bitbucket...
> ...it appears that there was some kind of activity in February. I guess that
> development of things has drifted over to Bitbucket without any real
> indication of why that happened. And the IRC logs have been even less
> informative than usual. I haven't been on IRC to ask questions, however.
> Of course, Moin 1.x (and Moin 2.0) can be as active as we want them to be,
> regardless of what Thomas and others are doing these days [*]. Since people
> are still actively using and deploying Moin, perhaps some efforts should be
> made to push it/them forward in the direction of our choosing.
> One thing that I thought about a while ago was to improve the anti-spam
> mechanisms. It seems that a lot of public Moin deployments these days use
> external mechanisms to grant accounts (such as the old-fashioned "ask someone
> to give you an account" approach), but there is some potential for improving
> the basic measures so that spam account creation doesn't happen so easily.
> Having a usable and secure "out of the box" policy for editing is probably the
> highest priority improvement I can think of.
> Other than enhancements like that, I can imagine some tidying up of the code
> being useful. I think the argument that we should all be making Moin 2.0 ready
> for wider usage doesn't really hold up so well any more. Ideally, Moin 2.0
> would indeed be ready for people to deploy and would support Moin 1.x features
> so that people would just migrate, but things didn't get that far. Meanwhile,
> people who like Moin still seem to deploy Moin 1.x.
> Does anyone else have any ideas for things that could be improved/fixed in
> Moin 1.x? Would a Moin 1.10 be a worthwhile exercise after all?
> [*] https://mail.python.org/pipermail/borgbackup/2016q1/date.html
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> Moin-user mailing list
> Moin-user at lists.sourceforge.net
More information about the Moin-user