Join an open-source community

#10

I added a contributing.md to a recent open source group project for our local (Melbourne) freeCodeCamp group.

I recommend you add one of those so that people know how to contribute. (Steal mine and change the links if you like :slight_smile: )

Since this is a greenfield project (i.e. you’re making it from scratch together), you should at a minimum put together a To-Do list of jobs that need to be done, so people have a sense of what you’re making.

Even better, create extensive User Stories, and use the GitHub projects Kanban style board to set out the road map of work to be completed.

New projects are exciting, but you’ll benefit from a good structure at the start to steer you in the right direction.

https://help.github.com/articles/about-project-boards/

5 Likes
#11

Indeed, it’ll definitely need one of those, haha. Considering @RandellDawson’s reply, the post is premature; I wish I would have waited until things were more “ready”, and thought out. :confused:

Thank you for offering the README, your post is greatly appreciated!

1 Like
#12

From the purpose of my learning, I don’t think this is premature at all. Good to see the steps that others are recommending you make. I’ll definitely be following along as each new step gets documented.

2 Likes
#13

That’s what I initially thought as well. I mean, that is why I created this, that is, to be a learning tool. I think the forum I have in mind may gather a decent amount of users(I posted about it in a Facebook group, and quite a few people messaged me saying they’d love it), which would be great, I think. Creating a real-world application that is actually used by a lot of people, just lands us closer to our goals, and in itself, is an awesome thing to accomplish. However, that isn’t the end-goal. The goal is to learn and build together. Whether or not people actually use any of the projects is a secondary concern.

Sorry for writing all of that unsolicited text, but I thought it might be useful for potential contributors. I agree that the advice of other people so far was great, definitely worth following along, haha.

#14

Just to clarify, Randell’s suggestion for a README was good, but that serves a slightly different purpose to a CONTRIBUTING document.

Typically, the README is to tell users how to use the product. Usually you see them on NPM modules or frameworks, explaining the API. Your forum idea might just have a README that explains the purpose of the forum, and if it’s a standalone piece of forum software you might include hosting instructions for those that wanted to clone it.

The CONTRIBUTING document is to tell contributors how to get involved. So that includes instructions for cloning the repo, how to format pull requests, and any requirements you have (such as using a specific ESlint config, or to ensure tests pass before PRs etc…)

2 Likes
#15

Yes, I’ve added both. Used your CONTRIBUTING.md :smile: I’ve linked your github, and the original repository which it’s from in the “attribution” section. I hope you don’t mind! Thanks again, @JacksonBates

#16

If you don’t want to manually send invites for ever, you can use a free service like OrgManager to do so :smile:

#17

Wow, how helpful! Thank you @m1guelpf :smile:

1 Like
#18

Presumably you made that @m1guelpf?

Could you explain what it does exactly?

#19

I just realized the name Miguel in the URL. Did you create this?? :astonished:

@JacksonBates, I’d like to know to, honestly. I just gave admin access to my organization :neutral_face:

#20

Yeah - I run an org to, and want to know how this processes my orgs data without compromising the privacy or safety of my volunteers…hence my question :slight_smile:

#21

Same concerns as you, haha. I see familiar faces in the OrgManager project.

I found this:
“OrgManager takes Github Organizations to a new level! We require the org:admin permission to send invites to your users, but remember that you can revoke that permission when you want, and that we won’t do anything without your permission.”

@m1guelpf, What does it mean by “send invites to your users”? Do we already need users?

#22

I’d like to know to, honestly. I just gave admin access to my organization

I run an org to, and want to know how this processes my orgs data without compromising the privacy or safety of my volunteers…hence my question

First, if you don’t want to trust your data blindly to the app (something that I wouldn’t do :smile:) the app is OSS, so you can check the code here.

Could you explain what it does exactly?

OrgManager allows you to create a “portal” where users can apply to your GitHub org and be auto-invited, or you can also set a password.

Did you create this??

Yep :smile:

2 Likes
#23

I guess I’ll trust it. Your extensive github use, membership of reputable orgs, it’s OSS, etc. lead me to trust… Which really might not be good… this is how people get pwned, lol.

So we don’t need users? How does it work, and can a user of the project join other organizations, as well allow people to join theirs?

#24

Yeah, I’m in 3 orgs myself.

It makes it easier to assign someone to work on a feature if they are in your org, among other things.

#25

So we don’t need users? How does it work, and can a user of the project join other organizations, as well allow people to join theirs?

Well, OrgManager providers the portal, getting users is your job. We simply make things easier by letting you share a link to join instead of asking GitHub username, waiting for a response, sending invitation…

1 Like
#26

Oh, I see. Very convenient. Thanks!

1 Like
#27

Have you considered rolling in a similar process for handling Trello and Slack invites with the same one off / one page solution?

That’s a related PITA :slight_smile:

1 Like
#28

Have you considered rolling in a similar process for handling Trello and Slack invites with the same one off / one page solution?

There are already existing solutions for Slack/Trello, but if you want, you can open an issue in the issue tracker and I’ll look into it :smile:

That’s a related PITA :slight_smile:

What’s a PITA? (Sorry, not english native)

#29

UK/Aus : Pain in the arse.

US: Pain in the ass.

Same sentiment, regardless of continent :slight_smile:

3 Likes