Project

General

Profile

Actions

action #125243

closed

Define GSOC project proposal next to https://github.com/openSUSE/mentoring/issues/120 size:M

Added by okurz about 1 year ago. Updated about 1 year ago.

Status:
Resolved
Priority:
Urgent
Assignee:
Target version:
Start date:
2023-03-01
Due date:
% Done:

0%

Estimated time:

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

Suggestions

Actions #1

Updated by okurz about 1 year ago

How about

Actions #2

Updated by okurz about 1 year ago

  • Description updated (diff)
Actions #3

Updated by okurz about 1 year ago

  • Description updated (diff)
Actions #4

Updated by mkittler about 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
Actions #5

Updated by mkittler about 1 year ago

  • Assignee set to mkittler
Actions #6

Updated by mkittler about 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?

Actions #7

Updated by okurz about 1 year ago

thx, deleted the sentence for now.

Actions #8

Updated by mkittler about 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.

Actions #9

Updated by mkittler about 1 year ago

  • Status changed from Workable to Feedback
Actions #10

Updated by mkittler about 1 year ago

  • Status changed from Feedback to Resolved

I'm marking the ticket as resolved based on @okurz's comment on Slack :-)

Actions

Also available in: Atom PDF