Open monroemann opened 5 years ago
I'm not against it. Might be a good way to get talent as you said.
I agree! I think this could be a good idea
I need to know the pros. Why? but more importantly, the cons.
Are we aware of https://github.com/tosdr/tosdr.org (site: https://tosdr.org/) I posted this a while ago but not sure if you saw. They opened their app up to the public and do TOS reviews. The con of opening this up might be wasted time reviewing faulty code. A pro would be getting more feedback and perspective on this site but I am unfamiliar as to how many people would be interested in working on this, as far as a lack of knowing this is here.
Interesting! I didn’t know anyone else did this.
Their reviews aren’t as good as ours. I don’t think they are done by attorneys.
But yes, it’s competition.
If we open the repo up publicly people will just find it on github. The main website was public at first and suddenly random people started contributing.
Making it public may help get more people to know about what we are doing...
We need to make a decision on this. Should we give it a try for one month and see what happens? @emestabillo @moeen @chen-robert @raerayc @ShreePatel95
We can try it for one month and see. If we don't like the results of this, we can always make it private again
Is there one more person who agrees that we give it a try for a month or two?
I agree. we can try it for one month to see if it works
On Wed, Jan 16, 2019 at 9:33 PM Monroe Mann notifications@github.com wrote:
Is there one more person who agrees that we give it a try for a month or two?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/monroemann/tosfairness/issues/104#issuecomment-455048221, or mute the thread https://github.com/notifications/unsubscribe-auth/AqK7ZwibBpNNJifMETAM9Pk0e4EvaAd0ks5vEAsagaJpZM4Y9icS .
--
Rae Charkarutpahu Marketing Manager
Break Diving, Inc. - a 501(c)(3) charity raekha@breakdiving.org Break Diving http://breakdiving.org | BD Blog http://breakdiving.blog
Join our inspiring free worldwide community at www.breakdiving.org/community
Okay, public it shall become!
Okay, the repo is now public. Now ANYONE can clone the repo, see the code, make branches, and push pull requests.
The question now is: what do we do? Should we fill up the repo will 50 issues that we need handled, and start to actively share this repo link in all the other slack groups we are a part of, and see what happens? What other ideas do you guys have?
Can someone do research on how to manage a public repository and encourage contributions?
If we do this right, this could be a HUGE publicity and marketing boon for us, if we can get hundreds of coding contributors, and turn this site into an amazing place for helpful information.
Yes, so we can do exactly that. We can add issues to the repo and then share with other slack groups. Let's see if people come and help. Also, we aren't sure if we are going to LIKE their work because we've had some difficulty with coders D:
By doing so: a) It shows we're really a charity in our mission b) It will help us enlist more help without bringing people on staff c) It serves as a 'proving ground' for potential staff coders d) It may help us spread the word, because coders working on this will probably talk to their friends
Thoughts?