Moving the repo to an organization

[kdpsingh]

Dear colleagues,

I'm planning to move this repository to an organization. I would still like to retain control of merges for now (to maintain consistency and style as we grow), but I think we have enough content in the package where it's important to signal to the community and prospective users that this is now a team effort.

I've reserved "TidierOrg" for now on GitHub. "Tidier" is already taken, and its owner hasn't replied to my outreach. This would be similar to "MakieOrg" and would help distinguish the organization from the underlying packages. We could ask to join an existing organization as well but I think we will be wrapping packages across the ecosystem and thus it may make sense to keep this as a separate (but parallel) effort.

Thoughts on TidierOrg?

Cc: @pdimens @lazarusA @camilogarciabotero @rdboyes @pitmonticone @zhezhaozz

[kdpsingh]

I'm anticipating we will have at least 3 packages in the near future:

• Tidier.jl (meta-package)
• TidierData.jl (all the DataFrame-oriented macros/functions in one place)
• TidierPlots.jl (all the AoG-based plotting functions in one place)

And potentially... TidierTools.jl, which would make it easier for other folks to write Tidier-style macros.

[lazarusA]

Honestly, I think it should be part of JuliaData where also DataFrames.jl currently lives in. I feel that having another org will split the Julia Ecosystem ever further. But, that's just my opinion.

[kdpsingh]

Appreciate the idea, @lazarusA. My main hesitations re: this are:

• The package is likely to expand into plotting, which currently lives outside of JuliaData
• The package uses a non-idiomatic coding style, which I think may be better co-located in a separate org

I personally view this package as a front-end to a number of other packages (and thus interdependent w/ other packages), not something intended to split the community further.

[zhezhaozz]

• The package is likely to expand into plotting, which currently lives outside of JuliaData
• The package uses a non-idiomatic coding style, which I think may be better co-located in a separate org

Agree with @kdpsingh, Tidier is not only about data manipulation in the future, and it's more a front-end to a number of other packages. I just feel that it would be a little strange to co-locate with other packages that have completely different coding style and design philosophy.

[bkamins]

I think a separate organization is OK. TidierOrg makes sense. I guess we would make it explicit that the ecosystem is meant to make it easy for R users to make transition to Julia in as frictionless way as possible. Right?

[kdpsingh]

Thanks @bkamins. Yes, the explicit intent of the org would be to make it easier for R users to transition to Julia.

We would make sure to place a spotlight on the underlying packages we are wrapping to ensure that folks can make the transition to idiomatic Julia packages.

[bkamins]

folks can make the transition to idiomatic Julia packages

I see it as opt-in. I think many folks will be happy enough with focusing on learning TidierOrg only.

[kdpsingh]

Hi everyone, welcome to TidierOrg!