what-can-i-do task lists brief, yet we have excessive duplication and redundancy

[quozl]

What a wonderful problem to have! We have several lists of tasks that can be done;

• project ideas for Outreachy engagement,
• project ideas for Google Summer of Code engagement,
• release engineer's feature tracking, apparently unmaintained after position rotation,
• design team user experience proposals, apparently unmaintained after design team silence,
• trac instance view tickets list of open bugs, many of which are abandoned, and the instance is protected against new users,
• next release feature list, currently empty but likely to grow.

Have I missed any? If I could list so many, there's bound to be another list somewhere I don't know about. :grin:

These lists might be combined in some fashion, deprecated, and then referenced on what-can-i-do here.

[GeekyShiva]

Hi @quozl I am planning to mentor for this and Get this completed during Google Code-In, Please specify what exactly you wish to achieve on this issue. It would be really helpful

[quozl]

Thanks. I've not seen you active with Sugar Labs, so you are unlikely to be able to effectively mentor for this task at the requirements level. Work with a mentor who has extensive experience at Sugar Labs. You will be helpful for detailed design and implementation, so keep engaged.

At a requirements level, each list of tasks has a historical context in the community. This context should be recognised, and the users of the lists identified and guided toward a more suitable task list service. If only we had a professional anthropologist to work with!

Some lists won't be in use, but some will.

A task list I missed in my list was;

• GitHub issues lists, spread across repositories, and across GitHub organisations or people accounts.

An effective result is community acceptance of the deprecation and shutdown of unused lists.

[GeekyShiva]

That's great! Do you suggest someone specific from sugar community whose help I can take to get this task completed during Google Code-in?

[samswag]

I can help you, if you want.

On Fri, Nov 17, 2017 at 5:48 PM, Shivank Shekhar notifications@github.com wrote:

That's great! Do you suggest someone specific from sugar community whose help I can take to get this task completed during Google Code-In ?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/sugarlabs/sugar-docs/issues/114#issuecomment-345297921, or mute the thread https://github.com/notifications/unsubscribe-auth/AFxLWTMg8K5tZe4Gtwc9b1IRP3RkBjs8ks5s3bjdgaJpZM4MNvHN .

[pipix51]

I did a sample task list which currently includes only the project ideas for Outreachy and GSoC engagement (they are exact replicas). The link to the list is https://github.com/pipix51/sugar-docs/blob/master/what-can-i-do.md . I did a few changes to the list-

• I took the table from the two wiki pages and condensed the task descriptions to allow for easier reading.
• I also removed some tasks which have been completed (eg. MusicBlocks guide).

Are there any other suggestions on how I can improve the list?

[quozl]

I see what you've done is to take two or the seven lists from outside this repository and edit them into this repository. Thanks, it looks good.

I had said before;

At a requirements level, each list of tasks has a historical context in the community. This context should be recognised, and the users of the lists identified and guided toward a more suitable task list service.

For the two lists you've acquired, what was the outcome of;

• [ ] recognising the historical context of the list; who made it, when, why, how is it maintained,
• [ ] identifying the users of the list,
• [ ] guiding these users to accept sugar-docs for future list maintenance.

This isn't a coding or writing task; this is a community engagement and service acquisition task. It might prove impractical to achieve.

The Sugar Labs community is widely spread across several media;

• the sugar-devel@ mailing list,
• the iaep@ mailing list,
• the systems@ mailing list,
• the Wiki,
• the Trac instance bugs.sugarlabs.org,
• the GitHub organisation https://github.com/sugarlabs,
• the Projects, Wiki, and Issues pages of GitHub repositories in the organisation,
• separate GitHub repositories, such as https://github.com/llaske/sugarizer,
• the Social Help instance of the DIscourse Forum software,
• IRC channel #sugar,
• IRC channel #sugar-meeting,
• Jabber server,
• Facebook, and;
• private mail and Skype.

Hope that helps you see the size of the problem? :grin:

[quozl]

Reviewed, still a problem.