19
\$\begingroup\$

Code Review. A community that learns as it grows, and grows as it learns.

projects are a huge opportunity to learn from each other. As individual coding marathons, these projects are fun.

Here's the proposition: each project gets a dedicated GitHub repository, where the canonical implementation comes to life; each "winning proposal" for a weekend challenge becomes an ongoing community project.

And then we can have other such community projects, like we could write an API for SE Chat, or whatever we as a community, decide we should come up with.

It's possible such an idea would not be possible because it would/could affiliate StackExchange with GitHub and we don't intend to instigate that. I wonder if, if not officially SE-stamped, we can do this.

When someone has code to commit, the modified class(es) can (should!) be posted on the main site to be reviewed by anyone; the CR question would need to be Community Wiki, and link to the GitHub repository, and the code that isn't the OP's code should be in a quote block.

Any other ideas? Objections? Suggestions? Unicorns?

\$\endgroup\$
  • 4
    \$\begingroup\$ I don't take part in the weekend challenges, but theorically speaking, this is a great idea! \$\endgroup\$ – Morwenn Dec 18 '13 at 10:07
  • 2
    \$\begingroup\$ I'm not entirely sure about the paragraph "When someone has code to commit", if you mean what I think you mean, why not only say in any post "I plan to add this to github [link]"? Why the need to make it a CW question? \$\endgroup\$ – Simon Forsberg Dec 18 '13 at 12:56
  • \$\begingroup\$ @codesparkle: Oh, I thought you were killing that tag. :-) Looks like it was supposed to be the Meta tag, not the main site's nonexistent one. \$\endgroup\$ – Jamal Dec 19 '13 at 6:24
  • \$\begingroup\$ @Jamal shouldn't this be wikified? \$\endgroup\$ – Mathieu Guindon Dec 19 '13 at 13:57
  • 1
    \$\begingroup\$ Possibly related: meta.codereview.stackexchange.com/questions/402/… \$\endgroup\$ – Simon Forsberg Dec 20 '13 at 18:31
  • \$\begingroup\$ What should the naming scheme be for repositories we create? Right now for the "Weekend Challenges" I'm thinking to create simple repository names, such as Sudoku Solver with maybe an indication of the language used included in the name. \$\endgroup\$ – syb0rg Dec 20 '13 at 21:48
  • 1
    \$\begingroup\$ @syb0rg let's try that. Also I'd like to know if we can use the CR beta-logo on there... \$\endgroup\$ – Mathieu Guindon Dec 21 '13 at 0:59
  • \$\begingroup\$ ongoing community project. Rock-paper-scissors? Are you sure? \$\endgroup\$ – Aseem Bansal Dec 21 '13 at 6:53
  • \$\begingroup\$ @AseemBansal canonical implementation - damn right! Check this out: nytimes.com/interactive/science/rock-paper-scissors.html?_r=0 \$\endgroup\$ – Mathieu Guindon Dec 21 '13 at 15:40
5
\$\begingroup\$

Please visit the GitHub Code Review Community page for more information on joining the group.

Please state what language/team(s) you would like to be added to when you open an issue. If your reputation on Code Review any StackExchange site is greater than or equal to 2000, you will be added to the "Admin" team automatically. Please be patient with the processing of your request.

Keep in mind that the reputation requirements for admins is subject to change at the decision of the group owners, and that the community page is still in development.


Questions I need answered by the community

  1. Should I keep or abolish "teams" (related: access permissions)? They seem to be more of a pain then an organization tool to sort the code by language.=

I have some points to make on this subject:

  • How the Code Review Community is going to use GitHub is still being debated and decided. If you want to be part of that process, I recommend you join the "The 2nd Monitor" (Code Review's chatroom).

  • This is not aimed to take you away from the Code Review site. The purpose of reviewing code is intended to find and fix mistakes overlooked in the initial development phase, improving both the overall quality of software and the developers' skills. We want to make this reviewed code available to all, as an example of what code should look like. This is a way we can do that.

  • This is a gateway to community projects (something I am really looking forward to). As @retailcoder put in his post, one project suggestion is to take up and maintain a Stack Exchange chat API (the old unofficial API has gone stagnant, and Stack Exchange does not provide an official API for chat yet). There are other possibilities as well, we just need to decide on a community what to work on together.

\$\endgroup\$
  • 7
    \$\begingroup\$ I think how GitHub is going to be used should be debated & discussed right here on meta :) \$\endgroup\$ – Mathieu Guindon Dec 19 '13 at 1:46

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .