Last modified: 2013-02-04 22:48:53 UTC
Right now, the feed at Special:MyCourses shows lots of non-course activity for the online volunteers (the experienced Wikipedians), which dominates the feed. Only posts by non-students to course students' talk pages, students' articles and article talk pages, or the course talk page should show up in the MyCourses feed. Otherwise, active Wikipedians' activity will dominate the feed, making it useless for tracking course-specific activity.
Current behaviour: only edits to articles in one of ( NS_MAIN, NS_TALK, NS_USER, NS_USER_TALK ) by a user enrolled in a cause result in the edit will be added to the feed of this course. What I'm understanding from your suggestion: only posts by people that are not enrolled in any course to the user pages or user talk pages of the students of a course, or any of the articles they are working on as part of that course, will be added to the feed of this course. Not sure I'm understanding you correctly though. The current approach was suggested by Frank and seems to make more sense to me. Also not sure that what you are proposing will result in less edits being shown. Perhaps I'm missing something?
That's not the way it is behaving right now (or was, before Special:MyCourses broke). In the beta test class [1], there are no enrolled students at this point, just an instructor and three online volunteers. The feed shows every edit made by those people in the target namespaces, which will completely dominate the feed even once students start editing, since those are the people who are super active all over the wiki. The feed should exclude edits from instructors and volunteers *except* in cases where the post is to an article associated with the class or the talk page of an enrolled student or fellow instructor/volunteer. If that's not feasible, showing *only* student edits is preferable to the current behavior. [1] = http://en.wikipedia.org/wiki/Education_Program:University_of_Guelph-Humber/Currents_in_Twentieth_Century_World_History_%282012_Q4%29
Jeroen, did this ever get a fix? If not, it's a high priority issue.
Not yet, will soonish
Scrap that, looks like I already fixed it
*** This bug has been marked as a duplicate of bug 43880 ***
Think the Foundation deployed stuff recently, so should be live. Let me know if there is still a problem.
