Finalizing 2.0 release plan

[TomDonoghue]

This is an overview issue for managing the full release of the specparam 2.0 version.

Key Code Development (PRs for 2.0 / can be used for ChangeLog):

• [x] Name overhaul (v2.0.0rc0): https://github.com/fooof-tools/fooof/pull/205
• [x] Time-resolved model objects (v2.0.0rc1): https://github.com/fooof-tools/fooof/pull/283
• [ ] Rework object organization: https://github.com/fooof-tools/fooof/pull/291
• [ ] Add explicit periodic / aperiodic modes: https://github.com/fooof-tools/fooof/pull/298
• [ ] Add support for different peak height spacings: https://github.com/fooof-tools/fooof/pull/297
• [ ] (anticipated) Sweep through for module layout / organization

For the above updates, each is a fairly sizable update / extension, and each will be released as a release candidate for testing (already released ones are listed above). Recent release candidate versions are on PYPI, and the documentation site is here: https://specparam-tools.github.io/

Release plan:

• [ ] Continue release candidates for key PRs, and finalize a 2.0 release to PYPI with the main release
• [ ] When officially ready, move & rename this repository to https://github.com/specparam-tools
  • This will create an automatic redirect from fooof-tools/fooof -> specparam-tools/specparam
• [ ] When released and moved, add final notes on the change to this org, fooof-docsite, etc

Release related updates:

• [ ] Do a sweep of dependants / downstream use and update on the new release
  • Python users might need to refactor / reimplementations (e.g. Matlab) may need
• [ ] Update links in the associated paper
  • Also, fix the typo regarding AMPA / GABA kernels