User:Maffblaster/Todo

My personal list of Article description::Gentoo stuff to do in order to get Gentoo stuff done.


 * Go to completed tasks.

Todo
Anything in the Todo category, but especially Open discussions in the Handbook namespace.

Catch up on all open discussions in the Handbook namespace

 * Open discussions

As I continue to clean up our docs in 2021, I am working to catch up with and hopefully close out all open discussions in the Handbook: namespace. Will move this section to Completed tasks when caught up to this point. Aiming for January, 2021 and plan to tackle (at least) one discussion per week, but hopefully multiple per day.

Wikidata
Wikidata implementation.

See Wikidata.

https://www.mediawiki.org/wiki/Wikibase

Add a "Fund me" link to developer and community wiki pages
Add a optional field to the developer template and form that will enable a "fund me" link on wiki profiles. Link can point to an arbitrary location (GitHub, Patreon, etc.). Consider also adding crypo wallet endpoints as well.

For example, as of 2022-01-17 marcan [link coming soon] still uses Gentoo as a developer environment as he hacks on getting the Linux kernel to run on Apple's M1 Mac hardware. His links are as follows:

Patreon: https://patreon.com/marcan GitHub Sponsors: https://github.com/sponsors/marcan

Link developer nickname to developer map on www.g.o
This will require some investigation into the possibility of linking a name to a coordinate on www.g.o.

https://www.gentoo.org/inside-gentoo/developers/map.html

Preferable to link to a location with using an  tag such as   on the ending.

Convert home directories to systemd homed
Follow the upstream guide. Determine how it applies to our users and the systemd article: https://systemd.io/CONVERTING_TO_HOMED/

Create a community maintained disk space document
See this discussion. Handbook should reference basic disk space requirements, whereas community page can document in more specificity how much space is necessary for typical installations on a per-profile basis.


 * Profile space requirements
 * distfiles space requirements (btrfs) as of 2021/09/22: 282G
 * gentoo repository space requirements (btrfs) as of 2021/09/22: 562M

Should be able to hook this up to an automated export available via HTTPS somehow...

Since "desktop" profiles are becoming available, it should be possible nab uncompressed filesystem sizes from RelEng builds, this data can be used to generate a table that can be used on the main site.... alternatively link to my space on pecker.

Prefix/Termux
Packages required to be installed in Termux (GitHub) for Gentoo Prefix to run:

Prefix/Cygwin
Packages required to be installed in Cygwin for Gentoo Prefix to run:

Tyrian

 * Devmanual should be added to the sites drop down menu...

Bound to fail
Using too high a MAKEOPS value and  set to   (or some other N), is a bad idea when compiling source in tmpfs or when Gentoo has been allocated only a small partition to PORTAGE_TMPDIR. In the example below the following default values are set in :

The previous example is bound to result in job failure output similar to the following:

Why does this happen?
The above occurs as explained in the OSError output from Portage: OSError: [Errno 28] No space left on device

In other words, space runs out in the directory Portage uses for compilation ( PORTAGE_TMPDIR ).

The fastest solution
Run + to close the Python interpreter, then do whatever is appropriate to obtain more disk space. Typically this can look like running and purging any failed compilations from Portage's TMPDIR:

Finally, resuming the with a smaller MAKEOPTS or jobs value (or both!) should work around the build failure:

Building stages with clang
Reddit discussion here.

This Debian sites keeps a nice list of packages that are successfully built with LLVM/Clang.

Captive portals
Explain how to access Cisco (and other) captive portals.

Add information on enabling FreeSync on AMDGPU

 * AMDGPU

Resolve PPC bootloader installation instructions
Handbook probably needs to be migrated from yaboot to GRUB2. See discussion on Handbook_Talk:PPC/Installation/Bootloader.

Pending testing with VOID Linux on a separate HDD. 11/16/2020

Add networking setup example to the Handbooks using ip command
Transision the Handbook to use the command with CIDR format rather than.

Finish new Gentoo wallpapers

 * Add new wallpapers to www.g.o. and create a package for quick and easy installation on Gentoo.
 * Work on getting a resize script for common supported display resolutions. Start with 4K, resize down as appropriate per form factor.
 * Consider mobile device resolutions. What are they?
 * Upload wallpapers sources (with attribution) to maffblaster's GitHub.
 * Cut releases on GitHub.
 * Write imagemagick resize script for end user reproducibility?
 * See this tutorial for possible options. Or this Digital Ocean article.
 * Pseudo-code from Robin:

Terminology update: Overlay -> ebuild repository
Figure out how to address the following articles (man pages will also need updated):

Layman references:


 * PORTDIR_OVERLAY variable.
 * command.

Continue work on: https://wiki.gentoo.org/index.php?title=Special:WhatLinksHere/Overlay&action=purge

Add new recentchanges bot to #gentoo-wiki
Investigate: https://wikitech.wikimedia.org/wiki/EventStreams

Right now I'm researching mw-bot (source).

Code for a similar recentchanges output:

Waiting on a response to issue 62 to add a new wiki to the bot's command.


 * Link from cronolio: https://www.mediawiki.org/wiki/Manual:$wgRCFeeds#Example
 * Setting up ircII with recentchanges: https://wikitech.wikimedia.org/wiki/IRCD#How_to_do_it_on_your_own_server

TODO: write a module to watch recent changes for sopel.

In Unix, what do some obscurely named commands stand for?
Link this somewhere: https://kb.iu.edu/d/abnd

Someone please work on these. Someone. ANYONE?! PLEASE!!

 * GitLab - Clean up article: meld it into proper article layout/formatting according to wiki Guidelines, review for correctness.
 * Work on bringing GitLab to Gentoo. This would be of use to infra as a GitHub fall back (since GitHub isn't nicely open source).
 * Start with a Gentoo-based container (if necessary), and build from there.