Peer4Commit.com FAQ

I’m new to github commits, and thought it might be nice to have a FAQ for this site where the Bounties are available:
peer4commit.com/projects

Questions:

  1. This lists several development funds available to be claimed by people who make “commits” to a github project. How does a person know what type of changes to submit for inclusion? Is it strictly from the items available in the ISSUES tab?

  2. Does the person fork their own version of the code under github in order to contribute a patch?
    (The reason I ask, is that I saw this here)

  3. Other than the website project and android project, is this principally all C++ code?

  4. Where did the majority of these funds come from?

  5. I read that each commit is worth 1% shown. So a small commit is worth just as much as a large commit? Doesn’t this just encourage people to make frequent small commits and nothing substantial that would require a large commit?

  6. I assume the project maintainer gets final say on what gets committed. Is there any point in submitting commits to the main Peercoin project if Sunny doesn’t explicitly say what he wants?

Thanks to any one who can answer some of these. Once we get them ironed out (with any additional Q&A), we can create a proper forum post and make it a stickie.

Any commit added to the default branch of the project gets a tip.

[quote=“ppcman, post:1, topic:1779”]2. Does the person fork their own version of the code under github in order to contribute a patch?
(The reason I ask, is that I saw this here)[/quote]

If you don’t have write access to the project the best way to have your commit merged is indeed to fork it and make a pull request.

When you visit the project on GitHub there’s a colored bar indicating language statistics. It’s not very accurate but it’s a good start.

Anonymous sponsors. You can follow the donation address of each project on the blockchain if you want.

The idea is the project maintainer won’t merge commits with nothing substantial.

But the ability to adjust the tip is a feature request which I just implemented but I haven’t deployed it yet.

It may indeed be better to first check the maintainer is willing to merge your changes before you make them.

May I applaud you on the answers and thank ppcman in formulating the right questions, but even more Sigmike on getting the ability to adjust the tip based on the contribution discretion of the project maintainer.

I think that was the one thing missing in peer4commit, a fair share of the donated resources based on effort and value to the project. Hope this will be adapted by the project maintainers and they will take a minute to define a few basic rules so everyone knows what to expect in advance.

Hope this FAQ will set the right expectations for contributors and for donators on how their donations will be spend. I think peer4commit provides a nice and with github integrated scheme which I would prefer over just a bounty. A bounty would just go to a few people doing all the work. With peer4commit it will become more of a community effort and everyone can contribute to their capacity and paid accordingly and boast that they worked on one of the many projects.

With the donations we also get a sense which projects the community is keen to progress. I like it and will support it where I can.

Sigmike, can we also make use of this Reddit sticky by putting down more information about Peer4Commit?

http://www.reddit.com/r/peercoin/comments/1y1l2s/peer4commit/

[quote=“Sentinelrv, post:4, topic:1779”]Sigmike, can we also make use of this Reddit sticky by putting down more information about Peer4Commit?

http://www.reddit.com/r/peercoin/comments/1y1l2s/peer4commit/[/quote]

You mean I should add these questions and answers to the reddit post?

[quote=“sigmike, post:5, topic:1779”][quote=“Sentinelrv, post:4, topic:1779”]Sigmike, can we also make use of this Reddit sticky by putting down more information about Peer4Commit?

http://www.reddit.com/r/peercoin/comments/1y1l2s/peer4commit/[/quote]

You mean I should add these questions and answers to the reddit post?[/quote]

You should add anything that might be helpful to newbies. A description of Peer4Commit might also be helpful for those who don’t know what it is. The description will give them a reason to click on the website link. Actually, what might drive even more donations and traffic to the website is if you created a more descriptive thread title. Instead of simply Peer4Commit, it should be something like the following…

Peer4Commit.com: (Donate to Peercoin Projects - Get Tipped for Making Commits)

Everyone visiting the subreddit will see that and immediately know what it means. Right now people might be glancing over it without a description in place. I know I did for a while. It should help drive more activity and donations to the website.

Great idea Sentinelrv! Helping to tweak the one-liner:

Peer4Commit.com: (Donate to Peercoin Projects / Earn PPC for code commits)

Peer4Commit.com: (Donate to Peercoin Projects or Earn Tips for contributing code)

Peer4Commit.com: (Donate to Peercoin Projects / Programmers get compensated)

Peer4Commit.com: (Developers get paid, Donators to Peercoin make it happen)

It looks like I can’t change the title of the post.

You’ll have to ask the Reddit mods to change the title for you. Kappamale responds to me, so I know he’s active. If you can’t edit your thread body either, I’d type up what information you want to display in the sticky and then contact the mods.

Alternatively, it is still early enough with the replies. Start a NEW post. Attention grabbing (and descriptive) post topics are extremely important.

Starting a new post looks like a good option. You’ll certainly do that better than me.

ppcman, I know you don’t post on Reddit. I also don’t know that much about Github or how this website works. If you wanted to write up the body, I’ll post it for you and ask the mods to sticky it.

Creating neat commits with git rebase

When you start to work on something create new branch for it- don’t work directly on master branch.

$ git checkout -b layoutFixes Switched to a new branch 'layoutFixes'
After hard work your log looks like that

$git log --pretty=oneline --abbrev-commit master... 8a9ee09 more edit on footer.php 9e2bc6d Revert "added header.php" f398e81 edited footer.php 327154a added footer.php 47a5b3d added header.php
You added header.php but later realised that it wasn’t good idea and reverted 47a5 commit. You can use rebase to cleanup this mess, start from 47a5.

$ git rebase -i 47a5^

Editor pops up where you can choose how to perform rebase

[code]pick 47a5b3d added header.php
pick 327154a added footer.php
pick f398e81 edited footer.php
pick 9e2bc6d Revert “added header.php”
pick 8a9ee09 more edit on footer.php

Rebase ace33eb…8a9ee09 onto ace33eb

Commands:

p, pick = use commit

r, reword = use commit, but edit the commit message

e, edit = use commit, but stop for amending

s, squash = use commit, but meld into previous commit

f, fixup = like “squash”, but discard this commit’s log message

x, exec = run command (the rest of the line) using shell

These lines can be re-ordered; they are executed from top to bottom.

If you remove a line here THAT COMMIT WILL BE LOST.

However, if you remove everything, the rebase will be aborted.

Note that empty commits are commented out[/code]

Remove lines(commits) related to header.php

[code]pick 327154a added footer.php
pick f398e81 edited footer.php
pick 8a9ee09 more edit on footer.php

Rebase ace33eb…8a9ee09 onto ace33eb


[/code]
And squash commits related to footer.php

[code]pick 327154a added footer.php
squash f398e81 edited footer.php
squash 8a9ee09 more edit on footer.php

Rebase ace33eb…8a9ee09 onto ace33eb


[/code]
Save and close editor. Your log is neat!

[code]$ git log master…
commit 7f668afe58c0e5c917a1bed0a693eb3f5b8fff9a
Author: foo bar@rex.com
Date: Sun Mar 16 10:00:09 2014 +0100

added footer.php

edited footer.php

more edit on footer.php[/code]

Now it’s time to grab some PPCs so merge your work into the master branch and push it

$ git checkout master Switched to branch 'master' $ git merge layoutFixes Updating ace33eb..7f668af Fast-forward footer.php | 1 + 1 file changed, 1 insertion(+) create mode 100644 footer.php $ git branch -d layoutFixes Deleted branch layoutFixes (was 7f668af). $ git push origin master
[sub]excuse my eng.[/sub]

Sigmike, if you want to try writing something up, I made a thread about it here…

http://www.peercointalk.org/index.php?board=36.0