I've got a bunch of code on my computer for the preference module. But I don't have commit access so it is only backed up as a zip file on a local server here. (Not the best situation).
If the module proposal is accepted and I get commit access I will add it to the 1.4.x/community/preference folder. I can update the community pom.xml as well if you would like.
I've got a bunch of code on my computer for the preference module. But I don't have commit access so it is only backed up as a zip file on a local server here. (Not the best situation).
If the module proposal is accepted and I get commit access I will add it to the 1.4.x/community/preference folder. I can update the community pom.xml as well if you would like.
He Jesse, we need Justin for this one (he has despot rights on codehaus for the project and I hope we did not miss him before his holiday?).
Brent was talking about some kind of work requirement before handing out commit rights, fixing bugs making a release or something. As far as I know he has not written than up and no formal procedure exists yet.
Hopefully we can work this out at todays breakout IRC meeting.
Jody
I've got a bunch of code on my computer for the preference module. But I don't have commit access so it is only backed up as a zip file on a local server here. (Not the best situation).
If the module proposal is accepted and I get commit access I will add it to the 1.4.x/community/preference folder. I can update the community pom.xml as well if you would like.
To gain commit rights, one first must submit several patches. See Reporting Issues <http://docs.codehaus.org/display/GEOSDOC/Reporting+Issues> for more information on this process. Bug fixes and feature improvements are reviewed by a core committer, not just for how well they work, but also for coding style and readability, making sure they follow all the relevant project rules. If a consistent contributor demonstrates good work and not breaking the project build, then any committer can nominate them for 'commit rights'. This is sent to the devel list, and to get commit rights the user must recieve 3 +1 votes and no -1 votes. After this they will be able to commit to the source tree, though should ask for reviews if they are committing to an area of the code that is outside their expertise.
I think you sent some patches to Justin did you not?
Jody
Sorry for the delay. I havent really had access to email the last few days. I was waiting on a code review before granting you commit access. In order to fast track I have reviewed your code and it looks good. I may have more feedback when I get more of a chance to look at it and actually apply the patch.
Scroll down to GeoServer and click on Join. Send me an email when its done and I will apply it.
-Justin
Jesse Eichar wrote:
I've got a bunch of code on my computer for the preference module. But I don't have commit access so it is only backed up as a zip file on a local server here. (Not the best situation).
If the module proposal is accepted and I get commit access I will add it to the 1.4.x/community/preference folder. I can update the community pom.xml as well if you would like.
I think we are leaving that for the PSC to decide, but I would still like to promote it.
Brent Owens
(The Open Planning Project)
Jody Garnett wrote:
Jesse Eichar wrote:
I've got a bunch of code on my computer for the preference module. But I don't have commit access so it is only backed up as a zip file on a local server here. (Not the best situation).
If the module proposal is accepted and I get commit access I will add it to the 1.4.x/community/preference folder. I can update the community pom.xml as well if you would like.
He Jesse, we need Justin for this one (he has despot rights on codehaus for the project and I hope we did not miss him before his holiday?).
Brent was talking about some kind of work requirement before handing out commit rights, fixing bugs making a release or something. As far as I know he has not written than up and no formal procedure exists yet.
Hopefully we can work this out at todays breakout IRC meeting.
Jody