Will GitHub be a requirement for plugin developers? Can they use GitLab or another git repository?
That’s a good question. My guess is, as long as the repo is public it won’t matter which service is used. But it’s not my call, and I’m curious to find out now.
From whatever code repository we use as a source, we need the ability to get a zip file for the plugin.
GitHub makes this easy: you can grab a zipfile for any version of the code from any repository. Or, if a plugin developer needs to serve a different set of files than what’s in the repository, they can do a release and host a zip file under the Releases section (we do this for the ClassicPress migration plugin for example).
Bitbucket appears to support zip downloads, but it does not support releases in the same way, so there would be some trade-offs to make there.
What about GitLab? I’m not sure, and I don’t think I have an account on their hosted service.
The easiest way to make all of this work is definitely going to be to use GitHub only. If people want another option with the first version of the plugin directory, then we will need some help and testing to make that work.
Gitlab has releases and allows download of zip, tar.gz, tar.bz2 and .tar files
Good to know, thanks! I’d definitely be in favor of building this using releases, but making it possible to use any repository provider as long as they implement all of the necessary pieces.