ninetydegrees: Drawing: a girl's face, with a yellow and green stripe over one eye (Default)
[personal profile] ninetydegrees

Title:
Admin posts: connect 'as admin' post with 'admin' icon keyword

Area:
icons, communities, entries, comments

Summary:
If one has an icon with the 'admin' or '_admin' keyword automatically select it when making a post or a comment as an admin (I meant when you tick the 'as admin' checkbox).

Edit: looks like _admin or something even more unusual would be better as there would be a good chance *only* users who wanna have this would.

Description:
Not sure automatic selection is possible in which case it could be automatically use (so you wouldn't even have to select an icon the way it works at support). The latter could be problematic if you wanted to use a different icon for once.

Poll #15508 Admin posts: connect 'as admin' post with 'admin' icon keyword
Open to: Registered Users, detailed results viewable to: All, participants: 35


This suggestion:

View Answers

Should be implemented as-is.
9 (25.7%)

Should be implemented with changes. (please comment)
1 (2.9%)

Shouldn't be implemented.
2 (5.7%)

(I have no opinion)
22 (62.9%)

(Other: please comment)
1 (2.9%)

wordbird: (Default)
[personal profile] wordbird

Title:
For multiple admins in a Community

Area:
Communities

Summary:
More editing options on posts in a community not made by the admin wanting to edit it.

Description:
In a community I am an admin for, there are several admins, and all take turns making new posts when previous posts max out on comments. Sometimes comments get out of hand and the post needs to have its comments frozen for an hour or two. Dreamwidth fluctuates between whether or not it allows an admin who did not pen the post to freeze the comments of that post, requiring the admin who penned the post to be online, which is inconvenient, especially if they are an admin less often around. I suggest that anyone who is at Admin level in a community be allowed to edit the comment options(including disabling them) in any post in the community. It would make moderating much easier.

Poll #14593 For multiple admins in a Community
Open to: Registered Users, detailed results viewable to: All, participants: 36


This suggestion:

View Answers

Should be implemented as-is.
25 (69.4%)

Should be implemented with changes. (please comment)
3 (8.3%)

Shouldn't be implemented.
1 (2.8%)

(I have no opinion)
6 (16.7%)

(Other: please comment)
1 (2.8%)

stormy: βͺ ππŽπ“πˆπ‚π„ ❫ 𝑫𝑢 𝑡𝑢𝑻 𝑻𝑨𝑲𝑬 𝑴𝒀 𝑰π‘ͺ𝑢𝑡𝑺 ⊘ (Default)
[personal profile] stormy

Title:
[css] Add admin-post css to entry-wrappers.

Area:
styles, entries

Summary:
When you mark a comment as an official admin/mod hat comment, it applies the admin-post class to the comment's comment-wrapper, but the same does not happen when you mark an entry as official. The entry-wrapper does not gain a admin-post class. I suggest that it does so you can use css to format those posts separately from others.

Description:
When you mark a comment as an official admin/mod hat comment, it applies the admin-post class to the comment's comment-wrapper, but the same does not happen when you mark an entry as official. The entry-wrapper does not gain a admin-post class. I suggest that it does so you can use css to format those posts separately from others. Personally, I'd love to use this as a way to call more attention to those specific entries without having to use a .poster class and have everything marked by a specific user stand out.

An additional suggestion related to this: At current the class .admin-post gets added to comments when they are made official moderator comments. It might be easier to suggest this css is changed to .admin-comment if it is a comment and .admin-post if it is added to an entry. This isn't a necessary step because you could format with ( .entry-wrapper .admin-post AND .comment-wrapper .admin-post ) but it might just be cleaner for those who don't like listing multiple classes together to specify.

Poll #14085 [css] Add admin-post css to entry-wrappers.
Open to: Registered Users, detailed results viewable to: All, participants: 37


This suggestion:

View Answers

Should be implemented as-is.
24 (64.9%)

Should be implemented with changes. (please comment)
1 (2.7%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
12 (32.4%)

(Other: please comment)
0 (0.0%)

phidari: (Default)
[personal profile] phidari

Title:
Allow ticking of mod hat from quick reply

Area:
Replies

Summary:
Currently the "comment as admin" feature can only be activated from "more options". This is inconvenient!

Description:
I went to reply to a post in a community I maintain so I could try out the new "comment as admin" feature, but I couldn't find it anywhere. Just as I was about to give up, I clicked the "more options" button on a whim and there it was. As someone who almost never uses "more options", I would never have expected to find it there.

It would definitely be a lot more convenient to have the option available when quick-replying, too. As an example, I see a lot of blank space to the right of the Post Comment/Preview/More Options boxes; maybe it could go there, next to "check spelling"?

Poll #13977 Allow ticking of mod hat from quick reply
Open to: Registered Users, detailed results viewable to: All, participants: 49


This suggestion:

View Answers

Should be implemented as-is.
34 (69.4%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
2 (4.1%)

(I have no opinion)
13 (26.5%)

(Other: please comment)
0 (0.0%)

kaberett: Overlaid Mars & Venus symbols, with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett

Title:
Community sticky posts editable by all admins

Area:
page: entries, site: community features, workflow: community administration

Summary:
It would be helpful if community accounts could make sticky posts inside the community, then editable by everyone with admin rights within that community.

Description:
Communities already make use of sticky posts for a variety of reasons - e.g. dw_suggestions has one (made by denise) that acts as an introduction and usage guide to the comm.

I suggest that it would be helpful for communities to be able to contain sticky posts nominally made by the community account itself, giving all community admins editing rights over it. I imagine this working via the "post as: another user" module in the new update page.

Example use cases: in dw_dev_training, I envisage this being used as an up-to-date centralised record of current babydev bait; Momijizukamori has said they'd love something like this to link to resources, beyond the bare bones in dreamscape's community profile.

ISSUES that I can come up with:
- community accounts currently can't be associated with posts, as far as I know, so that would be an exciting thing to work with
- would probably want there to be one post permitted per community (so would need to work out how to limit this - wouldn't just want automatic overwrite of pre-existing posts!)


Alternative solutions/workarounds:

(1) Create a mutual admin account (as in use at <user name="poetree"> with the shared account <user name="poetree_admin">). Downsides: security hassle - DW tends to discourage sharing accounts, I think? Logging out/in/out/in hassle - this will presumably be removed as and when seamless account switching is implemented.

(2) Some styles permit insertion of custom text to be displayed in the sidebar. Standardisation of this feature across styles (complete with full mark-up!), including choice as to where to site the custom text within the layout, might be a suitable alternative that would be editable by all admins.

Poll #13974 Community sticky posts editable by all admins
Open to: Registered Users, detailed results viewable to: All, participants: 40


This suggestion:

View Answers

Should be implemented as-is.
15 (37.5%)

Should be implemented with changes. (please comment)
4 (10.0%)

Shouldn't be implemented.
4 (10.0%)

(I have no opinion)
14 (35.0%)

(Other: please comment)
3 (7.5%)

Freeze Tag

Sep. 2nd, 2012 01:07 pm
azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Freeze Tag

Area:
tags, community management

Summary:
Freeze any given entry's tags against change by non-owner/non-admin even when general tagging permissions say otherwise (with optional reason why). This might be most useful for community management, but could be useful for personal journals too.

Description:
This case came up in writing another suggestion. Sometimes the tags on a specific entry should not be modified. This might be because a community administrator has set the tags as they should be and no one should mess with them by accident, or perhaps because a situation has started to get out of hand in a particular entry, and the battle has progressed to the tags.

Ordinarily the community's tag permissions are as they ought to be, and it would unfairly penalize the community members to disallow them from their ordinary tagging behavior because of this one special (or egregious) case.

Ideally, the edit tags link should not even be shown on that entry for non-admins, but any attempt to edit the tags from someone who is not a community administrator should result in an error message saying that changing the tags on this entry is not permitted because a community admin set it that way, and optionally with a reason why.

Admins should be able to unfreeze the tags on the entry.

If an entry has frozen tags, should the admin be able to change them without first unfreezing them? On the one hand, an admin, like a honey badger, should be able to do what they want. On the other hand, perhaps the tags are frozen also against admin carelessness or so a different community administrator doesn't accidentally mess up something the first admin set up. I suppose a "The tags on this entry are frozen [because reasons]. Ticky this box if you want to change them, and also ticky that box if you want to leave them unfrozen" message would protect against accidental changing while allowing the admins to keep doing their thing without going too far out of their way.

I see this as mostly useful in communities, but don't see a reason to keep personal journals from using it.

Poll #11691 Freeze Tag
Open to: Registered Users, detailed results viewable to: All, participants: 54


This suggestion:

View Answers

Should be implemented as-is.
37 (68.5%)

Should be implemented with changes. (please comment)
2 (3.7%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
14 (25.9%)

(Other: please comment)
1 (1.9%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Special "admin/owner only" add/remove setting for certain tags or maybe overhaul tagging permissions

Area:
tags, permissions

Summary:
Allow journal owners or community administrators to designate tagging permissions by tag. Tags as they are actually used contain both general topic labels and other things that are suitable for use by a larger group, and administrative tags that ought only to be used by people with permission to act administratively.

Description:
Currently, tag permissions are:

Who may see the tag (determined by security level of the entries to which the tag is attached)
Who may add any existing tag to an entry
Who may remove a tag from an entry & who may create new tags to apply to an entry

Adding, removing, and creating tag permissions can be based on community membership or community adminship, or personal journal general access/access group membership.

This is useful as far as it goes. However, tags as they are actually used have developed some other interesting differences.

In some communities, there are often special tags that are reserved for marking administrative actions. Using dw_suggestions as an example, there are several. http://dw-suggestions.dreamwidth.org/tag/

"admin" and "admin: opinion post" are clearly administrative. All of the "bugzilla:" tags are also administrative, and are used one at a time by [staff profile] denise at various points in the suggestions process for very specific purposes. The rest of the tags are descriptive of the content of the suggestion, and can be usefully applied by any interested layperson with attention to detail.

Other communities do similar things with tags, and make things work by either restricting the application of tags to administrators, or trusting the sensibility and goodwill of the community to not apply tags that are clearly designated as administrative with reckless abandon.

To fit this need roughly and based on the use model I described above, tags could be divided into two baskets, one reserved for admins/journal owners, and one that uses the existing settings. However, that doesn't quite satisfy me.

What if it were possible to:

* Set default permissions for newly created tags (tags that already existed at the time of swapover would go with the current account settings for global tag permissions)
* (unchanged) Set permissions for who may create new tags
* Set permissions for who may apply this particular tag to any entry
* Set permissions for who may remove this particular tag from any entry

It should be possible to modify individual tag permissions either singly or in multiple selected groups, and should be possible to sort the tag listing based on permissions.

I defer to people with better UI experience than I have on how that should be accomplished, because it would add an extra layer of WTFery on top of an already complex interface.

When applying tags to an entry, a user should only have the tags that they are allowed to apply be in a list that can be selected from. This would add possibly significant processing overhead to every load of a tagging page, and could be a reason to restrict some of the fancy stuff to paid accounts/accounts that have under the legal limit of tags. (This would prevent me in particular from using this until I got my tags pared down, which I think is only fair.)

I can see arguments for and against displaying a second list of tags that exist and are visible to the current user, but cannot be applied by them.

For: they exist, it makes sense to show them so they know that the problem is not that the tag does not exist; the refrain of "Mods, can you [tag request]?" is familiar in communities with restricted tagging. Having the list on the page to modify an entry's tags saves a click.
Against: why show you something you can't use? Link the full tag list if need be.

The ability to specifically designate a tag as "can be applied by [more permissive group than community admins]" might also solve the problem where admins create tags but don't attach them to an entry, so the tags remain admin-viewable-only until they're used.

Poll #11690 Special "admin/owner only" add/remove setting for certain tags or maybe overhaul tagging permissions
Open to: Registered Users, detailed results viewable to: All, participants: 43


This suggestion:

View Answers

Should be implemented as-is.
23 (53.5%)

Should be implemented with changes. (please comment)
3 (7.0%)

Shouldn't be implemented.
4 (9.3%)

(I have no opinion)
13 (30.2%)

(Other: please comment)
0 (0.0%)

holyschist: Image of a medieval crocodile from Herodotus, eating a person, with the caption "om nom nom" (Default)
[personal profile] holyschist

Title:
Customizable welcome email when joining a community

Area:
communities

Summary:
Community administrators would be able to customize a "getting started" email with posting guidelines, useful links, tips for getting started, etc. that would be autosent upon joining the community, much like the welcome emails sent by listservs.

Description:
While currently it's possible to provide a link to the community profile or a post with posting guidelines when someone joins a community, that's fairly impersonal and brief. I think it would be useful to have an optional feature to send a welcome email that could be customized by the community administrator(s) to help people get started when they join a community, much like the feature on Yahoo!Groups, Google Groups, and other email lists/listservs. This would make it possible to send a "friendlier" welcome message, as well as provide information about participating in the community and useful links not necessarily covered by posting guidelines.

Poll #11272 Customizable welcome email when joining a community
Open to: Registered Users, detailed results viewable to: All, participants: 57


This suggestion:

View Answers

Should be implemented as-is.
19 (33.3%)

Should be implemented with changes. (please comment)
23 (40.4%)

Shouldn't be implemented.
7 (12.3%)

(I have no opinion)
8 (14.0%)

(Other: please comment)
0 (0.0%)

kaberett: Overlaid Mars & Venus symbols, with Swiss Army knife tools at other positions around the central circle. (Default)
[personal profile] kaberett

Title:
Clearly flag tagging permissions for posts to communities

Area:
tagging, community administration, posting, error messages

Summary:
For many communities, creation of tags is limited to administrators-only, to prevent an ever-growing list of subcategories, misspellings, etc. For some communities, it's also the case that only administrators are able to apply tags to posts. It should be clear on the Post an Entry page whether either of these settings is in force for any given community.

Description:
When managing tag settings as a community, there are the options:

Who can create new tags and add or remove tags from entries? Anyone/Members only/Administrators only

Who can add existing tags to entries? Anyone/Members only/Administrators only/Entry author and administrators


On the Post An Entry page, it is not [as far as I know!] made clear which of these settings have been chosen for any given community, which can lead to confusion when e.g. someone is trying to be helpful by tagging their entry but adding tags to entries is restricted to administrators only. (The major use-case I've seen of this is in the LJ community vaginapagina, where administrators choose entries that are particularly well-framed and have particularly useful discussions in comments to tag, in order to build up a "resource library" of past posts, which would be less information-dense and useful if all entries relating to a topic were tagged.)

Suggested solution: when somebody selects a community from the "post to..." drop-down, or clicks "post to [community]" in the navstrip, the "tags" area of the Post An Entry page should automatically update with a useful legend. One way I envisage this working:

* if only administrators can /tag/ entries, the tag box should be greyed out with a brief legend to the tune of "only administrators can tag entries in this community". The full list of tags could perfectly well remain accessible, with a similar legend top & bottom and all the tick-boxes greyed out.

* if only administrators can /create/ tags, the tag box should have a brief explanation along the lines of "please choose from existing tags", and typing into the box should result in searching the community's current list of tags.

Poll #10449 Clearly flag tagging permissions for posts to communities
Open to: Registered Users, detailed results viewable to: All, participants: 68


This suggestion:

View Answers

Should be implemented as-is.
63 (92.6%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
5 (7.4%)

(Other: please comment)
0 (0.0%)

ninetydegrees: Drawing: a girl's face, with a yellow and green stripe over one eye (Default)
[personal profile] ninetydegrees

Title:
Community Management: keep track of canceled invitations

Area:
community management

Summary:
On http://www.dreamwidth.org/community/sentinvites, community admins can see who has accepted an invitation to their community, rejected it or hasn't answered yet. If you cancel an invitation for someone, their username disappears from the list. It would be nice if it didn't do that but added 'canceled' as the invitation status instead.

Description:
The cherry on top would be able to add a note explaining why we canceled the invite (wrong username, joined in the meantime, changed mind, etc.)

The moon would be a timestamp and the username of the admin who canceled it (quite like what Azz suggested in http://dw-suggestions.dreamwidth.org/1323180.html I believe).

Poll #9804 Community Management: keep track of canceled invitations
Open to: Registered Users, detailed results viewable to: All, participants: 59


This suggestion:

View Answers

Should be implemented as-is.
39 (66.1%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
20 (33.9%)

(Other: please comment)
0 (0.0%)

timeasmymeasure: kerry washington with a rose held right below her lips (Default)
[personal profile] timeasmymeasure

Title:
Be Able To Customize "Member Posts" Text In Communities

Area:
communities, customization

Summary:
We should be able to customize the navigation text for the reading in page in communities.

Description:
Currently, the reading text for communities defaults to "Member's Posts", which makes sense. However, it also makes sense that we should be able to customize the text in the 'Customize Journal Style - Text' page like we can with the other navigation links.

Poll #9397 Be Able To Customize "Member Posts" Text In Communities
Open to: Registered Users, detailed results viewable to: All, participants: 60


This suggestion:

View Answers

Should be implemented as-is.
40 (66.7%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
1 (1.7%)

(I have no opinion)
19 (31.7%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Community Membership Log

Area:
communities, community administration

Summary:
For community administrators: Log relevant community membership changes, such as new members joining, moderated membership activity, members leaving, attribute changes (post moderation, post permission, moderator, admin), and bans.

Description:
Some of these attributes are already logged for site administrators, but it would be useful to have them logged for community administrators.

Invitation -- username of invitee, server time of action, username of admin making the invitation.

Join -- username of member, server time of action, and whether it was in response to an invitation/through the member moderation (and who approved the membership if so).

Membership rejection -- username of applicant, server time of action, username of admin rejecting the application.

Invitation expiration -- username of invitee, server time of invitation & expiration, username of admin who invited them.

Attribute change -- username of member, server time of action, the change (gained/lost post, entry moderation, moderation power, admin power), and username of admin.

Ban/unban -- username, server time of action, ban/unban, username of admin.

Departure -- username, server time of action, and username of admin if this was an admin action.

Should reading page subscription/unsubscription also be logged?

Poll #9396 Community Membership Log
Open to: Registered Users, detailed results viewable to: All, participants: 62


This suggestion:

View Answers

Should be implemented as-is.
38 (61.3%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
24 (38.7%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Community Entry & Comment Action Log

Area:
communities, community moderation

Summary:
For community administrators: Log relevant entry and comment activities. This could include things like deleting entries, deleting comments, screening/unscreening comments, freezing/unfreezing comments, editing entries, and tag editing.

Description:
One challenge for community administrators is sometimes keeping track of various activities in their community. Different community populations require different levels of admin attention, and sometimes an administrator does not realize they need to know about a specific action in their community until something happens and they're left trying to sort out what exactly happened and who they need to talk to.

These are all community actions that currently leave little trace in the system, but can be crucial to sorting out what happened and why.

Entry deletion -- some communities ask that their members not delete their entries. Some communities ask that only one specific administrator delete any entries. Sometimes, as in the case of communities like dw_suggestions, a deleted entry means administrative work to track down the entry and reconcile the public-entry-to-private-admin-entry counts. Entry deletion should log the username of the entry owner, the server time the entry was initially posted to the community, the entry's subject and first ~100 characters (raw), the time of entry deletion, the username of the party who deleted the entry (and possibly their position: self or admin), and whether the entry was marked as spam.

Comment deletion -- some communities ask that comments with problems be left in place for an administrator to handle. Sometimes it is accepted for the person who left the comment to think better of what they said and delete their comment, but it is frowned upon for the entry poster to delete a comment even though they have the power to do so. Comment deletion should log the username of the comment owner, the subject and first ~100 characters, the server time the comment was initially posted, the entry (and thread, if applicable) in which the comment was posted, the username of the party who deleted the comment (and possibly their position: self, entry poster, admin), the time of the comment's deletion, and whether the comment was marked as spam.

Comment screening/unscreening, freezing/unfreezing -- I have seen entry poster vs. community administrator freezing and screening wars before, and they are not pretty. I did not know that I would want this logged until it happened to me. This should log the username of the comment owner, the subject & first ~100 characters, the server time the comment was initially posted, a link to the comment & thread (because sometimes you want to go straight there, sometimes you want the whole thread, possibly the direct parent too), what the action was, and the username of the person who did it (and possibly their position: entry poster or admin).

Entry editing -- I'm less concerned with editing of the entry text in this context as I am with things like editing to turn off comments, or that it would be really nice to log when community admins bump the NSFW setting or security. But other community admins may have different concerns. This should probably log the username of the entry poster, title & first ~100, server time of post, server time of edit, who edited it (and possibly position: entry poster or admin), and the attributes that were edited. Subject edits could probably display old subject & new subject. Body edits could display ... net change in character count? (Other community admins, please weigh in on what would be useful.) Entry attributes should display old value & new value if there was a change.

Tag editing -- this could be useful for mistaken tagging or tag vandalism, like if someone accidentally detags an entry, or selects all tags for an entry and saves it. Log should include information to identify the entry (username, server time of posting, subject & first ~100, link), the old tags, the new tags, and the username & position (non-member, member, entry poster, admin), and server time of change.

I'm not sure that comment editing needs to be logged, because there already exist notifications that can be emailed, admins from paid communities can subscribe to all comments (including all edits), and people edit comments a lot (and it could clog up the logs).

Anything else?

Poll #9395 Community Entry & Comment Action Log
Open to: Registered Users, detailed results viewable to: All, participants: 52


This suggestion:

View Answers

Should be implemented as-is.
31 (59.6%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
21 (40.4%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Community Moderation Log

Area:
communities, moderation queue

Summary:
Show the last (reasonable number of) community moderation actions on a special page. This should particularly include the username of the moderator.

Description:
Community moderation queues are one of the unfinished areas of the site that could use some sprucing up.

Currently there is no visible record of which community moderator took action in the moderation queue, nor exactly what that action was.

Keeping a record of the moderation queue from the beginning of time could conceivably take up a hefty chunk of space, especially in high-volume communities. Instead of keeping the records indefinitely, we could log them as they happened, and show up to a certain number of them (I suggest 200, as that is double the size of a paid community's maximum queue depth). Or, if hanging onto them indefinitely would not be a strain, they should be paginated maybe at 100 records at a time. They would be displayed on a special page that can be accessed only by users who have the right to see the moderation queue.

(While community moderators can see the moderation queue, administrators can grant themselves the right to moderate, and should probably be able to see the page whether or not they currently have that attribute turned on. Please do submit scenarios where an administrator should not be able to visit that page in the comments, if you can think of any, because I can't -- at least not until admin rights can be granted piece-by-piece, in which case we'll probably have owners by then, and owners should then be able to visit it without explicitly turning anything on.)

The page should log the following:

Username of submitter
Timestamp of submission
Title of submission
Escaped (plain-text with all HTML symbols displayed) version of first X characters of submission
Username of moderator
Action (disposition of submission)
Note (if any)
Timestamp of action
Link to entry (if posted)

It should log approval, rejection, and reject-as-spam.

It should display (by default) in the order of action, with newest actions on top, but it would be awesome if the page could be sorted by some of the other fields. Records would remain visible until pushed out of the active area.

This would be useful for community management tasks. Moderators could spend less time on communicating basic details to each other and more time talking about other community management needs. It would be easy to look up recent actions of other moderators even if they did not mention the incident. In case of problems on a moderation team, for example if moderators were taking actions by accident, by a mistaken understanding of the community policies, or out of malice, their actions would be visible to others and they could be spoken with based on a record of their actual actions rather than one person's word against another's.

Poll #9261 Community Moderation Log
Open to: Registered Users, detailed results viewable to: All, participants: 63


This suggestion:

View Answers

Should be implemented as-is.
42 (66.7%)

Should be implemented with changes. (please comment)
1 (1.6%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
20 (31.7%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Community admins/moderators: moderation queue action subscription

Area:
communities, notifications, entries, moderation queue

Summary:
Create a subscription for action (acceptance and rejection) for community moderation queues. Make this subscription available only to users who have access to see the moderation queue.

Description:
Community moderators may currently receive notifications for new submissions to their community's moderation queue.

It would also be useful for them to get notifications about moderation queue action, possibly from themselves, but definitely from other moderators.

The notification should include:

The username of the moderator who made the action, what the action was, what community this is in, the username of the user whose submission it was, the time the submission entered the queue and the time the action was made, the note (if any) the moderator left, the entry's title, contents, and possibly other relevant metadata (tags, location, mood); if this action was an approval, a link to the entry as posted.

(Should this be sent for items that are marked as spam? I can think of arguments in both directions: against: in case of legitimate spam it is useless overhead that will only bother the other moderators, emailing known spam may alarm email providers; for: if a moderator is marking things as spam that are not spam (either accidentally, mistakenly, or maliciously) the others should know, moderators who become accustomed to messages about queue action may be surprised when they see an entry come in but find it gone with no notification about why.)

This notification should only be available to people with access to see the moderation queue, which in practice is only moderators, but in terms of practical community oversight might need to include the community administrators.

The subscription should be separate for every community, and should (if possible for business reasons) not count against the subscription slot limit.

(Related: an on-site moderation queue log.)

Poll #9260 Community admins/moderators: moderation queue action subscription
Open to: Registered Users, detailed results viewable to: All, participants: 57


This suggestion:

View Answers

Should be implemented as-is.
20 (35.1%)

Should be implemented with changes. (please comment)
4 (7.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
33 (57.9%)

(Other: please comment)
0 (0.0%)

sara: S (Default)
[personal profile] sara

Title:
Comment indexing

Area:
commenting

Summary:
Build a thingy that will pull the subject lines and direct links from top-level comments on a post and output them in some kind of useful format (maybe a table or a list?) which can be inserted into the body of the post (hopefully under a cut-tag). Bonus points if it can be set to periodically run an automatic update.

Description:
This suggestion is motivated by my total lack of enthusiasm for spending an evening manually indexing a meme. I don't want to do that, that's a database query. Someone should build a thingy so the server can do this job for me.

Specific thingy-implementation-related issues should be conceptualized by someone with more thingy design and implementation experience than I have.

Poll #8881 Comment indexing
Open to: Registered Users, detailed results viewable to: All, participants: 75


This suggestion:

View Answers

Should be implemented as-is.
47 (62.7%)

Should be implemented with changes. (please comment)
1 (1.3%)

Shouldn't be implemented.
3 (4.0%)

(I have no opinion)
24 (32.0%)

(Other: please comment)
0 (0.0%)

azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
"Currently working as" on every "work as" page

Area:
community administration, ui, making things make sense

Summary:
Show a "currently working as: [community or user]" on every page that allows you to manage multiple journals. This would likely be a series of quick fixes or perhaps suitable for some beginning developers, although it might be replaced down the line if the current settings pages are overhauled.

Description:
Currently, when you load a page like http://www.dreamwidth.org/manage/tags you get a list of communities you can manage (if you administrate any) as well as your own journal, but you have to remember to click the "Switch" button to make it happen. I have more than once made changes for the wrong place and then been frustrated because I forgot to click that button (and I would consider myself a power user).

Also, if you're done working with your community and you want to go back there to see how it looks, sometimes there isn't a quick link.

Adding a "currently working as" notice would serve as a notice that maybe you need to click the button, a reassurance that you really are working on the right community, and a link to go back and check things out. It would probably save a lot of time and just look nicer.

Poll #8423 "Currently working as" on every "work as" page
Open to: Registered Users, detailed results viewable to: All, participants: 64


This suggestion:

View Answers

Should be implemented as-is.
55 (85.9%)

Should be implemented with changes. (please comment)
1 (1.6%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
7 (10.9%)

(Other: please comment)
1 (1.6%)

ninetydegrees: Drawing: a girl's face, with a yellow and green stripe over one eye (Default)
[personal profile] ninetydegrees

Title:
Community Management: ability to send a note when deleting an entry

Area:
Community Management

Summary:
Admins can delete any entry posted in their communities. It would be nice if they could send a note explaining why they did it should they wish to, the same way you can send one when you reject a moderated entry.

Description:
Deletions are not always caused by spam, irrelevant content or blatant disregard of the community rules. It can be the result of a honest mistake and I think having the possibility to explain or clarify something as you delete the entry could be useful. The entry could still be deleted immediately, which is useful when communication with the poster takes time or the entry contains HTML code which breaks one's reading page, and you wouldn't have to enable moderation in communities where 'problematic' entries are a rare occurrence.

Poll #8387 Community Management: ability to send a note when deleting an entry
Open to: Registered Users, detailed results viewable to: All, participants: 69


This suggestion:

View Answers

Should be implemented as-is.
63 (91.3%)

Should be implemented with changes. (please comment)
0 (0.0%)

Shouldn't be implemented.
0 (0.0%)

(I have no opinion)
6 (8.7%)

(Other: please comment)
0 (0.0%)

denise: Image: Me, facing away from camera, on top of the Castel Sant'Angelo in Rome (Default)
[staff profile] denise

Title:
Support instructors/teachers/professors using DW for class-related projects

Area:
posting, communities, using DW to conquer the world

Summary:
We get at least three or four instructors per semester asking for promo codes for account creations for their classes (which we're always happy to give!) Since DW is so well-suited to keeping class journals, submitting writing assignments, or requiring class participation, I'd love to be able to code some more support for academic use.

Description:
Obviously each teacher's use of DW would be different, depending on the type of class they're teaching and the level at which they're teaching it (high school, undergrad, graduate work, adult enrichment, etc). This suggestion is less "we should add this" and more "we should brainstorm what we can add that would actually be most helpful".

I'm basically proposing a new category of accounts: "instructor accounts" or "academic accounts" and "student accounts" or "learner accounts" (names obviously subject to change, yadda). This will allow us to set different capabilities for these accounts.

The "academic package" would consist of:

* one promo code per class/class section;
* one "academic community" account per section, with slight changes to the standard community model to make them more appropriate for teacher/class interaction;
* one (or more if co-taught or if class has a TA) "instructor account" to be the admin of the community (or the instructor could use their standard DW account, but all of the instructors I know don't want their students finding their regular DW account!)
* a number of "student accounts" created via the promo code, where the students can choose their own usernames and migrate the student account to a standard account later if they'd like.

Things I can think of, off the top of my head:

* the ability for the instructor to "clear out" a community's posts and comments, moving them to some form of archive (essentially a community rename?) each semester/quarter/marking period/etc in order to store each semester's classwork separately and start each semester with a blank slate

* ability to force a student account created with a specific promo code to be subscribed to/a member of the community for the project, without having to check the checkbox during account creation

* ability to designate an instructor account for each "academic package" that will automatically subscribe to any account created from the promo code (so the instructor won't 'lose' students or have to get them to submit their username to the instructor through some other method)

* ability for the instructor to subscribe to all posts and comments made in the community (without the comm needing to be a paid community, I mean)

What other things would instructors using DW for academic/teaching purposes want to see, or would find useful?

(Edited to remove poll #7997, since this is more of an information-gathering entry than a suggestion!)
azurelunatic: A glittery black pin badge with a blue holographic star in the middle. (Default)
[personal profile] azurelunatic

Title:
Community members list edit success: list pages

Area:
community administration, ui, making things make sense

Summary:
When saving community membership editing, present the pages menu and a link to return to the page you were on, the previous page, and the next page.

Description:
Current behavior of the community membership editing interface looks like it was inherited without much modification from our code parent.

Upon saving settings at http://www.dreamwidth.org/community/members?authas=communitynamehere there is a link, http://www.dreamwidth.org/community/members.bml?authas=communitynamehere, which goes to the first page of the community membership list, no matter what page you were on when you were editing, no matter how many pages there were.

The editing success page should ideally list all the possible pages in the familiar numbered menu as one sees normally, with perhaps quick and easy links to the page you were on, the previous page, and the next page. Maybe even first and last, if that wouldn't be too fancy and/or confusing.

Poll #7773 Community members list edit success: list pages
Open to: Registered Users, detailed results viewable to: All, participants: 48


This suggestion:

View Answers

Should be implemented as-is.
29 (60.4%)

Should be implemented with changes. (please comment)
4 (8.3%)

Shouldn't be implemented.
1 (2.1%)

(I have no opinion)
14 (29.2%)

(Other: please comment)
0 (0.0%)

Profile

Dreamwidth Suggestions

April 2017

S M T W T F S
      1
23456 7 8
9 101112131415
16171819202122
23242526272829
30      

Style Credit

Expand Cut Tags

No cut tags

Syndicate

RSS Atom