On Tue, Mar 12, 2019 at 12:42:36AM +0100, Mihaela wrote:

   The "Big Ideas" sound like a good candidate for the Epic feature in
   GitLab, although you need to upgrade to use it (maybe GitLab could
   sponsor Inkscape in this way? Any other useful GitLab features that
   aren't free?)

We thought about that, although I figure if we keep to a high level of
granularity we can probably just use a plain single kanban board.  If it
turns out everyone really likes kanban and we want to use it heavier, we
could consider using gitlab epics, or perhaps one of the many other
kanban services out there.

But what we need to decide right now is what to call it.  We didn't have
any solid thoughts, but a few ideas are:  "Big ideas", "Blueprints",
"Features", ...  Do you have any good ideas?

As you mention "blueprints" and "features": How do we prevent this from becoming one of the following?

• Launchpad Blueprints, where a huge amount of unsorted ideas ended up, that nobody ever looked at.
• Launchpad "Wishlist" bugs, which were a vast amount of mostly unactionable ideas of varying usefulness which were often not more than a nice way of "closing" a report.

Also you're asking for names already - but I think nobody except for the hackfest attendees knows what this feature is actually about and how it's supposed to work in the end. Are you planning a more detailed write-up on this?
From the things I read between the lines I especially wonder: How are "ideas" selected? How does it differ from discussions we're having in inbox already? What issues is it trying to solve in the first place (i.e. why do we even need a new place)? And related to the above: What do you want to do differently compared to previous models that will make it more likely it'll work this time?

The same goes for the "Forecast" btw, which could use some explaining, too, unless you want to explain it by doing "it" (whatever "it" might be...)

Cheers
Patrick