Date: prev next · Thread: first prev next last
2014 Archives by date, by thread · List index


Hi,

just briefly on two topics, as I'm rather swamped these days:

I'm glad the projects use Redmine and find it useful, that's great! What we should take care of is that everything that is product related should _not_ go into Redmine. For the design team, without knowing the concrete workflow, as an example: Iterations of designs can be handled in Redmine, but the issue to change icons in LibO should be in Bugzilla then.

Charles-H. Schulz wrote on 2014-09-17 at 16:47:

The suggestion for the experiment is to stop using the public marketing
list completely for one month, and to rely on the Issue tracker of
RedMine meanwhile. The main idea here is to move our activities entirely

I personally strongly suggest no _not_ close the mailing list or temporarily avoid using it. At least some pointers on the mailing lists are desired.

new wiki. I'm not suggesting that we open twenty new wiki pages on
RedMine tomorrow, but that we use it for a month if we need it.

I propose to, for wiki pages, stick with Mediawiki, so we have one tool for the task. :)

Florian

--
To unsubscribe e-mail to: marketing+unsubscribe@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

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.