KGSWishlist 2/ Discussion
KGSWishlist2 Temporary Page
In order to have the wishlist available while being restructured, this temporary page is created. As soon as it turns out to work ok, it's content can be moved to KGSWishlist. If you're interested in details about the change or would like to contribute, see KGSWishlist/ Discussion1 and KGSWishlist/discussion2. - rubilia
(Sebastian:) I think this is fine, and we can replace it as it is. My only trouble is that I assumed we would just rename the pages all at once - this would have taken care of all links from other pages. Did you also perform some changes in the pages themselves that you would want to preserve or would it still be OK with you to do it through a PageNameChangeRequest and just add that the existing "KGS Wishlist - *" pages should be replaced?
rubilia:
- I don't quite like to ship it right away. It's not better than the old one, yet. The introductional text wording will need quite a bit of attention to ensure a good start at once.
- If mere renaming was possible here, I'd have preferred it, of course. However, all but two new pages are just a part of a former one, you know?
- No, I didn't touch any content and won't do that today, either, because I think it's better to have the awaiting edits separated in the versions history.
- I guess both of us will not be able to conduct all the transformation to concise lists by ourselves. The most important issue to care about is probably the introducing standard appeal at top of each section. It should give a clear line so that other people who might help to transform the discussions into (ordered?) lists are enabled to work coherently.
- Fuchsnoir: Would it be possible to distinguish between a wish and the subsequent arguments? The way it seems to be done now, with both being list items, makes it difficult, for me, to visually scan for the next wish. Maybe list items for wishes and comment signs for comments? Or headings for wishes and lists for the discussion?
- rubilia: Distinguishing wishes from further discussions, comments, workarounds etc. is exactly what the planned restructuring aims at. The "how to" is not quite clear yet, though.
- Fuchsnoir: Ok. My impression (From not looking too closely, sorry), was that the restructuring was working on the content of subpages, not the presentation of that content within a certain subpage. I'll just be quiet then, ok?
Introduction Wordings
To be supplemented. I'd suggest, let's collect ideas for a few days, before putting the texts together. - rubilia
(italcized: proposed wordings; normal font: thoughts)
Main Entry Page
- rubilia: The main introduction supposedly should enable a better balance between encouraging to contribute and emphasizing the necessity of counterchecks, like: "Check thoroughly if the feature isn't already there. If you miss something rather obviously needed, better ask people at KGS first instead of adding a wish here."
- rubilia: The whole introduction mainly looks too talkative to me. I figure, an average KGS wishlist user is hardly aware of what is written there, because s/he doesn't bother to get through.
- (Sebastian:) Agree, some of it could be more terse. But in general, I think it's not so hard to read, because people can easily skip to the headline that suits them. And the information should be written somewhere. Except, of course, if we discontinue using the referred pages, or sort them into our structure. In addition to, as discused above, getting rid of the need to link to current and future plans, we could also give up pointing people explicitly to KGSFirstTimeUserExperience - in almost a year we had not a single first user write something there. This could become just another "KGS Issues" page and be linked from the wishlists it touches.
- rubilia: "See KGSPlans for what wms plans to add in the future. Adding a wish to KGSWishlist won't help anything if it's already about to get realized."
- (Sebastian:) We should not put the onus on every user to search through yet another list - it's simply not going to happen, that's just the way people are, and we can't force them. We have two realistic options: Either wms agrees to make a comment in the Wishlist when he decides to grant a wish (and delete it iff he implemented it) or some dedicated deshis look for wms's changes in KGS Status and do that work.
Section Pages
- rubilia: To the same degree as a wish stands for a bunch of proposals, reasonings and so on, rather than for just one person's idea, it should be treated as "depersonalized". Rewording a wish initially contributed by another person shouldn't be tabu.