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

Pullup as a reddit style layer for pull requests and issues. #382

Open
howardroark opened this issue Mar 1, 2016 · 8 comments
Open

Pullup as a reddit style layer for pull requests and issues. #382

howardroark opened this issue Mar 1, 2016 · 8 comments

Comments

@howardroark
Copy link

What if pullup was a tool that anyone could connect to a github repository. From there it could offer a reddit/hacker news style voting layer for pull requests and issues. It could be built around GitHub accounts and use the API. I think it would be a great way to understand what users are looking for while cutting out a lot of noise.

@megamattron
Copy link
Member

That would be an interesting direction, basically auto list any PR or issue and let people vote. It'd be a lot different than what we have here, but could be a good fork.

@rickhanlonii
Copy link
Collaborator

I like this as an addition to what we already have.

I imagine we could have different categories of posts (Designer News style) and you can view only certain categories at a time (subreddit style). So the front page would show the highest voted article/news/repo/pull, but you can view and participate in the sub-communities, so to speak.

Once that core is there, then you could essentially allow filtering by repo for the code/repo/issue category.

That would take a few steps:

  1. Implement categories on the backend
  2. Add categories indicators on the front-end
  3. Add categorization to adding a post (likely automatically at first)
  4. Add routes for viewing by a particular category
  5. Add handling for filtering by repo

@howardroark
Copy link
Author

Yeah really anything can be in the "stacking order"! Just need a base schema and extended schemas for each "thing". Then you can filter as you like. Just need a reusable UI +/- mechanism and a tool that converts GitHub data to the schemas and stores them.

@rickhanlonii
Copy link
Collaborator

We could create a /issues for any arbitrary public repo:

  • pullup.io/larvalabs/pullup/issues
  • pullup.io/reactjs/redux/issues

@howardroark
Copy link
Author

That would be great! Just have a basic algorithm that allows any GitHub id to vote.

@howardroark
Copy link
Author

https://gitsup.com/
https://gitsup.com/larvalabs/pullup

Was a great excuse to learn meteor.js :) Still in a beta state, but does the basic job.

@rickhanlonii
Copy link
Collaborator

That's really neat @howardroark!

Are you interested in integrating that into pullup directly? I'm happy to help in any way I can.

@howardroark
Copy link
Author

Hey @rickhanlonii I thought about how this could be done for while, but couldn't quite see how it would make cohesive sense aside from changing what the project is about. I think this project is more of an effort to build a community than anything else.

With that said... I think there is an opportunity to distill a UI toolkit and API schemas for content voting systems. All this app really does is talk to the github api via the browser and store votes as a schema and also update another schema that offers a tally of all votes related to a repo. Other things could source that data... like if someone wanted to embed a list in their project site and feed from the core data.

What I mean is... Would there be a good way to offer a up(down) vote system for any API data source.

Too bad the "pullup" org handle is taken so many projects couldn't be under the same umbrella.

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

No branches or pull requests

3 participants