Skip to content
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

Update homepage to point to guideance for our core expected user groups #873

Closed
abarciauskas-bgse opened this issue May 24, 2022 · 9 comments
Labels

Comments

@abarciauskas-bgse
Copy link
Contributor

My current assessment of who the core users of Pangeo might be:

  • For scientists (Guide for Scientists — Pangeo documentation) - This already provides a general “set of options for scientists” - contribute a package, explore the gallery
  • For systems admins: How to create and manage a pangeo environment on HPC or cloud (zero to jupyter hub) - Should we maintain and update these guides?
  • For data scientists/data engineers: How to create a Zarr dataset and upload it to the cloud (Pangeo and Data) - Should this become a reference to pangeo-forge documentation?
  • For data scientists: How to use existing pangeo cloud federation environments

If we agree these are the main groups I think we determine which guidance we should link to or create and open an issue to refine or create that page and make sure it's up to date, and add those "quick links" to the home page

@rabernat
Copy link
Member

I like the idea of breaking down different personas of people accessing the website.

My current assessment of who the core users of Pangeo might be:

Even "core users" might be too restrictive. I think there will be people accessing the website who are not users at all, but rather might want to just get basic information.

The groups you have outlined seem to have quite a bit of overlap. What's the difference between "scientist", "data scientists / data engineers", and "data engineers"? I know many people who might identify with all three. I would probably break it down as follows:

  • General interest, non-technical audience
  • Pangeo "users":
    • Domain Scientists
    • Data / ML Scientists
    • Data Engineers
    • [Might be useful also to single out "cloud users" vs. other users somehow]
  • System admins

@abkfenris
Copy link
Member

What about structuring around types of tasks or problems?

I want to:

  • work with cloud hosted datasets
  • scale my analysis (maybe split between pandas/xarray and ML)
  • get access to Pangeo
  • make a dataset easier to access
  • setup a Pangeo style environment
  • find out who's fault this is get a general overview of Pangeo and who is involved

That gets away from people choosing 'I am XYZ user' and not finding the right info, in addition to avoiding the battle of 'what is a data scientist'.

@RichardScottOZ
Copy link

and there is the systems problem of 'solve the politics of getting this started'

@abarciauskas-bgse
Copy link
Contributor Author

@abkfenris I like this breakdown of tasks and structuring the guides around tasks. It seems like we can either move forward with the set that you have proposed and/or discuss further which ones should be included.

I think I would also add: See examples of what others and I can do with Pangeo (which links to the pangeo showcase)

Should we prioritize this list? I'm inclined to starting with some of the low-hanging fruit / most beginner friendly:

  • get a general overview of Pangeo and who is involved
  • see examples of what others and I can do with Pangeo
  • get access to Pangeo

Then

  • setup a Pangeo style environment
  • work with cloud hosted datasets
  • make a dataset easier to access

Finally

  • scale my analysis (maybe split between pandas/xarray and ML)

@github-actions
Copy link

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Jul 31, 2022
@github-actions
Copy link

github-actions bot commented Aug 8, 2022

This issue has been automatically closed because it had not seen recent activity. The issue can always be reopened at a later date.

@paigem
Copy link
Contributor

paigem commented Sep 4, 2022

Reviving this issue after @abarciauskas-bgse and I had some discussions + hacking today!

Please see #878 for details

@paigem paigem reopened this Sep 4, 2022
@github-actions github-actions bot removed the stale label Sep 5, 2022
@github-actions
Copy link

github-actions bot commented Nov 4, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@github-actions github-actions bot added the stale label Nov 4, 2022
@github-actions
Copy link

This issue has been automatically closed because it had not seen recent activity. The issue can always be reopened at a later date.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants