| Commit message (Collapse) | Author | Age | Lines | 
| |  | 
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
| 
| 
| 
|  | 
The previous system required each extension's `setup` func to log
that the cog was loaded. This leads to inconsistent messages all
trying to convey the same thing, variable logger names in the output
file are difficult to read, and several extensions were not logging
at all.
By logging directly in the `add_cog` method, we reduce code repetition,
ensure consistent format, and remove the responsibility to remember
that a log should be made.
 | 
| |  | 
 | 
| | 
| 
| 
|  | 
Simplify internal structure & adjust var naming.
 | 
| | 
| 
| 
| 
|  | 
This simplifies the function and is more in-line with how the function
is being used.
 | 
| | 
| 
| 
| 
|  | 
To avoid confusion, the packages should no longer be referred to
as 'seasons'.
 | 
| | 
| 
| 
| 
| 
| 
| 
| 
|  | 
Since the original `seasons` package is now called just `exts`,
it makes sense to migrate all season-specific definitions out into
a separate module.
This module now contains everything relating to 'new' seasons, i.e.
just branding tooling.
 | 
|   
  
  
  
  
  
  
  
   | 
It is believed that this is now a more logical name for the package,
as extensions no longer bind to seasons.
Internally, packages are still grouped into seasonal sub-packages.
There are quite a few, and it makes sense to group them by a common
theme that inspired their functionality.
 |