Open rappo opened 10 years ago
+1 this
What would be a realistic bounty?
I might look into this; I wouldn't have to add authentication/linking accounts right?
Actually it looks like I won't be able to pursue this since this package requires Ruby 2.1.2, but I'm on Ruby 2.3.1 and a downgrade to 2.1.2 would require a downgrade of OpenSSL requiring a downgrade of virtually my entire system.
PlasmaPower:
I might look into this; I wouldn't have to add authentication/linking accounts right?
Similar to bountysource github integration.
PlasmaPower:
Actually it looks like I won't be able to pursue this since this package requires Ruby 2.1.2, but I'm on Ruby 2.3.1 and a downgrade to 2.1.2 would require a downgrade of OpenSSL requiring a downgrade of virtually my entire system.
Develop in a virtual machine, not your main system.
Develop in a virtual machine, not your main system.
Makes sense, in my case I'll use a chroot.
Similar to bountysource github integration.
Would I also need to add account linking support? That's what I was trying to ask.
Yes, otherwise it would be incomplete, no?
A lot of implementations don't have authentication from what I can tell, for example the launchpad implementation. I'm not sure if it is needed.
I guess the decision what is acceptable has to be made by @bountysource.
Halvy:
Hello.. I'm new around here.. sooo ;) I cannot find a detailed (or ANY) description of what needs to be done, other than the title 'Add support..'. This could mean many things (to me). I've looked over at git also.. but nothing to explain what is required.
Perhaps write down a list of things it means to you? Perhaps we are on the same page already.
bountysource is integrated with github.
In this ticket the goal is to see bountysource is integrated with phabricator.
We at Whonix primarily use phabircator as our issue tracking system. For stuff we want to set bounties for, these need to be manually duplicated to github. That is inconvenient. That is cumbersome since duplicated discussions.
Please consider talking to @bountysource team (By IRC or so? Otherwise mail or dunno) to find out what they think about this and how it could be implemented.
@adrelanos Those seem like good boundaries for the issue. I also appreciate the need for this due to major projects like yours and Mediawiki being hosted on Phabricator. Unfortunately due to a combination of this project being in Ruby and internals needing changes due to contacting multiple self hosted servers I'm not interested in implementing this, even with the $100 bounty.
As for contacting Bountysource the main things I'd be interested in are:
Lee Bousfield:
@adrelanos Those seem like good boundaries for the issue. I also appreciate the need for this due to major projects like yours and Mediawiki being hosted on Phabricator. Unfortunately due to a combination of this project being in Ruby and internals needing changes due to contacting multiple self hosted servers I'm not interested in implementing this, even with the $100 bounty.
Sure. Please state a realistic bounty and/or a bounty that would allow you implementing this.
For me the bounty isn't the problem ($100 seems reasonable), but I'm not familiar with Ruby. I'll look into it again, but I doubt I'll get very far.
Okay, a couple of notes that might help future visitors:
/usr/lib/ruby
to their older versions. One problem though, I'm not quite sure what version Ruby wants. I think it wants a version with SSLv3. I think this is enabled by default in newer versions of OpenSSL, but might be reenablable. You might also checkout version 1.0.0 or something. I couldn't get 0.9.8 working, but I might be replacing the libraries wrong (very likely). To get Ruby 2.1 working, don't try to build it yourself. Unlike built libraries, headers are not versioned. I've gotten an already built version from the Arch Linux Archive here: https://archive.archlinux.org/packages/r/ruby/ruby-2.1.2-1-x86_64.pkg.tar.xz and from there only the correct library versions are needed.Here be dragons. I'm not interested in working on this project, it is much too messy. I don't know much about the Ruby ecosystem, but this is definitely one of the worst projects I've worked on. Besides very minor HTML changes, @wkonkel is the only person to touch this project.
Sorry to disappoint @adrelanos, but you might look into your own solution. If you could limit the scope to Bitcoin it would be much simpler, but I'd expect there would still be a lot of non-technical hassle.
Payments in bitcoin [or any other common thing] would be possible as well.
@adrelanos What I'm suggesting there is make your own system. All you need is a bot that creates a BTC address per issue on request, the sends the BTC to a user or address upon the admin's request (they would be notified once an issue with a bounty is closed). If it gets out of hand maybe the issue owner should decide for smaller bounties. I can script something up if you'd like.
We wanted to use bountysource because that gives a higher visibility and offers the task to more prospective developers.
Makes sense, that is a big advantage of Bountysource.
Is there still someone working on it ? Blender uses Phabricator, it would be cool to be able to create bounties on their issues.
Hey @x-a-n-a-x - I don't think anybody is actively working on this. Two started looking but that was a while ago. The bounty has since gone up to $115, not a huge difference but just FYI.
In the last few months a few others have started up Bountysource the software locally to look at various issues so there are occasional help available on the IRC channel or Slack if you would like an invite sometime.
@Cervator Could you PM me the slack channel, thank-you.
also, please change the github title of the bug to reflect the new amount.
@3DJetengine title changed but I don't have anywhere to PM you? :-)
If you hop on our IRC channel (#bountysource on Freenode IRC) I'm usually idling there. You can leave me an email to send an invite to.
Example link brought to our attention: https://reviews.llvm.org/D28462 does show up on Bountysource at https://www.bountysource.com/issues/68520286-d28462-clang-format-add-new-style-option-alignconsecutivemacros but is automatically closed. Haven't been following here closely enough to know if support was partially (or fully) implemented then broke again with open issues showing as closed on Bountysource (a common issue with other integrations going buggy over time)
Or maybe that's the default behavior for un-implemented trackers. Really can't recall, but wanted to at least bump this issue with an example :-)
For the record there is some kind of initial (broken) support:
Even though it's marked as closed, it still managed to extract some info from this Phabricator instance.
There is a $100 open bounty on this issue. Add to the bounty at Bountysource.