Last summer we were tracking GSoC changes against the 1.5 trunk of Moin. Those change never got merged, so did not make the 1.6 release. FWIW, we're still looking for someone interested in Python, DocBook, and Moin to help maintain those patches; if we did, we might get them accepted into the trunk.
A current SoC project is working on providing a Wiki interface for editing man/info pages. More details are found on Ville-Pekka's project page[1].
The question has come up from Ville-Pekka if we want to track our changes against the current Moin version (1.6) or the upcoming (1.7), and we need to have a decision within the week.
Any thoughts on this?
From the project page[1]:
"* Finally decide on 1.6 vs. 1.7. This needs to happen this week as of writing (week 23). No major changes will get to 1.6 anymore, so if I based my project on it, then Fedora would need to run an unmerged branch of the code. Probably not what we want? My suggestion is to work on 1.7 branch and hopefully get my changes merged into mainline eventually."
[1] http://fedoraproject.org/wiki/SummerOfCode/2007/VillePekkaVainio
Karsten,
Personally i would go for 1.7, since im sure that noone will want to maintain their own moin branch, and keep patching it manually without breaking the rest of the "new" patches.
Paulo
On 6/6/07, Karsten Wade kwade@redhat.com wrote:
Last summer we were tracking GSoC changes against the 1.5 trunk of Moin. Those change never got merged, so did not make the 1.6 release. FWIW, we're still looking for someone interested in Python, DocBook, and Moin to help maintain those patches; if we did, we might get them accepted into the trunk.
A current SoC project is working on providing a Wiki interface for editing man/info pages. More details are found on Ville-Pekka's project page[1].
The question has come up from Ville-Pekka if we want to track our changes against the current Moin version (1.6) or the upcoming (1.7), and we need to have a decision within the week.
Any thoughts on this?
From the project page[1]:
"* Finally decide on 1.6 vs. 1.7. This needs to happen this week as of writing (week 23). No major changes will get to 1.6 anymore, so if I based my project on it, then Fedora would need to run an unmerged branch of the code. Probably not what we want? My suggestion is to work on 1.7 branch and hopefully get my changes merged into mainline eventually."
[1] http://fedoraproject.org/wiki/SummerOfCode/2007/VillePekkaVainio
-- Karsten Wade, 108 Editor ^ Fedora Documentation Project Sr. Developer Relations Mgr. | fedoraproject.org/wiki/DocsProject quaid.108.redhat.com | gpg key: AD0E0C41 ////////////////////////////////// \\\\\\\\\\\\\\\\\\
Fedora-infrastructure-list mailing list Fedora-infrastructure-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-infrastructure-list
O/H Paulo Santos έγραψε:
Personally i would go for 1.7, since im sure that noone will want to maintain their own moin branch, and keep patching it manually without breaking the rest of the "new" patches.
Working with upstream 1.7 sounds more sane.
-d
Dimitris Glezos kirjoitti viestissään (lähetysaika Wednesday, 6. June 2007 20:11:16):
O/H Paulo Santos έγραψε:
Personally i would go for 1.7, since im sure that noone will want to maintain their own moin branch, and keep patching it manually without breaking the rest of the "new" patches.
Working with upstream 1.7 sounds more sane.
-d
Thanks for your input. Everyone I've talked with from Fedora and Moin have recommended using 1.7, so that's what I'm going to base my work on. Then I'll also have a chance of getting my work merged into 1.7 mainline eventually.
infrastructure@lists.fedoraproject.org
-
Dimitris Glezos -
Karsten Wade -
Paulo Santos -
Ville-Pekka Vainio