Other than that, I can help Venatrix in creating lua files (I've looked at those files and it seems doable, for me). I've not lot of time, but if we find a way to divide workload I could help you.
Also, maybe another way to manage workflow could be proposed: like Astuur pushing a help.lua.txt file in the correct folder; chuck reviewing it renaming (via bzr move) to help.lua.txt.ok (or something similar) and me and Venatrix converting it to a proper help.lua file.
Or we can use a sort of mailing list to exchange files (without crowding this bug report - currently 78 comments!)
what do you think?
@Sirver:
Any suggestion for the workflow? And are the steps for working with the branch right?
I simply branched on my machine, merged Venatrix's work and pushed to LP (no merge-proposal involved). Is it ok?
I created the branch as suggested by Sirver and merged all work done on Venatrix's branch.
I think now everyone involved can follow these steps:
bzr branch lp:~widelands-dev/widelands/help_development (first time only)
bzr pull
commit locally and then
bzr push lp:~widelands-dev/widelands/help_development
Other than that, I can help Venatrix in creating lua files (I've looked at those files and it seems doable, for me). I've not lot of time, but if we find a way to divide workload I could help you.
Also, maybe another way to manage workflow could be proposed: like Astuur pushing a help.lua.txt file in the correct folder; chuck reviewing it renaming (via bzr move) to help.lua.txt.ok (or something similar) and me and Venatrix converting it to a proper help.lua file.
Or we can use a sort of mailing list to exchange files (without crowding this bug report - currently 78 comments!)
what do you think?
@Sirver:
Any suggestion for the workflow? And are the steps for working with the branch right?
I simply branched on my machine, merged Venatrix's work and pushed to LP (no merge-proposal involved). Is it ok?
@Astuur (#76): I think reading http:// wl.widelands. org/wiki/ BzrPrimer/ would help you.