pi-Base community call Fri 2025 Jan 24 at 4pm Eastern

[StevenClontz]

Agenda

• pi-Base tutorial next month https://github.com/orgs/pi-base/discussions/1077
• Clean up "Squash and Merge" commit messages?
• Recommendation to avoid cryptic PR titles?
• Experimenting with ID "badges": https://stevenclontz-ids-when-typese.topology.pages.dev/dev/preview and Add ID badges to typeset internal links web#194
• Discussions vs Issues
• Meta-properties Meta-properties section in Property pages #1071
• importance (or not) of language/grammar
• Approving but not merging?

Zoom link: https://southalabama.zoom.us/j/93833246214

Previous meeting: https://github.com/orgs/pi-base/discussions/846

Next meeting: TBA

[prabau]

@StevenClontz I don't want to attract attention by creating usable links to it, but you may want to check the spam comment added at the end of discussion number 654 (He also created a bogus issue). If possible, block that account.

I am sure this is against some rules of conduct of github, and he could maybe be banned sitewide.

[StevenClontz]

Thanks - I saw the spam message and reported it as such. It's been hidden but not yet deleted (in case that makes it more difficult for moderators to verify the spam).

[prabau]

Hmm, seems like pi-base is being targeted. You may have seen another spam comment from another account which just joined github three hours ago. :-(

[prabau]

@StevenClontz Can you give @pzjp write access to the pi-base repository? He has made great contributions so far.

[StevenClontz]

Done! Thanks @pzjp for your contributions. Please start creating your branches directly on the repository so it triggers automatic builds for your pull requests.

[pzjp]

Whenever this new permissions actually start working, should I abandon my fork and create branches directly in pi-base/data or it's recommended to do this copying trick from the tutorial video?

[prabau]

@pzjp For #1156 that is currently in progress, we can continue with your repository for now.
For your new #1164, it would be preferable to create a new branch in the official repository, for example by using the "copying trick". Then continue in that new branch. You will have to close your PR and open a new PR based on the cloned branch, because github does not allow to change the branch within the same PR.

And for later PRs, they can be done directly from branches in the official repository. So you won't be using your private pi-base repository anymore.

[StevenClontz]

Also I forgot to mention: your permissions are instant, but you need to accept the invitation (should be in your email and your GitHub notifications).

[pzjp]

This notification was surprisingly hidden...
Thank you!