I dont speak for patrick who has made most of the commits on this project but i would love some help.
Given your lack of previous assistance and commits on the issue queus though im hesitant to outright give you commit access.
Would you be interested in testing a few patches and marking them rtbc with rerolls where necessary? As soon as were comfortable with the process im totally open to adding you as a comaintainer and takign out the middleman. Youll receive credit of course for the commits as well.
I try to commit patches which are reviewed and tested by community, I know there are a few issues in my list to tackle next time I have some spare time, but it seems we're missing testers / reviewers... I think if you can start by stabilizing issues by re-rolling patches / triaging duplicate issues, things like that, we could have a better view or what's important to people / easy to put in, and -dev would accelerate (and you don't need any specific permission to do that ;-)).
#1515372 needs review. I think reviewing myself is against the rules. #2159925 probably needs a re-roll so I'll do that soon.
I'll check out some more interesting issues, but if I'm the only one, it's still not gonna happen. The main maintainer should be the one to put in the time, right? If (s)he doesn't, who will?
Well, currently, there is not much action going on with this module (you can see I'm the last one that has committed anything, and I'm not the main maintainer).
But the thing is, anybody who has time can help by reviewing issues (you're right, not your own patches), triaging the issue queue to identify which are the main issues to focus on right now (see #1563648-10: Taking a break from geocoder development as an example of what you can do). There is no obligation (but a moral one) to put in the time when you're maintainer, for example I've been given the right but it was for a temporary help, and I haven't been able to put as much time as I'd hope, so I only commit when patches are well reviewed and it seems they are the most pressing. If you can help me with that, some things will happen. If nobody helps, then you're probably right, nothing is gonna happen for a few weeks, for me to have some spare time.
But if you don't help either, then you can be sure nothing will happen ;-)
I committed a bunch of things this morning but I still need help in cleaning the rest of the issue queue (especially reviewing current "Needs review" issues and figuring if the RTBC one aren't breaking anything), so feel free to contribute ;-)
Comments
Comment #1
michaelfavia commentedI dont speak for patrick who has made most of the commits on this project but i would love some help.
Given your lack of previous assistance and commits on the issue queus though im hesitant to outright give you commit access.
Would you be interested in testing a few patches and marking them rtbc with rerolls where necessary? As soon as were comfortable with the process im totally open to adding you as a comaintainer and takign out the middleman. Youll receive credit of course for the commits as well.
Comment #2
kalki2013 commentedSure! sounds cool. thanks.
Comment #3
simon georges commentedComment #4
rudiedirkx commentedComment #5
rudiedirkx commentedI'd love to help, at least to get in
Comment #6
simon georges commentedI try to commit patches which are reviewed and tested by community, I know there are a few issues in my list to tackle next time I have some spare time, but it seems we're missing testers / reviewers... I think if you can start by stabilizing issues by re-rolling patches / triaging duplicate issues, things like that, we could have a better view or what's important to people / easy to put in, and -dev would accelerate (and you don't need any specific permission to do that ;-)).
Comment #7
rudiedirkx commented#1515372 needs review. I think reviewing myself is against the rules. #2159925 probably needs a re-roll so I'll do that soon.
I'll check out some more interesting issues, but if I'm the only one, it's still not gonna happen. The main maintainer should be the one to put in the time, right? If (s)he doesn't, who will?
Comment #8
simon georges commentedWell, currently, there is not much action going on with this module (you can see I'm the last one that has committed anything, and I'm not the main maintainer).
But the thing is, anybody who has time can help by reviewing issues (you're right, not your own patches), triaging the issue queue to identify which are the main issues to focus on right now (see #1563648-10: Taking a break from geocoder development as an example of what you can do). There is no obligation (but a moral one) to put in the time when you're maintainer, for example I've been given the right but it was for a temporary help, and I haven't been able to put as much time as I'd hope, so I only commit when patches are well reviewed and it seems they are the most pressing. If you can help me with that, some things will happen. If nobody helps, then you're probably right, nothing is gonna happen for a few weeks, for me to have some spare time.
But if you don't help either, then you can be sure nothing will happen ;-)
Comment #9
rudiedirkx commentedFair enough. =) I'll put you on the list. Keep that commit button handy!
Comment #10
simon georges commentedI committed a bunch of things this morning but I still need help in cleaning the rest of the issue queue (especially reviewing current "Needs review" issues and figuring if the RTBC one aren't breaking anything), so feel free to contribute ;-)
Comment #11
rudiedirkx commentedAlright, I'll do some more triage today. All the cool issues need review by someone else though, because I've been here before.
Comment #12
pol