Re: [board-discuss] Apache ODF Toolkit migration
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi *, On 28.11.2018 11:00, Michael Meeks wrote: >> 2. the web site, in SVN (will also be changed to read-only): >> >>https://svn.apache.org/repos/asf/incubator/odf/site/ >> >>the SVN repo contains some MarkDown files that are converted to > ... >>presumably there should be a way to preserve the (relatively small >>and simple) content of the repo to either Wiki markup, or somethin g >>that some other MarkDown-to-HTML tool can understand; volunteers a re >>certainly welcome to help with this. > Sounds sensible - what is the scale of the problem: how many lines/ta gs > of markdown ? > there are converters (see https://stackoverflow.com/questions/9824489/any-markdown-to-wikimarkup-c onverter-available ) so especially pandoc. I offer the help for the MWiki migration. ;-) Best regards, Dennis Roczek -BEGIN PGP SIGNATURE- Comment: Using GnuPG with Thunderbird - https://www.enigmail.net/ iQIzBAEBCAAdFiEEhYmMfFabYko4V91Tzj5B/c4qttkFAlv+gMsACgkQzj5B/c4q ttnSkA//WRKQXJ8PTHxjAT3ssMPKomcZlReaEtgnFzC3uRwNNhgfA92MX8WNaUqo PIuU5bPDXaJqfjyNsftdwnDtd5rcPCEd0NspEdAwv83JuYQEM9/6HbhyCfQqXWt/ hIc/ypZs9qJQtyvkag+Hvyzo7ezezOV0vUnV6uYWEF++Mb0C5rFJlmRIytYZkTZP evG7f7j3zGsnvr+ojDYQV2Iv9/p09A4OJKWhRbGsFm0QfRdH0/m47e06FnHVc7Hq cv98cWAeQJc7Bd70IXtJqX2zv0k5Y3T77JgLrgO+CfTDbX8DvFvqeWPmdJ/LQ6K+ ilA81b5+FPDFomc4xreLR7mlgrr6KKir+YTAAPB5YjfRHckBsX1AjwUaqQi84OrI 3Pu9Ode0p4BxwiFsmokwZ517Jwud/NPtFXASwJv6BIGC7L4JwyjvD4UXqw8Epnuu 5VqGsjy0VZ2fK30V8RS8H2fSnqVfMUfLh6nXhrFnzLKQJHR8TBnrCS7KIdibD9U/ LR2h1qC0sYVYeoeFR2/ctxXCQBV9dspCxGi74ebvWrcDqlcYqGSKkYCemUcJvzdu 17gSixqlPIQyJPzSo4oPVoqfX5AbShmzsVGzCIcluNfU7vaeD8FWlAYNlNKOYAsN PUkT6Rm9sB/1wFCJ94Ov6DI+AE+dHYU8p3xtVwSkOb/x1q6H8mY= =l/qW -END PGP SIGNATURE- -- To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.documentfoundation.org/www/board-discuss/ Privacy Policy: https://www.documentfoundation.org/privacy
Re: [board-discuss] Apache ODF Toolkit migration
Hi! On Wed, Nov 28, 2018 at 11:12 AM Thorsten Behrens < t...@documentfoundation.org> wrote: > Michael Meeks wrote: > > On 28/11/2018 09:40, Michael Stahl wrote: > > > so i'll propose to migrate the ODF Toolkit to The Document Foundation. > > > > Seems like something the BoD should vote on, In general, subject > to the > > marketing concerns at the end, it seems like a good idea to me. I assume > > there are no current contributors to be upset either way. > > > Indeed, very supportive of that idea. I'd be quite happy if the ASF > would formally agree handing this over to TDF. > I agree. I would be very pleased for TDF to host this as a service, and would prefer that it happened with the co-operation of the ASF. S.
Re: [board-discuss] Apache ODF Toolkit migration
Hi *, Michael Meeks wrote: > On 28/11/2018 09:40, Michael Stahl wrote: > > so i'll propose to migrate the ODF Toolkit to The Document Foundation. > > Seems like something the BoD should vote on, In general, subject to the > marketing concerns at the end, it seems like a good idea to me. I assume > there are no current contributors to be upset either way. > Indeed, very supportive of that idea. I'd be quite happy if the ASF would formally agree handing this over to TDF. The functionality the code provides is rather important to the ODF ecosystem, and LibreOffice in particular. Being able to maintain it (if only occasionally), and having an official upstream that is not read-only is crucial at least to me. > From a licensing / contributor / compliance perspective - I'd expect > this to be adapted to fit with our existing policies & practice. > Yes. Though I think that is a 2nd or a 3rd step, after consensus has emerged if/where to host this project (assuming that whoever commits to hosting it, can then set policies). > I like the idea of immediately sub-setting this - so if people want to > come along and resurrect the full project they can do so at Apache - > while we continue to maintain the bits that we need. > Agreed. > As such I think we should scope and frame this as "We are hosting and > maintaining a validation tool we use, while we use it" - rather than > creating an expectation that we're going to start a significant > evangelism effort around investing in, promoting, and improving a > Java-based ODF DOM implementation. Does that fit with your goal ? > ??? That is certainly nothing someone would want to do over here. But perhaps worth stating the obvious. ;) Cheers, -- Thorsten signature.asc Description: PGP signature
Re: [board-discuss] Apache ODF Toolkit migration
Hi Michael, First - thanks for working on this, (and Svante too) - it looks positive overall. On 28/11/2018 09:40, Michael Stahl wrote: > so i'll propose to migrate the ODF Toolkit to The Document Foundation. Seems like something the BoD should vote on, In general, subject to the marketing concerns at the end, it seems like a good idea to me. I assume there are no current contributors to be upset either way. From a licensing / contributor / compliance perspective - I'd expect this to be adapted to fit with our existing policies & practice. Then some other random preferences that I'm not deeply wedded. > the obvious options are: > a) move the git repository to gerrit.libreoffice.org Sounds sensible. > 2. the web site, in SVN (will also be changed to read-only): > > https://svn.apache.org/repos/asf/incubator/odf/site/ > > the SVN repo contains some MarkDown files that are converted to ... > presumably there should be a way to preserve the (relatively small > and simple) content of the repo to either Wiki markup, or something > that some other MarkDown-to-HTML tool can understand; volunteers are > certainly welcome to help with this. Sounds sensible - what is the scale of the problem: how many lines/tags of markdown ? > 3. the domain "odftoolkit.org" - this currently redirects to > "http://incubator.apache.org/odftoolkit/; > > this domain would need to be transferred from ASF to TDF before it > expires. Sounds sensible, if the ASF is willing of course. > 4. mailing list: the "odf-...@incubator.apache.org" will be retired; > probably the amount of traffic is going to be quite small, hence > suggest to just use "libreoff...@freedesktop.org" for now; if the > traffic increases and becomes a problem a dedicated list can be > set up later. Sounds great. > 5. currently the ASF JIRA is used as bug tracker, with project > "ODFTOOLKIT": > > https://issues.apache.org/jira/browse/ODFTOOLKIT-479?jql=project%20%3D%20ODFTOOLKIT > > there are currently 137 issues that are neither RESOLVED nor CLOSED. > > so there are 2 decisions to be made here: > > a) do we want a new component in "bugs.documentfoundation.org" > Bugzilla, I'd say yes; but Xisco should make the call. > b) should open issues be migrated? as long as they will be accessible > read-only in ASF JIRA (and i don't see any reason why not), i > don't see much value in it, since there aren't currently > developers available with time to fix the issues; if anybody feels > strongly about their issue they can re-create/copy it over > manually. Sounds very sensible. > another point that we should probably discuss after the migration is > finished is whether the so-called "Simple API" should be removed from > ODFDOM due to being duplicative and unmaintained for years. I like the idea of immediately sub-setting this - so if people want to come along and resurrect the full project they can do so at Apache - while we continue to maintain the bits that we need. I am slightly wary of how the LibreOffice / TDF support could be used in a marketing context around whatever new stuff goes into odf-dom. I'm not eager for this to become a distraction to our core mission around LibreOffice. As such I think we should scope and frame this as "We are hosting and maintaining a validation tool we use, while we use it" - rather than creating an expectation that we're going to start a significant evangelism effort around investing in, promoting, and improving a Java-based ODF DOM implementation. Does that fit with your goal ? That may sound an odd request =) however there have been innumerable proposals in the past by well meaning, but not terribly technically competent people to "Re-write LibreOffice based on an ODF DOM" - and I want to stop that (damaging) hot-air before it re-starts - it has the potential to be quite harmful to our credibility. From a marketing perspective we should probably continue to emphasize that LibreOffice has no Java dependency - and that this is not going to change. Anyhow; I support the proposal, thanks Michael - waiting for other BoD members' input. ATB, Michael. -- michael.me...@collabora.com <><, GM Collabora Productivity Hangout: mejme...@gmail.com, Skype: mmeeks (M) +44 7795 666 147 - timezone usually UK / Europe -- To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.documentfoundation.org/www/board-discuss/ Privacy Policy: https://www.documentfoundation.org/privacy
[board-discuss] Apache ODF Toolkit migration
hello TDF folks, hello ODF Toolkit community, i'm writing here as a Committer (fwiw) of the Apache ODF Toolkit (incubating) project. it turns out the ASF has voted to rename the Apache ODF Toolkit (incubating) project to Apache ODF Toolkit (retired). https://lists.apache.org/thread.html/d4b4b33470a7bc3e70dc6192527168bb5907810045df5453c784cc93@%3Codf-dev.incubator.apache.org%3E https://mail-archives.apache.org/mod_mbox/incubator-general/201811.mbox/%3cca61fcd0-ff43-4e4a-bc30-5a942ae53...@comcast.net%3e the ODF Toolkit project is important for the ODF ecosystem in general and for LibreOffice in particular, since it contains not only the ODFDOM Java library, but also the most accurate ODF Validator, which we use in the LibreOffice test suite to check the ODF export filter. so i'll propose to migrate the ODF Toolkit to The Document Foundation. this is my (probably incomplete) understanding of the various different parts of the project that need some action: 1. git: the repository of record is on GitHub, and will be changed to read-only by the ASF: https://github.com/apache/odftoolkit the obvious options are: a) move the git repository to gerrit.libreoffice.org b) fork the GitHub project and continue hosting on GitHub In any case, we should have a redirect from the old incubator project to the new sources (perhaps a big red notice in README will be enough?). 2. the web site, in SVN (will also be changed to read-only): https://svn.apache.org/repos/asf/incubator/odf/site/ the SVN repo contains some MarkDown files that are converted to static HTML by some mysterious ASF-grown tool (Svante claims that Perl scripts that rewrite references and a custom CMS are involved somehow) that doesn't talk to anything other than the ASF SVN server and which nobody in the ODF Toolkit project understands. presumably there should be a way to preserve the (relatively small and simple) content of the repo to either Wiki markup, or something that some other MarkDown-to-HTML tool can understand; volunteers are certainly welcome to help with this. for a quick start it could also be an option to scrape the existing HTML from http://incubator.apache.org/odftoolkit/ and replace the internal URLs for consistency... 3. the domain "odftoolkit.org" - this currently redirects to "http://incubator.apache.org/odftoolkit/; this domain would need to be transferred from ASF to TDF before it expires. (i don't know whether other domains related to ODF Toolkit exist; apparently "odftoolkit.com" was registered at some time but it's already expired/for sale) 4. mailing list: the "odf-...@incubator.apache.org" will be retired; probably the amount of traffic is going to be quite small, hence suggest to just use "libreoff...@freedesktop.org" for now; if the traffic increases and becomes a problem a dedicated list can be set up later. 5. currently the ASF JIRA is used as bug tracker, with project "ODFTOOLKIT": https://issues.apache.org/jira/browse/ODFTOOLKIT-479?jql=project%20%3D%20ODFTOOLKIT there are currently 137 issues that are neither RESOLVED nor CLOSED. so there are 2 decisions to be made here: a) do we want a new component in "bugs.documentfoundation.org" Bugzilla, or use GitHub issues (only makes sense if GitHub is used for the repo, of course) b) should open issues be migrated? as long as they will be accessible read-only in ASF JIRA (and i don't see any reason why not), i don't see much value in it, since there aren't currently developers available with time to fix the issues; if anybody feels strongly about their issue they can re-create/copy it over manually. another point that we should probably discuss after the migration is finished is whether the so-called "Simple API" should be removed from ODFDOM due to being duplicative and unmaintained for years. regards, michael PS: thanks to Svante for proofreading this, if any errors remain it's my fault -- To unsubscribe e-mail to: board-discuss+unsubscr...@documentfoundation.org Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette List archive: https://listarchives.documentfoundation.org/www/board-discuss/ Privacy Policy: https://www.documentfoundation.org/privacy