Human Connection
docs_fix_link
docs_fix_link
  • Introduction
  • Edit this Documentation
  • Installation
  • Backend
    • graphql-with-apollo
      • GraphQL with Apollo
        • Mocking
        • Seeding
    • Import
    • Middleware
  • Webapp
    • COMPONENTS
    • PLUGINS
    • STORE
    • PAGES
    • ASSETS
    • LAYOUTS
    • Styleguide
    • STATIC
    • MIDDLEWARE
  • Testing Guide
    • End-to-end tests
    • Frontend tests
    • Backend tests
  • Contributing
  • Deployment
  • Feature Specification
  • Code of conduct
  • License
Powered by GitBook
On this page
  • Getting Set Up
  • Development
  • Philosophy
  • Notes

Was this helpful?

Contributing

PreviousBackend testsNextDeployment

Last updated 6 years ago

Was this helpful?

Thanks so much for thinking of contributing to the Human Connection project, we really appreciate it! :-)

Getting Set Up

Instructions for how to install all the necessary software can be found in our

We recommend that new folks should ideally work together with an existing developer. Please join our discord instance to chat with developers or just ask them in tickets in :

Here are some general notes on our development flow:

Development

  • Currently operating in two week sprints

  • We are using ZenHub to coordinate

    • ordering on ZenHub not necessarily reflected on github projects

  • AgileVentures run open pairing sessions at 10:30am UTC each week on Tuesdays and Thursdays

  • Core team

    • all the people who are hired by HC non-profit corporation

    • 9 people

      • 3 marketeers Jasi, Dennis and Sensi

      • Hardy doing business development

      • Martin head of IT and previously data protection officer

      • Victor doing accounting and controlling

      • Nicolas is the community manager (reviews content in the network) reflects community opinion back to the core team

  • when can folks pair with Robert

    • 10am UTC until 5pm UTC every working day

Philosophy

  • anyone can start working on anyone elses code

  • we avoid blocking because someone else isn't working on something

  • however it's sometimes good to leave something in order to create successful education experience

  • everyone should always push their code to branches so others can see it

Everyone feel free to request merges or answers to issues from the project managers

But what do we do when waiting for merge into master (wanting to keep PRs small) --> Robert recommends creating a pull request for each step

  • programming is also about thinking about other people - empathy for your co-workers

    • but what about when you are waiting for merge?

    • solutions

      • 1) put 2nd PR into branch that the first PR is hitting - but requires update after merging

      • 2) prefer to leave exiting PR until it can be reviewed, and instead go and work on some other part of the codebase that is not impacted by the first PR

Notes

question: when you want to pick a task - (find out priority) - is it in discord? is it in AV slack? --> Robert says you can always ask in discord - group channels are the best

Matt makes point that new stories will have to be taken off the "New Issues" and Robert says that's fine, if you don't like the first one, then you can take the next one. Volunteeers have no commitment except their own self development and their awesomeness by contributing to free and open-source software projects.

Robert notes that everyone is invited to join the kickoff meetings

Robert - difference between "important" (creates a lot of value) and "beginner friendly" (easy to implement)

estimating time per issue is the crucial feature of that Github does not have

"up-for-grabs" links to [Github project]()

you can Meet-the-team and .

2 core developers (Robert and Greg )

We practise rather than strong code ownership, which means that:

Robert shares: Robert says the order of tickets are preserved in ZenHub and reflect their priority (most important at the top) and so check out the current milestones

Matt - question about who can work on --> Robert - in rare occasions it might be exclusive to someone with admin permissions Robert: notes greg just pushed this today:

Zenhub
https://github.com/orgs/Human-Connection/projects/10?card_filter_query=label%3A"good+first+issue
every two weeks in German
every month in English
@roschaefer
@appinteractive
collective code ownership
Zenhub board
ticket 100
https://github.com/Human-Connection/Nitro-Deployment
documentation
Zenhub