JavaOne proposal rejected
Like many others, today I received an e-mail from the JavaOne conference team saying that they are unable to accept my (one and only) proposal.
Project Blogs
With blogs and newsfeeds becoming more pervasive, individuals are using blogs to share their thoughts, and software products are using newsfeeds to distribute information in a standard format. In the context of a project, a blog can become the central hub for the distribution of information, improving communication within the team and enhancing visibility to the client. While publishing static content such as technical tips, progress against milestones and documentation is undoubtedly useful, publishing dynamic content can add another dimension to a project blog. There are typically many sources of dynamic information that can be aggregated into a project blog, including build reports from CruiseControl, project artefacts from Ant and the current status of bugs from your issue tracking tool.
This session takes a look at how blogging technologies such as XML-RPC, RSS and Atom can be used to publish and aggregate dynamic content to a project blog. Case studies are presented of projects that used a project blog and code samples are used to demonstrate the principles discussed. At the end of this session you’ll be able to start your own project blog and integrate data sources from your project into it, all with Java technology.
I thought that this would be a fun little BOF, perhaps a niche topic not specifically about Java, but a nice break away from endless talks about EJB, JSF and web services. Oh well, maybe next time. ;-)
Re: JavaOne proposal rejected
That is pretty cool, proposal. I was thinking about developing a project around something similar.
And I actually wanted to go to JavaOne, but the $3000? + Hotel/Plane * 3 were way outside the company budget. You guys should start a JavaOne Rejected Proposal convention, I would go.
Simon is a hands-on software architect who works within 