June 8, 2012 at 15:25

GitHabr: His collective Habrahabr with blackjacks

    First dive

    imageI decided to start studying the distributed GIT file version control system from the Github web interface . Moreover, I was primarily interested in such a theoretical opportunity: participation in the collective development of some small (but very responsible) project, without the need to install any additional software, limited to only a web interface accessible from any browser, and, be maybe with the built-in Notepad (for more comfortable editing of the source code).

    Hypothetically, the entire project could be a single source code file, so that anyone can always access it, and also, after making changes, could send a request to the project manager to add the corrections made to the main one (or the alternative) project branch.

    Disclaimer

    I am not a real programmer, because I have never used in my work either a collective development environment, or a version control system, or automated testing tools for my projects, not to mention that I did not keep any working documentation (with the possible exception of the most trivial comments inside the code).

    Clearance in Laziness

    But, Now, the time has come when I began to realize how much I was deprived, and how limited my ability to create a truly high-quality product.
    My choice fell on Github.
    Registration at Github is not just simple, but very simple:

    Github

    https://github.com/signup/free
    Username: githabr
Email Address: githabr@github.com
Password: *******
Confirm Password: *******

    By the way, during registration, you can also specify a fictitious E-Mail address, since it is not checked in any way, and no confirmations and no mailings are sent to it. The main thing is that it be globally unique within the git hub.

    Next, just as easily, create a new repository for the project:

    Githabr

    https://github.com/new
    Repository name: habrahabr
Description (optional): Хабрахабр
[x] Initialize this repository with a README

    Installing the last checkbox will allow you to automatically insert a README file with mark-down markup into the project.

    Wikihabria

    https://raw.github.com/githabr/habrahabr/master/README.md
    habrahabr
=========
Хабрахабр

    By the way, this file is then easily edited directly on the site through a web form.

    Having seen such an opportunity, I quickly noticed that in this way it is possible to publish the source texts of draft articles, which are planned to be published on Habr.
    It’s the same, and, after publication, it will give an opportunity to anyone who noticed a typo or inaccuracy in the text to immediately fix the fix so as not to litter in the comments and not write in PM. Moreover, such an opportunity will be available to absolutely any habrayuzer, including Read-Only contacts (which do not have the ability to send comments or write in PM), thereby opening up much more opportunities for further improving the quality of published material.

    In fact, I propose to translate all habrapublication in open source.

    By the way, such a question: how can you, in principle, on Habr, show your draft article to a specific person (and, ideally, I would just like to open it to my friends from the list of added friends) before publishing it? Well, do not do screen shots of the preview in the actual case!

    My proposed approach with sharing sources allows solving the problem of previewing by simply “feeding” the shared code to Habraparser, for example, through the same web interface of the Habr sandbox.

    So, now let's try to upload something to the git hub:

    Loading

    https://github.com/githabr/habrahabr/downloads
    Upload a new file
<> Choose a new file: c:\githabr\1.txt
Short Description: test

    All. Now the file is available to the whole world:

    http : //cloud.github.com/downloads/githabr/habrahabr/1.txt

    By the way, at the same time it is distributed over HTTP (and not HTTPS), which has its advantages in some cases.
    HTTP/1.0 200 OK
x-amz-id-2: 9CR8MvvocEfjYL/99TjOf2yPogURMenmPl/SVTfDwS8ForBAZ1+ahMY1BH3bm+LJ
x-amz-request-id: D7AAFEFF905C59E4
Date: Fri, 08 Jun 2012 10:32:58 GMT
Last-Modified: Tue, 05 Jun 2012 10:27:01 GMT
ETag: "9fe7b2cc8b758cb05cd9dfbae8a825bb"
Accept-Ranges: bytes
Content-Type: text/plain
Content-Length: 443
Server: AmazonS3
X-Cache: Miss from cloudfront
X-Amz-Cf-Id: 0zpTMVSKtrVzBYTgxYS1RKFeVmcmHfj7a2LCIKwW3tvNK66tYhSN_w==,LQ9Uc46keGuXp2jnljH0SlmgtKFjenOn17raP2sYQckYh2fNg3HP2Q==,s7ibZDVHTSpJ0oGasHniYoU4QomnmfJ2x-3prHbYWfO4yi9PaGvgIQ==
Via: 1.0 c1639d907cade557ebff29e5be78b0b6.cloudfront.net (CloudFront)
Connection: close

    This file is displayed in the
    Manage Downloads section.

    And, everything seems to be chiki-bunches, but one thing is not clear: the file downloaded in this way ended up in the “cloud”, and not in the “master branch”. That is, unlike a README file, for some reason I don’t have the ability to edit it just as easily through a web form.

    Well, oh well: for this post of mine http://habrahabr.ru/post/145302/ I also uploaded the source to the cloud:

    http://cloud.github.com/downloads/githabr/habrahabr/145302.txt

    What next?

    Then I do not know what to do. Can someone tell me good advice?
    Now I need to somehow be able to attach this downloaded file to the workshop branch, and to give the opportunity to update it to anyone.

    References

    How to get started with GitHub: quick start
    Tags:

    Also popular now: