Skip to content
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

Add link to Resources wiki page #41

Merged
merged 1 commit into from
Nov 18, 2013
Merged

Conversation

bf4
Copy link
Collaborator

@bf4 bf4 commented Oct 17, 2013

What do you think about promoting some wiki-based user-content?

@joonty
Copy link
Collaborator

joonty commented Oct 17, 2013

👍

@bf4
Copy link
Collaborator Author

bf4 commented Oct 17, 2013

@joonty Thanks for the +1. I'm adding here more details of my thoughts about this PR.

  1. ppwm-the-website is curated by maintainers who may have opinions. Getting info on the site requires both a successful PR and a release
  2. A wiki allows the user-community to actively maintain and curate its own resources in real-time, but raises the risk of either duplicating content, having two sources of content (violates DRY), or keeping out good content from getting into the site.

I think the benefits of the wiki outweigh the cons, but created the issue so this can be discussed.

@rwjblue
Copy link
Collaborator

rwjblue commented Oct 17, 2013

We can remove the deployment issues by using Travis's auto-deployment upon successful build. That way all that we would need to do is merge a PR, and the site would be updated.

In general, I think that perhaps a curated list is still the better way to go. I'm not 100% sure how others feel about this (I may be nuts), but it seems to me that this site is used as a reference to new-comers, and as such we should attempt not to lead them down rabbit-holes. If we allow user created content, the suggestions have not been vetted and confirmed as good practice, and it could cause a less than ideal starting point for new pairers...

I do think that there is a place for a wiki in general, but I don't think it can replace what we have here...

@joonty
Copy link
Collaborator

joonty commented Oct 17, 2013

My understanding was that the wiki wouldn't be replacing the existing content, but would be an addition for those who want to search a bit further. That means that we can watch as users agree on the best practices, and update the main site accordingly.

A bit like a bleeding edge (the wiki) and a stable version (the site).

Or have I misunderstood?

@rwjblue
Copy link
Collaborator

rwjblue commented Oct 17, 2013

@joonty - That makes total sense, and I think a Wiki definitely has a place here (as you described). I just want to make sure we are all on the same page...

@bf4
Copy link
Collaborator Author

bf4 commented Oct 17, 2013

@joonty @rjackson my thoughts exactly. I think there's a place for bleeding edge, but am not sure how we can ensure it doesn't interfere with or confuse the site's recommendations/resources.

e.g. we don't recommend screen, but why not allow someone on the wiki to offer resources for pairing with screen?

or e.g. a place to share user-contributed pairing scripts like https://gist.github.com/marksim/5785406 / http://blog.quarternotecoda.com/blog/2013/06/06/quick-script-for-tmux-pair-sessions/

@bf4
Copy link
Collaborator Author

bf4 commented Oct 24, 2013

@avdi @joonty @rjackson ok to merge? I cleaned out the wiki page to make it only additional info.

@rwjblue
Copy link
Collaborator

rwjblue commented Oct 24, 2013

Seems good to me.

@chrisradford
Copy link
Collaborator

Are there other resources that should be on the wiki that are currently under 'resources'? It's a pretty bit list down there.

Alternatively should there be a 'recommended setup' for new users as a jumping off point; not that I fancy having the discussion as to which tool is best.

Also the wording of the sidebars seems inconsistent:

Is this page missing something?
Pull requests are welcome!
As well as updating the wiki

Shouldn't it be:

Is this page missing something?
Pull requests are welcome!
As well as updates to the wiki

Edit: I knew I'd seen 'recommended setup' somewhere before: Golden Path #2

@avdi
Copy link
Owner

avdi commented Nov 11, 2013

I'm definitely down for having some more open user-curated content in the form of a wiki. 👍

@bf4
Copy link
Collaborator Author

bf4 commented Nov 11, 2013

@avdi good enough for merging and then perhaps some pruning of site content to the wiki?

bf4 added a commit that referenced this pull request Nov 18, 2013
Add link to Resources wiki page
@bf4 bf4 merged commit f42713b into avdi:master Nov 18, 2013
@bf4 bf4 deleted the link_wiki_resources branch November 18, 2013 15:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants