3:18 p.m.
On 11 Apr 2013, at 18:08, Keith Babo <kbabo(a)redhat.com> wrote:
Howdy,
We have a ton of quickstarts already:
https://github.com/jboss-switchyard/quickstarts
I don't think they relate 1:1 to the type of thing we would do for JDF, but I think
they can be used as source materials to create something better. My two main beefs with
our project quickstarts at the moment:
- Original use cases for examples are tough to come by and people tend to copy and paste
the same example artifacts.
- They tend to be very focused on a particular feature being demonstrated vs. a showcase
of the project.
These are what we refer to as quickstarts. Showcasing something simple and constrained.
Your quickstarts look great for what we need, so it's just a case of aligning them
well.
I think the JDF stuff for SOA should have some business relevance with original examples
and demonstration of multiple aspects of the platform working together. There was a home
loan demo for SOA P 5 that we could do in SY/SOA 6 with no problem whatsoever.
This is what we are referring to as a showcase example, and we plan to do something here,
probably starting in June, if that is ok with you guys (as I have a new guy starting then
whose focus will be on building showcase examples). So my proposal is that we focus on
quickstarts for now :-)
I'm not a huge fan of archetypes in general, but I think they can be very useful if
they represent a common pattern or practice. For example, SOAP proxying is something that
happens quite a bit in SOA land and an archetype which spits out an application based on
that template could be valuable.
Yes, I agree archetypes aren't great. However we've found they are useful as they
are common format which everyone can write. Then we have Forge for more advanced project
manipulation.
cheers,
keith
On Apr 11, 2013, at 12:32 PM, Pete Muir <pmuir(a)redhat.com> wrote:
> Hi all,
>
> Kenny has offered to help out getting the SOA-P quickstarts into shape - making sure
they are consistent with those we have for EAP etc.
>
> From our side, Sande and Rafael can both help you, as can I. The best way to get help
is to join #jboss-jdf on freenode.
>
> A few resources to start with:
>
> * Contribution guide -
https://github.com/jboss-jdf/jboss-as-quickstart/blob/master/CONTRIBUTING.md - cover lots
of stuff like code formatting
> * For those with access - overall developer experience requirements -
https://docspace.corp.redhat.com/docs/DOC-136011
> * QSTools - Rafael, please provide the link - this tool automates many of the checks
we do on quickstarts
>
> In general, one of our big requirements is that there are a lot of comments in the
code, this is often the most laborious area, and hopefully one where Kenny can really
help, as he knows about the subject :-)
>
> The goal here is to get any quickstarts that we have on the SOA-P side ready for
inclusion in JDF, and also to identify any gaps we may have, and find volunteers to work
on those.
>
> It's also worth thinking about an archetype or two for SOA-P at the same time.
Rafael's QSTools is able to generate archetypes from quickstarts, so it's really
just a case of identifying which quickstart(s) to base it on.
>
> Finally, I should mention that do want to focus on SOA-P here, not on the upstream
projects.
>
> Kev, Keith, could you respond with what you know we have in SOA-P land today, and
where Kenny et al can start to take a look?
>
> Pete