Tomcat Apache and wiki migration
Hi, I like to join Tomcat Apache group. Also, any idea who is managing the migration of old Tomcat Wiki pages. https://cwiki.apache.org/confluence/display/TOMCAT/SupportAndTraining -- Cheers, Matt Zand myhsts.org coding-bootcamps.com
Re: Wiki migration
On 26/03/2019 17:52, Mark Thomas wrote: > On 25/03/2019 22:24, Konstantin Kolinko wrote: >> пт, 15 мар. 2019 г. в 21:32, Mark Thomas : >>> On 15/03/2019 18:05, Konstantin Kolinko wrote: As currently, it is not configured to echo changes to the dev@ mailing list, and if done so it cannot send plaintext e-mails. >>> >>> That issue is 50% confluence (it marks the changes email as bulk with no >>> option to change that) and 50% ezmlm (it automatically drops bulk >>> email). That problem should be solvable. I'll pester infra about that one. >> >> Any progress here? > > I asked on slack but I think the question got overlooked. I've raised: > https://issues.apache.org/jira/browse/INFRA-18107 As you have probably noticed, this has been fixed - mostly thanks to sebb. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Wiki migration
On 25/03/2019 22:24, Konstantin Kolinko wrote: > пт, 15 мар. 2019 г. в 21:32, Mark Thomas : >> >> On 15/03/2019 18:05, Konstantin Kolinko wrote: >>> пт, 15 мар. 2019 г. в 20:07, Mark Thomas : >>>> >>>> All, >>>> >>>> I am going to attempt the wiki migration. [...] >> >>> 2. Links used by Confluence are not pretty, with all those '+'s >>> >>> 3. It does to integrate well with e-mail. >>> >>> As currently, it is not configured to echo changes to the dev@ mailing list, >>> and if done so it cannot send plaintext e-mails. >> >> That issue is 50% confluence (it marks the changes email as bulk with no >> option to change that) and 50% ezmlm (it automatically drops bulk >> email). That problem should be solvable. I'll pester infra about that one. > > Any progress here? I asked on slack but I think the question got overlooked. I've raised: https://issues.apache.org/jira/browse/INFRA-18107 Mark > As an idea: Maybe configure a separate mailing list to which such > notifications are posted? > > If there needs to be a special configuration to accept "bulk" emails > and accept HTML emails, it may be easier to configure a separate > mailing list with such relaxed configuration rather then fine-tune > configuration of dev@tomcat. > > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Wiki migration
пт, 15 мар. 2019 г. в 21:32, Mark Thomas : > > On 15/03/2019 18:05, Konstantin Kolinko wrote: > > пт, 15 мар. 2019 г. в 20:07, Mark Thomas : > >> > >> All, > >> > >> I am going to attempt the wiki migration. [...] > > > 2. Links used by Confluence are not pretty, with all those '+'s > > > > 3. It does to integrate well with e-mail. > > > > As currently, it is not configured to echo changes to the dev@ mailing list, > > and if done so it cannot send plaintext e-mails. > > That issue is 50% confluence (it marks the changes email as bulk with no > option to change that) and 50% ezmlm (it automatically drops bulk > email). That problem should be solvable. I'll pester infra about that one. Any progress here? As an idea: Maybe configure a separate mailing list to which such notifications are posted? If there needs to be a special configuration to accept "bulk" emails and accept HTML emails, it may be easier to configure a separate mailing list with such relaxed configuration rather then fine-tune configuration of dev@tomcat. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Wiki migration
Thanks! I've done the following - Created a page called "Parent page for Trash" - Moved all user pages and many spam pages under that page (drag/drop a lot faster than clicking page then choose delete from options) - Put most FAQ pages under FAQ parent and removed FAQ from most page names - Did basic formatting cleanup and very minimal content removal for inaccurate information - Moved FAQ out of the "Migrated Content folder" Next todo's - Either create a top level how to and move more pages under it. Or put them under a HowTo in the FAQ hierarchy. This should cleanup quite a few pages out of the Migrated Content folder - Go back trough the FAQs and decide what to do with many of the dated tomcat 5/6 references. - Determine how to fix many of the broken mailing list links. - Try to determine where any remaining Migrated Content pages go. On Sun, Mar 17, 2019 at 4:12 PM Mark Thomas wrote: > It was a permission issue. I've just fixed that. > > Mark > > > On 17/03/2019 20:02, Tim Funk wrote: > > Hmm ... > > > > Either I don't have permissions to make edits, or I need read a > tutorial. I > > was going to delete some obvious spam pages which were migrated and then > > start moving other questionable pages to a sandbox to be debated later. > > > > I signed up via my apache email address. > > > > -Tim > > >
Re: Wiki migration
It was a permission issue. I've just fixed that. Mark On 17/03/2019 20:02, Tim Funk wrote: Hmm ... Either I don't have permissions to make edits, or I need read a tutorial. I was going to delete some obvious spam pages which were migrated and then start moving other questionable pages to a sandbox to be debated later. I signed up via my apache email address. -Tim - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Wiki migration
Hmm ... Either I don't have permissions to make edits, or I need read a tutorial. I was going to delete some obvious spam pages which were migrated and then start moving other questionable pages to a sandbox to be debated later. I signed up via my apache email address. -Tim
Re: Wiki migration
Thanks Mark. Through the rest of the month, I can try to set aside some time to take a look at fixing the pages Confluence. -Tim On Fri, Mar 15, 2019 at 7:32 PM Mark Thomas wrote: > On 15/03/2019 18:32, Mark Thomas wrote: > > On 15/03/2019 18:05, Konstantin Kolinko wrote: > >> пт, 15 мар. 2019 г. в 20:07, Mark Thomas : > ... > The migration is complete. > > We have a couple of options: > > 1. Make moin read-only at this point and start tidying up the pages that > were migrated Confluence > > 2. Leave moin as, treat this migration as a test. Review what was > migrated and do the real migration at a later point. > > 3. Something else. > ... > > >
Re: Wiki migration
On 15/03/2019 18:32, Mark Thomas wrote: > On 15/03/2019 18:05, Konstantin Kolinko wrote: >> пт, 15 мар. 2019 г. в 20:07, Mark Thomas : >>> >>> All, >>> >>> I am going to attempt the wiki migration. Given it is last thing on a >>> Friday, it will either work perfectly or be a complete disaster. I have >>> a backup of our Confluence Space in case it is the latter. >>> >>> If it works, I'll update the links on the website after the migration. >> >> I do not like it! > > Moin is being shutdown in less than three months. The choice is when we > migrate, not if we migrate. > >> 1. All links will be broken, including ones >> a) in e-mail archives >> b) on other sites, like stackoverflow > > That is going to be the case whatever we migrate to. It wouldn't be too > hard to put redirects in place. We can talk to infra about that. The old > pages will stay in place too so we have time. We just need to make the > old pages read-only. The migration is complete. We have a couple of options: 1. Make moin read-only at this point and start tidying up the pages that were migrated Confluence 2. Leave moin as, treat this migration as a test. Review what was migrated and do the real migration at a later point. 3. Something else. I'm going to move all the migrated pages under a 'Migrated' page so it is clear what is what. Mark > >> 2. Links used by Confluence are not pretty, with all those '+'s >> >> 3. It does to integrate well with e-mail. >> >> As currently, it is not configured to echo changes to the dev@ mailing list, >> and if done so it cannot send plaintext e-mails. > > That issue is 50% confluence (it marks the changes email as bulk with no > option to change that) and 50% ezmlm (it automatically drops bulk > email). That problem should be solvable. I'll pester infra about that one. > >> 4. Proprietary close-source software. > > As are GitHub and GitLab... > > We have already started moving some pages to Confluence manually. > >> Are there other ways? >> >> E.g. >> 1) static web site, managed via git pub-sub > > Not an option. You'd need to be a committer to use it. > >> 2) GitHub wiki pages? >> 3) GitLab wiki pages? >> >> There also exists the following project, >> http://jspwiki.apache.org/ >> if we talk about "our own dog food". > > Infra has chosen Confluence. If we want to run jspwiki on our own VM > that is an option but it needs *long term* volunteers to maintain the > VM. Experience elsewhere in the ASF is that that usually doesn't work. > > Mark > >> >> >> Best regards, >> Konstantin Kolinko >> >> - >> To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org >> For additional commands, e-mail: dev-h...@tomcat.apache.org >> > > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Wiki migration
On 3/15/2019 11:32 AM, Mark Thomas wrote: There also exists the following project, http://jspwiki.apache.org/ if we talk about "our own dog food". Infra has chosen Confluence. If we want to run jspwiki on our own VM that is an option but it needs *long term* volunteers to maintain the VM. Experience elsewhere in the ASF is that that usually doesn't work. I'm neither for nor against this option, but I am looking for ways to contribute more so if we go that route I'd be happy to volunteer for that ongoing task. Best, Igal - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Wiki migration
On 15/03/2019 18:05, Konstantin Kolinko wrote: > пт, 15 мар. 2019 г. в 20:07, Mark Thomas : >> >> All, >> >> I am going to attempt the wiki migration. Given it is last thing on a >> Friday, it will either work perfectly or be a complete disaster. I have >> a backup of our Confluence Space in case it is the latter. >> >> If it works, I'll update the links on the website after the migration. > > I do not like it! Moin is being shutdown in less than three months. The choice is when we migrate, not if we migrate. > 1. All links will be broken, including ones > a) in e-mail archives > b) on other sites, like stackoverflow That is going to be the case whatever we migrate to. It wouldn't be too hard to put redirects in place. We can talk to infra about that. The old pages will stay in place too so we have time. We just need to make the old pages read-only. > 2. Links used by Confluence are not pretty, with all those '+'s > > 3. It does to integrate well with e-mail. > > As currently, it is not configured to echo changes to the dev@ mailing list, > and if done so it cannot send plaintext e-mails. That issue is 50% confluence (it marks the changes email as bulk with no option to change that) and 50% ezmlm (it automatically drops bulk email). That problem should be solvable. I'll pester infra about that one. > 4. Proprietary close-source software. As are GitHub and GitLab... We have already started moving some pages to Confluence manually. > Are there other ways? > > E.g. > 1) static web site, managed via git pub-sub Not an option. You'd need to be a committer to use it. > 2) GitHub wiki pages? > 3) GitLab wiki pages? > > There also exists the following project, > http://jspwiki.apache.org/ > if we talk about "our own dog food". Infra has chosen Confluence. If we want to run jspwiki on our own VM that is an option but it needs *long term* volunteers to maintain the VM. Experience elsewhere in the ASF is that that usually doesn't work. Mark > > > Best regards, > Konstantin Kolinko > > - > To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org > For additional commands, e-mail: dev-h...@tomcat.apache.org > - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Re: Wiki migration
пт, 15 мар. 2019 г. в 20:07, Mark Thomas : > > All, > > I am going to attempt the wiki migration. Given it is last thing on a > Friday, it will either work perfectly or be a complete disaster. I have > a backup of our Confluence Space in case it is the latter. > > If it works, I'll update the links on the website after the migration. I do not like it! 1. All links will be broken, including ones a) in e-mail archives b) on other sites, like stackoverflow 2. Links used by Confluence are not pretty, with all those '+'s 3. It does to integrate well with e-mail. As currently, it is not configured to echo changes to the dev@ mailing list, and if done so it cannot send plaintext e-mails. 4. Proprietary close-source software. Are there other ways? E.g. 1) static web site, managed via git pub-sub 2) GitHub wiki pages? 3) GitLab wiki pages? There also exists the following project, http://jspwiki.apache.org/ if we talk about "our own dog food". Best regards, Konstantin Kolinko - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
Wiki migration
All, I am going to attempt the wiki migration. Given it is last thing on a Friday, it will either work perfectly or be a complete disaster. I have a backup of our Confluence Space in case it is the latter. If it works, I'll update the links on the website after the migration. Mark - To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org For additional commands, e-mail: dev-h...@tomcat.apache.org
