action #125243
closedDefine GSOC project proposal next to https://github.com/openSUSE/mentoring/issues/120 size:M
0%
Description
Motivation¶
GSOC contributor application period begins 2023-03-20 but so far we only have https://github.com/openSUSE/mentoring/issues/120 and also https://github.com/openSUSE/mentoring/issues/201. I am sure we can brainstorm some more good ideas.
Acceptance criteria¶
- AC1: At least one more project proposal related to our topics exists on https://github.com/openSUSE/mentoring/issues
Suggestions¶
- Read https://github.com/openSUSE/mentoring/issues/120 and https://github.com/openSUSE/mentoring/issues/201 as examples and what are already defined
- Look through our "future" ticket ideas like from https://v.gd/C6IW2g
- pick one or multiple of those and create a project proposal out of that
Updated by mkittler over 1 year ago
- Subject changed from Define GSOC project proposal next to https://github.com/openSUSE/mentoring/issues/120 to Define GSOC project proposal next to https://github.com/openSUSE/mentoring/issues/120 size:M
- Status changed from New to Workable
Updated by mkittler over 1 year ago
I don't understand the sentence:
Additionally using container management frameworks to work on
on https://github.com/openSUSE/mentoring/issues/120.
@okurz Since I really don't know what this incomplete sentence is getting at I'm not just editing the issue. Can you do it?
Updated by mkittler over 1 year ago
I've been creating a proposal to improve accessibility: https://github.com/openSUSE/mentoring/issues/202
I think it is a good topic because we already have different issues in the backlog, it has user-visible impact and does not require any specific knowledge about openSUSE/SUSE or even openQA. It may be a little bit too simple. However, considering our previous experience we should likely not set the bar too high anyways.
Since you cannot just edit the issue, please tell me if you find any typos or have other improvements.
Updated by mkittler over 1 year ago
- Status changed from Feedback to Resolved
I'm marking the ticket as resolved based on @okurz's comment on Slack :-)