-
Notifications
You must be signed in to change notification settings - Fork 0
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
Nazareth Recipe's Vision #47
Comments
I think at first it did start as dishes that were consumed in the guesthouse in Nazareth. But if we want to expand it and get people's attention we might need to consider writing down a mission statement, IMO we should open it to the entire organization cause it doesn't feel like a FAC thing to do, to just make this repo accessible to only people in Nazareth. but here comes the problem where people need to test the dishes, and it's only here in Nazareth where people get together and have dinner together, and only these people can review the pull request cause only they have tried it and can confirm it. this comment was transferred from #43 |
Agreeing with @Karyum, I believe this should be a repo for fac's communal meals, the vision should include bringing members together to have delicious food! |
So should Nazareth Recipes be a repo to hold all the communal recipe's within FAC? So why should it be called Nazareth Recipes? I think the way works now is that because in Nazareth we are always cooking for each other, people can make PRs that other people within the community who ate the food can have relevant input in. People cook for each other 4-5 times a week in Naz, but pretty much only 2-3 times a cohort elsewhere. So I guess we can say this is mainly about recipes within Nazareth as that is where it came from, but other, communally cooked meals can be added from the wider FAC community |
When they make a documentary about the most successful, open source, co-operatively produced hub for recipes online, this issue is going to play a huge role. Be part of history people! |
@matthewdking made an interesting suggestion: the wider community should feel free to make PRs with new recipes, but those PRs should not be merged until the meal is cooked by someone at the guesthouse. That way we could maintain the original plan for the repo, while also potentially gaining a healthy backlog of community recipes. |
@finnhodgkin that's a great idea. it would also encourage people in the guesthouse to cook, and try new recipes that would be awesome!! we should make it clear though that everyone can raise an issue for a recipe and make pull request but can't be reviewed until it was cooked |
should be documented in the README |
@Karyum are you saying the vision should be documented in the readme? I was kind of under that assumption anyway I guess. Or this new idea? But yeah, both. With regards to @matthewdking's suggestion I do like it a lot, we would need guidelines on what to name the PR (they should all be PENDING) or something, maybe give them labels? |
However, though I do like the idea, lets not get away from the broader question of what is the vision - this suggestion implies @matthewdking you have some ideas of what you see as the vision? and @finnhodgkin |
I was just replying to the discussion above about community participation. I think I'll have to sleep on the broader topic. |
@finnhodgkin Fair, I think a considered response is much more valuable and appreciate you approaching the issue with the full seriousness it deserves. We will await your contribution with bated breath. |
@/all I have updated the initial comment with the following initial suggestion for a Vision to give us something to work from:
|
@m4v15 I would imagine Nazareth recipes as a huge library of recipes or strive to be atleast. Just visit this repo watch serious github workflow with silly topics 😜 , for example the forzen chocolate cake PR discussing what is an English tray was probably one of the funniest discussions i had on github 😆 . |
This looks like a good start, the rest feels like it belongs to the |
A lot of agreement from me here with @Karyum and @shiryz. My key principles for this repo:
I think we are already achieving high levels of fun, but I think community interaction could be improved; here are a couple of suggestions for that:
|
@mattlub is there something you would change in the Vision Statement I posted to reflect those? I think we need to get an overall vision sorted ASAP and then we can sort out how to achieve it later - so the vision can have something about engaging the wider community, but doesn't have to say explicitly about having comments. @shiryz I know what you mean, the original is a bit wordy, but to reflect the calls for wider community participation we need a bit more, so maybe:
@mattlub does this cover your points (emoji's === fun, right?) |
@m4v15 I think that all of it should exist in the readme but perhaps our mission could include "encouraging the wider community to contribute to reach ..." |
There have been multiple discussions of late about the aims and direction of Nazareth recipes, and I think we need to formalise these to guide us forward and prevent any disagreements in the future.
From wikipedia:
So, any ideas?
#44 #43 similar issue on a rival repo
Edit 21:39 5/11/2017 to add a suggested vision
The text was updated successfully, but these errors were encountered: