-
Notifications
You must be signed in to change notification settings - Fork 59
DNS name, SSL cert for bounty budget voting system #451
Comments
@dckc What is the timeline for the bounty web app to be completed? |
This is assigned to milestone/3; my best guess at a launch date is kept there. |
bounties.rchain.coop? |
I didn't want to give the impression that it was the whole bounty system, since so much of the action is here in github. But it (bounties.rchain.coop) is worth considering. |
some suggestions
|
I am inclined towards bounty-system.rchain.coop or bounties.rchain.coop |
Bounties.rchain.coop is less cumbersome. Because the - may give some problems.
Sent from Yahoo Mail on Android
On Sun, 4 Mar 2018 at 17:17, Donald A. Iljazi<[email protected]> wrote:
I am inclined towards bounty-system.rchain.coop or bounties.rchain.coop
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
|
Is there a web application prototype for RAM distributed budgeting and bounty? @dckc |
I really like rewards.rchain.coop suggested by @Keaycee I tried to look up the difference between Reward and Bounty online even though we use the term bounty often. "Bounty is a synonym of reward. "A bounty (from Latin bonitās, goodness) is a payment or reward often offered by a group as an incentive for the accomplishment of a task by someone usually not associated with the group. "(source Wikipedia). We have established that we want only member to be part of the bounty (or better put rewards) program. |
current deployment is: rchain-dbr.nfshost.com |
I'm hesitant to go with rewards.rchain.coop; I lean toward something more obscure: maybe dbr.rchain.coop (distributed budgeting and rewards). |
@jeremybusk I need your help with the SSL cert. @ian-bloom did the CNAME, so we have https://rewards.rchain.coop/rchain-dbr-beta/ , but with scary SSL warnings. |
@jeremybusk took care of the SSL cert. |
I'm folding the $200 budget for this into #477 . |
for production deployment:
cc @kitblake @lapin7 @ian-bloom @jeremybusk @hyperevo @patrick727
see also #260
The text was updated successfully, but these errors were encountered: