Re: Module Ownership Rollcall
Jason <[email protected]>
| Newsgroups | gmane.comp.cms.xaraya.devel |
|---|---|
| Organization | Xaraya |
| Message-ID | <[email protected]> |
Marty Vance wrote: > Jason wrote: > >> Marty Vance wrote: >> >>> Marty Vance wrote: >>> >>> Under 1x I claim HTML, Polls and Messages. >>> >>> If Rabbitt doesn't lay claim to comments, I will. >>> >>> If Jason doesn't claim IEvents and/or jQuery, I will. >> >> >> I would still like to oversee IEvents and jQuery modules. >> >> Submitting policy: suck it and see. Let's see how it goes. We can >> undo, fork, >> redo, whatever as necessary. >> > > "Suck it and see", is pretty much how things are now, if I take your > meaning correctly, and the taste one may get can vary a lot. The main > intent here is that unsolicited commits not be met with "why the hell > did you do that, this module is mine!" venom, and so newcomers know who > to contact. Whether a maintainer chooses a lassez faire attitude or > another is up to them, but whichever they choose needs to be known. If there are little fixes and suchlike, just push them (preferably with a bug reference). I'll be watching, and if I spot a potential problem, I'll mention it. If there are major rewrites or changes, then run it past me first and I'll look out for any potential problems further down the line. What I don't want to be, is a bottleneck approving every change and applying patches. However, if the modules appear to be losing their direction, I'll either try to push it back on track, see if there is a compromise to reach, or recommend a fork. Compared to the core (where every little change seems to affect lots of people, or breaks lots of unexpected things), this should not be hard. Obviously anyone can pick up a module and see how it works. It's more difficult to see why it works the way it works. If my first reply had come across as "yeah, whatever", then I probably did not express myself well enough. All I'm saying is this for these particular modules, it's not mission critical (well, they are to me, but not to the project). I have my own local copies, so can isolate myself from any new directions the modules take. If you want to make a change, drop me a line and I'll do what I can to help. Beyond that, the modules have been given to the community, so they are not in my 'control', but I will speak out for them if need be. -- Jason