-
Notifications
You must be signed in to change notification settings - Fork 13
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
Prepare a comprehensive tool list #14
Comments
Hey @bkamapantula, Should we need to add more tools apart from the ones in google sheet? |
hi @nirmaljeffrey! the list has been expanded since I created the issue. I'll check with the team tonight and share an update here in ~6 hrs |
hi @nirmaljeffrey, the current list is more of a guideline and not necessarily a comprehensive one. Sorry for the late response! Please go ahead create a PR. We can periodically update it. |
sure @bkamapantula will raise it by today. Can you also please mention the location where I should add this readme file in this repository? |
Thanks! Is it possible to add it in the Wiki? Not sure if it's version controlled though. If it isn't, adding under |
https://docs.github.com/en/communities/documenting-your-project-with-wikis/viewing-a-wikis-history-of-changes - github wiki is version controlled. It will be the correct place for adding all these docs that we have in google sheets. @bkamapantula I'm unable to create a wiki. So can you please create a wiki for this repo? , so that I can clone and raise a PR for tools list. |
@bkamapantula, I'm unable push my branch to remote. please check. It looks like i dont have permission. |
@bkamapantula, If I don't have the access to the repo, should I need to fork this repo and raise PR? |
I think it's a permission issue, I can't add you as a developer (I don't have access). can you please fork and raise a PR? |
i see, please create it in your repo and share the link here, I'll create. for subsequent edits we can use this issue thread. |
I will share the updated markdown file. please add the file to the remote repo. whenever an edit is requested, I will share the updated markdown in this issue thread. is that fine for you @bkamapantula |
looks good, thanks @nirmaljeffrey! |
@bkamapantula in this markdown file, I just copied the items from google sheets. But I didn't do any changes as of now. If I add images, will there any copyright issues? and also If i add links to amazon or flipkart or other online sellers, will there be any problem? Am I allowed to add images and add links? |
images and links are fine, no problem. |
Also, it would be great if developer access are given to all and merge access for master branch can be restricted to maintainers. So that everyone can raise PRs. Atleast this will be a problem for people who wants to contribute for wiki. |
agreed, @Anool -- please review on the dev access when you get a chance. Wiki is live: https://github.com/MakersAsylumIndia/M19_OxiKit/wiki/Lab-tools-list thanks much @nirmaljeffrey! |
@bkamapantula, Glad to help. Ping me if anything is required in git. will spend my free time to contribute to this project. |
How to get involved in M19 Initiavite as a FY student Mechanical |
closing this issue as the tool list is live on Wiki. |
hi @Hemant-Git911, please register your interest with us: once your details are in, we will reach out on how to get involved. thanks! |
Can I add you folks as "maintainer", or will you need higher access levels? |
@Anool, it's not required. The problem is with wikis. |
yes for non-wiki contributions, contributors can use the fork + PR approach. for the Wiki contributions, we could do that or (if it looks complicated to set up) use the Issues + discussion + maintainers adding to this repo. |
For new labs, we need to identify a comprehensive tool list. Here's a preliminary draft:
https://docs.google.com/spreadsheets/d/1DynT9Mh8jcV9qHxwFuQxj1fcQQHj_v_ymwpoZD1L23g/edit#gid=1782181776
Note: this is posted here from the FAQs sheet post discussion on 2nd May.
Please identify an assignee.
The text was updated successfully, but these errors were encountered: