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

Understanding the reason for an instruction #110

Open
Temidayo32 opened this issue Oct 18, 2021 · 6 comments
Open

Understanding the reason for an instruction #110

Temidayo32 opened this issue Oct 18, 2021 · 6 comments

Comments

@Temidayo32
Copy link

Temidayo32 commented Oct 18, 2021

What does the current documentation state?
Screenshot_20211018-081338

Where is this stated?
This is a link to the page where the issue is raised from

Why do you want to improve the statement?
The need to improve the circled section of the page hinges upon a need to better understand why the instruction required of the user of the doc was given. That is, answering the question on, "why the user should make sure to have checked out to the develop Branch for the FLINT Installation?"
What is the reason for this requirement here? What is the implications of not taking the required action?
I strongly believe this is a knowledge gap that needs to be filled in to create better documentation and satisfy users' innate need to understand why they have to take a step.

Proposed statement
The proposed solution, hence, is to state clearly the reason for the action requirement, alongside possible implication of not taking the step.

@Temidayo32 Temidayo32 changed the title Understanding the reason for an instruction LUnderstanding the reason for an instruction Oct 18, 2021
@Temidayo32 Temidayo32 changed the title LUnderstanding the reason for an instruction Understanding the reason for an instruction Oct 18, 2021
@Mohitkumar6122
Copy link

Mohitkumar6122 commented Oct 19, 2021

@Knowledgeissweet, that's a good catch!.
Since the develop branch is the branch where all the latest technical changes are merged into ( code enhancement, adding new features or removing dead code etc) by the developers. So in terms of the latest branch (in terms of technical aspect), the develop branch is the best to work with.
Also, the modules are all written to work with the develop branch of the FLINT and any actively maintained branches will work with the most recent version (and are broken with old enough builds of the FLINT).

Maybe we can include it in the documentation.

Tagging @chicken-biryani, @HarshCasper, @shubhamkarande13 for more insight into this!

@shloka-gupta
Copy link
Member

@Knowledgeissweet that's a great suggestion.

Maybe one or two lines would be enough.

Something like:

'Make sure you've switched to the develop branch since it consists of all the latest changes.'

Or something similar.

@King-kay
Copy link

King-kay commented Nov 1, 2021

@HarshCasper , something I can do??

@King-kay
Copy link

King-kay commented Nov 1, 2021

" Make sure you've switched to the develop branch To be updated, it consists of all the latest changes." @chicken-biryani does this suffice?

@shloka-gupta
Copy link
Member

@King-kay yep. Sounds reasonable!

@King-kay
Copy link

King-kay commented Nov 2, 2021

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

No branches or pull requests

4 participants