[seam-dev] Seam University

Wed Apr 6 23:33:54 EDT 2011

Sure, I'll put together a more detailed list of my thoughts tomorrow... 
currently I'm rushing to meet a deadline for a conference paper so I 
can't do it right now.

On 07/04/11 13:12, Jason Porter wrote:
> Could we get some ability statements or stories going that you have in
> mind Shane? Maybe some of the technical direction you were thinking
> about as well. I also don't see this being a huge problem for
> development. We have many hands to help with the lifting, no reason we
> can't do it in an iterative fashion. That'll help cut down on the
> amount of work and also timeframe. It would also be a great time to
> really test out Arquillian Alpha5.
>
> On Wednesday, April 6, 2011, Shane Bryzak<sbryzak at redhat.com>  wrote:
>> On 06/04/11 19:22, Antoine Sabot-Durand wrote:
>>> Hi Shane,
>>>
>>> Your vision is pretty cool, but I'm not sure to understand your means to achieve it.
>>> Do you want to develop the platform from scratch on GAE or use an existing collaborative plateform ?
>>>
>>> I love the idea of using Seam and java EE to create such a platform (I could see a lot of project were I could reuse it ;-) ) for this university but don't you think it's a very big project and that it's very similar with the Seam Wiki example / project that host seamframework.org and in.relation.to today ?
>> It will have some similarities to functionality provided by
>> seamframework.org, but much more accessible.  It's honestly not going to
>> be that complex (the key is to keep things simple) and I don't think it
>> will be a significant development effort.  Most of the time will be
>> spent on usability analysis I imagine.
>>
>>> IMHO to be realistic and result focus we should start on an existing platform. Either with a web standard platform that will not be in Java (wordpress, drupal, etc...)  or better with a solution based on Java like jives or even better exo-platform (built on top of gatein portal). An other solution would be to port Seam Wiki from Seam 2 to Seam 3 and make it evolves t meet our needs...
>> Unfortunately none of these solutions offer the functionality that I
>> want the site to provide.  The Seam 2 wiki example is too
>> over-engineered for the simpler requirements of the new site (not to
>> mention is based on JSF, which I don't want to use).
>>
>>> Concerning the cloud platform, I'm not very found of GAE, because it's very restrictive and a proprietary version of Java EE (datastore, thread management, bad JSF support, no EJB support...) and is not in the spirit of Java EE. Amazon's Elasticbeanstalk or some of your Redhat / JBoss cloud solution looks better to me. In the case we would like to promote the dev part a solution like cloudbees could also a good solution to me. It would be nice to have a part of the site build around Seam Forge and that could allow user to test, share code (a kind of Github with possibility to run code). A kind of Seam Genius Bar ;-).
>> Using GAE was just an idea, I'm not set on it by any means and am happy
>> for us to consider alternatives such as Amazon.  I picked GAE out of the
>> air because a) it's popular with a lot of developers and it would be
>> nice to have a "real" CDI/Seam example running on this platform, and b)
>> its free quotas are quite generous.
>>
>>> I keep in mind that the coming Java EE 7 will be about cloud, so if we want to communicate and promote this we have to choose an environment that will probably follow this path.
>>>
>>> To finish, I'm not very found of having resources split between multiple sites and users experience and I think we should look for a solution that will host all Seam resources to give an image of professionalism and coherence.
>> The key with creating a successful Seam knowledgebase site is to have it
>> owned by the community.  If we host it at jboss.org then I'm certain it
>> will work against this goal.  That's not to say though that we can't
>> link between the two.  Also, I want to support OpenID (and the new OAuth
>> features you've been working on) on the new site, which we can't do on
>> jboss.org.
>>
>>>
>>> Antoine SABOT-DURAND
>>> ---------------------------------------
>>> Twitter ; http://twitter.com/antoine_sd
>>> LinkedIn : http://fr.linkedin.com/in/antoinesabotdurand
>>>
>>>
>>>
>>> Le 6 avr. 2011 à 10:14, Shane Bryzak a écrit :
>>>
>>>> Now that the Seam final release has been out for about a week (and I've
>>>> had a chance to gather my wits), I've been thinking a bit about what we
>>>> should do with the seamframework.org web site.  I think that we're all
>>>> in agreement that we need to do something, however the devil is in the
>>>> details - it's plain to me that we can't do a straight migration of all
>>>> content to the jboss.org community site and still retain all the value
>>>> that the current site provides.
>>>>
>>>> Essentially, the contents of the site can be broken down into a few
>>>> categories:
>>>>
>>>> 1. Forums
>>>> 2. Knowledgebase
>>>> 3. Marketing
>>>> 4. Reference - links to documentation, downloads, Maven artifacts, etc
>>>>
>>>> I believe that 1, 3 and 4 are the types of content that we can
>>>> successfully host on the jboss.org infrastructure (still accessible from
>>>> www.seamframework.org), in a similar way that hibernate.org does it.
>>>> What I don't believe that we can host there is the knowledgebase.  I
>>>> think that this is one area where we're currently failing our community,
>>>> and that we have the potential to make vast improvements on.
>>>>
>>>> This is where Seam University comes in.  My vision for this is to build
>>>> a site that is run with the same collaborative community effort that has
>>>> exploded into existence as a result of Seam 3.  This would be a site
>>>> where Seam users could submit their own articles, tutorials and tips for
>>>> using Seam, and have it properly indexed via a powerful keyword search
>>>> algorithm (this bit is quite important).  I know we have in.relation.to,
>>>> but the problem with this site is a) only a select few can submit
>>>> content to it, b) new content falls off the radar quite quickly and c)
>>>> it's mainly centered around product announcements.
>>>>
>>>> As for hosting this, my preference would be to use Google App Engine so
>>>> that the site could double up in purpose as being a showcase of CDI/Seam
>>>> technology in the cloud.
>>>>
>>>> Anyway, these are my initial thoughts on this subject and I would really
>>>> love to hear some feedback on these ideas.  So don't be shy to let me
>>>> know what you think. :)
>>>>
>>>> Shane
>>>>
>>>>
>>>> _______________________________________________
>>>> seam-dev mailing list
>>>> seam-dev at lists.jboss.org
>>>> https://lists.jboss.org/mailman/listinfo/seam-dev
>> _______________________________________________
>> seam-dev mailing list
>> seam-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/seam-dev
>>