Upayavira wrote:
> Dear All,
>
> I have got a prototype CocoonBean that I would like to make available. A few questions:
>
> 1) I have used my own package names, but would like to use org.apache.cocoon ones.
> What is the process for deciding these?
decide them yourself, as they seem more appropriate.
When we will commit the patch, we could change them for consistency
sake. I cannot help you more without seeing the code.
Suggestion: org.apache.cocoon.environment.bean
> 2) If my code consists of a number of Java files, can I submit a bug to Bugzilla? Does
> the bean go into the sandbox, and does the sandbox require a different packagename?
Submit a zip file with all the new files and patches to bugzilla.
Prepend [PATCH] to the subject.
It will go in the scratchpad.
No, it does not need special packagenames.
> 3) Presumably, not being a Committer, I need someone with Commit priveledges to
> commit my code for me?
Yup, the first one that accepts the job on the patch.
> Thanks for your help. I hope you'll like what I've done so far.
It will be surely interesting :-)
> When I've successfully handed over my work so far, I've got further things I want to
> implement to improve this bean.
Cool :-)
We are also talking about eventually enhancing the environment to handle
input, so your code is just at the right moment.
Thanks :-)
--
Nicola Ken Barozzi nicolaken@apache.org
- verba volant, scripta manent -
(discussions get forgotten, just code remains)
---------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org
|