+1 Actually Eclipse help is made this way, and in one of our previous projects in IBM Egypt we made the similar thing.
On Mon, Mar 24, 2008 at 4:35 PM, Daniel S. Haischt <[EMAIL PROTECTED]> wrote: > Hi all, > > regarding the documentation ... What do you think about if I create an > accompanying help plugin for the OpenEJB Eclipse plugin? > > That way you would as well be able to tightly couple help with the > actual plugin. Eclipse Help is HTML based as you may already know. > > > > Jacek Laskowski wrote: > > On Mon, Mar 24, 2008 at 11:21 AM, Jonathan Gallimore > > <[EMAIL PROTECTED]> wrote: > > > >> 1. What's the best way to contribute documentation if we can't have > >> write access to the Wiki? I'm quite happy to add documentation to the > >> JIRA issue. If that would work, what's the best format? It would be nice > >> to include some images, so how about some very simple html, zipped up > >> with the images? > > > > Place a html file with all the artifacts or follow maven rules as far > > as documentation goes (generate the doc with mvn site). > > > >> 2. Longer term, I would like to be an OpenEJB committer. How does one go > >> about this? > > > > You're doing very well and I'm sure noone's surprised you'll soon > > become an openejb committer. Just give us (the openejb community not > > the openejb pmc) a little bit more time to know you more, esp. how > > you're going about user technical and non-technical questions and > > other parts of openejb. I think it won't take long yet your sustained > > engagement is the very first criteria the OpenEJB team takes into > > account when voting in (or against) and some time "to watch your > > steps" is important. Technical and non-technical, community-wise > > engagements in the projects are what merits. > > > > Jacek > > > > -- Thanks - Mohammad Nour
