Forums Cleanup - Githubissues

I don't know if it would be good to move all the things listed here. The skinning subforum allread isnt very active/informative and this would remove most of the usefull aspects the forum has atm. I don't know anyone from the skinning community that's active in the wiki, atm it is pretty easy to get things added to any of the mentioned lists and everything is easy to find.

The tutorial is incomplete (didn't checked if it still is up-to-date). It would need to be heavily edited. Maybe it is time for a new, better organized skinning suppport (maybe combined with the FAQ?)

The part I definitly wouldn't move over to the wiki is the completed skins compendium. It was dead for a long time, because no one from the staff wanted to take care of it. Since the beginning of the year I'm taking care of it. I don't know how the wiki-system works exactly, but I guess it wouldn't be easier than the forum-system (BB code). It allready is a pain to edit, that's why there are 175skins in the subforum, but only ~150 in the compendium. It needs much time to edit the compendium and checking skins for completion is also pretty time consuming (there are still several pages left for me to check from deadbeat's old queue). My concern is that no one would continue the compendium after it gets moved, because no one did it the last 3 years.

MegaApplePi commented 6 years ago

@RockRoller01

I don't know if it would be good to move all the things listed here. [...]

I see what you mean, but by adding it to the wiki, it can allow anyone to correct and update the information.

The tutorial is incomplete (didn't checked if it still is up-to-date).

I (and many other people) know :<. MLGnom's tutorial is still collecting dust for the past 4 years. We need people to write the skinning tutorial to plan on a new proposal for how it should be done and actually do it :s.

Maybe it is time for a new, better organized skinning suppport (maybe combined with the FAQ?)

It's easier said than done (If you have a proposal, open an issue, pull request, or discuss about it in #osu-wiki). Can you explain your last part of that sentence?

The part I definitly wouldn't move over to the wiki is the completed skins compendium. [...]

Moving the skinning compendium to the wiki wouldn't (and shouldn't) do much; you would be using Markdown instead of BBCode (they're intentions are basically the same, their markup is different however). By having it in the wiki, this opens the window of editors to basically everyone (since this is a wiki).

RockRoller01 commented 6 years ago

Writting the tutorial wouldn't be a problem for me.

Why is it easier said than done? My last sentence meant, that asked questions could get add to the main post, I don't want to know how many duplicates are in the current skinning support.

(Will comment about your part abiut the compendium later, need to go.)

MegaApplePi commented 6 years ago

@RockRoller01

Writting the tutorial wouldn't be a problem for me.

If you can, that would be great.

Why is it easier said than done?

I tried to rewrite it, following MLGnom's style (talk about an element then show picture examples from other skins). However, when I began to do that, I got stuck and couldn't get it that plan to work. (Now thinking back, I just planned it poorly then executed it badly 🤷‍♂️)

My last sentence meant, that asked questions could get add to the main post, I don't want to know how many duplicates are in the current skinning support.

(I'm sorry but) can you explain that or give more context... are you talking about the skinning FAQ?

peppy commented 6 years ago

Removing milestone. Add back when you are confident this is going to get done.

FreezyLemon commented 6 years ago

Thinking about porting the Help->"Windows 10 Creator Update Crusor & Raw Input issues" post/thread.

Where do you think I should put the article? There's a "collection" of articles for Guides, but nothing for Troubleshooting/Help, or did I miss something? I might just create a "help" category for this if it's okay.

h3oCharles commented 4 years ago

about the skinning portion of this (cuz i only care about this part of the forum), specifically important guides and thread

there's also my part of these below OP, but very outdated because hardly anyone even looks at that unless me or one of my fellow skinners point it out. I was thinking of updating it but there's nothing/nobody pushing me to do so.

alternatively everything mentioned on important guides and threads forum thread should have their own dedicated wiki entry (except for community discord servers)

one counter argument to all of this is that just like @RockRoller01 mentioned - no one REALLY goes to the osu! wiki for skinning help, most of the time people go to /r/osuskins subreddit or ~~skinship~~ one of community discord servers.

i was also going to complain about the state of the skinning forum here too but i resisted myself to do so

cl8n commented 4 years ago

I was thinking of updating it but there's nothing/nobody pushing me to do so.

this is pretty much why the skinning part of the wiki is so poorly maintained; very few people use it, the people who care a lot about skinning are busy maintaining projects elsewhere, and otherwise there's just not enough wiki manpower as-is to pick up large tasks like this. it's honestly difficult to come up with a good argument why people should put in the effort here, because like you say there's already some great public resources available. it's a similar case with storyboarding wiki

can't comment much on the skinning forum but I've definitely heard a lot of complaints there, it's unfortunate that there's little focus being put on this

Gamingzone123 commented 2 years ago

in relation to running osu! on linux, users can self-compile with lazer

Walavouchey commented 2 years ago

Peppy would like to see this converted to wiki in combination with https://osu.ppy.sh/community/forums/topics/367783)

huh, https://github.com/ppy/osu-wiki/pull/6507 was basically trying to do that, but got shut down. probably either changed his mind or realised it wouldn't really fly with focus shifting to lazer over the years. either way, if anyone wants to write installation instructions for stable on linux, it'd have to be just a short stub with general steps linking to other resources.

bdach commented 2 years ago

6507 was basically trying to do that, but got shut down

I'd say the primary reason why that was closed is links to random executables hosted on google drives.

peppy commented 2 years ago

Correct. The idea was to provide the basic required to get things working, back when that forum thread was the best information available. I'm still fine with having the information in that thread used, but what was done in #6507 was taking things a step too far.

Also, now that osu!(lazer) will run on linux without any of this stuff, the usefulness of such an article could be debated.

FazlyMR commented 1 year ago

I'd be willing, and are currently working on writing a short article on installing osu!(lazer) on Linux, but with both AppImage and Flatpak versions available, which one will be officially supported and should I cover?

And with my current version that I'm writing being quite short, should it be combined with an existing article covering the installation of osu!(stable) on macOS (also rename it if this is the way to go) that also covers the installation of osu!(lazer) if instructions to get osu!(stable) working on Linux is no longer a priority?

TicClick commented 1 year ago

I'd say lazer is simple enough to get installed, so you don't need to do anything in that regard — better focus on guides/pages that address complicated or error-prone procedures

ppy / osu-wiki

Forums Cleanup #962

osu!

Development

1138

1012

985

1271

1000

1013

Completed Projects

967

Gameplay & Rankings

964

Tournaments

Taiko

Catch the Beat

osu!mania

Skinning

1171

1114

1028

1153

Completed Skins

1031

Help

2171

Resolved Issues

1085

Beatmaps

Ranked/Approved Beatmaps

1251

Pending Beatmaps

Works In Progress/Help

General Questions

Storyboarding

Beatmap Projects

Beatmap Management

975

1162

Other

Art

6507 was basically trying to do that, but got shut down