Someone to collaborate on the next major release

[satwikkansal]

Hi all!

A major release of WTFPython is long overdue, there are some great potential inclusions already in the Issues section, and I have a few of myself too that I've been maintaining separately.

I'm looking for someone who'd want to take a stab at working up the next major release, which typically involves,

• Including newer snippets with explanations.
• Making rearrangements in the grouping of the examples or the orders of the examples, to make things more intuitive and fun. This needs to be done anyway with addition of new snippets.
• Adding newer modes of consumption (last time I added jupyter notebooks via google colab, and then I worked on an interactive version using pyiodide which I didn't share that much publicly)
• Doing a proofread and sanity check of all the snippets with the latest Python version to make sure outputs and explanations are correct.

There aren't any monetary benefits, but based on my past experience, you do get to learn a LOT (about Python and about creative writing if you put decent focus on presentation and reading flow), and I'm more than happy to transparently attribute you for all the awesome work. It's also exciting to share the new release on the internet with thousands of developers, so you get to share that feeling as well :)

If interested, please let me know at discuss@satwikkansal.xyz with few lines about your background, what got you interested, the timeline you're comfortable with, and the kind of changes you'd want to make in the newer release (apart from the ones already covered in Github issues).

[nifadyev]

Hey @satwikkansal , what do you think about converting this issue into discussion?

[satwikkansal]

Done 👍

[nifadyev]

I suppose it would be better to make another release before 4.0, let's say 3.1.
It will include every change since last release + preparations for next major release (mostly internal stuff to ease contribution and repo management) - markdown linter and formatter, typos, old issues and PRs, some guidelines for local development, CI and pre-commit checks.

[nifadyev]

Another important question is formats of provided information. Are you sure that the project need cli version? And so on

[satwikkansal]

Yes, let's develop a plan for the 3.1 release. As for the pre-commit checks, we should have a spell checker for non-code blocks in README.md. Many of the fixes we see involve spelling corrections.

Long run, what'd also be nice to have is a GitHub action that could run the snippets and verify the output, I've not thought about how it'll work, but it's something that could be useful.

As for the formats we need to keep, I agree we need to consolidate a bit. We can drop cli support, it isn't convenient to read anyway. We can just stick to Google colab notebooks (1 for each translation). Interactive web version and CLI versions can be dropped. I'd like to introduce a pdf version for those reading offline, this has been a frequent ask and long overdue.

[nifadyev]

Cool, then I'll create issues and you will add release milestone or label for them

[nifadyev]

Hey Satwik,
Could you also check what files are extra and can be easily deleted. For example, .travis.yml

[satwikkansal]

• The entire pypi directory
• There might be a few scripts in irrelevant directory that we can delete, but you can leave it to me. We can delete after we know we aren't going to use any of that stuff.