RE: JavaOne Schedule Handout
-Original Message- From: Christian Geisert [mailto:[EMAIL PROTECTED] Sent: Friday, June 24, 2005 7:10 PM To: community@apache.org Subject: Re: JavaOne Schedule Handout Tim O'Brien schrieb: Will be printed on Sunday. Please review this PDF by Sunday Morning. [WWW] http://brahe.discursive.com/ASF-JavaOne.pdf Let me know if there is anything missing, preferably by Sun. morning. XML Graphics (Batik FOP) is missing Alright, sorry, the omission was not intentional. I fixed it, please hit the same link and verify that XML Graphics is there. Christian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JavaOne Schedule Handout
Will be printed on Sunday. Please review this PDF by Sunday Morning. [WWW] http://brahe.discursive.com/ASF-JavaOne.pdf Let me know if there is anything missing, preferably by Sun. morning. - Tim O'Brien [EMAIL PROTECTED] (847) 863-7045 -Original Message- From: Geir Magnusson Jr. [mailto:[EMAIL PROTECTED] Sent: Friday, June 24, 2005 3:52 PM To: community@apache.org; [EMAIL PROTECTED] Cc: Public Relations Committee Subject: JavaOne Booth : info (w/ URL!) [Sorry about the repeat - the URL is critical...] http://wiki.apache.org/jakarta/ApacheAtJavaOne2005 We have most things sorted out for the JavaOne booth. I took the liberty of filling in the matrix of projects - I just went down the list putting one in a slot. No prefs was given, and randomly doubled up. We can choose to re-order. Please put a * next to the name of the project if you confirm that timeslot after you choose when you want to be there. IMPORTANT - we'll be working out the protocol for badge handoff and it will be on the wiki. Please pay attention to it. I've crossposted to get max awareness - any project that would like to participate is welcome. Please reply to community only. I've set the reply-to, but double check, please. geir -- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Avalon Closed
If the ASF doesn't work for you then get busy at dpml. Really, go and innovate. But, please don't stick around and try to prove a point by continuously trolling the community@ list. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Question about Board resolutions
Anyone know where board resolutions are kept in CVS? I'm wondering if there is any historical record of board resolutions available to members of a PMC? Thanks in advance, Tim O'Brien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Single Location for syndicated Apache blogs
Many other open source projects, including Debian, the Linux Kernel developers, and Mono, are aggregating the RSS feeds of their blogging contributors and putting them up on a web site. This is something that would be good for the ASF to do as well Everything that has to do with official ASF needs some sort of official corporate oversight. Aggregating personal blogs, seems like something that contradicts that idea. This isn't to say that this is a bad idea. I think this is a **great** idea, but this is also something that could be done on someone's personal hardware resources. If someone created an unofficial aggregation of Apache feeds, I don't think anyone would object at all. (And, as an added bonus, we wouldn't have to listen to the same old jerks debate this to death.) -- Tim O'Brien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Common documents across the ASF
On Thu, 19 Jun 2003, Noel J. Bergman wrote: I think you are confusing the fact that people don't generally like to contribute documentation. Although I consider this orthogonal to shared pages (people can cut and paste vs. link on the Wiki as easily as the static sites), I do believe that lowering the barrier (CVS or XML) has demonstrably increased documentation contribution. Agreed, there is a problem in that guidelines and policies are duplicated across the apache.org domain and sometimes presented in draft form on the site. This leads to confusing situations where two people disagree on process, who can propose a release, what is a PMC, etc. In the case of James, we have had far more contribution to our pages via the Wiki from normal users, than their taking time to learn the XML documentation scheme. Users feel directly empowered. But I consider shared content and Wiki use to be unrelated. I consider these issues to be unrelated as well. I'm not questioning the value of the Wiki, I think it has worked for the projects that have decided to use it, but from what I see it is no substitute for documents that need to be viewed as policy. The docs I think people are talking about are more analogous to the Magna Carta, or a legal document. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
