Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Le Fri, 20 Jun 2014 00:14:10 +0200, William Gathoye will...@gathoye.be a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2014 03:20 PM, Charles-H. Schulz wrote: Yes indeed. I'm just wondering whether we could tweak this a bit with successive posts and links on separate topics. Tagging and separate topics might just fit within such a platform. Let develop this feature in the near future, I mean as soon the new planet has been released ;-) I'm gonna put LOWN on the wiki on the evening and will create a new page in the header (according to sophi, no need to ask other teams, excepted if it is related to developers). To keep a hierarchy/organization, the page will be subclassed like this, : LOWN\1 LOWN\2 LOWN\3 ... OK. Make sure projects@ and this list here know about the URL so that people can add content. We keep this easy I think; Wordpress if we use wordpress, another backend if we use another. Ok I see your Wordpress instance does support image inline [1]. Illustration images can be inserted easily then. Note that I'm unsure whether Wordpress is the best solution here. I don't have something specific in mind, so feel free to suggest something else. I've no other solution in mind, so let's go for the wordpress. hold on there, I only trust a wordpress post once I've taken a look at the post about to be published and how it fits visually within the page, so no cron job for me :-) Ok let's do (you :P or me if I've credentials) this step manually, then ;-) - Use a cron to extract the text version from the wiki and post it on the mailing list. yes the cron job here would indeed be very useful. I'll execute the cron on Sunday evening, in that way contributors can review the subjects if needed, and correct my poor English ;-) The WordPress publication should be made on Sunday too, to keep consistency. Yes. And note that even that publication can be scheduled from within WP. Best, Charles. Regards, [1] http://blog.documentfoundation.org/2014/03/13/libreoffice-4-2-2-fresh-is-ready-for-download/ - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJTo2CyAAoJEA595SwE1xaDa2wQANd6f5GvI2AHfSGDbfigFXev pI5QRn6cEcIV9oNL19XuoZ0oHexVRYmIE/79rVdtt3uPdRpmy8TRTbLI2u4jLQKf Ay7GXTAzHEy3W3oJj927bD6W/luD2FQzviuEXOZbg2W2rEE+//8ZebEUZHg/q+j8 gQl1vYR7UicHXKGJ+SWkB79oMKKz9ZSp2cRX7MkTqWnXjoQDQuOfIPXXBziuXR3L 03oPpU5q3pUOQCtpbWdgNjEgcc32o93HSVxXsHaoqtRo9ThJQJylvi8vOzAd6604 P6osrsPiaI0ix+bhC+qEeoG0gusu2Gua8sKrVbXLougJABZSWZ3WHATBmJOViOkS p/br2v1i6XRHrWgDAYfjirc86maag2R4SfYyVGX0d2D0QpXVMWnwWZbLq/mNZx81 x6qvpjS7B2McqXbeYME6h8uPZXHtEKoCJsuaqNOb7HQ2l0VY1NDbfQiaJXmqO7mN rkE7yxK6UJ+KDcbOC7KSqdpBafcDY4TaFEaRorpRby3PHlnYNJ0nL0Oix2WxZOkh cvexQuHWuVUTUnmxTkKydJt0+g12YGgj3sER7kgla7wL1jMdPY1L+gk9jh3+nrhg OCmWBS08ALhmj86Z2lmvpeW1k8I2ssX6FjphvcncB21EYUJttaLOPf5JyknSMg2l uDUmpQdrdQUdWHagaCpY =i5wq -END PGP SIGNATURE- - -- Charles-H. Schulz Co-founder, The Document Foundation, Kurfürstendamm 188, 10707 Berlin Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts Legal details: http://www.documentfoundation.org/imprint Mobile Number: +33 (0)6 98 65 54 24. -BEGIN PGP SIGNATURE- Version: GnuPG v2 iD8DBQFTo9T2oC0xO/kLVsQRAq9cAJ9IKurWtmiHxg1Nx/tv40uSWv3rTACgikGh cWbY0ZI/hKZii/rc1XhPYeY= =eV1/ -END PGP SIGNATURE- -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2014 03:20 PM, Charles-H. Schulz wrote: Yes indeed. I'm just wondering whether we could tweak this a bit with successive posts and links on separate topics. Tagging and separate topics might just fit within such a platform. Let develop this feature in the near future, I mean as soon the new planet has been released ;-) I'm gonna put LOWN on the wiki on the evening and will create a new page in the header (according to sophi, no need to ask other teams, excepted if it is related to developers). To keep a hierarchy/organization, the page will be subclassed like this, : LOWN\1 LOWN\2 LOWN\3 ... We keep this easy I think; Wordpress if we use wordpress, another backend if we use another. Ok I see your Wordpress instance does support image inline [1]. Illustration images can be inserted easily then. Note that I'm unsure whether Wordpress is the best solution here. I don't have something specific in mind, so feel free to suggest something else. I've no other solution in mind, so let's go for the wordpress. hold on there, I only trust a wordpress post once I've taken a look at the post about to be published and how it fits visually within the page, so no cron job for me :-) Ok let's do (you :P or me if I've credentials) this step manually, then ;-) - Use a cron to extract the text version from the wiki and post it on the mailing list. yes the cron job here would indeed be very useful. I'll execute the cron on Sunday evening, in that way contributors can review the subjects if needed, and correct my poor English ;-) The WordPress publication should be made on Sunday too, to keep consistency. Regards, [1] http://blog.documentfoundation.org/2014/03/13/libreoffice-4-2-2-fresh-is-ready-for-download/ - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJTo2CyAAoJEA595SwE1xaDa2wQANd6f5GvI2AHfSGDbfigFXev pI5QRn6cEcIV9oNL19XuoZ0oHexVRYmIE/79rVdtt3uPdRpmy8TRTbLI2u4jLQKf Ay7GXTAzHEy3W3oJj927bD6W/luD2FQzviuEXOZbg2W2rEE+//8ZebEUZHg/q+j8 gQl1vYR7UicHXKGJ+SWkB79oMKKz9ZSp2cRX7MkTqWnXjoQDQuOfIPXXBziuXR3L 03oPpU5q3pUOQCtpbWdgNjEgcc32o93HSVxXsHaoqtRo9ThJQJylvi8vOzAd6604 P6osrsPiaI0ix+bhC+qEeoG0gusu2Gua8sKrVbXLougJABZSWZ3WHATBmJOViOkS p/br2v1i6XRHrWgDAYfjirc86maag2R4SfYyVGX0d2D0QpXVMWnwWZbLq/mNZx81 x6qvpjS7B2McqXbeYME6h8uPZXHtEKoCJsuaqNOb7HQ2l0VY1NDbfQiaJXmqO7mN rkE7yxK6UJ+KDcbOC7KSqdpBafcDY4TaFEaRorpRby3PHlnYNJ0nL0Oix2WxZOkh cvexQuHWuVUTUnmxTkKydJt0+g12YGgj3sER7kgla7wL1jMdPY1L+gk9jh3+nrhg OCmWBS08ALhmj86Z2lmvpeW1k8I2ssX6FjphvcncB21EYUJttaLOPf5JyknSMg2l uDUmpQdrdQUdWHagaCpY =i5wq -END PGP SIGNATURE- -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
On Mon, Jun 16, 2014 at 10:03:45AM +0200, Charles-H. Schulz wrote: - again, thank you for all this I like the breadth and quality of content. Let's make this a collaborative effort. For sure. But the initial idea was to keep it oriented to developers as much possible. Although I'm not against to broaden the audience. If you have interesting content I'm not aware of, you can let me know and I will gonna integrate it. At first, I thought that - - using pull requests on Github - - and sending content via email for those who don't use Github would be a great idea. After a discussion on #libreoffice-fr, I realised that a Wiki page for each LOWN is a great solution. yup; perhaps even an official blog platform. What do you think? FWIW, there is: http://sourceforge.net/projects/latex2wp/ which might be quite helpful for this task. Best, Bjoern -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2014 01:16 PM, Bjoern Michaelsen wrote: FWIW, there is: http://sourceforge.net/projects/latex2wp/ which might be quite helpful for this task. Thanks for the hint; but we still need to define if we will use a blog or the Wiki. I don't like the Wordpress idea: more difficult to make LOWN a community project, and to see the commits made to the article. AFAIK LibreOffice infrastructure doesn't have a Wordpress instance. I found a latex to wiki converter: pandoc. It is actually a swiss-army knife according to the description[1]. [1] http://johnmacfarlane.net/pandoc/ - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJToXxuAAoJEA595SwE1xaDI8sP+wUj9pP3pzFQnj34PceYVi7M iew2AS8BKn0FYLkXQeeyjgvq4Ofxi+0M1KHeyjbQgtzxRQz8NaWWoodVprPXPc9j 71bZWVfvDtvElt3r9B2YfNrsLbzqJ6kEF8ONXXAAmUyzJ8Ah1PE24eybVIO9vHRK HhUlp81zKoPkwoDLc05DiG1jhnR6xxNaT+u3UWNJVTEt8odACA70VzpndRIOVUth 9c5KjsOmTpZR2z8rANDtZbUGQcFFTHm+wRKwr2rh3JgUXeWfFKZkTaJyjCwzr8+K kxb/8UtlgLjpEuFKZZl5iZwLgc1kpAFe19MN792Ibpa2OwjJse1zzj3GxybvK8qz 7s/uJR4H+YrMhcgjDKmA1xLPdrs3Vh+W+HW9JqWQ+qAJfS/WUvoomLnax5DYxWnM 67pthlq/7Z7rAO5mYO9PdFNgN8sbivOjDjefpxMm9rpwmDnmVEoLwNMkCzUgdGAf QfkbKuBcHv7LIg90HpIehual5IJa/NoziJcZ6yPdRRJSew1rdAjECIMLxOjY1FNm GiAwixhRgiyeNwKsmaQ9MxzlyYOPgq+uF0UoVB2ltyswYr0n8zMSDNl9VB6+I0KY UEwjNZeb+JXCBD2zG+0tPEa48iwG0+dkIZg/VtuWT82h5IXbR24KmNMIGNdp14N8 QQNlYLtFaW6L4OaogP+x =uEgR -END PGP SIGNATURE- -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
Hello William, Sorry for not having come back to you sooner. My comments inline... Le 18.06.2014 13:47, William Gathoye a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2014 01:16 PM, Bjoern Michaelsen wrote: FWIW, there is: http://sourceforge.net/projects/latex2wp/ which might be quite helpful for this task. Thanks for the hint; but we still need to define if we will use a blog or the Wiki. I will open an issue on RedMine soon but let's discuss here what it is that we want in terms of needs. What I see (feel free to add to it, of course!): * one actual newsletter sent to specific lists on the projects (projects@ marketing@ + dev@): this is the standard, text only newsletter. * another one -same content, different looks- that's published for the outside world to see. No one will look for it on the wiki so we need a blog platform, a webpage on the site, or something visually pleasing and easily searchable and retrievable, like www.libreoffice.org/newsletter or somesuch. * one platform that's in the form of lxer; somewhat more technical than the newsletter and slightly more focused. To me this last need is perhaps more important than the two others as it encompasses them, but it is also the more demanding in terms of resources and skills. The audience is really the community of LibreOffice and more specifically people who contribute to the project. Meaning, people who will find the content to be either downright informative (I just didn't know that but now it makes sense) or at least providing helpful background (beta 1 comes in two weeks, where do we stand with regard to our localization project?) I don't like the Wordpress idea: more difficult to make LOWN a community project, and to see the commits made to the article. AFAIK LibreOffice infrastructure doesn't have a Wordpress instance. I found a latex to wiki converter: pandoc. It is actually a swiss-army knife according to the description[1]. Once I've written my comments above I realize that you focused more on the content production. :-) I believe we should make it easy for people to contribute content, therefore latex, vim, emacs (I use emacs) are effective tools but keep in mind only a short portion of us here use them. My guess would be to use a dedicated space on the wiki for content production. It is collaborative enough and can be reused in different formats (webpage, newsletter, feeds, etc.) What do you think? Best, Charles. [1] http://johnmacfarlane.net/pandoc/ - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJToXxuAAoJEA595SwE1xaDI8sP+wUj9pP3pzFQnj34PceYVi7M iew2AS8BKn0FYLkXQeeyjgvq4Ofxi+0M1KHeyjbQgtzxRQz8NaWWoodVprPXPc9j 71bZWVfvDtvElt3r9B2YfNrsLbzqJ6kEF8ONXXAAmUyzJ8Ah1PE24eybVIO9vHRK HhUlp81zKoPkwoDLc05DiG1jhnR6xxNaT+u3UWNJVTEt8odACA70VzpndRIOVUth 9c5KjsOmTpZR2z8rANDtZbUGQcFFTHm+wRKwr2rh3JgUXeWfFKZkTaJyjCwzr8+K kxb/8UtlgLjpEuFKZZl5iZwLgc1kpAFe19MN792Ibpa2OwjJse1zzj3GxybvK8qz 7s/uJR4H+YrMhcgjDKmA1xLPdrs3Vh+W+HW9JqWQ+qAJfS/WUvoomLnax5DYxWnM 67pthlq/7Z7rAO5mYO9PdFNgN8sbivOjDjefpxMm9rpwmDnmVEoLwNMkCzUgdGAf QfkbKuBcHv7LIg90HpIehual5IJa/NoziJcZ6yPdRRJSew1rdAjECIMLxOjY1FNm GiAwixhRgiyeNwKsmaQ9MxzlyYOPgq+uF0UoVB2ltyswYr0n8zMSDNl9VB6+I0KY UEwjNZeb+JXCBD2zG+0tPEa48iwG0+dkIZg/VtuWT82h5IXbR24KmNMIGNdp14N8 QQNlYLtFaW6L4OaogP+x =uEgR -END PGP SIGNATURE- -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2014 02:05 PM, Charles-H. Schulz wrote: My guess would be to use a dedicated space on the wiki for content production. It is collaborative enough and can be reused in different formats (webpage, newsletter, feeds, etc.) Ok for the wiki. Regarding the reference extension we talked about[1]. It is available with the Cite extension which is ALREADY installed on our Wiki instance[2]. ;-) Thanks Sophi for the hint. On my side, I would still be able to use LaTeX since I've found an extension to convert LaTeX to MediaWiki syntax: pandoc[3] or another I still need to test which consists of using Vim directly from the Wiki [4];-) Regarding the 3 different interfaces, I'm not an expert regarding CMS. (Didn't know what lxer was about, now I know ;-) ) But Pandoc could still come in handy this time, use whatever CMS you want and we will still be able to convert the syntax. Let's reuse the existent, no need to create a WordPress instance if the TDF hasn't one already; is Plone not able to handle such a use case? Or maybe, we could reuse the TDF blog [5]? [1] https://www.mediawiki.org/wiki/Extension:Cite/Cite.php#.3Creferences_.2F.3E [2] https://wiki.documentfoundation.org/Special:Version [3] http://johnmacfarlane.net/pandoc/ [4] https://en.wikipedia.org/wiki/Wikipedia:Text_editor_support#Using_Vim_or_another_console_editor [5] http://blog.documentfoundation.org/ - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJToYSEAAoJEA595SwE1xaDc2YQAOZ4pYZnmdZ8AZIYwmTwWtwi mSpBvebKbeNjQrDPhZLk4dadQwTmBSvSRY9IPbdHtwpBHU/FRjtwI0oOxjL1Xh0H EbRH7th9VBhyyLOfH5XLSxEd9vl9qGj6W4DVtfIAZz+lgj9SPplOc2R6cKIBlL/e sy1B9XbfZzOQfSwGYv1AioXiaZeGTg8KWjuuqiKvGNcFb22XF1aSC0dfCTwlP7Jz +joqa0z/w168pkaAWkbLDFse7Qcgn+ptMWURPgek52nRNpcuGtz2VHKPkTY+zCy7 23OF1rZWfIik6elLU1I/n/29SmGsBBEYFxbleGmKVlcQjtCkntSrA9T98kVxKeRi 5ouvRQjxq+CeZkrfz8HqQUY2+LhJWYN0epuyBmhWlLGEvQDl10hQHNmfskTn5/w3 m9aaro+I56wZ3Mbx+oVl8t9P1XSkNk0FrPkzzuV+WiCQ26H5GXVALd9k8yXiZWDb h9Bun/Pzhh8wgDw43A4tW6rjbKSYVrg7D+fFWupp/ABs4L45AKY+Y4webju9aodi /h3e+D9SsGw92x5QFHGi9x6RPkr/bDDC1Vm5Zcn1m3yHoBxLuqOMyoqPE/+DeKP+ 6A0cP7ISX4N/RHWngmh1fkWwSxMi4OXkKZjauTbxzbVXeoeLcWTDa40nrRtvy65V yjDgt7zTzxEPMMc4ehK0 =6TJo -END PGP SIGNATURE- -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
Le 18.06.2014 14:22, William Gathoye a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2014 02:05 PM, Charles-H. Schulz wrote: My guess would be to use a dedicated space on the wiki for content production. It is collaborative enough and can be reused in different formats (webpage, newsletter, feeds, etc.) Ok for the wiki. Regarding the reference extension we talked about[1]. It is available with the Cite extension which is ALREADY installed on our Wiki instance[2]. ;-) Thanks Sophi for the hint. On my side, I would still be able to use LaTeX since I've found an extension to convert LaTeX to MediaWiki syntax: pandoc[3] or another I still need to test which consists of using Vim directly from the Wiki [4];-) There's got to be the same for emacs to mediawiki somewhere. This being said, the sad part is that we do have an old OOo extension converting ODF documents to mediawiki, but it has not been maintained and is thus quite buggy. Regarding the 3 different interfaces, I'm not an expert regarding CMS. (Didn't know what lxer was about, now I know ;-) ) But Pandoc could still come in handy this time, use whatever CMS you want and we will still be able to convert the syntax. Let's reuse the existent, no need to create a WordPress instance if the TDF hasn't one already; is Plone not able to handle such a use case? Or maybe, we could reuse the TDF blog [5]? Well the TDF blog does use Wordpress, the website uses SilverStripe, the extensions site uses Plone, and we may end up with an OpenSuse like system for the planet, which, incidently might just be what we're looking for at least for the lxer style platform (https://redmine.documentfoundation.org/issues/400) This being said, there could be other options but we have to at least list our needs first. Cheers, Charles. [1] https://www.mediawiki.org/wiki/Extension:Cite/Cite.php#.3Creferences_.2F.3E [2] https://wiki.documentfoundation.org/Special:Version [3] http://johnmacfarlane.net/pandoc/ [4] https://en.wikipedia.org/wiki/Wikipedia:Text_editor_support#Using_Vim_or_another_console_editor [5] http://blog.documentfoundation.org/ - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJToYSEAAoJEA595SwE1xaDc2YQAOZ4pYZnmdZ8AZIYwmTwWtwi mSpBvebKbeNjQrDPhZLk4dadQwTmBSvSRY9IPbdHtwpBHU/FRjtwI0oOxjL1Xh0H EbRH7th9VBhyyLOfH5XLSxEd9vl9qGj6W4DVtfIAZz+lgj9SPplOc2R6cKIBlL/e sy1B9XbfZzOQfSwGYv1AioXiaZeGTg8KWjuuqiKvGNcFb22XF1aSC0dfCTwlP7Jz +joqa0z/w168pkaAWkbLDFse7Qcgn+ptMWURPgek52nRNpcuGtz2VHKPkTY+zCy7 23OF1rZWfIik6elLU1I/n/29SmGsBBEYFxbleGmKVlcQjtCkntSrA9T98kVxKeRi 5ouvRQjxq+CeZkrfz8HqQUY2+LhJWYN0epuyBmhWlLGEvQDl10hQHNmfskTn5/w3 m9aaro+I56wZ3Mbx+oVl8t9P1XSkNk0FrPkzzuV+WiCQ26H5GXVALd9k8yXiZWDb h9Bun/Pzhh8wgDw43A4tW6rjbKSYVrg7D+fFWupp/ABs4L45AKY+Y4webju9aodi /h3e+D9SsGw92x5QFHGi9x6RPkr/bDDC1Vm5Zcn1m3yHoBxLuqOMyoqPE/+DeKP+ 6A0cP7ISX4N/RHWngmh1fkWwSxMi4OXkKZjauTbxzbVXeoeLcWTDa40nrRtvy65V yjDgt7zTzxEPMMc4ehK0 =6TJo -END PGP SIGNATURE- -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2014 02:40 PM, Charles-H. Schulz wrote: Well the TDF blog does use Wordpress, the website uses SilverStripe, the extensions site uses Plone, and we may end up with an OpenSuse like system for the planet, which, incidently might just be what we're looking for at least for the lxer style platform (https://redmine.documentfoundation.org/issues/400) As I understand correctly, Planet is just a blog aggregator and cannot be used as a host for LOWN. This being said, there could be other options but we have to at least list our needs first. As you said, we have to provide 2 LOWN versions: a web one and a text based for the MLs. Let's thus define our needs by considering this situation: - - We use the wiki where we will put our full web version: allowing contribution from the whole community. My question: Where are we gonna upload the images/screenshots (if any article needs illustration?): on Owncloud or on the wiki itself? This could have issues for next steps. - - Use a cron to export the web version each week from the wiki to the TDF Wordpress. Do we need to use absolute links to the images (hosted on Owncloud or the wiki itself?) or do we need to reupload the images on the wordpress instance? Maybe I could have a look how to implement such a cron using PHP with MediaWiki [1] and WordPress [2]. - - Use a cron to extract the text version from the wiki and post it on the mailing list. [1] https://www.mediawiki.org/wiki/API:Main_page [2] http://codex.wordpress.org/XML-RPC_Support Regards, - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJToY+8AAoJEA595SwE1xaDl30QANczjuUf6N6DApMKrID6OjaM T3yCs0ozrI6EUjKN4Jtn+V0p/NGSD3fkHBB6gus9GRAZTN89Txmo7ENRT/Sm0xXu 59Ds/x21/vYULL7ALQVZ38ZLEh8IiwP+Tdsqy0LOOhGF/Me3Lm0VswLu0T9J2U8I c6lFNVExBtzDNe1iyIYlD3SX6sUAJPPwVn0uCTj9llz5ndA72BOSBw/bSpOJ5cBl sOdCH+VBDJDsdrgEjHUYCgxx4EkLJdpbElEL3qR0n7s328sSLkoMkaVCAcl3xptA pAmlKvttG5CiCVHiC/jHKl4BVbovxEFWWB5wDvXg5LTEdPwFCuAdQ9HU4PjGsKLX Hv0ydMz8tCAPwek0xjpKqv+ZBIEUfgFZ8n4slpRdZNM9GTWATu/Itaqe5HJ5c/eH snMDQjDs4D+vVwYenuzw2lqZ02HB4J+JtRr1NEvqM3demVQ9MLeqJrmSlcSWFu1n aZLbfAR9Wv6UzJ08KFWHCa4zFZVQTF8R1PxUAElvZQFhn0xSukmDhVnA+oUAQWaz EMyGxcJsIEoWnfp1tAjx+h+ejVcCTm1YfOzGf87q9+ZezQrlWbxYdxUG/C9flZBh w1cMBBnA3bO9bZ2x8dpZaV874s3dwXgAkoMryvYav/+HxfGQb2fTmQRGuBcW7fNB yxYMsjnx8lINIOwJwaOD =e28m -END PGP SIGNATURE- -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
Le 18.06.2014 15:10, William Gathoye a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 06/18/2014 02:40 PM, Charles-H. Schulz wrote: Well the TDF blog does use Wordpress, the website uses SilverStripe, the extensions site uses Plone, and we may end up with an OpenSuse like system for the planet, which, incidently might just be what we're looking for at least for the lxer style platform (https://redmine.documentfoundation.org/issues/400) As I understand correctly, Planet is just a blog aggregator and cannot be used as a host for LOWN. Yes indeed. I'm just wondering whether we could tweak this a bit with successive posts and links on separate topics. Tagging and separate topics might just fit within such a platform. This being said, there could be other options but we have to at least list our needs first. As you said, we have to provide 2 LOWN versions: a web one and a text based for the MLs. Let's thus define our needs by considering this situation: - - We use the wiki where we will put our full web version: allowing contribution from the whole community. +1 My question: Where are we gonna upload the images/screenshots (if any article needs illustration?): on Owncloud or on the wiki itself? This could have issues for next steps. We keep this easy I think; Wordpress if we use wordpress, another backend if we use another. Note that I'm unsure whether Wordpress is the best solution here. I don't have something specific in mind, so feel free to suggest something else. - - Use a cron to export the web version each week from the wiki to the TDF Wordpress. hold on there, I only trust a wordpress post once I've taken a look at the post about to be published and how it fits visually within the page, so no cron job for me :-) Do we need to use absolute links to the images (hosted on Owncloud or the wiki itself?) or do we need to reupload the images on the wordpress instance? see my answer above. Maybe I could have a look how to implement such a cron using PHP with MediaWiki [1] and WordPress [2]. - - Use a cron to extract the text version from the wiki and post it on the mailing list. yes the cron job here would indeed be very useful. Thanks! Charles. [1] https://www.mediawiki.org/wiki/API:Main_page [2] http://codex.wordpress.org/XML-RPC_Support Regards, - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJToY+8AAoJEA595SwE1xaDl30QANczjuUf6N6DApMKrID6OjaM T3yCs0ozrI6EUjKN4Jtn+V0p/NGSD3fkHBB6gus9GRAZTN89Txmo7ENRT/Sm0xXu 59Ds/x21/vYULL7ALQVZ38ZLEh8IiwP+Tdsqy0LOOhGF/Me3Lm0VswLu0T9J2U8I c6lFNVExBtzDNe1iyIYlD3SX6sUAJPPwVn0uCTj9llz5ndA72BOSBw/bSpOJ5cBl sOdCH+VBDJDsdrgEjHUYCgxx4EkLJdpbElEL3qR0n7s328sSLkoMkaVCAcl3xptA pAmlKvttG5CiCVHiC/jHKl4BVbovxEFWWB5wDvXg5LTEdPwFCuAdQ9HU4PjGsKLX Hv0ydMz8tCAPwek0xjpKqv+ZBIEUfgFZ8n4slpRdZNM9GTWATu/Itaqe5HJ5c/eH snMDQjDs4D+vVwYenuzw2lqZ02HB4J+JtRr1NEvqM3demVQ9MLeqJrmSlcSWFu1n aZLbfAR9Wv6UzJ08KFWHCa4zFZVQTF8R1PxUAElvZQFhn0xSukmDhVnA+oUAQWaz EMyGxcJsIEoWnfp1tAjx+h+ejVcCTm1YfOzGf87q9+ZezQrlWbxYdxUG/C9flZBh w1cMBBnA3bO9bZ2x8dpZaV874s3dwXgAkoMryvYav/+HxfGQb2fTmQRGuBcW7fNB yxYMsjnx8lINIOwJwaOD =e28m -END PGP SIGNATURE- -- To unsubscribe e-mail to: marketing+unsubscr...@global.libreoffice.org Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/ Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/marketing/ All messages sent to this list will be publicly archived and cannot be deleted
Re: [libreoffice-marketing] Re: LibreOffice weekly newsletter
Hello William, Le 15.06.2014 18:50, William Gathoye a écrit : -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Charles, * First, thanks you all for your feedback, I'm really pleased ;-) On 06/14/2014 09:43 AM, Charles-H. Schulz wrote: - could you describe how you select content? Actually, as I'm subscribed to all ML lists, I take the time to read all what I find interesting on ML and Bugzilla. The subjects I find interesting are: - - the rather long threads on ML: having a brief summary of the current situation of the discussion is always great; - - the most recurrent subjects; - - subject difficult to understand; - - controversial topics; - - first contributions; - - progress on the hackfest organization. nice, I like your approach! - you can make it attractive if we give you a few logos, but surely you need acccess to our wiki or some sort of official blog for this... interested? I want to keep the document as clean as possible, and will include only additional content needed for the comprehension of the article like X/Y graphics, modified feature in the GUI, etc. So I'm thinking about putting this newsletter online, meaning, on a wiki or on a blog post; then ensuring it can be spread via mailing list (text only) so we'll have to work on the style itself, although most of it can be improved by the choice of the right online platform. A text only solution is not only useful but can co-exist; it's all about refactoring the message. Publishing a PDF document via Twitter wasn't clearly the ideal format to use. Making LOWN official would be nice, indeed. I think we should do this, probably by adding a bit more content though. See below. Sorry for having used LaTeX, I know from a marketing POV it isn't great. But what I wanted was: - - be allowed to use Vim: I don't like to use a GUI for writing: it is distracting and hurting my eyes. - - have an auto-citation system; - - see the changes made between 2 commits. What the hell are you doing contributing to Libreoffice then? :p LaTeX and Github were answering these problem quite nicely. As Git is used more effectively on text-based files, I needed a text based tool like markdown or LaTeX. I dropped markdown since it has not citation system. The remaining defacto solution was the LaTeX. More seriously: use whatever tool you like, just don't think of it as a document but as a webpage. Better use txt + html. Again,, we want to have this online, not as a document or just as a text. - again, thank you for all this I like the breadth and quality of content. Let's make this a collaborative effort. For sure. But the initial idea was to keep it oriented to developers as much possible. Although I'm not against to broaden the audience. If you have interesting content I'm not aware of, you can let me know and I will gonna integrate it. At first, I thought that - - using pull requests on Github - - and sending content via email for those who don't use Github would be a great idea. After a discussion on #libreoffice-fr, I realised that a Wiki page for each LOWN is a great solution. yup; perhaps even an official blog platform. What do you think? I can still use Vim if I copy paste the changes to the wiki, the commit are saved and we have block references with [1]. Are you confident in that extension? - we can see how best to circulate this newsletter and make not just a tool for the outside, but a means of information for the entire project. At this stage, we should improve it on two levels then imho: -formatting/style/web page - adding more non-developers topic: native-lang communities, localization work matters a lot and I expect this newsletter to be read by them as one of our major audiences. Best, Charles. On 06/14/2014 02:21 PM, Charles-H. Schulz wrote: For some reason, the given link will not lead me to any webpage in my browser :-( Is anybody else experiencing problems to make it work??? Maybe Will has deleted the pdf? Nope, the link is till valid and always will be. It's a link to the document hosted on my Github which is a pdf. I tested on IE, FF and Chrom(e/ium) and the link is working fine. BUT according to the tests I made with curl -IL, the pdf is detected as binary -- can cause problem on some platforms. Cannot fix this, the mimetype error comes from Github. [1] https://www.mediawiki.org/wiki/Extension:Cite/Cite.php#.3Creferences_.2F.3E - -- William Gathoye will...@gathoye.be -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQIcBAEBAgAGBQJTnc7DAAoJEA595SwE1xaDx+oQAJ35uWtQmKgTfotc47VF++z4 EKvTjv6tonCb5MOidIU/aMidvsmwE5pH4/0eXvkHhq23Ev3XN3y537UlPvBwLwRo ad9jKbbVc1omN3PKOGueyDTNwPpIq/LW9gYN2ru00tDpSvI5aEYWAGJHe4gpOj6b 6nsJL0Z9oAZLYBAqs24XvW6wNbxoiqQzkcaL1mwaWx/7REbZGvYGdyGwNlaxXCiC whrLbUWZHcBKqAFsZU6j5XgbjgThvfMfQNi2EZL5xSr3F8Vo7HdnuiJUX4mVd37w VDWZxi3G9uqIoV0bFweFpxP6CcDqf55xOXtxh15HOY3PaynUL6RAJH4Xq5HqBqnW
