Let me start with a brief introduction of myself to FOSS. Actually, I started developing free and #opensource software with #raylib, it was 7 years ago and at that point I didn't specially care about FOSS, I just knew it was an option for soft development... 1/n
I had created several games and software in the past but it was mostly private, I actually didn't know how to make it "open source", most platforms to publish code looked quite confusing and unfriendly to me, so I hardly considered that option... 2/n
When I started #raylib development in summer 2013 I found a basic library called GLFW (github.com/glfw/glfw) to manage window and inputs, it was open source, zlib/libpng licensed. As far as I was building my software using it, I decided to use the same licensing option... 3/n
From that moment, GLFW became a reference to follow... and the first step was publishing my code on @github, a really friendly platform to publish, manage and share code projects. At that point started an amazing adventure that has lasted for 7 years now... 4/n
@github In that time I learned a lot about FOSS, actually, I looked at many open source libraries (mostly in C/C++) as a reference to build raylib, checking project organization, files/directories conventions, library presentation... I'll share some of them in the following days... 5/n
@github I'm used to put a great care to detail in everything I do and raylib was no exception. Not only on the code itself (naming, formating, comments...) but also on all the elemements that surround code sharing. I've seen many "open source" projects that fail in that point... 6/n
@github Actually, most of the time I've put into #raylib in all those years has not probably been coding but organizing and presenting all the project in the best possible way to make it attractive to the users... and one key factor is simplicity. More on that in the next days! #kiss 7/7
• • •
Missing some Tweet in this thread? You can try to
force a refresh
