Web: as a repo maintainer, i want to be able to fund an issue from a private repo, so i can have contributors work on private stuff

[owocki]

(not ready to be worked on.. just tracking it here)

[e-n-l]

Seems like this might eventually want integrations with other private repo hubs, like GitLab and BitBucket.

It would also probably escalate the need for one-time, pre-work agreements to be settled prior to claiming an issue--things like NDAs, contribution guidelines, style / linting guides, perhaps an overview / orientation of the organization or repo, etc.

I would LOVE to see that kind of thing delegated to a 3rd party micro-learning dApp or platform, e.g., ConveYour by @srhyne

[owocki]

Seems like this might eventually want integrations with other private repo hubs, like GitLab and BitBucket.

yup!

It would also probably escalate the need for one-time, pre-work agreements to be settled prior to claiming an issue--things like NDAs, contribution guidelines, style / linting guides, perhaps an overview / orientation of the organization or repo, etc.

yup.. NDAs and onboarding are at the top of this list fto me

[owocki]

might be worth speccing this out next community call

[owocki]

from a friend who runs a private repo:

Darn. I could have a $2-3K budget for that each month if it existed...

So I work for REDACTED and we have several private repos that have issues filed with pretty clear directions on what to do, but not enough engineers to close them all.

The problem is that the repositories themselves are private. But I'm ok having almost anyone talented work on them as long as they've signed the right paperwork and are in the US.

So I can't really openly list on gitcoin, but I could put a project description and terms that to get access to the repo, you need to sign a doc and maybe verify ID in some other way. And maybe have potential devs send me a quick email about themselves. We can't really waste time with too many bad PRs, but I do want to tap into the gitcoin talent network! So it's kind of hard to say, "basically anybody could have access" - I'd want to balance it out somehow if possible so 90% of people trying issues can actually close them.

That may give you some idea...glad to expand upon it a bit if it's helpful. But I think if you could figure this out there's a huge untapped market!

[mkosowsk]

Very compelling stuff! Would be interesting to have a discussion on the best way for Gitcoin to streamline the process of getting the the correct paperwork to the Contributor and getting them onboarded on a private repo with as little pain as possible.

OSS is huge but also a ton of opportunity in closed source 😍

[owocki]

could maybe be a premium feature.

[leonprou]

For now, github suggests to open another public repo for the issues:
https://help.github.com/articles/creating-an-issues-only-repositor

[owocki]

we might want to make this into a goal for next quarter @PixelantDesign -- i keep seeing requests for it

[PixelantDesign]

Yes! I’ve heard it a few times as awell, on the list already.

[owocki]

@PixelantDesign if i wrote up a spec and bounty-ed, would that be premature / against our focus? i want to respect the process, but i also want to get this moving...

[PixelantDesign]

If there are technical things approaches that we know we'll need to make this work and can make progress on through a bounty, I think that could be helpful. From an experience perspective, I can add to tackle in Q2. Thoughts @owocki ?

[owocki]

@PixelantDesign I think we first need to figure out the optimal UX and then the technical things will be downstream from there.

For example, the following is needed

• How do we want to manage giving gitcoinbot access to the issue scope for the private repo? Within that access, how do we manage private information vs public information?
• Do we need to facilitate NDAs for private repo owners? How do we manage granting access to the private codebase? Are we then responsible for revoking access after the relationship is voer?
• If there is a dispute, how does someone arbitrate without looking at the IP / public PR?

Do you have any special insight on any of the above from funder research? Want to take a stab at writing up a MVP spec? If not, I can.

[e-n-l]

How about creating a sort of "gitcoin contributor relationship boilerplate" (GCRB) repo, which could act as a mediator between private and public repos?

The boilerplate would include samples of an NDA, code of conduct, necessary documentation needed + how to provide it, arbitration process, etc. Put a bounty on that public repo's issues, and then when the issuing organization marks it complete, the contributor gets a special tag (e.g, the organization's gitcoin ENS + timestamp) associated with their gitcoin profile, which opens visibility into further issue details.

Here's a story about how this might play out:
AcmeCo has a private repo that meets their internal criteria for assigning bounties on some issues.

AcmeCo's project manager gets on GitCoin.co/tools, where she finds the "GitCoin Secret Agent" (GSA) tool which provides a private repo integration configuration tool.

There's a sample configuration file and documentation for DIYers, but she's already engaged with a dynamic, branching webform that's building her config file through dialogue. She defines access roles, (e.g., admin, employee, contributor, public) associates issue tags / users, etc.

Part of this process will direct her to fork the gitcoin contributor relationship boilerplate (GCRB) into a public repo in her organization, and send instructions to legal etc to make the necessary changes / approval.

The GSA tool incorporates the URL for their new GCRB repo into a config file, along with the rest of her settings. She then adds / commits this to the private repo she wants to bounty, and adds a GitCoin GitHub App (either gitcoinbot, or something more specific) to the GCRB, and any eligible private repo in question.

This creates a waterfall of interactions:

• Interactions with the GitCoin Secret Agent (GSA) via private repo issues that have tag:public
• ...translate into GCRB public repo issues (1:1)
• ...which will integrate via gitcoinbot
• ...populating into on the issue explorer / triggering notifications of two flavors:

1. Un-tagged / new contributors, (if AcmeCo is looking for new contributors) all of their open issues roll up into a single issue associated with the organization, e.g., "AcmeCo has 12 open issues totaling $1325.30," and perhaps some general stats on those issues. "Start Work" in this context means applying to / working on filling the requirements of the GCRB.

2. Contributors with an unexpired AcmeCo tag (i.e., they have already satisfied the relationship requirements) will see AcmeCo issues listed / filterable alongside open source issues.

Tagged Contributors can express interest in the issue via the public GCRB issue if they don't already have access to the private repo, and go straight to the private repo to "Start Work" via interactions with GSA if they do have access.

[owocki]

@e-n-l i dont know how i missed this.. this is a good idea, i like how elegant it is technically :)

@PixelantDesign i'd love to just build this nights and weekends, but im afraid i dont have enough user input on exactly what the funder expectations are here. could we maybe spend a couple hours over the next several weeks doing user research and informing the spec so we know the dev cycles are put to good use?

i have a few leads in my inbox we could talk to. and im sure the content team (cc @vs77bb ) can hook up a few also

[PixelantDesign]

We had potential customers ask about this at Nifty. For work that is IP for the company, they'd like to keep it on a private repo.

[e-n-l]

That makes sense to me... a second pass at this might involve integrations
with GitLab and BitBucket, as they're widely used for closed-source.

On Tue, Jul 31, 2018 at 12:19 PM, Pixelant [e-mail] wrote:

We had potential customers ask about this at Nifty. For work that is IP
for the company, they'd like to keep it on a private repo.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gitcoinco/web/issues/556#issuecomment-409336907, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAdvjBQAqA-ZujOPU1Jy-k0_3-wbglanks5uMK3AgaJpZM4Sg2kg
.

[e-n-l]

@owocki / @PixelantDesign - just thought of an ultra-simple MVP for this:

• Allow users to create Bounties that designate a specific bounty-hunter. (pool of hunters? -> mission creep...)
• Bounty hunter can then start work (or not), submit for completion, etc.

Why do this?

As a user, I want to be able to create and accept contracts for work that is closed-source / private. The legwork involved in finding this work, speccing it out, and negotiating pricing has already been completed. I just want Gitcoin to help me know / prove that:

a) my compensation exists, in escrow, and...
b) an agreement to work together is audit-able / public / on-chain, so that our...
c) contract / work history can accumulate with the same assurances.

[PixelantDesign]

Ideas: request additional perm

[owocki]

>Hi! I was thinking yesterday about monetization and I wanted to bring this here (not sure if is the right channel). 

Awesomeeee — we *all* need to be thinking / learning about monetization.  Its the singular thing that gives us leverage against Joe Lubin Buxx going away.

> Not sure if in our case will be better a commission by bounty or a subscription to avoid churn, but in general looks like a good idea to monetize.

Did you guyz know there is a `monetization` tag on the Gitcoin Issue board.  Check it out, some of these ideas are in there: https://github.com/gitcoinco/web/projects/21  (its also posted in the scratchpad for easy housekeeping)

> I think the most challenging is how let someone work in a private repo if is not in the org and also the most important “legal problems”, thinking in that I think show the bounty in the explorer is a need (can be without the gh issue link)  with a good description, also something we can combine with this is the feature “reserved bounties” and also with the current plans where we manage the project can be easy to have a select group of devs working as “freelancers” for this projects and also open the possibility to the company make a hire of this remote workers, with some kind of indication payment by hire.

> also something we can combine with this is the feature “reserved bounties”

Interesting, I hadn’t thought of that idea.. I can see a use case for this for sure.  Probably the type of users who would be willing to pay for it too.

Capturing this conversation in https://github.com/gitcoinco/web/issues/556 for housekeeping and for eventual execution.

more research notes from a convo between myself and @octavioamu

[owocki]

now hosted at https://github.com/gitcoinco/web/issues/3449

[owocki]

@neutraladvocate thatd be awesome! want to email me to find a time to chat?

[neutraladvocate]

Hi Kevin, I would love to chat. I removed my post as I needed to dig
deeper. I will repost probably as a separate topic as you have this one
covered really well.

Best Regards Martin

On Thu, Jan 24, 2019 at 10:41 PM Kevin Owocki [e-mail]
wrote:

@neutraladvocate https://github.com/neutraladvocate thatd be awesome!
want to email me to find a time to chat?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gitcoinco/web/issues/556#issuecomment-457445079, or mute
the thread
https://github.com/notifications/unsubscribe-auth/Aq13XJ2N0cOtelf_KvMR-SqGrJJrpCopks5vGnzygaJpZM4Sg2kg
.

--
Regards

Martin

Martin West
Founder - Neutral Advocate

14164145882

[owocki]

@neutraladvocate sounds great