Re: general@velocity mailing list
Well, it's been 10 days, so I'll assume lazy consensus for the rest of the velocity team. Our first step is to remove the mailing list information from our web site. This is a good excuse to figure out how the web site is generated and published, so I'll take a look at this one, as I understand at least the second part. Our second step is send out a message and shut down the general@ list. How does this sound? Subject: Discontinuing general@velocity mailing list. Switch to user@velocity. Velocity community members: We are shutting down the gene...@velocity.apache.org mailing list as it duplicates the u...@velocity.apache.org mailing list and is not publicly mirrored elsewhere, unlike our other mailing lists on nabble.com or mail-archive.org. If you no longer wish to receive velocity-related information, or you are already subscribed to the u...@velocity.apache.org mailing list, no further action is required. If you are subscribed to gene...@velocity.apache.org but not subscribed to u...@velocity.apache.org, and you wish to continue to receive velocity-related messages, you will need to subscribe to u...@velocity.apache.org by sending an email to user-subscr...@velocity.apache.org to sign up (no subject or message body required) as described here: http://velocity.apache.org/engine/devel/mail-lists.html Best regards, The Apache Velocity development team Our third and final step will be to open an INFRA ticket and ask that the general@ mailing list be removed. On Sat, May 30, 2015 at 12:29 PM, Nathan Bubna nbu...@gmail.com wrote: +1 On Sat, May 30, 2015 at 7:58 AM, Frederick N. Brier fnbr...@gmail.com wrote: Sounds good to me :). On 05/30/2015 04:11 AM, Mike Kienenberger wrote: And while we're at it, why have a general@apache mailing list? Something inherited from Jakarta? It's not archived or publicly visible on nabble or mail-archive.com. Users have a difficult enough time determining whether a posting should go to user@ and dev@. I see nothing that differentiates between general@ and user@. I propose we remove the mailing list from our mailing lists page, and post a last message to general@ that we're shutting down general@ and switching existing subscribers to user@, and include instructions on how to unsubscribe from user@. That's if we want to go opt-out. Or go with opt-in, and post a last message to general@ that we're shutting down general@ and include instructions on how to subscribe to user@. Opt-in is probably the better approach. Then we ask infra to shut down the mailing list and optionally set up a redirect from general@ to user@. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: general@velocity mailing list
Sounds great, thanks! On Tue, Jun 9, 2015 at 7:17 AM, Mike Kienenberger mkien...@gmail.com wrote: Well, it's been 10 days, so I'll assume lazy consensus for the rest of the velocity team. Our first step is to remove the mailing list information from our web site. This is a good excuse to figure out how the web site is generated and published, so I'll take a look at this one, as I understand at least the second part. Our second step is send out a message and shut down the general@ list. How does this sound? Subject: Discontinuing general@velocity mailing list. Switch to user@velocity. Velocity community members: We are shutting down the gene...@velocity.apache.org mailing list as it duplicates the u...@velocity.apache.org mailing list and is not publicly mirrored elsewhere, unlike our other mailing lists on nabble.com or mail-archive.org. If you no longer wish to receive velocity-related information, or you are already subscribed to the u...@velocity.apache.org mailing list, no further action is required. If you are subscribed to gene...@velocity.apache.org but not subscribed to u...@velocity.apache.org, and you wish to continue to receive velocity-related messages, you will need to subscribe to u...@velocity.apache.org by sending an email to user-subscr...@velocity.apache.org to sign up (no subject or message body required) as described here: http://velocity.apache.org/engine/devel/mail-lists.html Best regards, The Apache Velocity development team Our third and final step will be to open an INFRA ticket and ask that the general@ mailing list be removed. On Sat, May 30, 2015 at 12:29 PM, Nathan Bubna nbu...@gmail.com wrote: +1 On Sat, May 30, 2015 at 7:58 AM, Frederick N. Brier fnbr...@gmail.com wrote: Sounds good to me :). On 05/30/2015 04:11 AM, Mike Kienenberger wrote: And while we're at it, why have a general@apache mailing list? Something inherited from Jakarta? It's not archived or publicly visible on nabble or mail-archive.com. Users have a difficult enough time determining whether a posting should go to user@ and dev@. I see nothing that differentiates between general@ and user@. I propose we remove the mailing list from our mailing lists page, and post a last message to general@ that we're shutting down general@ and switching existing subscribers to user@, and include instructions on how to unsubscribe from user@. That's if we want to go opt-out. Or go with opt-in, and post a last message to general@ that we're shutting down general@ and include instructions on how to subscribe to user@. Opt-in is probably the better approach. Then we ask infra to shut down the mailing list and optionally set up a redirect from general@ to user@. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: Changing velocity web site
Thanks for pointing that one out. I missed it despite Will mentioning committer section. I was looking at this one: http://wiki.apache.org/velocity/VelocitySite So that helps. In the old days, the site was build in pieces, checked in, and then merged using zones. So the trick will be to either move that merging process back to the local system or to directly push the pieces into the right place in site/production. I'll see if I can find a copy of /export/home/velocity/bin/*.sh in svn On Tue, Jun 9, 2015 at 4:26 PM, Sergiu Dumitriu sergiu.dumit...@gmail.com wrote: Especially http://wiki.apache.org/velocity/RebuildSites On 06/09/2015 04:18 PM, Will Glass-Husain wrote: Hi Mike, Have you reviewed the nots on the wiki? They are old but may be of use. Look at Committer info section on this page. http://wiki.apache.org/velocity/ WILL On Tue, Jun 9, 2015 at 12:41 PM, Mike Kienenberger mkien...@gmail.com wrote: I've done some poking around. https://svn.apache.org/repos/asf/velocity/site/production is indeed the svnsubpub directory: any changes committed here are instantly deployed to the web site. https://svn.apache.org/repos/asf/velocity/site/site appears to be the maven project to build the site. I've had limited success with this. If I compare the target/site/* files with the production/* files, I find: - The front page files are rebuilt with an updated copyright and last published date, but they lose the Project Documentation section (project info and project report links) - Same for the reports/ directory contents. - Many files are missing. I'm guessing that subprojects need to build the missing pieces (each seems to have a src/site directory). I attempted to build site using mvn on trunk (2.x) but generated pages that look very different from what's deployed. I attempted to build site using mvn on 1.x (had to upgrade findbugs-maven-plugin to what 2.x was using to make the build work) and got a mostly blank page with a header that still looked different. So I'm not sure how to build the web site so that it matches what's currently out there. If anyone has any hints, please let me know. On Mon, Jun 8, 2015 at 10:38 AM, Mike Kienenberger mkien...@gmail.com wrote: On Sun, Jun 7, 2015 at 7:11 PM, Will Glass-Husain wglasshus...@gmail.com wrote: The build process for the site is very old -- is that still applicable after the svnpubsub change? svnpubsub makes it so that whenever you commit to the svnpubsub directory, those changes are immediately pushed out into the live web site. So it's more of a change in how pages are published than a change in how pages are created.I haven't looked that the build process for the site, but I would guess only the deployment stage needs to be updated. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org -- Sergiu Dumitriu http://purl.org/net/sergiu - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: Changing velocity web site
Hi Mike, Have you reviewed the nots on the wiki? They are old but may be of use. Look at Committer info section on this page. http://wiki.apache.org/velocity/ WILL On Tue, Jun 9, 2015 at 12:41 PM, Mike Kienenberger mkien...@gmail.com wrote: I've done some poking around. https://svn.apache.org/repos/asf/velocity/site/production is indeed the svnsubpub directory: any changes committed here are instantly deployed to the web site. https://svn.apache.org/repos/asf/velocity/site/site appears to be the maven project to build the site. I've had limited success with this. If I compare the target/site/* files with the production/* files, I find: - The front page files are rebuilt with an updated copyright and last published date, but they lose the Project Documentation section (project info and project report links) - Same for the reports/ directory contents. - Many files are missing. I'm guessing that subprojects need to build the missing pieces (each seems to have a src/site directory). I attempted to build site using mvn on trunk (2.x) but generated pages that look very different from what's deployed. I attempted to build site using mvn on 1.x (had to upgrade findbugs-maven-plugin to what 2.x was using to make the build work) and got a mostly blank page with a header that still looked different. So I'm not sure how to build the web site so that it matches what's currently out there. If anyone has any hints, please let me know. On Mon, Jun 8, 2015 at 10:38 AM, Mike Kienenberger mkien...@gmail.com wrote: On Sun, Jun 7, 2015 at 7:11 PM, Will Glass-Husain wglasshus...@gmail.com wrote: The build process for the site is very old -- is that still applicable after the svnpubsub change? svnpubsub makes it so that whenever you commit to the svnpubsub directory, those changes are immediately pushed out into the live web site. So it's more of a change in how pages are published than a change in how pages are created.I haven't looked that the build process for the site, but I would guess only the deployment stage needs to be updated. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: Changing velocity web site
Thanks. I wasn't aware of that page. Unfortunately, it confirms what I've guessed so far by reading through the existing maven site docs + experimentation, without actually providing the missing pieces :) Everything past the site module is marked TODO The one new piece of information I see there is a reference to building engine site docs with ant but publishing via maven -- I'll see if I can track that one down. On Tue, Jun 9, 2015 at 4:18 PM, Will Glass-Husain wglasshus...@gmail.com wrote: Hi Mike, Have you reviewed the nots on the wiki? They are old but may be of use. Look at Committer info section on this page. http://wiki.apache.org/velocity/ WILL On Tue, Jun 9, 2015 at 12:41 PM, Mike Kienenberger mkien...@gmail.com wrote: I've done some poking around. https://svn.apache.org/repos/asf/velocity/site/production is indeed the svnsubpub directory: any changes committed here are instantly deployed to the web site. https://svn.apache.org/repos/asf/velocity/site/site appears to be the maven project to build the site. I've had limited success with this. If I compare the target/site/* files with the production/* files, I find: - The front page files are rebuilt with an updated copyright and last published date, but they lose the Project Documentation section (project info and project report links) - Same for the reports/ directory contents. - Many files are missing. I'm guessing that subprojects need to build the missing pieces (each seems to have a src/site directory). I attempted to build site using mvn on trunk (2.x) but generated pages that look very different from what's deployed. I attempted to build site using mvn on 1.x (had to upgrade findbugs-maven-plugin to what 2.x was using to make the build work) and got a mostly blank page with a header that still looked different. So I'm not sure how to build the web site so that it matches what's currently out there. If anyone has any hints, please let me know. On Mon, Jun 8, 2015 at 10:38 AM, Mike Kienenberger mkien...@gmail.com wrote: On Sun, Jun 7, 2015 at 7:11 PM, Will Glass-Husain wglasshus...@gmail.com wrote: The build process for the site is very old -- is that still applicable after the svnpubsub change? svnpubsub makes it so that whenever you commit to the svnpubsub directory, those changes are immediately pushed out into the live web site. So it's more of a change in how pages are published than a change in how pages are created.I haven't looked that the build process for the site, but I would guess only the deployment stage needs to be updated. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
Re: Changing velocity web site
Especially http://wiki.apache.org/velocity/RebuildSites On 06/09/2015 04:18 PM, Will Glass-Husain wrote: Hi Mike, Have you reviewed the nots on the wiki? They are old but may be of use. Look at Committer info section on this page. http://wiki.apache.org/velocity/ WILL On Tue, Jun 9, 2015 at 12:41 PM, Mike Kienenberger mkien...@gmail.com wrote: I've done some poking around. https://svn.apache.org/repos/asf/velocity/site/production is indeed the svnsubpub directory: any changes committed here are instantly deployed to the web site. https://svn.apache.org/repos/asf/velocity/site/site appears to be the maven project to build the site. I've had limited success with this. If I compare the target/site/* files with the production/* files, I find: - The front page files are rebuilt with an updated copyright and last published date, but they lose the Project Documentation section (project info and project report links) - Same for the reports/ directory contents. - Many files are missing. I'm guessing that subprojects need to build the missing pieces (each seems to have a src/site directory). I attempted to build site using mvn on trunk (2.x) but generated pages that look very different from what's deployed. I attempted to build site using mvn on 1.x (had to upgrade findbugs-maven-plugin to what 2.x was using to make the build work) and got a mostly blank page with a header that still looked different. So I'm not sure how to build the web site so that it matches what's currently out there. If anyone has any hints, please let me know. On Mon, Jun 8, 2015 at 10:38 AM, Mike Kienenberger mkien...@gmail.com wrote: On Sun, Jun 7, 2015 at 7:11 PM, Will Glass-Husain wglasshus...@gmail.com wrote: The build process for the site is very old -- is that still applicable after the svnpubsub change? svnpubsub makes it so that whenever you commit to the svnpubsub directory, those changes are immediately pushed out into the live web site. So it's more of a change in how pages are published than a change in how pages are created.I haven't looked that the build process for the site, but I would guess only the deployment stage needs to be updated. - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org -- Sergiu Dumitriu http://purl.org/net/sergiu - To unsubscribe, e-mail: dev-unsubscr...@velocity.apache.org For additional commands, e-mail: dev-h...@velocity.apache.org
