openSUSE / openSUSE/static.opensuse.org
Clean up unused stuff, so we can push more unused stuff
Nobody has claimed this yet.
- Dominant language
- CSS
- Stars
- 3
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
I mean, static is a mess :P
It would be great to clean up old themes, stuff that goes unused anyway, because we already moved on.
- common-yaml* - themes that were used around 2005-2006, they were replaced on all the sites with boosters transitions in 2010-2011 afaict
- css - doesn't seem to be used anymore, mirrorbrain uses different style now, cannot tell if the other stylesheet is used though
- screenshots - no longer representative of distro, even if used somewhere, they should not be
- login - looking at current login pages, this is no longer used anywhere
- images - this is connected with replacing 404, 503 etc pages in general, can I take care of that already, or is something else required to be moved to github?
- fonts - should be replaced with current theme submodule, as in, versioned chameleon versions should be in static (chameleon has versions since some time ago)
- webdesign - no longer used, it's related to creating new pages in bento, which we shouldn't do
Paging heroes so we can discuss all the changes, because they are relevant to majority of infra in the project:
@openSUSE/opensuse-heroes
Would be nice to get a list of websites hosted on .opensuse.org, so we can reliably check for all the stuff.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inventorying the common-yaml, css, screenshots, login, images, fonts, and webdesign directories, then identify which hosted .opensuse.org websites still use them. Review the discussion with openSUSE heroes before changing shared infrastructure. Done means obsolete content is removed or replaced only after its usage is verified and the affected pages remain covered.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css, yaml
- Domain
- frontend, infrastructure, web-dev
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100