1. Separate 2 follow-up actions: updating an issue with new content (or changing metadata) vs subscribing to an issue (no update on issues content or metadata, just marking the issue “touched by me”). While the latter action is encouraged and popular use case, the “#xx just subscribing” follow-ups just add cruft to the issue and generate “false alert” for people who are expecting to find new content on issue.
Simple fix for this is just not to generate new followup when “empty” followup is posted + an explanation string in followup form that announces this hackish “subscription” feature.
More comprehensive solution: “action box” in bottom of the issue tries to do clear split between the tasks above. It also surfaces the RSS tracking feature (can we do it issue-based?)
2. Allow Media attachment previews: should create “visual commentary” to an issue, encouraging more contributors to submit screenshots and mockups. At least common image formats should be supported, video support, such as in my mockup should be added in future. (speaking of video – it is a great visualization tool for dynamic flows, we need to do more of this in development)
3. Allow multiple attachments per issue: there are too many cases when people do want to post several attachments: such as a path, new file, perhaps a mockup, all under the same issue. Creating separate followups for all these seem awkward. But there are good reason for attachment-per-followup – referencing, it is easy to point to “liking screenshot #1” and “#2 does not apply”. To support that, perhaps the UI can do the merging – checking if two concurrent followups are from same person, “wrap” them visually into the one followup – while preserving the referencing #x for each.
4. Allow editing followups Related to the previous issue: allow people to edit their follow-ups if their followup happens to be the last one. This suppresses the cruft followups like “oops forgot to add that file”
5. add a #x content filter to the followups what creates relative links to the same issue page on the fly, for example: “I like solution [#1]”
Below is the mockup with some of these ideas implemented.
There is a lot more to do though: attachment presentation needs some love (clearer distinction between .patch and other attachment types), wording is sloppy etc but this is a start.
Pretty cool post. It’s really
Pretty cool post. It’s really very nice and useful post.Thanks for sharing this with us!it’s my first visit. Another great post, I appreciate all the work you put into this site, helping out others with your fun and creative works. 000–560 / HP2-E38 / 000–421 / LOT-983 / 000-M38 / 250–270 / BH0–010 / 6002–1
I found it really
I found it really informational and useful.Thanks a lot foe sharing such an interesting and meaningful article. 646–205 dumps 646–223 dumps 646–230 dumps 646–364 braindumps 646–578 braindump 646–656 braindumps 646–671 braindump dumps for 646–985
What is easy and what is
What is easy and what is difficult? Easy is to judge others mistakes and difficult is to recognize our own mistakes. Classification Essay Help
Post new comment