Repository access to the sandbox would be for committers only. We could commit your changes more or less as often as needed but that is an extra step. The flip side is that if that the components are developed outside of the ASF process (through mailing list discussion, etc.) then they can't really be added to MyFaces straight away.
Ted Husted was reminding us of this just yesterday on a PMC thread. Outside code needs to go through the incubator first. This is actually the route that MyFaces had to take. If your ultimate goal is to contribute to MyFaces then I would suggest working offline for a few weeks and then mailing your stuff to the dev list for inclusion in the sandbox and community review. Those are the ASF rules so there is not much leeway there. If the components are useful and the team wants to add you as a committer, then things will obviously become easier as far as you making contributions. sean On 4/26/05, Jesse Alexander (KBSA 21) <[EMAIL PROTECTED]> wrote: > -----Original Message----- > My preference is to have them in the sandbox once its available. It > will be easier to get them into MyFaces that way (bypassing the > incubator). As Martin suggests, go ahead with SF if you need to get > started right away. As soon as the sandbox is available, we'll post > an announcement and we should probably move it then. > -----/Original Message----- > Question is how easy it will be to setup the repository-access in the > sandbox... > The sf-stage could be used to let developers "earn their merits" and > also keep the MyFaces project cleaner... > > Alexander >
