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


On Thu, Sep 27, 2012 at 04:37:43PM +0100, Michael Meeks wrote:
AI:   + create a new wiki page, based on GSOC page,
        present as the next-step on the Easy Hacks page (Michael)
              + AmbitiousHacks.
So a few additional thoughts on that:
- having all the stuff in one database (bugzilla) IMHO still makes sense, OTOH
  bugs will clutter with comment noise for larger features
- a three sentence abstract in bugzilla bug ending with "details and discussion
  here: WIKILINK" could still make sense though: it keeps the thing
  discoverable and queriable (esp. for the folks who are already moving around
  on the EasyHacks)
  Yes, that likely means introducing a AmbitiousHacks whiteboard status -- for:
   http://wiki.documentfoundation.org/Development/Easy_Hacks_by_Difficulty
  thats quick and easy, for:
   http://wiki.documentfoundation.org/Development/Easy_Hacks_by_required_Skill
   http://wiki.documentfoundation.org/Development/Easy_Hacks_by_Topic
  it is a bit more work, but OTOH maybe not that urgent ...
- if the scale is ~three month for such an AmbitiousHack, there will be a lot
  of back and forth once work on it is started. IMHO such AmbitiousHacks should
  by that time move to a wikipage on its own, not one shared with other
  AmbitiousHacks -- otherwise things will get messy.

Best,

Bjoern

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.