4
$\begingroup$

As UI/design inconstancies are not considered bugs (rightly so), they are off topic on the bug tracker.

Is there a place where these sorts of things can be reported and discussed? Or a place to write issues/ideas where the new UI team will read them?

$\endgroup$
  • $\begingroup$ I believe this wiki page was created for that purpose. $\endgroup$ – sambler Feb 6 '14 at 9:33
2
$\begingroup$

If you have a full proposal (detailed design docs), it should be ok to open a task on http://developer.blender.org/ and discuss there (staff only!)

You can discuss with the community at http://blenderartists.org/ to generate ideas, exchange mockups and find to a practical proposal. Then it's time to write it down on a wiki page for example.

Implement the ideas or find someone who does, then submit something working (a patch/diff) to the tracker. If there's no one to actually code it, it will likely be considered a feature request and not gain much attention there are just too many and not everyone will agree on a certain solution...

$\endgroup$
  • 3
    $\begingroup$ Only team members are suppose to create tasks. This is to avoid an influx of tasks and such. Instead the WIKI should be used to create a proposal. Then attention can be brought to the proposal via IRC, the BF-UI mailing list, or feel free to tweet me directly @carter2422 $\endgroup$ – Jonathan Williamson Feb 6 '14 at 19:50
  • 1
    $\begingroup$ Updated answer, left "open a task" part in with a giant strikethrough line, to make things clear :) Thank you for your additions about the communication channels, upvoted! $\endgroup$ – CoDEmanX Feb 6 '14 at 20:29
  • $\begingroup$ The question was about inconsistency, not UI design proposal. I understand UI proposal should not be made by everyone to prevent influx, but inconsistencies are not subjective that much. Adding a new type 'inconsistency' in the bugtracker, would greatly help improve the UI. Team members are experienced users and experienced users don't see inconsistencies anymore. $\endgroup$ – matali Feb 7 '14 at 10:33
  • $\begingroup$ Well, I guess there are two types of inconsistencies: a) slips of the pen (or rather coding fingers), where there's no doubt how to correct it (like misspellings). b) Inconsistencies by design, something not nice but unavoidable unless the groundlaying design is changed. I had the latter on mind, and these really need proper proposals how to solve the problem, not only a bug report saying it exists and that it shouldn't be like that. $\endgroup$ – CoDEmanX Feb 7 '14 at 13:02

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.