GitHub "Organization" Management: Please Comment!

[elsiehupp]

As you may have noticed, I just moved wikiteam3 and wikitools3 to a new GitHub "organization" profile, because it seems like doing so would facilitate teamwork across repositories (and also make my name less central, considering I have kind of a background role at this point).

I'm opening this topic as a thread so that collaborators (and anyone else) can make suggestions or otherwise let me know what administrative changes would be helpful on the level of the new "organization" profile.

Please do let me know what I can do to help move things along here. Thanks!

[NyaMisty]

1. It seems that I still don't have write access
2. We can use a Github Projects. It works like this: https://github.com/orgs/microsoft/projects/582
   I've create one: https://github.com/orgs/mediawiki-client-tools/projects/1
   As a owner you'll need to do this to link this project to repo: https://docs.github.com/en/issues/planning-and-tracking-with-projects/managing-your-project/adding-your-project-to-a-repository

[elsiehupp]

It's not always immediately clear in the admin interface which member privileges are enabled and which are not. Apparently I needed to enable projects on that repository in addition to enabling them on the organization level.

By the way, the versioning of the main repository is not yet set in stone. I initially made it version 3 to correspond with the port to Python 3, but given the fact that our progress does not in any way track Python's development progress, that might be less than ideal? Maybe instead the initial PyPI release could be 1.0.0, and we could increment (with semantic versioning) from there?

[NyaMisty]

Got it

[robkam]

I've been trying to find a way to get the changelog to auto-generate. It seems to include all the changes since the start of the upstream Wikiteam project.

[elsiehupp]

That's... probably okay? I mean, the progress can be a bit tidier once we have versioning nailed down?