Open Source Hardware

Open Source Hardwarehttps://community.element14.com/technologies/open-source-hardware/What is the connection between Open Source Hardware and traditional engineering companies. How can professionals & hobbyists learn from each other. What can hardware developers learn from Open Source Software.en-USTelligent Community 12<link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=4fb3fdcd-fdcd-405f-a840-1bb44e6cca7e</link><pubDate>Tue, 16 Jun 2026 17:59:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:4fb3fdcd-fdcd-405f-a840-1bb44e6cca7e</guid><dc:creator>shabaz</dc:creator><description>Even if I don't have a proper strategy, and am just working on a small personal project, bits of the process can be followed minus the development branch. For example, I have a small project in my own repository, I know no-one else is working on it, and I only have a main branch. This would be the situation at the start of a lot of simple projects I imagine. On the PC, I had done a git clone to obtain the repo contents, and directly made and tested some code changes which have essentially ended up implementing a new feature. How can I get those changes into the repository? I decided to create a feature branch after the fact that I had already worked on the feature, and merge that into main. You'd never do this for a real project where you'd want the ability to test multiple features before putting them into main; for that, you'd need the development branch to test an entire combination of new features thoroughly before merging into main. But this is my small project, I'm the only coder and tester, and I only want to merge one feature that I have tested (both feature and integration, since there are no other features to be integrated), and I'm not creating releases (so far!). I did this: git switch -c feature-acmeas # create and switch to a branch called feature-acmeas git add . # prepare/stage the files for commit git commit -m "Add AC measurement functionality" git push -u origin feature-acmeas # publish your feature branch to the remote (origin) Then, I went to the GitHub repo web page, and clicked on Pull request, and created that as described in the blog post, requesting a merge into main, from the feature branch. I clicked through to perform the merge. Finally, to delete the feature branch: git checkout main # get away from the branch that is to be deleted git pull # update the view with the latest from the origin git branch -d feature-acmeas # delete the local feature branch git push origin --delete feature-acmeas # delete the branch at the origin All done!</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=b9f1ef67-88d7-4748-820e-f62df4ec2f27</link><pubDate>Tue, 09 Jun 2026 04:32:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:b9f1ef67-88d7-4748-820e-f62df4ec2f27</guid><dc:creator>balajivan1995</dc:creator><description>All I wanted to say is to include the image you've captured above in the 4th step as an additional information. "You may be prompted to login to GitHub platform to push the changes for the first time". That's it. Guess I should've been clearer.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=14f5dfd8-c793-45ff-b46f-040d030e3e71</link><pubDate>Tue, 09 Jun 2026 03:12:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:14f5dfd8-c793-45ff-b46f-040d030e3e71</guid><dc:creator>shabaz</dc:creator><description>Sorry, I still don't get your point. If credentials are required you'll be prompted for them. Is it the case that you're concerned that a user may find it unexpected to see slightly different output whereas the example didn't show a prompt for credentials? If that is your concern, I think it's a minor issue, simply because I think users will not find it too unexpected nor unmanageable by themselves, that output can be slightly different - I cannot be expected to show the precise detail for every eventuality, nor would I want to. Outputs change and precise command line output can too, over releases. I expect people to use their own judgement at times, especially when there is a lot to go through and they may be using different versions of software and different operating systems too. I have tried to understand where you're going with this, but it makes no sense to me. I tried destroying my credentials and re-running the commands, and I see a very unconfusing request to sign in: As mentioned, this is sufficient to get through the blog post with GitHub specifically - it's in the title. Any more detail regarding credentials is not within the scope - and I'm OK with that, because I don't see any further detail on this topic in other tutorials either, e.g. the one in Code magazine that I referred to. How about this - since I genuinely still don't understand your precise concern, please create a blog post showing the detail that you think readers require to follow the blog post, and if you provide a link to it, people will be able to navigate to it if they do indeed get stuck, and it will be appreciated a lot.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=fd5a4229-b73a-4d20-81b8-7f4165767a9e</link><pubDate>Tue, 09 Jun 2026 02:34:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:fd5a4229-b73a-4d20-81b8-7f4165767a9e</guid><dc:creator>balajivan1995</dc:creator><description>Git doesn't ask for authentication either after installing or during first usage. It'll ask for username and an email ID when user try to commit some changes. Authentication is required when we clone private repo which we have access to, or pushing the changes to remote first time - regardless of whether it's a public or private repo. Git doesn't need authentication to clone a public repo or to make local commits. I thought this might be worth adding considering people who are new to GitHub might be new to git in general as well, and this might be the first time they will configure git to use with remote repositories.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=0dd16a0d-ef4c-48e6-ba40-d7e79c0e0a41</link><pubDate>Mon, 08 Jun 2026 17:45:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:0dd16a0d-ef4c-48e6-ba40-d7e79c0e0a41</guid><dc:creator>shabaz</dc:creator><description>I think that's fairly unlikely to occur for someone following the blog. There's a link to installing Git, and it will ask for authentication (either after install or when first used). At least, for Windows, it did (I have not tested on Linux recently, but I believe it would be the same). It would increase the blog post a fair amount to start adding credential related material. I think that's very much beyond the scope of this blog.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=bbbff81f-c658-48c9-b97b-f68ca7af97e7</link><pubDate>Mon, 08 Jun 2026 17:28:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:bbbff81f-c658-48c9-b97b-f68ca7af97e7</guid><dc:creator>balajivan1995</dc:creator><description>No, that's not what I intended to mean. If someone wants to work with a remote repo, they need to provide authentication. This blog does not cover how to use either ssh or PAT to connect git for windows to GitHub. Without that information, even if someone new to GitHub and git in general has created a public repo, they can't push their local commits.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=742a2cf5-5ba4-496b-be57-93b8a246aa1f</link><pubDate>Mon, 08 Jun 2026 17:19:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:742a2cf5-5ba4-496b-be57-93b8a246aa1f</guid><dc:creator>shabaz</dc:creator><description>If you don't wish to start again (but this time with either your own repo, or one created from a fork), let me know your GitHub username, and I'll add you as a collaborator to project1</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=34432f22-ce7f-4f15-805b-43930aba1337</link><pubDate>Mon, 08 Jun 2026 17:18:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:34432f22-ce7f-4f15-805b-43930aba1337</guid><dc:creator>shabaz</dc:creator><description>I guess you're using my project1 repo, and not creating your own, right? In that case you're right, there will be this difficulty (and it would normally be avoided if a fork of the project was first done, so that you're using your own repository URL). I was in two minds whether to suggest people use my repository or create their own. Thanks for pointing it out, I'll add a comment mentioning it's best to use a fork if using my repository, otherwise they'd need to be added as a collaborator.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=2b9457b3-596f-4d45-ba58-85611cec4144</link><pubDate>Mon, 08 Jun 2026 16:54:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:2b9457b3-596f-4d45-ba58-85611cec4144</guid><dc:creator>balajivan1995</dc:creator><description>If the repo is private, cloning the repo will require authentication as well.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=58c2885a-b8e7-4d7d-8927-f2d7872a27c5</link><pubDate>Mon, 08 Jun 2026 16:47:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:58c2885a-b8e7-4d7d-8927-f2d7872a27c5</guid><dc:creator>balajivan1995</dc:creator><description>Nice write up. But something seem to be missing and it took me a while to realise the part where git asks for password to push local commits to remote branch is missing.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=72ff39b8-a9ad-4d3d-8fe1-4ed5ac1a0c0e</link><pubDate>Sun, 07 Jun 2026 23:11:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:72ff39b8-a9ad-4d3d-8fe1-4ed5ac1a0c0e</guid><dc:creator>kmikemoo</dc:creator><description>shabaz I like the diagram. The write-ups do an excellent job of describing the process. The picture just pulls it all together at a glance. Well done!!</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=7e032200-8739-4b8d-90be-e0af72202d76</link><pubDate>Sun, 07 Jun 2026 19:58:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:7e032200-8739-4b8d-90be-e0af72202d76</guid><dc:creator>DAB</dc:creator><description>Very good post.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=f53eca20-6797-470a-a16e-d60428da25bd</link><pubDate>Sun, 07 Jun 2026 17:11:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:f53eca20-6797-470a-a16e-d60428da25bd</guid><dc:creator>shabaz</dc:creator><description>Just added the following diagram to help follow things. I hope it's correct, but if anyone spots any error, please let me know!</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=40f8afe4-0122-4a60-8a6b-d5e73376d5b6</link><pubDate>Sun, 07 Jun 2026 17:10:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:40f8afe4-0122-4a60-8a6b-d5e73376d5b6</guid><dc:creator>shabaz</dc:creator><description>Hi Gene, Thanks for the comments! As I understand, even the professionals are sometimes a little rusty about all the steps, especially if not done themselves regularly enough. Same as you, I used CVS for quite a while, I liked it was easy-to-use. However for many subsequent projects, we used IBM ClearCase (powerful system, but complicated; however scripts were created to simplify things for engineers, they didn't need to remember all the minute command-line detail). But nowadays Git is key to so many projects.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=1d438abf-7176-4954-a239-195f01efef1d</link><pubDate>Sun, 07 Jun 2026 15:35:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:1d438abf-7176-4954-a239-195f01efef1d</guid><dc:creator>genebren</dc:creator><description>Thanks for the great explanation! I have used Git in the past, but I am still rusty on all the ins and outs of the process, so this was a great review. Having started my software development on Unix environments, I have had a lot of experience using CVS. I have also used SVN (tortoise) on PCs, but I was never very impressed with that environment. I can see a lot of value in starting to use Git for my internal software development, so I have bookmarked this post to refer back to it when I am ready use it. Thanks for sharing this with the community!</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=30d11ed9-d59b-4d59-a9b8-6764368f89c9</link><pubDate>Sun, 07 Jun 2026 15:34:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:30d11ed9-d59b-4d59-a9b8-6764368f89c9</guid><dc:creator>shabaz</dc:creator><description>Hi Mike, Thanks!</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=db811422-c26f-429c-8666-2ca6e3eb091c</link><pubDate>Sun, 07 Jun 2026 02:31:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:db811422-c26f-429c-8666-2ca6e3eb091c</guid><dc:creator>kmikemoo</dc:creator><description>Great information! I may never get to this level, but it's noce to know that this guide is here if/when I need it. Thanks!</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=8c98b678-44af-459e-9833-0add6dfc68fe</link><pubDate>Sun, 07 Jun 2026 00:14:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:8c98b678-44af-459e-9833-0add6dfc68fe</guid><dc:creator>shabaz</dc:creator><description>I hope you find it useful!</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/github-for-professional-beginners-from-first-repository-to-first-release?CommentId=515f86c0-da1c-44c0-9a61-eb94825ea1d6</link><pubDate>Sat, 06 Jun 2026 17:03:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:515f86c0-da1c-44c0-9a61-eb94825ea1d6</guid><dc:creator>manojroy123</dc:creator><description>Very Interesting. I was looking for such Beginners guide t GitHub.</description></item><item><title /><link>https://community.element14.com/technologies/open-source-hardware/b/blog/posts/building-a-transistor-audio-preamplifier?CommentId=e489392d-bdd8-4c53-a5f9-1ad8a8283d44</link><pubDate>Sat, 06 Jun 2026 12:23:00 GMT</pubDate><guid isPermaLink="false">93d5dcb4-84c2-446f-b2cb-99731719e767:e489392d-bdd8-4c53-a5f9-1ad8a8283d44</guid><dc:creator>shabaz</dc:creator><description>Interesting.. I might have that book, I'll take a look to see the charts. I'm away from desk for most of the weekend but will try to give it a shot with the SDK hopefully next week. In the past I deliberately built for 32-bit so it would work with new and old versions of Windows. (Not tried the SDK with Linux or Mac yet).</description></item></channel></rss>