On Mon, May 2, 2011 at 18:46, Colomban Wendling lists.ban@herbesfolles.org wrote:
Le 02/05/2011 00:03, Jiří Techet a écrit :
I'll need one more thing - to bump the plugin API version number. Even though the API hasn't changed, people shouldn't use my plugin with previous versions of geany (it wouldn't work because they couldn't specify the patterns).
A bit ugly in the idea, but I understand the point and it's nothing like a big change, so it's now done (API 211).
Thanks.
As the next step I'd like to get the plugin into the Geany Plugins project. Can I get commit access (or how does it work)?
You need a SF.net account, and then tell it to one of the admins and he'll add you to the project.
Apart from that the plugin is now missing some mandatory files like README's NEWS and so on - I'll fix that in the upcoming days. What else needs to be done?
Integration with the geany-plugins build system if you want to be part of the geany-plugin releases. This may be done by others if you ask to -- e.g. Enrico maintains the Waf build system and Loong Jin the autotools one, but some others may be able to do it too, so just ask here.
I think I can do it myself, the build system doesn't look too complicated. I'll ask for my plugin's inclusion into geany-plugins once I'm done with that.
By the way, if you feel bored, you can have a look at the remaining patches in my branch ;-). A few of them are trivial ones, it's just a matter of deciding whether they should be part of geany or not. And if you don't like how something is implemented, just tell me and I'll make the necessary modifications.
Cheers,
Jiri