Wheelmap OpenSource

[lennerd]

• [x] Add license file
• [x] Last check for any security vulnerabilities
• [ ] Add contribution guidelines
• [ ] Issue Templates
• [x] Add code of conduct - PR #298
• [x] Add automatic testing (Travis CI) #24
• [x] Define milestones or todos
• [x] Push the button

[lennerd]

@skade Would you mind to have the last check for any security vulnerabilities? Would be great to open the repository to the community before the event later in the evening today.

[skade]

Yep, will do.

On 28 Sep 2015, at 08:17, Lennart Hildebrandt notifications@github.com wrote:

@skade https://github.com/skade Would you mind to have the last check for any security vulnerabilities? Would be great to open the repository to the community before the event later in the evening today.

— Reply to this email directly or view it on GitHub https://github.com/sozialhelden/wheelmap/issues/17#issuecomment-143650314.

[christoph-buente]

The travis build can only be activated, once the repo is public. Otherwise we have to pay for it.

[lennerd]

Ah right. Yeah, more importantly is the last security check. The rest can come when this repo is open.

[skade]

@lennerd maybe present this as the first issue that can be worked on? ;)

[skade]

This is obviously not a complete and long review, but I'm fine with the current state. Also, we handle most non-public data out of our system.

[lennerd]

Awesome! :+1:

[1000miles]

cc @holgerd @lennerd

As discussed with @lennerd today I can take care of the last two open tasks (if there is a bit time):

• [ ] Add contribution guidelines
• [x] Add code of conduct

For the code of conduct I need the infos from Sozialhelden which code of conduct you want to use, an overview of some code of conducts in tech are listed here: https://github.com/1000miles/coc-collections

Regarding the contribution guidelines I need the input from Sozialhelden, maybe you (@holgerd) can provide us some text by your collegues for content management?

[lennerd]

See example: https://github.com/pouchdb/pouchdb

[lennerd]

• [ ] spike: how shall onboarding new contributers work?

[1000miles]

More ideas for contributions:

Phase 1:

• [ ] Short text: welcome, important infos
• [ ] Links to wiki, code of conduct, license, website, faq
• [ ] Contact options (which contact infos should we use?)

Phase 2 (later):

• [ ] Values & expectations for collaboration
• [ ] Steps for creating issues or pull requests
• [ ] Links to more external documentation (testing, debugging, changelog, etc.)