Re: 3-column jakarta.apache.org?
On 29 Dec 2004, at 20:44, Henri Yandell wrote: snip 4) Various parts of Resources struck out. I think this was all covered in previous emails. I think www.apache.org covers these issues now and we don't have to. FWIW some of the content (and the stuff you moved) is covered. unfortunately, there's still a lot that's not and already quite a bit of information has been lost when the old wiki was removed. IMHO if (in the future) these things should be documented at the foundation level, it'll be easier in the long run to bite the bullet: decide what content is suitable for the new jakarta site and then make an effort to move everything else to more appropriate places before it's removed. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On 29 Dec 2004, at 16:10, Henri Yandell wrote: I'm a fan of the www.apache.org look and how it gives us a lot more usability in terms of available column space. I'd like to change Jakarta to the 3-columns (though not the lf or anything). Switching to 3-columns means less space in the center for content, however I also want to simplify the content so I think it will look fine. Any views? if we're moving to this format, then i'd suggest getting rid of the news section. http://www.apachenews.org/ does this much better than us. we're not even getting syndicating on stuff like java.net anymore so i'm now really sure it's worth the effort. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dormancy worries
On 27 Dec 2004, at 11:35, Torsten Curdt wrote: Noel J. Bergman wrote: snip There has been some suggestion that they be cleaned up by migrating them to some other domain to be mothballed. The code, web site, and mailing list archives would be preserved, and could be restored at such time in the future when a community might arise. Hmm... the question is whether we really *can* mothballing them. IMHO too many projects rely on them. It's an important piece of technology. At least bugfixes need to be applied. FWICS migration costs (e.g. to asm) are fairly high. There *are* people that have patches in the queue. i would like to suggest again something that costin suggested a long while ago now: for mature sub-projects we remove the extra layer and organize them directly under jakarta. so rather than being run as sub-projects with their own separate committer lists, the jakarta community runs them directly. the commons uses an honour system (the committers for the components are listed in a STATUS file) which i think would work well in this case, with any interested committer being granted karma upon request (technically lazy vote of the pmc) and any required VOTEs (which should not be many) being done directly by the pmc. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On Sat, 1 Jan 2005, robert burrell donkin wrote: On 29 Dec 2004, at 16:10, Henri Yandell wrote: I'm a fan of the www.apache.org look and how it gives us a lot more usability in terms of available column space. I'd like to change Jakarta to the 3-columns (though not the lf or anything). Switching to 3-columns means less space in the center for content, however I also want to simplify the content so I think it will look fine. Any views? if we're moving to this format, then i'd suggest getting rid of the news section. http://www.apachenews.org/ does this much better than us. we're not even getting syndicating on stuff like java.net anymore so i'm now really sure it's worth the effort. Even our own release news? I see us just focusing on our own news; xxx moves to TLP, yyy moves out of Commons, 10.4 of Foo released etc. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cleaning up Site2
On 28 Dec 2004, at 20:15, Martin Cooper wrote: On Tue, 28 Dec 2004 00:35:08 -0500 (EST), Henri Yandell [EMAIL PROTECTED] wrote: snip 6) Less contraversial (as no mention of Jon or idiots): Kill vendors page? How about legal and acknowledgements? Should these be under the ASF umbrella level now and not Jakarta specific. If there's stuff that makes sense to move to the main ASF site, then we should do that. Other stuff, like perhaps the vendors page, might make more sense on the wiki. I'd be leery of moving too much out, though, since I suspect a lot of people don't think to look outside the Jakarta site for help. please beware that the energy available to maintain the foundation site seems to be even less than for the jakarta site. there is a lot on the jakarta site that needs moving upwards or at least replacements writing. starting from the jakarta pages would at least provide some impetus... - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dormancy worries
On Sat, 1 Jan 2005, robert burrell donkin wrote: On 27 Dec 2004, at 11:35, Torsten Curdt wrote: Noel J. Bergman wrote: snip There has been some suggestion that they be cleaned up by migrating them to some other domain to be mothballed. The code, web site, and mailing list archives would be preserved, and could be restored at such time in the future when a community might arise. Hmm... the question is whether we really *can* mothballing them. IMHO too many projects rely on them. It's an important piece of technology. At least bugfixes need to be applied. FWICS migration costs (e.g. to asm) are fairly high. There *are* people that have patches in the queue. i would like to suggest again something that costin suggested a long while ago now: for mature sub-projects we remove the extra layer and organize them directly under jakarta. so rather than being run as sub-projects with their own separate committer lists, the jakarta community runs them directly. Effectively I'm +1 on that. I think of it as hope that enough of the self-contained projects ask to move to TLP and then we promote Commons components to sub-project level and make CVS Jakarta-wide. Suggestions that they move into Commons is effectively an attempt to get this community feature. So how should we do it under the assumption that everyone doesn't up for TLP? Do we add a jakarta-user and jakarta-dev mailing list that is the merger of N sub-projects and effectively another Commons, or just kill the N mailing-lists in favour of the commons lists and give CVS access to Commons committers to the N sub-projects? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On Sat, 1 Jan 2005, robert burrell donkin wrote: On 29 Dec 2004, at 20:44, Henri Yandell wrote: snip 4) Various parts of Resources struck out. I think this was all covered in previous emails. I think www.apache.org covers these issues now and we don't have to. FWIW some of the content (and the stuff you moved) is covered. unfortunately, there's still a lot that's not and already quite a bit of information has been lost when the old wiki was removed. http://wiki.apache.org/old/ Which bits in particular? On the mock-up I'm suggesting we kill: Our Mission (Repeat of the front page) Vendor Support (List of 13 companies - surprised no one is against this removal) Reference Library (This page is just plain wrong, we require no 6 book reading list. Could move bits to Project Guidelines/CVS page) Website Maintenance (Wiki? Just the CVS version?) Apache on the JSPA (Geir will be making a www.apache.org JCP page) Acknowledgements (Definitely ASF now, no-one supports 'jakarta' as such afaik) Translation links (See other thread) The Legal bit ended up just going to the bottom of the page. The only page that's been killed so far is guides.html (http://cvs.apache.org/viewcvs.cgi/jakarta-site2/xdocs/site/guides.xml?hideattic=0rev=1.15view=auto) I can dump its info into the Wiki so we can splice out the non-repeating bits. IMHO if (in the future) these things should be documented at the foundation level, it'll be easier in the long run to bite the bullet: decide what content is suitable for the new jakarta site and then make an effort to move everything else to more appropriate places before it's removed. Yup, I'm an aggressive deleter and need checks to make sure I don't go too far. I don't think I have yet (editor.html and ide*.html still exist for example :) ). Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On 1 Jan 2005, at 11:45, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 29 Dec 2004, at 16:10, Henri Yandell wrote: I'm a fan of the www.apache.org look and how it gives us a lot more usability in terms of available column space. I'd like to change Jakarta to the 3-columns (though not the lf or anything). Switching to 3-columns means less space in the center for content, however I also want to simplify the content so I think it will look fine. Any views? if we're moving to this format, then i'd suggest getting rid of the news section. http://www.apachenews.org/ does this much better than us. we're not even getting syndicating on stuff like java.net anymore so i'm now really sure it's worth the effort. Even our own release news? ditch the whole lot :) not only is it no longer pleasing to the eye (in those three columns) but it also ineffective... I see us just focusing on our own news; xxx moves to TLP, yyy moves out of Commons, 10.4 of Foo released etc. jakarta isn't the important resource it used to be for news. our place has been taken. people no longer come to read our news. it would be far more effective to ensure that the announcements are made to the right lists, that the resources which are important now (java.net, apachenews.org, serverside.com) receive the news and that users know which announcement lists they should subscribe to. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On 1 Jan 2005, at 11:54, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 29 Dec 2004, at 20:44, Henri Yandell wrote: snip 4) Various parts of Resources struck out. I think this was all covered in previous emails. I think www.apache.org covers these issues now and we don't have to. FWIW some of the content (and the stuff you moved) is covered. unfortunately, there's still a lot that's not and already quite a bit of information has been lost when the old wiki was removed. http://wiki.apache.org/old/ Which bits in particular? release manager stuff. i need to pull out and reorganize the information then submit some patches to infrastructure. On the mock-up I'm suggesting we kill: Our Mission (Repeat of the front page) Vendor Support (List of 13 companies - surprised no one is against this removal) i don't think anyone's released :) it's been a PITA for a while and may be better on the wiki. maybe it'd be better to get a board/members view on this. Reference Library (This page is just plain wrong, we require no 6 book reading list. Could move bits to Project Guidelines/CVS page) this needs rewriting for foundation new committer material Website Maintenance (Wiki? Just the CVS version?) this will need rewriting anyway (if we're moving from anakia) Apache on the JSPA (Geir will be making a www.apache.org JCP page) this is actually a quite important bit of history. if possible, i'd like to suggest that we move this up to the foundation level as a placeholder and put in a redirect. probably should be discussed with geir. Acknowledgements (Definitely ASF now, no-one supports 'jakarta' as such afaik) i'd suggest checking about this one since some of these acknowledgments may well have been promised. if these are all covered at the foundation level then redirection would be the best idea. Translation links (See other thread) The Legal bit ended up just going to the bottom of the page. The only page that's been killed so far is guides.html (http://cvs.apache.org/viewcvs.cgi/jakarta-site2/xdocs/site/ guides.xml?hideattic=0rev=1.15view=auto) bit funny, that document. i have a vague recollection that it was an unfinished project from the heroic era... I can dump its info into the Wiki so we can splice out the non-repeating bits. that sounds like a very good plan (it's probably start a few different worthwhile pages there) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On Sat, 1 Jan 2005, robert burrell donkin wrote: On 1 Jan 2005, at 11:45, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 29 Dec 2004, at 16:10, Henri Yandell wrote: I'm a fan of the www.apache.org look and how it gives us a lot more usability in terms of available column space. I'd like to change Jakarta to the 3-columns (though not the lf or anything). Switching to 3-columns means less space in the center for content, however I also want to simplify the content so I think it will look fine. Any views? if we're moving to this format, then i'd suggest getting rid of the news section. http://www.apachenews.org/ does this much better than us. we're not even getting syndicating on stuff like java.net anymore so i'm now really sure it's worth the effort. Even our own release news? ditch the whole lot :) not only is it no longer pleasing to the eye (in those three columns) but it also ineffective... I see us just focusing on our own news; xxx moves to TLP, yyy moves out of Commons, 10.4 of Foo released etc. jakarta isn't the important resource it used to be for news. our place has been taken. people no longer come to read our news. it would be far more effective to ensure that the announcements are made to the right lists, that the resources which are important now (java.net, apachenews.org, serverside.com) receive the news and that users know which announcement lists they should subscribe to. Unconvinced. None of those resources are good at supplying historical news; apachenews has the common blog problem of a calendar-view being a poor historical index, java.net seems to have no history and theserverside.com uses a linked-list style system to get old news. The last two also have a high noise to signal level for Jakarta info. The only good source for Apache news is the mail-archive for the announcement lists, but there's a bizarre plethora of those, which is another item on my to-investiage list. Do we need jakarta-announcements, why do other TLPs not all have it, why do I get announcements over community@ etc. I definitely think we should dump the elsewhere news, and the news.html page needs to dump the top two paragraphs as unnecessary. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On Sat, 1 Jan 2005, robert burrell donkin wrote: On 1 Jan 2005, at 11:54, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 29 Dec 2004, at 20:44, Henri Yandell wrote: snip 4) Various parts of Resources struck out. I think this was all covered in previous emails. I think www.apache.org covers these issues now and we don't have to. FWIW some of the content (and the stuff you moved) is covered. unfortunately, there's still a lot that's not and already quite a bit of information has been lost when the old wiki was removed. http://wiki.apache.org/old/ Which bits in particular? release manager stuff. i need to pull out and reorganize the information then submit some patches to infrastructure. Sounds good. I'm happy for it to be in Jakarta for the time being too, it just needs organizing. The guides.html had a small bit about release management that you might want to check against. Apache on the JSPA (Geir will be making a www.apache.org JCP page) this is actually a quite important bit of history. if possible, i'd like to suggest that we move this up to the foundation level as a placeholder and put in a redirect. probably should be discussed with geir. Yup, already talked with him about it. I'll start a list of redirects to add/come up with. There's actually a second JCP page hidden in Jakarta that I'm expecting him to take too. If he's not ready at the time I'm ready on the 3-tier, I'll just keep the JSPA bit and keep hassling him. Acknowledgements (Definitely ASF now, no-one supports 'jakarta' as such afaik) i'd suggest checking about this one since some of these acknowledgments may well have been promised. if these are all covered at the foundation level then redirection would be the best idea. Above.Net and Hyperreal no longer actually provide support (I think, will check). Sun's support is a) JCP thing, b) Tomcat and other RI specific. IBM+CollabNet just seem to employ various ASF people and I've no clue who Clear Ink are. The only page that's been killed so far is guides.html (http://cvs.apache.org/viewcvs.cgi/jakarta-site2/xdocs/site/ guides.xml?hideattic=0rev=1.15view=auto) bit funny, that document. i have a vague recollection that it was an unfinished project from the heroic era... I can dump its info into the Wiki so we can splice out the non-repeating bits. that sounds like a very good plan (it's probably start a few different worthwhile pages there) Easy enough. Sometime this weekend. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dormancy worries
On 1 Jan 2005, at 11:52, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 27 Dec 2004, at 11:35, Torsten Curdt wrote: Noel J. Bergman wrote: snip There has been some suggestion that they be cleaned up by migrating them to some other domain to be mothballed. The code, web site, and mailing list archives would be preserved, and could be restored at such time in the future when a community might arise. Hmm... the question is whether we really *can* mothballing them. IMHO too many projects rely on them. It's an important piece of technology. At least bugfixes need to be applied. FWICS migration costs (e.g. to asm) are fairly high. There *are* people that have patches in the queue. i would like to suggest again something that costin suggested a long while ago now: for mature sub-projects we remove the extra layer and organize them directly under jakarta. so rather than being run as sub-projects with their own separate committer lists, the jakarta community runs them directly. Effectively I'm +1 on that. I think of it as hope that enough of the self-contained projects ask to move to TLP and then we promote Commons components to sub-project level and make CVS Jakarta-wide. i'm not sure that moving commons components to sub-project level would be a good idea. IMHO it would be far better to leave them exactly as they currently are: components distributed by jakarta. i can see no benefits from designating them as sub-projects. even the name has become more than a little tainted. Suggestions that they move into Commons is effectively an attempt to get this community feature. yeh, thought that might be the case :) commons seems to be working ok now and IMHO it'd be better to leave it alone... So how should we do it under the assumption that everyone doesn't up for TLP? Do we add a jakarta-user and jakarta-dev mailing list that is the merger of N sub-projects and effectively another Commons, or just kill the N mailing-lists in favour of the commons lists and give CVS access to Commons committers to the N sub-projects? the commons started out as an experiment. why not just start a new experiment? the new experiment would not be a sub-project and not have any sub-project layer (in organizational terms). the only binding votes would be from jakarta pmc'ers and karma would be granted (upon request) to any jakarta committer who wished to contribute (by means of a status file). i'd say leave the mailing lists for now (there are infrastructure implications) but let's give the mature sub-projects you listed earlier a choice: join the new experimental not-sub-project or move to TLP status. i don't know how this will all work out in the longer term but it's closer to the preferred model than the mature sub-projects are now and so is a step in the right direction. maybe a little further along the process it'll be easier to see the best way forward from where we are then. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mess in jakarta.apache.org/
i wonder whether a long term home for these could be found in archive.apache.org... - robert On 30 Dec 2004, at 23:08, Henri Yandell wrote: The following have all been moved from the jakarta site to ~bayard/jakarta-site-deletions/ bcel.orgjjar buildsite.shmain.template cjanoldsite.tar.gz commons-mavenized tac.jar index-new.html turbine.old jakarta-gnats.tar.gzBUGS gump, struts, pluto, log4j, resources, userGuide have all been deleted. I've replaced the meta refresh in ojb with a .htaccess version. This leaves: broken jmeter201 tomcat-4.0 tomcat-old as the list to be deleted. Owners have all been hassled about them. Hen - 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: Mess in jakarta.apache.org/
Hope not. They're generally all examples of people having something cp'd briefly etc and not cleaning. jjar/ and cjan/ are possibly archivable. Hen On Sat, 1 Jan 2005, robert burrell donkin wrote: i wonder whether a long term home for these could be found in archive.apache.org... - robert On 30 Dec 2004, at 23:08, Henri Yandell wrote: The following have all been moved from the jakarta site to ~bayard/jakarta-site-deletions/ bcel.orgjjar buildsite.shmain.template cjanoldsite.tar.gz commons-mavenized tac.jar index-new.html turbine.old jakarta-gnats.tar.gzBUGS gump, struts, pluto, log4j, resources, userGuide have all been deleted. I've replaced the meta refresh in ojb with a .htaccess version. This leaves: broken jmeter201 tomcat-4.0 tomcat-old as the list to be deleted. Owners have all been hassled about them. Hen - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dormancy worries
On Sat, 1 Jan 2005, robert burrell donkin wrote: On 1 Jan 2005, at 11:52, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 27 Dec 2004, at 11:35, Torsten Curdt wrote: Noel J. Bergman wrote: snip There has been some suggestion that they be cleaned up by migrating them to some other domain to be mothballed. The code, web site, and mailing list archives would be preserved, and could be restored at such time in the future when a community might arise. Hmm... the question is whether we really *can* mothballing them. IMHO too many projects rely on them. It's an important piece of technology. At least bugfixes need to be applied. FWICS migration costs (e.g. to asm) are fairly high. There *are* people that have patches in the queue. i would like to suggest again something that costin suggested a long while ago now: for mature sub-projects we remove the extra layer and organize them directly under jakarta. so rather than being run as sub-projects with their own separate committer lists, the jakarta community runs them directly. Effectively I'm +1 on that. I think of it as hope that enough of the self-contained projects ask to move to TLP and then we promote Commons components to sub-project level and make CVS Jakarta-wide. i'm not sure that moving commons components to sub-project level would be a good idea. IMHO it would be far better to leave them exactly as they currently are: components distributed by jakarta. i can see no benefits from designating them as sub-projects. even the name has become more than a little tainted. Well, the impossible dream runs: 1) Various things goto TLP. 2) We're left with Commons, various component like subprojects (ORO/Regexp/ECS etc) 3) Promote Commons components to Jakarta level 4) Rename Subprojects to Components So how should we do it under the assumption that everyone doesn't up for TLP? Do we add a jakarta-user and jakarta-dev mailing list that is the merger of N sub-projects and effectively another Commons, or just kill the N mailing-lists in favour of the commons lists and give CVS access to Commons committers to the N sub-projects? the commons started out as an experiment. why not just start a new experiment? the new experiment would not be a sub-project and not have any sub-project layer (in organizational terms). the only binding votes would be from jakarta pmc'ers and karma would be granted (upon request) to any jakarta committer who wished to contribute (by means of a status file). I'm not sure what this consists of apart from adding a Components section to the nav section and putting a few things under it instead of Subprojects. Would we change the SVN structure in anyway? What actually would change? Just commit perms? i'd say leave the mailing lists for now (there are infrastructure implications) but let's give the mature sub-projects you listed earlier a choice: join the new experimental not-sub-project or move to TLP status. Not a choice I can give. I can dream of TLPness, but as far as I know the community does not want to be pushing to TLPness. Interestingly, time is working against us. If we view TLP-ers as liberal and Jakarta-ers as conservative (not politically, just in approach to the idea of location), then as time goes by the community is more and more against pushing for TLP :) i don't know how this will all work out in the longer term but it's closer to the preferred model than the mature sub-projects are now and so is a step in the right direction. maybe a little further along the process it'll be easier to see the best way forward from where we are then. I'm always in favour of ways to take baby steps to good long term goals, but not sure what the steps would change here. If, say, we change commit rights to BCEL, BSF, ECS, ORO and Regexp to any Jakarta committer, they'd still only be changed by people listening to the mail lists. If we offer commit to any Jakarta committer who asks, I suspect no one would ask. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta download pages Was: download pages in j.a.o.
On 28 Dec 2004, at 20:43, Martin Cooper wrote: On Mon, 27 Dec 2004 23:27:51 -0500 (EST), Henri Yandell [EMAIL PROTECTED] wrote: snip It has problems. Mainly in that it doesn't really provide much a context sensitive message. It should be mentioning signatures, keys, md5s etc. It also loses the navigation of the project it's on and dumps you into a global Apache navigation. However, I think it's the right solution architectually. A dynamic page that contains a standard message and is filled with dynamic info. I actually think that page is horrible. Almost the entire page is filled with stuff the user doesn't care a whit about - a big list of mirror sites. The vast majority of users don't care about mirror sites, they just want to download what they want. The list of mirror sites should be stashed away in a drop-down list, as we have it now. horrible it might be but it was also horribly effective at it's job (which was to stop using download direct from apache.org). however, i think that users have got used to downloading from mirrors now so the time's probably ripe for change. I think, if we had a standard template for download pages, each subproject could have its own download page, something like we have for Struts: http://struts.apache.org/download.cgi this would be a more workable approach. I don't see a need to have one page with all of the available downloads (with the possible exception of Commons, but I'm not sure we need that either). it's better but would require some effort. it's also quite a PITA for non-members (changes would be required to some scripts which is what stopped me last time i thought about revising the download pages). any members with good infrastructure links feel like volunteering...? i actually think that henri's idea about a single summary page for each sub-project would be a good idea containing mailing lists, a brief description, downloads and so on. would make it easy to add redirects later (as projects moved to top level). it'd make some sense in terms of making jakarta more like a portal and less like an ASF mini-me. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deletion suggesiton
Another suggestion for content deletion: http://jakarta.apache.org/site/pmc/ Any reason to keep this, any ideas for better places to keep this? Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 3-column jakarta.apache.org?
Acknowledgements (Definitely ASF now, no-one supports 'jakarta' as such afaik) Turn over all of this to the PRC, and let them handle it on an ASF-wide basis. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 3-column jakarta.apache.org?
unfortunately, there's still a lot that's not and already quite a bit of information has been lost when the old wiki was removed. As noted by Henri, the old Wiki was moved, not removed. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On 1 Jan 2005, at 15:36, Noel J. Bergman wrote: unfortunately, there's still a lot that's not and already quite a bit of information has been lost when the old wiki was removed. As noted by Henri, the old Wiki was moved, not removed. good. effectively is still lost as far as links are concerned and the material needs rewriting for the foundation site but it's easier if the information still exists. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On 1 Jan 2005, at 12:31, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 1 Jan 2005, at 11:54, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 29 Dec 2004, at 20:44, Henri Yandell wrote: snip 4) Various parts of Resources struck out. I think this was all covered in previous emails. I think www.apache.org covers these issues now and we don't have to. FWIW some of the content (and the stuff you moved) is covered. unfortunately, there's still a lot that's not and already quite a bit of information has been lost when the old wiki was removed. http://wiki.apache.org/old/ Which bits in particular? release manager stuff. i need to pull out and reorganize the information then submit some patches to infrastructure. Sounds good. I'm happy for it to be in Jakarta for the time being too, it just needs organizing. The guides.html had a small bit about release management that you might want to check against. the release stuff needs to go into the foundation stuff somewhere infrastructure related, not jakarta. (i talked to them a while ago about this.) - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deletion suggesiton
On 1 Jan 2005, at 14:59, Henri Yandell wrote: Another suggestion for content deletion: http://jakarta.apache.org/site/pmc/ Any reason to keep this, any ideas for better places to keep this? this is definitely of historic value. (there are a number of other bits and pieces of history on the current website which may have some archival value.) maybe it'd be nice to move these to archive.apache.org or iblibio or somewhere. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mess in jakarta.apache.org/
not sure what jakarta-gnats is but it rings a bell from the days when i converted all those releases to the mirrors. may be some reason i didn't delete it then (or none at all). i've googled and it's possible that it's a pre-bugzilla bug tracker (in which can it could easily be deleted) but hopefully someone else may be able to remember more... - robert On 1 Jan 2005, at 12:47, Henri Yandell wrote: Hope not. They're generally all examples of people having something cp'd briefly etc and not cleaning. jjar/ and cjan/ are possibly archivable. Hen On Sat, 1 Jan 2005, robert burrell donkin wrote: i wonder whether a long term home for these could be found in archive.apache.org... - robert On 30 Dec 2004, at 23:08, Henri Yandell wrote: The following have all been moved from the jakarta site to ~bayard/jakarta-site-deletions/ bcel.orgjjar buildsite.shmain.template cjanoldsite.tar.gz commons-mavenized tac.jar index-new.html turbine.old jakarta-gnats.tar.gzBUGS gump, struts, pluto, log4j, resources, userGuide have all been deleted. I've replaced the meta refresh in ojb with a .htaccess version. This leaves: broken jmeter201 tomcat-4.0 tomcat-old as the list to be deleted. Owners have all been hassled about them. Hen - 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] - 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: Dormancy worries
On 1 Jan 2005, at 12:58, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: On 1 Jan 2005, at 11:52, Henri Yandell wrote: On Sat, 1 Jan 2005, robert burrell donkin wrote: snip So how should we do it under the assumption that everyone doesn't up for TLP? Do we add a jakarta-user and jakarta-dev mailing list that is the merger of N sub-projects and effectively another Commons, or just kill the N mailing-lists in favour of the commons lists and give CVS access to Commons committers to the N sub-projects? the commons started out as an experiment. why not just start a new experiment? the new experiment would not be a sub-project and not have any sub-project layer (in organizational terms). the only binding votes would be from jakarta pmc'ers and karma would be granted (upon request) to any jakarta committer who wished to contribute (by means of a status file). I'm not sure what this consists of apart from adding a Components section to the nav section and putting a few things under it instead of Subprojects. Would we change the SVN structure in anyway? What actually would change? Just commit perms? the major change would be organizational: they would no longer be sub-projects but products directly managed by the jakarta project. in practical terms, the major change noticable would be that any necessary VOTEs would happen on the pmc and all jakarta committers would be treated equally (karma granted on request). the rest could remain the same. i would personally favour moving away from the division into sub-projects on the navigation bar into something more suitable as a directory or portal. snip i don't know how this will all work out in the longer term but it's closer to the preferred model than the mature sub-projects are now and so is a step in the right direction. maybe a little further along the process it'll be easier to see the best way forward from where we are then. I'm always in favour of ways to take baby steps to good long term goals, but not sure what the steps would change here. If, say, we change commit rights to BCEL, BSF, ECS, ORO and Regexp to any Jakarta committer, they'd still only be changed by people listening to the mail lists. If we offer commit to any Jakarta committer who asks, I suspect no one would ask. most of these projects are mature with few reasons for further development. it is possible that with more liberal commit rights, one or two may come alive again but i'd say that the main motivation should be to provide an effective maintenance environment for mature code. all of these have experienced issues with the sub-project organization model (since they have too few active sub-project committers to form a quorum). the products-within-project may turn out to be a better model. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 3-column jakarta.apache.org?
robert burrell donkin wrote: unfortunately, there's still a lot that's not and already quite a bit of information has been lost when the old wiki was removed. As noted by Henri, the old Wiki was moved, not removed. effectively is still lost as far as links are concerned Well, if people would stop using machine names in URLs, we could at least try to map them. For the Wiki it would have been pretty easy. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On 1 Jan 2005, at 15:36, Noel J. Bergman wrote: Acknowledgements (Definitely ASF now, no-one supports 'jakarta' as such afaik) Turn over all of this to the PRC, and let them handle it on an ASF-wide basis. cool. what's the right to set about doing this? - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On Wed, 29 Dec 2004 14:01:27 -0500 (EST), Henri Yandell [EMAIL PROTECTED] wrote: Here's my mockup proposal: http://www.apache.org/~bayard/mock-jakarta-frontpage.html Changes: 3 column Strikethrough of links/pages I'd like to kill. Less news. Removal of Related section (aim is to make this a new page). Rewrite of the welcome message to hopefully say the same main thing, but use a lot less space. The aim would also be to switch entirely over to the XSL build version which seems to work fine and dump Anakia creation. Have you tried the XSL version of the binary and source pages? These are a bit different from other pages... Hen On Wed, 29 Dec 2004, Henri Yandell wrote: I'm a fan of the www.apache.org look and how it gives us a lot more usability in terms of available column space. I'd like to change Jakarta to the 3-columns (though not the lf or anything). Switching to 3-columns means less space in the center for content, however I also want to simplify the content so I think it will look fine. Any views? Hen - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 3-column jakarta.apache.org?
robert burrell donkin asked: Noel J. Bergman wrote: Acknowledgements (Definitely ASF now, no-one supports 'jakarta' as such afaik) Turn over all of this to the PRC, and let them handle it on an ASF-wide basis. cool. what's the right to set about doing this? Send e-mail to [EMAIL PROTECTED] --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On 1 Jan 2005, at 18:55, Noel J. Bergman wrote: robert burrell donkin asked: Noel J. Bergman wrote: Acknowledgements (Definitely ASF now, no-one supports 'jakarta' as such afaik) Turn over all of this to the PRC, and let them handle it on an ASF-wide basis. cool. what's the right to set about doing this? Send e-mail to [EMAIL PROTECTED] thanks. i'll take a look at fixing this one. - robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 3-column jakarta.apache.org?
On Sat, 1 Jan 2005, sebb wrote: On Wed, 29 Dec 2004 14:01:27 -0500 (EST), Henri Yandell [EMAIL PROTECTED] wrote: The aim would also be to switch entirely over to the XSL build version which seems to work fine and dump Anakia creation. Have you tried the XSL version of the binary and source pages? These are a bit different from other pages... The only difference that leapt out was that the tables had bad backgrounds, so I fixed that one. Thanks for point them out, I'll relook at them. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 3-column jakarta.apache.org?
snip Vendor Support (List of 13 companies - surprised no one is against this removal) Hen - There's a time for everything, I suppose. Speaking as one of the companies listed, we are quite pleased to be identified in a small way as part of the Jakarta community. However, I also understand the desire to clean up the site and simplify the message. The vendors page is a benefit to us and we would love to see it survive the site redesign, but we are happy to use, support, and recommend Jakarta whether our name shows up or not. FWIW I appreciate your leadership on this effort. Tom - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
question about use of jakarta project icons on other sites...
if my website contains a reference (link) to a Jakarta project, for example Ant or Tomcat, and I want the user to be able to click that reference and have that take them to the project's home page, would it be ok for me to display the icon for that project on my site and make that the clickable item (as opposed to just having the text name of the project as the clickable item)? Thanks. -Pete - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: question about use of jakarta project icons on other sites...
I'll find out. Hen On Sat, 1 Jan 2005, Pete Eakle wrote: if my website contains a reference (link) to a Jakarta project, for example Ant or Tomcat, and I want the user to be able to click that reference and have that take them to the project's home page, would it be ok for me to display the icon for that project on my site and make that the clickable item (as opposed to just having the text name of the project as the clickable item)? Thanks. -Pete - 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]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T16:05:44 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo no comment Change Log: -- @@ -1,13 +1,13 @@ = Plan for the future of the Jakarta site = - 0. 2005 copyright update. - 0. Cleanup of dead parts of the site. - 1. Migrate to Subversion - [Site2 Conversion Instructions]. + 0. 2005 copyright update. - '''DONE''' + 0. Cleanup of dead parts of the site. - '''tomcat-old, tomcat-4.0 and jmeter201 to go''' + 1. Removal of Anakia build and usage of Ant/XSL as the only build system. 2. New look site. a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. - a. Removal of Anakia build and usage of Ant/XSL as the only build system. a. Modification of XSL system to support mockup. a. Use of CSS. + 1. Migrate to Subversion - [Site2 Conversion Instructions]. 2. Improvement of download pages. Creation of cgi pages. 3. [EMAIL PROTECTED] considerations. Indexing systems for javadoc, jars, downloads etc. IRC channel? 4. SVN information in addition to CVS information. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T16:33:10 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo no comment Change Log: -- @@ -3,6 +3,7 @@ 0. 2005 copyright update. - '''DONE''' 0. Cleanup of dead parts of the site. - '''tomcat-old, tomcat-4.0 and jmeter201 to go''' 1. Removal of Anakia build and usage of Ant/XSL as the only build system. + 1. Move site/news.* to redirects instead of meta refreshes. 2. New look site. a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. a. Modification of XSL system to support mockup. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
jakarta-site2 now live on xslt
I've fixed the various spacing issues in the XSLT system (over time the Anakia style sheet changed slightly) and as far as I can tell it looks the same. I cautiously pushed a few pages up to check them out and then the whole lot. Still looks fine to me :) At least from the front page and linked pages, might be some deeper pages with issues that won't be picked up until we get around to deciding if they should exist (which is soon). I've removed the Website Maintenance link too, it no longer makes much sense and nobody seemed to mind the suggestion of killing it. It has (the page isn't gone yet, just the link) a lot of stuff about using jakarta-site2 as a system for other sites (I thought somebody mentioned Tomcat did this, but looking at their CVS repo I can't see references to jakarta-site2). If the old version is needed however, it is tagged under the tag PRE-ANAKIA-REMOVAL. If anyone can take a look and see if they can see problems, I'd appreciate it a lot. New years day means not a lot of users looking compared to usual (though also not a lot of committers around to check etc). Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T17:04:29 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo XSLT done, *cheer*. Change Log: -- @@ -2,7 +2,7 @@ 0. 2005 copyright update. - '''DONE''' 0. Cleanup of dead parts of the site. - '''tomcat-old, tomcat-4.0 and jmeter201 to go''' - 1. Removal of Anakia build and usage of Ant/XSL as the only build system. + 1. Removal of Anakia build and usage of Ant/XSL as the only build system. - '''DONE''' 1. Move site/news.* to redirects instead of meta refreshes. 2. New look site. a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T17:06:14 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo More tasks. Change Log: -- @@ -4,11 +4,13 @@ 0. Cleanup of dead parts of the site. - '''tomcat-old, tomcat-4.0 and jmeter201 to go''' 1. Removal of Anakia build and usage of Ant/XSL as the only build system. - '''DONE''' 1. Move site/news.* to redirects instead of meta refreshes. + 1. See if PRC will take Acknowledgements - ''Robert''. 2. New look site. a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. - a. Modification of XSL system to support mockup. + a. Modification of XSL system to support mockup. ''Hen''. a. Use of CSS. - 1. Migrate to Subversion - [Site2 Conversion Instructions]. + 1. Migrate to Subversion - [Site2 Conversion Instructions]. ''Tim''. + 1. Migration of reference pages into Foundation. 2. Improvement of download pages. Creation of cgi pages. 3. [EMAIL PROTECTED] considerations. Indexing systems for javadoc, jars, downloads etc. IRC channel? 4. SVN information in addition to CVS information. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T19:03:10 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo no comment Change Log: -- @@ -3,7 +3,7 @@ 0. 2005 copyright update. - '''DONE''' 0. Cleanup of dead parts of the site. - '''tomcat-old, tomcat-4.0 and jmeter201 to go''' 1. Removal of Anakia build and usage of Ant/XSL as the only build system. - '''DONE''' - 1. Move site/news.* to redirects instead of meta refreshes. + 1. Move site/news.* to redirects instead of meta refreshes. Also agreement.html. 1. See if PRC will take Acknowledgements - ''Robert''. 2. New look site. a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T19:11:41 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo no comment Change Log: -- @@ -3,7 +3,7 @@ 0. 2005 copyright update. - '''DONE''' 0. Cleanup of dead parts of the site. - '''tomcat-old, tomcat-4.0 and jmeter201 to go''' 1. Removal of Anakia build and usage of Ant/XSL as the only build system. - '''DONE''' - 1. Move site/news.* to redirects instead of meta refreshes. Also agreement.html. + 1. Move site/news.* to redirects instead of meta refreshes. Also agreement.html. - '''DONE''' 1. See if PRC will take Acknowledgements - ''Robert''. 2. New look site. a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T19:15:23 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo no comment Change Log: -- @@ -5,6 +5,7 @@ 1. Removal of Anakia build and usage of Ant/XSL as the only build system. - '''DONE''' 1. Move site/news.* to redirects instead of meta refreshes. Also agreement.html. - '''DONE''' 1. See if PRC will take Acknowledgements - ''Robert''. + 1. Figure out how to remove idedev-*.html. Tomcat pages in jakarta-site2. 2. New look site. a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. a. Modification of XSL system to support mockup. ''Hen''. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jakarta-site2 now live on xslt
On Sat, 1 Jan 2005 19:50:10 -0500 (EST), Henri Yandell [EMAIL PROTECTED] wrote: I've fixed the various spacing issues in the XSLT system (over time the Anakia style sheet changed slightly) and as far as I can tell it looks the same. BTW, the source files don't look the same - but that is an advantage, as the Anakia output was not all that well laid out. I cautiously pushed a few pages up to check them out and then the whole lot. Still looks fine to me :) At least from the front page and linked pages, might be some deeper pages with issues that won't be picked up until we get around to deciding if they should exist (which is soon). I've removed the Website Maintenance link too, it no longer makes much sense and nobody seemed to mind the suggestion of killing it. It has (the page isn't gone yet, just the link) a lot of stuff about using jakarta-site2 as a system for other sites (I thought somebody mentioned Tomcat did this, but looking at their CVS repo I can't see references to jakarta-site2). If the old version is needed however, it is tagged under the tag PRE-ANAKIA-REMOVAL. If anyone can take a look and see if they can see problems, I'd appreciate it a lot. New years day means not a lot of users looking compared to usual (though also not a lot of committers around to check etc). I've not noticed any visible browsing errors in a brief check. The JMeter binary and source links work fine. However, the base tags have disappeared from the binindex and sourceindex output. I don't know if these are required or not - could it be that some mirror sites require them? If they are not required, that is an advantage, as it means that internal page links work much quicker. Dunno why, but it seems that the base tag causes intermal links to be treated as being on a new page, so the whole lot is reloaded... Another difference on the downloads pages (at least) is that the meta tags aren't closed. The Anakia stylesheet used to close these by including a trailing /; looks like the XSL version never did. Perhaps it should? Hen - 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: jakarta-site2 now live on xslt
On Sun, 2 Jan 2005, sebb wrote: On Sat, 1 Jan 2005 19:50:10 -0500 (EST), Henri Yandell [EMAIL PROTECTED] wrote: I've fixed the various spacing issues in the XSLT system (over time the Anakia style sheet changed slightly) and as far as I can tell it looks the same. BTW, the source files don't look the same - but that is an advantage, as the Anakia output was not all that well laid out. The XSLT version is a bit of a pain in that it's not doing newlines; I think it's quite easy to get them to stay I just need to remember how. I spent a lot of time hacking the html pages in debugging to find out that not having the DOCTYPE at the top causes some weird spacing issues :) If the old version is needed however, it is tagged under the tag PRE-ANAKIA-REMOVAL. If anyone can take a look and see if they can see problems, I'd appreciate it a lot. New years day means not a lot of users looking compared to usual (though also not a lot of committers around to check etc). I've not noticed any visible browsing errors in a brief check. The JMeter binary and source links work fine. However, the base tags have disappeared from the binindex and sourceindex output. I don't know if these are required or not - could it be that some mirror sites require them? If they are not required, that is an advantage, as it means that internal page links work much quicker. Dunno why, but it seems that the base tag causes intermal links to be treated as being on a new page, so the whole lot is reloaded... I'd been wondering why that was happening. There's nothing in either the comment history for either site.vsl or binindex.xml to imply that the base was put in for any special reason. However, Stefan Bodewig added the functionality for base tags into site.vsl in 1.27 with a comment of: Enable downloads via mirrors which suggests that it's probably important. I'll get it added back in, #1 priority. In fact, I'll hack it by hand first and figure out how to xsl it second :) Another difference on the downloads pages (at least) is that the meta tags aren't closed. The Anakia stylesheet used to close these by including a trailing /; looks like the XSL version never did. Perhaps it should? Bizarre that they're not closed given that XSL has to be XML compliant. I'll look into fixing this, lesser priority. Thanks, Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jakarta-site2 now live on xslt
On Sat, 1 Jan 2005, Henri Yandell wrote: On Sun, 2 Jan 2005, sebb wrote: However, the base tags have disappeared from the binindex and sourceindex output. I don't know if these are required or not - could it be that some mirror sites require them? They're back now. Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Jakarta-site2 - orphaned files in docs
On Sat, 4 Dec 2004, sebb wrote: Just happened to notice that some of the HTML files in the docs tree don't have corresponding XML files in the xdocs tree. For example docs/site/cvsonunix.html docs/site/elsewhere.html both of these correspond to deleted xml files in xdocs/site Seems to me that there's no point keeping the html files if the source xml files have been deleted (or moved elsewhere). There are also differences for some of the image types (gif jpeg jpg svg xcf png) that are copied from xdocs - though in this case the images have been deleted from docs/images, but not from xdocs/images. There are some files that are only in the docs tree - for example .htaccess, .cgi and some .txt files. These look OK. But it looks like docs/tac.jar and docs/buildsite.sh could be deleted. Any objections if I start clearing this up? Sorry no one replied when you sent this. All of the above should be taken care of now I think. The elsewhere pages had slipped through, so am glad I saw this email eventually :) Hen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T21:00:04 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo no comment Change Log: -- @@ -6,6 +6,8 @@ 1. Move site/news.* to redirects instead of meta refreshes. Also agreement.html. - '''DONE''' 1. See if PRC will take Acknowledgements - ''Robert''. 1. Figure out how to remove idedev-*.html. Tomcat pages in jakarta-site2. + 1. Why are meta tags being generated as bad xml? Is it the doctype of loose? + 1. The generated html could definitely do with pretty printing. 2. New look site. a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. a. Modification of XSL system to support mockup. ''Hen''. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Jakarta Wiki] Updated: SiteInfo
Date: 2005-01-01T21:33:41 Editor: HenriYandell Wiki: Jakarta Wiki Page: SiteInfo URL: http://wiki.apache.org/jakarta/SiteInfo More tasks. Change Log: -- @@ -12,6 +12,18 @@ a. Switch to three-column display - [http://www.apache.org/~bayard/mock-jakarta-frontpage.html]. a. Modification of XSL system to support mockup. ''Hen''. a. Use of CSS. + 1. Tighter front page. + 1. Delete content: + a. Vendor page + a. Acknowledgements page + a. Elsewhere news + a. Our Mission + a. Newsletter Editor page + a. Reference library + a. Related project stuff. + 1. Flatten Project Guidelines and all the other 'how to' pages into a shallower structure. + 1. Move JSPA stuff to www.apache.org. ''Geir''. + 1. Move Legal link from navbar to bottom of page. 1. Migrate to Subversion - [Site2 Conversion Instructions]. ''Tim''. 1. Migration of reference pages into Foundation. 2. Improvement of download pages. Creation of cgi pages. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
