I'm a jboss contributor (in JBossWS project) and I'd like to become an overlord contributor too. In fact I'm discussing about the project with Mark Little before Overlord was called Overlord :)
I report here my last mail to Mark summarizing some ideas we got in an irc brain storming good to share with all community (project's channel haven't a lot of users...let me say it have just 2 user :D)
Here is my mail, cut down in uninteresting part. Please, Mark, complete or comment whatever need to be clarified
I loved your idea to choose a couple of things to make them (hopefully) the genesis of the project.
I would distinguish in this email two different goals: tools for developers and the runtime governance software.
For the first one, probably the killer application and the most interesting development would be the service modeller. Definitely interesting for me, even if my current skills are stronger in other area.
Regarding the runtime governance software, I think we need a very good design and a slick web interface to present to our users. As I told you in some previous email, I'm convinced it's important to give user a unique and easy to use console. IOW it's our car's body...
I'm convinced that consoles and user interfaces are as good as good are what they have under the hood, and so it's important to have a good design of the architecture behind in this phase.
IMHO we have 3 central component in runtime governance architecture that have to cooperate and be basis for the platform.
* WS-P and its extensions for SLAs: As said I already made an
implementation for JBossWS and you are one of the author of the specification . We could be a good
team on this stuff :P.
* Repository and query language. IMHO one of the most important. It
can't be considered unrelated to UDDIv3 I think. And probably it
(or UDDI) have to be aware of our WS-P extensions.
[Mark has answered me: We need to support UDDIv3, but we also need to make sure we're not tied to it. ]
* SAM. Maybe the killer component for runtime governance if
implemented with some new approach. I recall I read something
about using semantic databases and ontology to represent and store
activity during my master thesis reading...I have to get back on
that idea, but I think RDF can have chance in this are if I well
understood what you have in mind speaking about SAM. RDF could be
a different approach than jcr also for repository...but I have to
think better about...I'm not sure it's a great idea :)
[Mark has answered me:Yes, I'm not sure about RDF for the repository either ;) ]
Well, I'd like to work on all this aspect, also because I think they have to be thought at some level together.
[And Mark answered me:
Next step: should we take the discussions to the Overlord forums? It might help get others involved too. ]
Done! now it's your time to give some feedback and be involved in the discussion ;)
Waiting for comments I'm going to take a look to DNA and lend an hand in code, since I agree with Mark saying the repository is a good starting point for my contribution.
Of course these are just a couple of ideas on which work and start discussions and thoughts. I don't know how many of these are already developed or at least thought by some others, but I think it's place where eventually share these infos.
Thanks in advance