-
Notifications
You must be signed in to change notification settings - Fork 36
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
Docs/add studio to readme #549
Conversation
Updates the main readme with information on how to get started with FEDn Studio.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, good and clear description.
For the part "Develop a FEDn project in a local development environment, and then deploy it to FEDn Studio"
We can make two branches:
1 - FL Data Scientist path -> All-in-one to more FEDn SDK
2 - FL Production FL -> All-in-one to FEDn Studio
Strong points of this approach:
- Will show the depth
- Make it more clear based on the different roles
Weak points of this approach:
- May be confusing and lengthy
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it's a good improvement!
A couple of thoughts though:
- Maybe we should get rid of the top logo in favor of the new one (we could perhaps "draw" it our selfs in the README to make it look "tech")? Also the logos (contributions) in the bottom could be better arranged and the Scaleout one is old...
- Do we need to mention Pytorch in the Quickstart section or could it simply say Getting started or Quickstart? Also I am still not thrilled about the term SDK. For med FEDn is first and foremost a framework.
- The link to the FEDn Studio docs will change soon. Don't have to wait for it though...
Description
Add more information about FEDn Studio to main readme.