Feb Payroll

Commits on Oct 26, 2018
Merge pull request #48 from thesnat21/Update_Default_Theme  …

@biblepay
biblepay committed on Oct 26, 2018
 
Commits on Oct 17, 2018
1.1.5.9c-No-Op  …

@biblepay
biblepay committed on Oct 17, 2018
 
Commits on Oct 16, 2018
1.1.5.9b-No-Op  …

@biblepay
biblepay committed on Oct 16, 2018
 
Commits on Oct 7, 2018
1.1.5.9-Leisure Upgrade  …

@biblepay
biblepay committed on Oct 7, 2018
 
Commits on Oct 6, 2018
1.1.5.8-Leisure Upgrade  …

@biblepay
biblepay committed on Oct 6, 2018
 
Commits on Oct 3, 2018
1.1.5.7d-No-Op  …

@biblepay
biblepay committed on Oct 3, 2018
 
Commits on Oct 2, 2018
1.1.5.7c-No-op  …

@biblepay
biblepay committed on Oct 2, 2018
 
Commits on Oct 1, 2018
1.1.5.7b-Leisure Upgrade  …

@biblepay
biblepay committed on Oct 1, 2018
 
1.1.5.7-Mandatory Upgrade (at block 77000)  …

@biblepay
biblepay committed on Oct 1, 2018


Commits on Oct 30, 2018
1.1.5.9e-Leisure Upgrade  …

@biblepay
biblepay committed on Oct 30, 2018
 
1.1.5.9d - Leisure  …

@biblepay
biblepay committed on Oct 30, 2018
 
Commits on Oct 26, 2018
Merge pull request #47 from thesnat21/Add_exec_helper  …

@biblepay
biblepay committed on Oct 26, 2018
 


_____________________________________________________________________________________________________________________________________

120 hours for the month of October:
?4800/.000208
 23,076,923 bbp

Capping at 3.5 Million

Is the IT budget 3.2M now?

I think investors feel backlog of payroll of any sort of IT expense looks like a liability. Can we cap invoicing back to say 90 days (3 months) back? So if invoiced in the month of Feb 2019, you can ask for Jan 2019, Dec 2018, and/or Nov 2018 but not prior? This is not to say developers should not be compensated... it just looks bad carrying liabilities so far back.

I think investors feel backlog of payroll of any sort of IT expense looks like a liability. Can we cap invoicing back to say 90 days (3 months) back? So if invoiced in the month of Feb 2019, you can ask for Jan 2019, Dec 2018, and/or Nov 2018 but not prior? This is not to say developers should not be compensated... it just looks bad carrying liabilities so far back.

No, I think our devs who put in time for development should be paid, especially since we work free 94% of the time.

Could you help us create a fundraiser to pay the devs for the other 94% compensation they havent received from yourself and a new group of people with honest hearts?

Is the IT budget 3.2M now?

Yes, and the IT budget is not capped at 3.2 MM, just as the Charity budget is not capped.

Its a shame we once had someone vote against the Hope for Widows.  I pray that this same person opens their heart to Jesus.

In Jesus name I cast out any ill-will directed toward this project, and command these demons to leave this project Now in Jesus Loving Name!

Its a shame we once had someone vote against the Hope for Widows.  I pray that this same person opens their heart to Jesus.

Perhaps some people didn't feel it was a worthy proposal. Do you expect every proposal to pass?

No, I think our devs who put in time for development should be paid, especially since we work free 94% of the time.

Could you help us create a fundraiser to pay the devs for the other 94% compensation they havent received from yourself and a new group of people with honest hearts?

Yes, I agree the devs should be paid. Every dev has so far been generous with their time and not asking much in return. Your sacrifice is noted and appreciated by everyone. I think you misunderstand my point. I'm just suggesting that perhaps you bill for your time in advance or in a more timely manner for past development hours.


If you want to discuss fundraising, that's a separate topic. I'm more than happy to brainstorm with you on this.