-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Priorities for discussion & setup for the organization #3
Comments
Code of conduct |
Contributing guidelines |
Logo design (ok for now? compete proposals? volunteers? ideas?) |
A registry repo (do we want one early on? can wait?) |
Periodic telecons (how soon? how often? format?) |
Discourse channels (now? later? how many? names / scope?) |
To justify my votes: I love logos, I've designed four of them by now, most in collaboration by cormullion. Have a look and tell me what you think: if you like them I can try to hack something for here. https://juliadynamics.github.io/JuliaDynamics/ (6 logos here) https://github.com/JuliaMusic (the org logo) I think registries are extremely important, given how many things are now in a highly unstable manner and thus should not be used in serious scientific contexts. I like the idea of sort, lets say monthly video calls. One to two hours per month seems to be a good medium ground. For the code of conduit, I never found it important. I think we are welcoming enough as people that we don't have to write it in a piece of paper as if the lawyer of our institute forced us to... (I hope I don't raise too many eyebrows here :D ) For the rest I don/t have plus/minus. |
Regarding the Discourse channels, since there is already a Geo domain that has this topic description:
And this domain is not overly crowded, I'd say lets just use that? In the About the Geo category wiki post I just added JuliaEarth and JuliaClimate as two other relevant organizations, feel free to edit it more. |
Telecons would be good once in a while, I agree! At least we'll get to meet each other all at the same time instead of having all separate convos scattered around, and we'll be able to get everyone on the same page. Registry repo/website/logos should wait imo until we've gotten more stable versions of the current repos in the organization, then we can go wild with publicity, etc. |
I would love to have some example notebooks that show how the various packages we already have can be used together. I still don't really have a good sense of what all of these packages people are referencing do and definitely have no idea how they fit together (if at all?) and if there are any redundancies (whether good or bad). |
Good point about notebooks. I'll try to cobble together some examples for ClimateEasy and ClimateSatellite over the next week before school starts. |
The idea of notebooks is perhaps a good starting point. We know the package by name but not necessarily used them!
|
I could move https://github.com/gaelforget/GlobalOceanNotebooks to the org -- these are meant to illustrate the use of MeshArrays (C-grids), NCTiles (tiled netcdf), and compute ocean transports to machine precision (OHT, streamfunctions). I am working on additions in the near future, which could include e.g.
The repo scope could also later (or now?) be extended to cover more of the Julia climate stack (see #2) if there is interest in doing that? |
That we be quite relevant imho! |
Do you mean our own JuliaCimate registry, separate from the general registry (https://julialang.github.io/Pkg.jl/v1.1/registries/#Adding-registries-1) ? If, yes, it is unclear what the advantages are. I think that the package there would loose significantly in visibility. The maintenance burden can be quite high too and it is unclear if the github bots also work on a separate registry. |
What about showing the 3 main components of the climate system: atmosphere, ocean, land reusing the 3 colors of the julia logo? |
Anyone with some artist skills? |
Dare I tag chief logo officer @cormullion to see if he would be up for it? |
I’m always happy to help! I’ll make a start soon. 😂 |
Awesome! 😄 |
I like the general intention! I'm wondering how possible it is to have the "flow" more dependent on the system? For instance, air is pretty turbulent, ocean less and land is "almost" static. I don't know if this idea is adequate once executed artistically though! |
:) It's always worth remembering that icons and logos are rarely accurate depictions of anything in reality - their job is to be a simple, distinctive, memorable, and eye-catching image that's generally in harmony with the project There's often no literal depiction of any reality - Julia's dots, Apple's apple, Google's er, whatever... At least this is symmetrical at the moment, which is nice. I can play with the parameters if you think it's worth pursuing. |
Could you try rendering it with a few less lines (maybe half)? Looks great! |
Maybe the background could be white (or close to white) instead of dark grey? But loving it! Edit: I took a vectorstock of a hurricane and recolored it just for fun. Not sure if it's allowed, but I kinda like the end result so just dropping it here. Original image was taken from vectorstock. Edit 2: I'm enjoying this too much for my own good, so I made a spinner. |
@cormullion Awesome job! I'd love to see the same as the last one but with the less organized flow that you had first, with thicker white lines too. I liked it because it hints at some convergence/divergence while the last one looks more organized and IMHO too laminar (not sure this is the correct term here). I apologize if asking all this is a pain for you, I just find them really cool! BTW do you generate these with Julia only? If yes would it be possible to see the code, too? |
No problem. Remember, these aren't diagrams! 😂🤣😅 source: https://gist.github.com/cormullion/b212622d4e92d26596ea800ce7753272 |
Thanks @cormullion for these awesome logo drafts. I kept scrolling down in the discussion thread and getting more and more excited by this! Might just suggest a couple tweaks to the last one above: (1) rm the outer ring and (2) reorder the color. Like this: https://gist.github.com/gaelforget/4744a63b86f74362a71a89d27de44c90 About the colors ordering: I feel this one a bit more natural & loosely representative of the stacking of climate system components. (to me red could thus be thought to represent e.g. earth / geology / mantle, green as land or ocean ecosystems, blue as either ocean or atmosphere, purple as the night sky / space) About the outer ring: I find the logo more aestetically pleasing without it, and I like to think of earth as an open system (there is no lid between atmosphere and space; eg material or radiation can go in and out) |
Looks good to me! |
Awesome! |
Please take a look at GlobalOceanNotebooks. For now it's centered on packages that I know best but hopefully this is already a useful start. Should work in I hope to keep moving this notebook folder forward over coming weeks probably with a focus on stuff I have been doing with databasis frameworks (e.g. erdapp, Pangeo), analyses frameworks (e.g. climate tools , esdl), and numerical models (e.g. climate tasks, mitgcmtools) |
Since it seems that we have broad agreement on the logo design I will swap it in place of the placeholder enso plot. Thanks to all for such efficiency! Later today I will try to send a PR to the meta repo incl. png, gist link, & credit to @cormullion + @JuliaClimate community for the design (in meta/readme.md) |
definitely a team effort - |
Quick update. Did more work on this recently to streamline the following notebooks which I just ran without issue on :
and
The rest of |
In addition to #1 & #2 there might be other obvious things that you should be discussed in priority or asap.
Candidates may include:
Happy to open issues for each one of of these but seems better to let everyone weigh in on a priority list first. Please consider giving +1 or -1 to individual items below and add more items?
The text was updated successfully, but these errors were encountered: