Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 5 years ago.
Improve this question
I am really thinking of how I can build a very minimal Git-like software only for my self for now!
I have gone through Git documentations and even the way git works and I have quite an understanding on it.
Is there any example for me to study as a bonus before I dive into this project?.
In addition to the Documentation/technical folder which explains the internals of Git, you can study how Git was re-implemented, as an exercice, in other languages.
See for instance:
in Go the project src-d/go-git (recent 2018),
in Javascript: danlucraft/git.js (much older),
In Javascript (more recent 2015): Gitlet.
In Java, the project eclipse/jgit (used by EGit)
In C (with a lot of bindings for other languages), LibGit2 (and its GitHub repository, apologies to Edward Thomson for not mentioning it first.)
Related
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 2 years ago.
Improve this question
I would like to display a code snippet from my own public GitHub source repo in my own web site, without having to make a copy. This is for a tutorial to illustrate some programming concepts. So not to run it but to pretty print it, as it were.
I bet this is something that many people need. I am looking for a lead on how to do this.
You could use the GitHub API to accomplish this.
See the Get Contents endpoint.
Yes, you can do that either by publishing your repo on npm and then referring it as npm dependency in projects package.json.
or 2nd , you can directly refer GitHub repo as dependency in package.json.
Hope this gets you in right direction.
thanks
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
Lately i have been using Notepad ++ and i was wondering if any of y'all would recommend a different platform that would allow me and another person to code on the same project at the same time?
I like using Sublime text.
It's very lightweight and extemely versatile :).
You can install alot of free very creative plugins to help you coding too including some SVN plugins.
To share your code another way i guess you could use something like github or tortoise SVN too.
To work on thesame file online i recommend collabedit.com (Online editor for multiple users)
Good luck
Er, well, you could try Vim or Aptana Studio or Net Beans?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I am involved in a project which is meant to eventually become open-source and have a code contributor community. Is there any "right" way of doing this and what should/can I expect?
Thanks
There's a pretty good book on this topic, Producing Open Source Software by Karl Fogel, which is available for free online or in dead tree form if you prefer to read it that way. It would be hard to expand much on it in a single answer. Every project will, of course, be different, so I'd recommend reading that book, and then asking more specific questions about your particular project; answers will depend on the language and platform you use, how active an open source community there already is in your area, what your business model is, and many other factors.
I would recommand using Github or Google Project Hosting (subversion/mercurial), and of course use social media network to promote the project helps too.
You can start something like this - http://wxwidgets.org/develop/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 9 years ago.
Improve this question
You can see lots of briliant ideas in Open source projects. How authors found these ideas whey they don't exist yet?
Should I learn software dynamics, history and trends(Nothing new under the sun?) for that?
I don't want to start another github project called "API to xyz". What should I do??
Scratch an itch. Find something that you feel is a problem or annoying and write some code to solve that problem. Chances are you aren't the only person who is affected by that particular problem.
I believe a lot of software projects, open source or not, start as someone identifying a demand and working to supply it.
Think you're not satisfied with wherever photo management apps you found. Starting (or forking an existing one) with your needs in mind is an option.
What kind of software you would like to use but can find one that suits you? If yours needs are more or less supplied by already existing applications, why not working on improving one you like most?
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
When I browse github I have a hard time differentiating high quality code from half-finished crap without taking a serious look at the code. What are some good ways to quickly size up a project? Rubyforge allows people to designate a "Development Status". SourceForge has a "recommend" feature. Is there some feature that I've overlooked? I just look at the number of forks and watchers. Is there a better way? I don't see a checkout count, or any other measure of popularity.
I would check for documentation. Well advanced code should have associated documentation, while fledgling projects are too busy getting their code and architecture done to create documentation, which will probably have to change by the time they release anyway. Basically, writing documentation says to me that you think the code is stable and functional enough for users to be able to benefit from it.
Recent activity is a big one. If the project does not have recent developer commits or there are open bugs, tickets, issues, questions, etc without developer responses then move on.