-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Have a way for local IPFS communities to organize #64
Comments
(new idea) we could have meetup folder here and then meetup/lisbon, meetup/portland, etc and then have a README with orgs, location and other links + one markdown file per meetup with resources of that meetup (presentations, photos, etc) |
👍 on a meetup folder here as a first step. |
We could have a I think we should do something similar to nodeschool or Papers-We-Love. I opened an issue on PapersWeLove here and helped them switch to the NodeSchool model; a lot of what I said there applies here, so I'll copy it over (replace Papers We Love with IPFS, and imagine that we already have a few chapters up and running):
I think this approach works particularly well for NodeSchool, and would work very well for IPFS, especially with our github-issues-all-the-things mindset. I'm happy to write up a README about proper protocol for this. Also 👍 for the map. |
@RichardLitt im all for that. do we want this in a separate org? or the same? i know people like separate orgs. it's also nice to be able to say:
which we could get on the same ipfs org. otherwise:
or something... |
(i.e. id prefer same org, but others may kill me if that goes on too long) |
I think the same org. There's really no cost, at this point, to having more repos. The only issue is that we need to be very clear about teams for people who can contribute to repos - someone deleted all of NodeSchool the other month, which was super awkward. |
yeah this is why i want to hand out permissions granularly. oh trust! |
@skylarnorris have you stumbled upon this issue before? |
@diasdavid had not as I am not subscribed to this repo but @RichardLitt is handling most Meetup stuff now. |
@kumavis would it have been easier to organize your meetup with a separate organization, or with a separate |
See #64 License: MIT Signed-off-by: Richard Littauer <[email protected]>
I am going to veto making a new organization or repositories for meetups, for now. What we have seems to be working. We can revisit this later. For now, communities can open an issue, read the guide in |
We need a clear way for IPFS community to organize, or at least some guidelines, so that people that want to host an IPFS meetup or be part of one can find it and be informed of when it is happening.
We've looked into attending.io and meetup.com, both have pros and cons, but none lets us create a succinct and clean experience.
@RichardLitt you have been developing a lot of the materials, calendars and resources for the IPFS community, would you be able to make this happen? I feel that a guideline plus a community map (#39) added on ipfs.io could be something really good.
The text was updated successfully, but these errors were encountered: