sqlfluff github org

@NiallRees had an excellent suggestion. Rather than sqlfluff just living on my private github account, maybe the time has come for it to have it’s own github org (https://github.com/sqlfluff)

This is a callout for two things:

1. Feedback on how having sqlfluff/sqlfluff would impact people’s contributions to sqlfluff (rather than alanmcruickshank/sqlfluff, as it is now).
2. If we do migrate the repository, what things should we do at the same time? e.g. Should it be part of a major release? Can it happen any time? In particular if anyone has any learnings from similar migrations.
3. Would any of the more active committers want to be part of that organisation and consider becoming part of the team that can review PRs and other community activities? I’m thinking particularly of @barrywhart , @pwildenhain, @dmateusp, @nolanbconaway & @flpezet, but I’m curious for any other volunteers.

[alanmcruickshank]

@alanmcruickshank , I’d be happy to move sqlfluff-online to the new org if desired! Also pls add me if it is low cost (my contribution will be low volume for a while but i do love this project ❤️)

If you’re happy to then that would be awesome - I’ve sent you an org invite. Would you mind either adding a “contributing” section or a “contributing.md” file in the repo so that it’s clear how you want people to interact with the repo going forward? Similar to https://opensource.creativecommons.org/contributing-code/github-repo-guidelines/.

and to @nolanbconaway’s point about adding more repos to the org, I can reach out to the owner of the VSCode plugin to see if he’s interested in transitioning his repo here.

If you’re happy to, that would be great. I think that would help people discover his awesome project much more easily. I don’t want it to feel like his project is being stolen at all, and I’d still love him to continue to develop and support it. If they’re keen let me know here and I’ll drop them an invite to the org. I think they’ll maintain most of the same controls, there are two tiers of user within an org, members and owners. So far I’ve only added people as members, but I think the only thing that restricts is destructive stuff like permanently deleting repos and transfers out. Especially with public repos, they basically work exactly the same as otherwise. If they’ve got any concerns, then feel free to funnel them here - or if it doesn’t work out I’m also happy to migrate it back out of the org if it’s too much of a pain. Totally up to them.

I’ve also added the sourcecode for sqlfluff.com [https://github.com/sqlfluff/sqlfluff.com] to the org too as a private repository. I don’t think it’s where I want to direct people who want to contribute straight away, but for people who help maintain the projects we’re collecting together - I think it makes sense to collaborate on that too [although be nice about my really shoddy javascript!! 😬 ].

I’ll have a go at updating some potential roadmap items later this week so we can talk properly about 0.4.0.

[alanmcruickshank]

So… it’s done!

We now have:

• https://github.com/sqlfluff
• https://github.com/sqlfluff/sqlfluff

You can still go to https://github.com/alanmcruickshank/sqlfluff, and github will safely redirect. I’ve checked issue assignments and it looks like everything has survived the transition. Can the people on this thread do a quick sanity check that everything seems to still work on their side?

I’ve also added the people who volunteered on this thread to the organisation. 👍

I totally hear the questions around what we need to crack before the next major milestone. I’d like to firm that up in due course. I think a good way of doing that might be the “projects” feature of the new org. Unless anyone has any other good ideas for doing this?