Talk:Wishlist

From VFXPedia

I think it is a great idea to make the Wish List centralised and public. Now it would be good to have the facility to make the wishes categorized or otherwise grouped by theme. It would be also good to be able to begin a separate discussion per wish. Finally, some kind of voting facility would make it possible to (more or less crudely) gauge the interest of Vfxpedia readers. Maya used to have a site where each logged-in user had a limited number of “approval points” to distribute between the wishes she wanted to support…

--Cvisco : Categorizing is easy...I just added a few basic headings to group the current requests under. As far as a separate discussion for each wish, I suppose each wish could have it's own PAGE linked from the wishlist page...where in it could be described in detail, images could be added and full discussion could take place. Voting system would be great, just not sure how you'd do that on a wiki.

Could be there a "General" category for stuffs like ROI (or DOD) or jittered motion blur (my favorite wish) and other main things? --Ata

--Cvisco : It's a wiki, remember. If your item doesn't fit under an existing category, just make a new one yourself.

--Ata : Just wanted to discuss it ;)

--Gringo : We could vote for features just adding our nicks and grades after a proposition. Grades could be from -100% (if You don't want a feature) to 100% (if You think it's great)

--Chad 10:26, 23 January 2007 (Central Standard Time) Should we be leaving signatures for wishes?

--Ata : It won't be a bed idea!

Ugg. This list is getting out of hand... Pretty soon someone will add "Make it 2x better!". How should we manage this? --Chad

--Cvisco : Not sure that you can manage it without making it very UN-Wiki-like. Maybe eyeon sets it up so that requests have to be formalized and agreed upon on a separate page before making it to the master list? Maybe its up to peers to remove those that don't fit or are never sufficiently thought out or explained. Personally I think each request should have it's own Wiki page linked off the main list where it can be laid out in detail. This might naturally discourage the short, ambiguous or nonsensical postings.

--Daniel Sounds like a good idea to me. I'd encourage this for anything that's gets a few comments at least. However, it's difficult to force people to explain everything in detail, and not all requests require detailed screenshots etc, so it'll probably be left up to people to expand their own contributions.

--Chad Hmmm... Two wishlists... One that is a draft list where users add ideas and comment on them, and one that is a master list. Agreed upon items or well explained items could be moved by admin to the master list. The master list one would be read only to the rest of the users, but each wishlist item could get its own discussion page where the original comments from the draft page would be copied, and we could expound upon the wish, add use cases, link to examples, etc. Maybe we could even have a poll on those?

--Cvisco Polling would be great actually. That is, if it's possible (and reliable) enough to do in a wiki. Having the public wishlist is great, but if people see their request already posted they will perhaps be unlikely to "email" the same or similar request to eyeon. At the moment the only way requests can truly be measured in terms of popularity is via that email influx I would imagine.

--Daniel I'll go through this page in a week or so to try and tidy it up a bit. Requests that we just don't understand will simply be removed (feel free to re-add them with more detail, if important). I may also make some attempt to flag or separate out likely or near-future requests from unlikely/long way off, to give a bit of feedback (note that some minor items on this page have already been implemented for the next release).

--Hevonen This list is getting long. I propose slicing sections to individual subpages and somehow organizing contents to subcategories soon. For example: new page for tool requests with sections for 3d tools, particle tools and other tools. Each wish could be organized by perceived importance, like "critical", "medium" and "nice to have", and by amount of work, like "hard", "medium" and "simple". Some voting about wishlist items should be organized on Eyeon website or some forum, maybe flying pigs, though the latter's scope might be limited.

--Is the Table of Contents needed on the main Wishlist page now? This page is in fact a table of contents itself. --Gringo

What do you think about creating a new section: "Already Implemented Wishes"? --Gringo

-I don't understand, how would this be different than the "Completed Request" sections? --Chad

-It had been an old message before the section was created. --Gringo

--Chad: What would you guys think about moving some of the existing-tool-specific wishes into the discussion section of that tool in the manual? Like I want to add a wish "Add pivot to UVMap3D transform" but that's so UVMap3D specific, it seems silly to bury it in a huge list of more generic wishes.

--Stuart I'm not a huge fan of that idea. From our point of view, if we need to go through the current list of wishes, it's much easier if they're in one list. If it's spread across lots of separate tool specific pages, it's more likely to go un-noticed, or be forgotten about.

--Tilt I also think that the discussion pages would be too hidden (general problem of the mediawiki theme).

--Chad: Maybe it would be better to do it the other way? Like group the UVMap3D wishes together on the wishlist page and add a link to it from the UVMap3D manual page.

--Stuart We already have a random selection of wishes that have links to threads on pigsfly, that contain images and so forth, that require an account and logging in to view - very annoying! One hopes that those threads never go away or become inaccessible.