The camp from hoodiehq

[hoodie.camp] Custom Team Pages

❓ The Motivation

We aim to be one of open source's most diverse and inclusive communities. One way we try to live up to that ideal is to acknowledge that code contributions are only one part of a healthy Open Source community, hence the different teams in Hoodie: Code, Design, Documentation and Editorial, all equally important. And we are open to add more teams in future as we grow. Everyone who wants to contribute to Hoodie should feel they belong, no matter their talent and interests.

🎯 The goal

Each team should have full control of what to present on their respective team pages. Each team should introduce their mascot, the team’s objective and the people who are currently in charge and what their responsibilities are, but beyond that it’s entirely up to them.

📋 Step by Step

Claim this issue: @gr2m
Create separate templates for each team. Instead of the shared app/templates/team.hbs file, make 4 separate app/templates/teams/:name.hbs files
start a pull request: #33
/teams/code
Dev Beaver welcomes visitor, link to their story. Document on how to Contribute Code, how to Triage issues on the code repositories, role of code maintainers, link to Architecture (or explain architecture), Introduce Gregor as team lead, his responsibilities, show code issues, ...
/teams/editorial
Blog Bear welcomes visitor, link to her story. Move content from the editorial repository’s README and Wiki, introduce Jenn as Editorial lead and her responsibilities. Show editorial issues. Check in with @renrutnnej for review.
/teams/documentation and /teams/design have currently no team leads. Create the pages with content as far as possible, make clear that we are looking for a team lead respectively and what their responsibilities would be. Show issues for both teams.
deploy preview of app somewhere for review: https://hoodie-camp-33.surge.sh/

Update LICENSE in hoodie-store repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-store’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-store’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #47. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

SSL for the deployed site

Is it possible to enable https for github pages?

🐦 Update Twitter, background and avatar

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

Photoshop or equivalent photo-editing software.

🐞 The Issue

A good time to start promoting the Camp Release, as we will host a hackathon as part of EmpireJS week: https://ti.to/hoodie/nyc-meet-the-hoodies-3

Here are source files for a super nice Hoodie Camp illustration: https://www.dropbox.com/sh/ulympy8huj3asnf/AAAPCmgYhio0hATsSLTsEFfHa?dl=0 – shall we use that in the Twitter header? Maybe replacing the current image entirely, or just a few squares as we did in hoodiehq/editorial#60?

We could also update the avatar to remove the hat :) Birthday is over. Here is Low Profile dog without the hat: https://dl.dropboxusercontent.com/u/732913/hoodie/low-profile-dog.png

Would be great if someone could help with it. Any objections?

🎯 The goal

Promote Hoodie Camp at EmpireJS! 🎉

📋 Step by Step

claim this issue: @norkuy
Make changes to source files above.
Submit links to updated source files here by commenting below!
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Blog post about Hoodie 🐶 at OSCON!

This is a starter issue. It’s reserved for participants of OSCON Contribute until May 20th, 2016.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

English, knowledge of markdown is great, but not required!

🐞 The Issue

On May 18, @gr2m will be hosting a new open source event at OSCON in Austin, Texas, to introduce new contributors to Hoodie! 🎉 🐶

We need a contributor to write a brief synopsis about the event and/or take some photos if onsite. ☺️

Also if there are links from mentions on Twitter or to new features/first time PRs please include those!

Helpful resource: our glossary of commonly used terms. Double check your references to popular tech lingo here.

To take on this blog post:

Claim this issue (comment below to claim or assign yourself)
Compose a blog post about the event
Find the instructions for posting a blog post to the Hoodie blog in the hoodiehq/hood.ie repo here.
Submit a pull request (PR) as part of the end of the blog process.
You are done 👏 comment below that your PR is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Update LICENSE in hoodie-account-client repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-account-client’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-account-client’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #40. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

use standard universallay unique IDs for account IDs

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who
did not yet contribute to Hoodie to work on this issue. Follow
@YourFirstPR on Twitter for more of
these issues across many open source projects :)

🤔 What you will need to know

Node.js

❓ The Motivation

Once your Hoodie app reaches a billion user accounts, the likability of id conflicts becomes to high. So before you build the next Facebook with Hoodie, let’s fix this first ;)

🎯 The goal

The current implementation is here: https://github.com/hoodiehq/hoodie-account-server/blob/master/api/accounts/add.js#L13-L15. It uses 12 random hex characters.

What we think makes sense is to follow the convention, see https://en.wikipedia.org/wiki/Universally_unique_identifier.

📋 Step by Step

Claim this issue: @akhillb
Setup the repository locally Ensure the tests pass, or docs build...
Replace the ID generation currently using random string with something that generates a conventional universally unique identifier (version 4). For example, you can use uuid.v4() for that, but we are open for suggestions.
Commit with fix: UUID for account id
Start a Pull Request. hoodiehq/hoodie-account-server#185
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Update LICENSE in hoodie-store-server repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-store-server’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-store-server’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #38. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Update LICENSE in hoodie-log repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you through the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-log’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-log’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #45. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Update LICENSE in hoodie-admin repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-admin’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-admin’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #48. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

🤐🔒 (ssh!) Write Blog Post announcing something very exciting

🤔 What you will need to know

You do not need to know any coding, git or GitHub. Google Docs is perfectly fine for editing, we can take it from there :)
You should have experience with writing and agree that stickers are just the best thing ever. Review our blog to get an idea of what we are looking for, and have a look at our blog process.

About unixstickers and their donation system

donation system http://www.unixstickers.com/blog/unixstickers-new-donation-system-open-letter
😮 buy stickers on their terminal! https://www.unixstickers.com/terminal
partnership with Sticker Mule http://www.unixstickers.com/blog/unixstickers-announces-partnership-with-sticker-mule

🎯 The goal

Two things we have not yet announced (so keep it between us :)) but want to do so in form of a blog post:

We have a Sticker Shop
Unixstickers’ October Campaign is for Hoodie \o/

I know it’s very short term :( but we want to publish a blog post on Monday if possible

💭 Some thoughts / brainstorming

At Hoodie we are very proud of the brand we are building, and our animals and their stories play an integral role.
As an independent Open Source project, being fun is key to win and retain contributors, and stickers are a great way promote our brand. People put them on their laptops, other people see them, ask about them, a conversation starts and the awarness of Hoodie spreads :) Besides they are just cute and a great way for us to say thank you and to share with others.
50% of the revenue goas towards our goal to hire a community manager, see https://twitter.com/hoodiehq/status/744915237854416896
It would be nice to talk to someone at Unix Stickers (or collaborate on this blog post) to get their perspectives on stickers and the motivation behind their monthly donation campaigns
I wonder if we can find out where this whole sticker hysteria came from in Open Source? That would be a nice story to tell :)

📋 Step by Step

🙋 Claim this issue: Comment below (or assign yourself and continue at step 4 :)
Once claimed we add you as contributor to this repository. Please add a link to your blog or articles that you wrote before :)
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind with us 😊
🔄 replace the up for grabs label with in progress.
📝 create a Google Doc and tell us the link at which we can comment on it
Write a first draft of the blog post.
🔀 Start a Pull Request. Mention closes hoodiehq/camp#THIS_ISSUE_NUMBER in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request using the terminal.
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)
Before publishing, add a Stickers! Section to Hoodie’s README file with the image below linked to our shop :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Create a Wikipedia entry for Hoodie

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

How to add/edit entries for Wikipedia, as noted here Your first article and Article development.

🐞 The Issue

There's no Wikipedia entry for Hoodie.

🎯 The goal

Create an entry for Hoodie! 🐶

📋 Step by Step

claim this issue @etopiei
Familiarize yourself with the Wikipedia publication process.
Write a draft of an article for Hoodie
Get feedback on the article from the editorial team
Submit to Wikipedia
Done 👍 Replace up for grabs label with the ready label and ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

using hoodie as hapi plugin: replace options.db with options.PouchDB

🤔 What you will need to know

You should be experienced with JavaScript, Node.js and testing. Some knowledge about hapi.js will help, but won’t be required.

❓ The Motivation

Hoodie is very modular. You can use the main hoodie module standalone or as hapi plugin. Currently the options passed to the server modules are not coherent. For example, hoodie accepts options.db, hoodie-server accepts options.PouchDB and hoodie-account-server accepts options.usersDb. We want to normalise these options across all server modules.

🎯 The goal

The server modules all interact with a database in one way or another, for which we use PouchDB. Currently, hoodie accepts options.db and turns in internally into options.PouchDB in server/index.js#L19-L59. What we want instead is that the register functions defined in server/index.js accepts options.PouchDB, and all the code should live in cli instead.

So make sure to not just rename the option itself, but also adapt the code accordingly :)

📋 Step by Step

🙋 Claim this issue: Comment below
Please only claim if you want to start working on it during the event.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind with us 😊
🔄 replace the up for grabs label with in progress.
If you are an existing Hoodie Contributor, create a new branch. If you are a new contributor, welcome 👋 Please fork hoodie.
Setup the repository locally as described in the testing section. Ensure the tests are all passing.
Adapt test/integration/server-test.js to use the new API, tests should now fail.
🔀 Start a Pull Request. Mention closes hoodiehq/camp#51 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request using the terminal.
Make the necessary changes in the code to make the test pass.
🏁 Done 👍 Once you think your pull request is ready for a first review, replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

🎃🕵💻 Update hoodie to latest good

This is a starter issue.

🎃🙀👕🎓😻 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Node.js, hapi and good.

hapi is a server plugin that we use for all of Hoodie’s server bits. good is a hapi plugin for logging. We use npmlog for setting the log level and for logging warnings, errors etc. We combine the two at https://github.com/hoodiehq/hoodie/blob/master/server/plugins/logger.js.

❓ The Motivation

A new version of good has been released a while ago, and we did not yet managed to update to it. The API has changed.

📋 Step by Step

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

incorrect events in scoped stores

🤔 What you will need to know

JavaScript, git. Basics of Node.js & npm

🐞 The Bug

We run into an issue with our "scoped store API". Hoodie comes with a store API in the browser that looks like hoodie.store.add({foo: 'bar'}) and hoodie.store.find('id123'). A scoped store implicitly sets / assumes the type property, it looks like this:

var todoStore = hoodie.store('todo')
todoStore.add({foo: 'bar'})
// creates document {foo: 'bar', type: 'todo'}

The bug that we found is that our events "add", "update", "remove" and "change" are not behaving correctly on scoped stores. See the full description here: hoodiehq/hoodie-store-client#95

🎯 The goal

We already prepared tests for this issue in this pull request, you only need to enable them and find out how to make them pass :)

📋 Step by Step

Claim this issue @capellini
Setup the repository locally – make sure the setup worked by running all tests with npm test
enable the prepared tests in hoodie-store-client/tests/specs/scoped.js Replace test.skip with just test, remove the comments // prepared for .... Safe the file, then run npm test. You now should see the two tests failing, as expected
Commit the change with test: scoped store events
Start a Pull Request. Mention closes hoodiehq/camp#30 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Fix tests in hoodie-store

This is a starter issue.

🤔 What you will need to know

hoodie-store is one of the core components of Hoodie’s architecture. It integrates the Store Server and the Store Client. It has a demo built in that you can run with npm start, it will show a html page that loads the store client for testing. This demo server is also used for testing.

For testing we use a module called frontend-test-setup, which uses selenium, webdriver, mocha and chai and start a server and then remote control real browsers to run so called end-to-end tests tests. The tests are defined in hoodie-store/test/integration.js. For example, here is the test for store.isConnected

🐞 The Bug

Two tests are currently failing, see this travis build. We don’t know what change introduce the issue, but besides having a potential bug in Hoodie, having failing tests is very inconvenient as we automate our dependency updates with Greenkeeper, and each time there is an update of any dependency and the test fail, Greenkeeper starts a pull request because it thinks that the update broke hoodie-store, while the reason for the failing test is not related to the new module at all. So we get a lot of false positives like this one.

🎯 The goal

Figure out what the issue is. It might be the tests or the implementation in hoodie-store-server, hoodie-store-client, pouchdb-hoodie-api or pouchdb-hoodie-sync.

📋 Step by Step

Claim this issue: @alanmbarr
Setup the repository locally and make sure that you have the same failing tests as in this travis build.
Figure out what the issue is and fix it in the respective repository. Don’t worry about commit messages, we can clean them up before merging your pull request.
Start a Pull Request: hoodiehq-archive/hoodie-store#17
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Upgrade hoodie-app-mapchat to new Hoodie

This is a starter issue.

🎯 The goal

The MapChat App is an example application we built quite a while a go for the old Hoodie. As our Camp Release is about to come out we would like to update it to the latest hoodie. We also use it for a tutorial and would like to update it for the new release, see http://docs.hood.ie/camp/tutorials/map-app.html

📋 Step by Step

claim this issue: @machikoyasuda
Migrate all the usage of Hoodie to the new API :) We recently migrated hoodie-app-skeleton, see the diff here: hoodiehq/hoodie-app-skeleton@master...camp. You can compare the old hoodie.store API to the new one, and the old hoodie.account API to the new one
Commit anyway you like :) We can clean up before merging. I’d suggest you commit something as soon as you get started.
Start a Pull Request. Mention closes hoodiehq/camp#10 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Bundle /hoodie/client.js on demand

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js, some hapi. Knowledge about browserify would be helpful but are not required.

❓ The Motivation

The Hoodie Client is a JavaScript library that gets loaded in the browser using a <script src="/hoodie/client.js> tag, just like jQuery. But unlike jQuery a Hoodie Client is always specific to its Hoodie Server, and must therefore be generated dynamically. We currently do that on every server start, which is quite resource intensive. Sometime the client doesn’t get loaded from server but is bundled into the frontend app, in that case it doesn’t need to be bundled at all.

🎯 The goal

Bundle the Hoodie Client the first with the first GET /hoodie/client.js request. Queue up all following requests until it’s generated and stored in .hoodie/client.js.

The logic for that is currently in hoodie/server/bundle-client.js, it gets required in hoodie/server/index.js

📋 Step by Step

claim this issue
comment below. Once claimed we add you as contributor to this repository, so we can assign you to the ticket and you can start checking off the checkboxes below as you progress. We will also replace the up for grabs label with in progress.
Setup the hoodie repository locally and make sure that all tests pass
Implement the feature. Currently the /hoodie/client.js route is implemented in hoodie/server/plugins/public.js. We might want to move the logic for the hoodie client paths into an own plugin, maybe hoodie/server/plugins/client.js?
Commit with feat: bundle /hoodie/client.js on demand
Don’t worry about wording or amount of commits. We will clean up everything before we merge :) Also feel free to commit work in progress work if you get stuck
Start a Pull Request. Mention closes hoodiehq/camp#5 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Bonus points if you also implement /hoodie/client.min.js, /hoodie/admin/client.js and /hoodie/admin/client.min.js, but we can also create follow up issues for it.
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Update LICENSE in hoodie-client repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-client’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-client’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #39. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Blogpost: Hoodies in NYC for 🗽 EmpireJS!

This is a starter issue. It’s reserved for participants of EmpireJS OSS Night or NYC, Meet the Hoodies!

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

English, knowledge of markdown isn't necessary but it helps. ☺️

🐞 The Issue

The Hoodies (Gregor, Nick, Jenn, Nathan, Nolan) are in NYC this week for EmpireJS and we need to write a blog post about the different events!

We need a contributor to write a brief synopsis about the event and/or gather some photos of the event. ☺️

Also if there are links from mentions on Twitter (from talks or hack events) please include those!

To take on this blog post:

Claim this issue (comment below to claim or assign yourself)
Compose a blog post about the event
Find the instructions for posting a blog post to the Hoodie blog in the hoodiehq/hood.ie repo here.
Submit a pull request (PR) as part of the end of the blog process.
You are done 👏 comment below that your PR is ready for review 🎉

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Run setup in `npm install --save hoodie` posthook script

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

This issue depends on #2.

JavaScript, Node.js, npm post script hooks (see postinstall)

❓ The Motivation

Currently, setting up hoodie takes 2 steps:

npm install --save hoodie
Set the "start" script to "hoodie"

We want to get rid of the 2nd step :)

🎯 The goal

Run the setup from #2 in "postinstall", but only if the install command isnpm install --save hoodieornpm i -S hoodie, not for e.g.npm install`

📋 Step by Step

claim this issue
comment below. Once claimed we add you as contributor to this repository, so we can assign you to the ticket and you can start checking off the checkboxes below as you progress. We will also replace the up for grabs label with in progress.
Setup the hoodie repository locally and make sure that all tests pass
Implement the feature. You’ll need to set "postinstall" script to "npm start setup" but somehow with an extra check, so that it only runs if the original command was npm start setup or npm install --save hoodie (or using one of the aliases like i for install)
Commit with feat: run setup on npm install --save hoodie
Don’t worry about wording or amount of commits. We will clean up everything before we merge :)
Start a Pull Request. Mention closes hoodiehq/camp#3 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

admin.sessions.add({username}) fails with Not Found

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js. Although this is code that runs in the browser, it looks like Node.js code and can be tested with node only.

🐞 The Bug

Setup https://github.com/hoodiehq/hoodie-app-tracker

git clone https://github.com/hoodiehq/hoodie-app-tracker.git
cd hoodie-app-tracker
npm install
npm start

Open http://localhost:8080/hoodie/admin. Sign in with "secret" unless you’ve setup an admin password (don’t worry if not).
Ceate a user account by running this code in your console
```
hoodieAdmin.accounts.add({username: 'foo', password: 'bar'})
```
Reload the page, it should now appear at /hoodie/admin
Now Paste this code in the browser console, watch your network tab in developer tools
```
hoodieAdmin.sessions.add({username: 'foo'})
```

See the Network requests as *.har file at https://gist.githubusercontent.com/gr2m/cad2dc6c39cbdd4098b753ab15e54510/raw/ecd9c801529c475e186a631b90ea2311424ba6b3/camp-issue-11-requests.har. You can downdload it and then upload to https://ericduran.github.io/chromeHAR/ for a webviewer.

🎯 The goal

When signed in as admin (hoodieAdmin.isSignedIn() returns true), hoodieAdmin.sessions.add({username: 'foo'}) should create a user session as documented in https://github.com/hoodiehq/hoodie-account-client/tree/master/admin#adminsessionsadd.

📋 Step by Step

For a bonus, check out all the other methods that require the admin to be signed in. I think e.g. admin.accounts.findAll() are affected, too.

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

admin.signOut() throws "TypeError: Cannot read property 'session' of null"

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js. Although this is code that runs in the browser, it looks like Node.js code and can be tested with node only.

🐞 The Bug

Setup https://github.com/hoodiehq/hoodie-app-tracker

git clone https://github.com/hoodiehq/hoodie-app-tracker.git
cd hoodie-app-tracker
npm install
npm start

Open http://localhost:8080/hoodie/admin.
Run this code in your console
```
hoodieAdmin.signOut()
```

🎯 The goal

When not signed in, hoodieAdmin.signOut() should reject with UnauthenticatedError: Not signed in

📋 Step by Step

claim this issue @capellini
Setup the hoodie repository locally and make sure that all tests pass
Update the docs at hoodie-account-client/admin/README.md. Add UnauthenticatedError: Not signed in to the "rejects with" table
Write a test. You can add it to hoodie-account-client/test/unit/sign-out-test.js. You can also add a new file for sign out to hoodie-account-client/test/integration
make sure that the test fails. If it does, commit the change with test: admin.signOut() throws error when signed out. If you get stuck, feel free to push your work in progress, don’t worry about commit messages, we can clean up things before we merge your work.
Start a Pull Request hoodiehq/hoodie-account-client#113
Implement the fix :) Make sure that tests pass again
Commit with fix: admin.signOut() throws error when signed out
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Update "Getting started with Hoodie - Part 2" tutorial to the Hoodie Camp Release

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🎯 The goal

The current tutorial is empty: http://docs.hood.ie/camp/tutorials/, the docs for the old Hoodie are at http://docs.hood.ie/en/tutorials/. It would be great if we could update it for the new Hoodie. Maybe helpful to see what APIs changed is the diff from the current migration of our Hoodie Skeleton App

📋 Step by Step

claim this issue: @tinyinkling
Update the tutorial :) Even if it’s work in progress, you can start a pull request for https://github.com/hoodiehq/documentation/blob/gh-pages/camp/tutorials/index.md. You can do that right from the browser: click on the edit icon on top right, make your changes, then at the bottom of the page click "Propose File Change" and then "Start Pull Request"
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

What could be a useful UI if an app has no `public/` folder

This is a starter issue.

🤔 What you will need to know

Hoodie is a generic backend for your application, but can also serve your static html application. The latter is not required, it’s a common use case that people run their Hoodie Server somewhere like https://myhoodieapp.com` and the static app is served directly from GitHub pages or surge.s or another hoster for static apps. In that case, when opening the URL of the Hoodie Server should show some generic fallback UI.

🎯 The goal

What could we show in this generic Hoodie UI? Maybe the version? Maybe an explenation of what it is? Maybe link to the other generic UIs at /hoodie, /hoodie/account and /hoodie/store? Maybe we should directly show the admin UI that is usually at /hoodie/admin? We are open for ideas

This is not really a bug that needs to be fixed or a feature that needs to be implement, but an invite for a discussion. Please ask all your questions here, we are looking forward for your thoughts! Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Review Camp App tutorial

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

We created a tutorial in form of a web page that uses Hoodie & ServiceWorker to show how to build an offline app. The source code is at https://github.com/hoodiehq/hoodie-camp-tutorial, you can test it out online at https://camp-tutorial.hood.ie/.

🎯 The goal

We created this tutorial in a hurry and we are not native English Speakers, nor do we have much experience in technical writing. It would be great if you could help us by reviewing it.

Feel free to edit the pages directly on GitHub and send pull requests with suggestions. All html pages are here: https://github.com/hoodiehq/hoodie-camp-tutorial/tree/master/public, you can edit them directly in your browse (click on one of them, then click the edit icon on top right, make your change, click the button "Propose File Change" then click "Start Pull Request".

If you have any questions or have ideas, we can discuss in this issue, comment below

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

What could be a useful UI for `/hoodie/store`?

This is a starter issue.

🤔 What you will need to know

Hoodie is a generic backend for your application, but also provides a few UIs (html pages) out of the box. There is /hoodie/store, /hoodie/account and /hoodie/admin at this point.

🎯 The goal

What could we show at /hoodie/store? Every Hoodie Server will have this page. For example we could display some kind of generic tables, showing all data by the current user. We could dynamically read out what types of data the user stored and show tabs for different tables. We could provide an export button so a user of a hoodie app can export their data at anytime. We are looking forward to your thoughts.

The current placeholder page is at https://github.com/hoodiehq/hoodie-store/blob/master/public/index.html. But we can also implement more sophisticated UIs with a single page application. Everything is possible right now :)

This is not really a bug that needs to be fixed or a feature that needs to be implement, but an invite for a discussion. Please ask all your questions here, we are looking forward for your thoughts! Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Proofread Camp Docs 📝

This is a starter issue. It’s reserved for participants of OSCON Contribute until May 20th, 2016.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

Strong command of English language/grammar. Knowledge of code (JavaScript, Node.js) is not essential, but helpful.

🐞 The Issue

Proofread and suggest corrections to the new Camp documentation found here: http://docs.hood.ie/camp/.

🎯 The goal

Finding typos, formatting errors, etc. – any small error that might distract a new contributor when trying to learn from the new documentation.

Helpful resource: our glossary of commonly used terms. Double check your references to popular tech lingo here.

📋 Step by Step

claim this issue
comment below. Once claimed we add you as contributor to this repository, so we can assign you to the ticket and you can start checking off the checkboxes below as you progress. We will also replace the ready label with in progress.
Review the documentation beginning on the welcoming page all the way through the glossary.
Start a Pull Request. hoodiehq-archive/documentation#219
Done 👍 Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

don’t write files when run in memory

This is a starter issue.

🤔 What you will need to know

JavaScript, Node.js.

❓ The Motivation

Hoodie can run in an "in memory" mode, meaning that it doesn’t persist any data to the hard drive. All data vanishes when the server stops. This is great for testing, and for quick deployments to read-only systems like Heroku or now.

But even when run in memory, the Hoodie Server still writes .hoodie/config.json and .hoodie/client.js, which is causing issues in read-only systems and is unexpected behavior.

🎯 The goal

When started with npm start -- --inMemory no files should be written at all. The Hoodie client can be kept in memory after bundling and not written to the hard drive. And the .hoodie/config.json file should not be written at all. But if it exists, Add a log.info("Configuration read from .hoodie/config.json") (with the right dynamic path.

Currently the .hoodie/config.json is written when the server secret is generated, see hoodie/server/config/db/pouchdb.js . But when run in memory, that doesn’t make any sense as there is no initial data like user accounts. The server secret is used to calculate session IDs, but all existing sessions get invalidated on restart as all accounts vanish.

📋 Step by Step

claim this issue @gr2m
Setup the hoodie repository locally and make sure that all tests pass
Implement the feature :)
Commit with feat: don’t write files when run in memory
Don’t worry about wording or amount of commits. We will clean up everything before we merge :) Also please commit work in progress things if you get stuck, we can work on it together in the PR.
Start a Pull Request: hoodiehq/hoodie#510
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

What could be a useful UI for `/hoodie`

This is a starter issue.

🤔 What you will need to know

Hoodie is a generic backend for your application, but also provides a few UIs (html pages) out of the box. These are /hoodie where we want to show some generic information about Hoodie or what ever makes sense. There is also /hoodie/store and /hoodie/account

🎯 The goal

What could we show at /hoodie? Every Hoodie Server will have this page. The current placeholder page is here: https://github.com/hoodiehq/hoodie/blob/master/public/index.html, you can see it in action at https://tracker.hood.ie/hoodie/

This is not really a bug that needs to be fixed or a feature that needs to be implement, but an invite for a discussion. Please ask all your questions here, we are looking forward for your thoughts! Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Make `npm start help` an alias for `npm start -- --help`

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js. Knowledge about npm would be helpful but are not required.

❓ The Motivation

We try to integrate very tightly with npm and its eco system. Instead of creating our own CLI tool, we want to use npm directly. At this point we only use the npm start script to start the Hoodie Server, in future we might want to have all kind of commands like npm start setup, npm start console, etc. npm start help is a simple way to prepare the basic setup for it.

🎯 The goal

When running npm start help, the output should be the same as npm start -- --help. Tests are not required, but of course very much welcomed.

📋 Step by Step

claim this issue: @kellyjandrews
mentor: @gr2m
Setup the hoodie repository locally and make sure that all tests pass
Implement the feature. npm start executes the hoodie binary which is hoodie/bin/start.js as defined here. The source code of package-scripts might be helpful to figure out how to read out the part after npm start ...
Commit with feat: npm start help
Don’t worry about wording or amount of commits. We will clean up everything before we merge :)
Start a Pull Request. Mention closes hoodiehq/camp#1 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Update Deployment Docs to a Linux Server

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

We have documentation on how to deploy the old Hoodie to a linux server at https://github.com/hoodiehq/documentation/blob/gh-pages/en/deployment/linux.md. For the new "Camp Release", a lot has changed (and got simpler we hope), so the docs need to be updated. The current version is at http://docs.hood.ie/en/latest/guides/deployment.html.

🎯 The goal

It would be nice to have docs on how to deploy an app based on the new Hoodie to Linux. We have setup continous deployment for our Hoodie Tracker example app, docs are here: https://github.com/hoodiehq/hoodie-app-tracker/blob/master/deployment.md – maybe that’l help?

📋 Step by Step

🙋 Claim this issue: Comment below (or assign yourself and continue at step 4 :)
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind with us 😊
🔄 replace the up for grabs label with in progress.
Update the docs :) Even if it’s work in progress, you can start a pull request for https://github.com/hoodiehq/hoodie/blob/master/docs/guides/deployment.rst. You can do that right from the browser: click on the edit icon on top right, make your changes, then at the bottom of the page click "Propose File Change" and then "Start Pull Request"
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Update LICENSE in hoodie-connection-status repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-connection-status’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-connection-status’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #44. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Hoodie default UI

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js. Maybe some hapi but shouldn’t be too much.

❓ The Motivation

Hoodie as a page that is displayed at /hoodie. It’s not very helpful at this page, but we’ll get there :) Here’s how it currently looks like: https://tracker.hood.ie/hoodie/

The same html page is shown at the / root path if your app has no public/ folder. But we want to differentiate between these two cases, as they have two different use cases.

🎯 The goal

If your app has no public/ folder, the Hoodie Server should show a fallback UI. When opening /hoodie in your app, the server should show the contents of hoodie/public.

📋 Step by Step

claim this issue: @distalx
Setup the hoodie repository locally and make sure that all tests pass
Implement the feature :) The check if the app has a public/ folder is currently implemented in hoodie/server/config/index.js
Commit with feat: Hoodie default UI
Don’t worry about wording or amount of commits. We will clean up everything before we merge :) Also please commit work in progress things if you get stuck, we can work on it together in the PR, and others can take over.
Start a Pull Request. Mention closes hoodiehq/camp#8 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

💯 Code Coverage for Hoodie Account Server

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js. Knowledge about npm would be helpful but are not required, you’ll figure it out as you go :)

🎯 The goal

100% code coverage makes sure that every single line of code is covered by tests. And it looks pretty cool once we have all the 💯 for all modules in Hoodie’s Architecture

The current status is

📋 Step by Step

🙋 Claim this issue: Comment below (or assign yourself and continue at step 4 :)
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind with us 😊
🔄 replace the up for grabs label with in progress.
Setup the repository locally Ensure the tests pass
Bring coverage to 100%. Use the following steps
- run node_modules/.bin/nyc report --reporter=lcov
- open coverage/lcov-report/index.html. It will look something like this:
- ProTip™: run a single test with node_modules/.bin/tap tests/integration/api/accounts-test.js
- If you get stuck or have any questions, start a pull request, that will help
  with the discussion
🔀 Start a Pull Request. Mention closes hoodiehq/camp#53 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request using the terminal.
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Coordinate with #52 as we need to write a test for plugin/index.js, to avoid duplicated work :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Update LICENSE in hoodie-account repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-account’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-account’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #46. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Update LICENSE in hoodie-store-client repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-store-client’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-store-client’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #41. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

💯 Code Coverage for hoodie

This is a starter issue. It’s reserved for participants of OSCON Contribute until May 20th, 2016.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js. Knowledge about npm would be helpful but are not required, you’ll figure it out as you go :)

🎯 The goal

100% code coverage makes sure that every single line of code is covered by tests. And it looks pretty cool once we have all the 💯 for all modules in Hoodie’s Architecture

The current status is

📋 Step by Step

claim this issue: assign yourself if you are part of the Hoodie team, otherwise comment below :)
replace up for grabs label with in progress
Setup the hoodie repository locally and make sure that all tests pass
Bring coverage to 100%. Use the following steps
- run npm test
- run node_modules/.bin/nyc report --reporter=lcov
- open coverage/lcov-report/index.html. It will look something like this:
If you are all 100%, commit with test: 100% coverage. If you have blockers commit with test: coverage and move on, we can discuss details in the pull request
Start a Pull Request. Mention closes hoodiehq/camp#4 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Update LICENSE in hoodie-account-server repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-account-server’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-account-server’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #37. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

What could be a useful UI for `/hoodie/account`?

This is a starter issue.

🤔 What you will need to know

Hoodie is a generic backend for your application, but also provides a few UIs (html pages) out of the box. There is /hoodie/account, /hoodie/store and /hoodie/admin at this point.

🎯 The goal

What could we show at /hoodie/account? Every Hoodie Server will have this page. Maybe something like the Account Page of our Tracker Example app?

The current placeholder page is at https://github.com/hoodiehq/hoodie-account/blob/master/public/index.html. But we can also implement more sophisticated UIs with a single page application. Everything is possible right now :)

This is not really a bug that needs to be fixed or a feature that needs to be implement, but an invite for a discussion. Please ask all your questions here, we are looking forward for your thoughts! Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Hoodie Account Server: replace options.usersDb with options.PouchDB

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

You should be experienced with JavaScript, Node.js and testing. Some knowledge about hapi.js will help, but won’t be required.

❓ The Motivation

Hoodie is very modular. Currently the options passed to the server modules are not coherent. For example, hoodie accepts options.db, hoodie-server accepts options.PouchDB and hoodie-account-server accepts options.usersDb. We want to normalise these options across all server modules.

🎯 The goal

The server modules all interact with a database in one way or another, for which we use PouchDB. Currently, hoodie-account-server accepts options.usersDb which is a PouchDB instance, and then internally gets PouchDB from its constructor at plugin/index.js#L23. What we want instead is that the register functions defined in plugin/index.js accepts options.PouchDB, and the users database should be initialised in there instead of outside of the plugin.

📋 Step by Step

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

pouchdb-hoodie-api: use .changes() for events

🤔 What you will need to know

This one is challenging. I tried it myself a few months ago and failed. You should know the JavaScript Event Loop, understand why an immediately resolved Promise and process.nextTick() do not call their callbacks always in the same order, ideally find a way to change that or a work around.

🎯 The goal

We once had a very simple, beautiful solution for events in pouchdb-hoodie-api: we started listening to PouchDB’s changes feed and used that to emit add, update and change events. But then we hit hoodiehq/pouchdb-hoodie-api#54 which caused a timing issue, and after trying for a while to work around the problem while still using the changes feed, we eventually gave up. Instead of listening to the changes feed, we wrap all our methods and emit events manually, see changes here: https://github.com/hoodiehq/pouchdb-hoodie-api/pull/56/files

Another problem with just using .changes() is that we cannot differentiate between changes coming from remote (via sync) or changes created locally.

But we feel there is a better way, and it’s worth looking for it, it would remove a lot of complexity. And whoever finds a solution for this, gets a special Hoodie treat that I’ll have to make up first, but I promise it will be something nice <3

📋 Step by Step

🙋 Claim this issue: Comment below
Please only claim if you want to start working on it during the event.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
Setup the hoodie repository locally and make sure that all tests pass
Find a solution 💚
Start a Pull Request. Mention closes hoodiehq/camp#13 in the description.
You don’t need to be finished to start the PR, I’d suggest to start it as soon as possible so we can discuss different approaches and collaborate on it
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

📑🖋 Update LICENSE in hoodie-server repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-server’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-server’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #36. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Update LICENSE in pouchdb-hoodie-sync repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/pouchdb-hoodie-sync’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/pouchdb-hoodie-sync’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #43. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

Update LICENSE in pouchdb-hoodie-api repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/pouchdb-hoodie-api’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/pouchdb-hoodie-api’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #42. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

allow `new Account(url)` as shortcut for `new Account({url: url})`

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js. Although this is code that runs in the browser, it looks like Node.js code and can be tested with node only.

🎯 The goal

A URL is required to initialise the Account Client. But instead of requiring to pass in an object with a .url property, we want to allow to pass in a string as a shortcut, so these two would be equivalent:

new Account({url: 'http://example.com/account/api'})
new Account('http://example.com/account/api')

📋 Step by Step

claim this issue @thomasjinlo
Setup the hoodie repository locally and make sure that all tests pass
Write a test. You can add it to hoodie-account-client/test/integration/constructor-test.js
make sure that the test fails. If it does, commit the change with test: new Account(url). If you get stuck, feel free to push your work in progress, don’t worry about commit messages, we can clean up things before we merge your work.
Start a Pull Request: hoodiehq/hoodie-account-client#114
Implement the fix :) Make sure that tests pass again
Commit with feat: new Account(url)
If you like, do the same for new AccountAdmin(url). See hoodie-account-client/admin/index.js and hoodie-account-client/test/integration/admin-constructor-test.js. If not we can do a follow up issue for this one
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

npm start -- console

This is a starter issue.

Your First Pull Request?

We would like to take the opportunity to invite someone who did not yet contribute to Hoodie to work on this issue. Follow @YourFirstPR on Twitter for more of these issues across many open source projects :)

🤔 What you will need to know

JavaScript, Node.js. See also #1 and #2 if we have aliases in place, then we can also support npm start console as alias for npm start -- console

❓ The Motivation

Rails has it and we think it’d be pretty cool for Hoodie, too. It would be great to quickly send queries to the database using simple JavaScript methods.

🎯 The goal

npm start -- console starts the Hoodie Server in the background and a REPL with a pre-initialised HoodieAdmin Client instance and logged in as admin. All instance methods are directly accessible (without signIn, signOut, isSignedIn, username), so you can do things like

> accounts.findAll()

the REPL would see that a promise got returned, show a loader, then either show the error or what ever the promise resolved with in the best way possible, e.g. a table in this case

📋 Step by Step

claim this issue
comment below. Once claimed we add you as contributor to this repository, so we can assign you to the ticket and you can start checking off the checkboxes below as you progress. We will also replace the up for grabs label with in progress.
Setup the hoodie repository locally and make sure that all tests pass
Implement the feature :) We know this is quite a challenge, no need to finish it off completely, it’s not blocking any other work, we can do this step by step
Commit with feat: npm start -- console
Don’t worry about wording or amount of commits. We will clean up everything before we merge :) Also please commit work in progress things if you get stuck, we can work on it together in the PR.
Start a Pull Request. Mention closes hoodiehq/camp#7 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

Update LICENSE in hoodie-admin-client repository

This is a starter issue.

🆕🐥☝ First Timers Only

This issue is reserved for people who never contributed to Open Source before. We know that the process of creating a pull request is the biggest barrier for new contributors. This issue is for you 💝 Read more about First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

If you haven’t yet, sign up for Hacktoberfest to earn an exclusive T-Shirt. Plus I’m sure we can teach you a cool trick or two in the process

🤔 What you will need to know

Nothing. This issue is meant to welcome you to Open Source :) We are happy to walk you trough the process

❓ The Motivation

GitHub recently released a new feature which shows the repository’s license on the overview page. While all of Hoodie’s repositories have a License (Apache-2.0), it is not displayed on the overview. The reason is that our LICENSE files are missing a few parts.

🎯 The goal

The license should be displayed on hoodiehq/hoodie-admin-client’s overview page like it is displayed on the hoodiehq/hoodie repository

📋 Step by Step

🙋 Claim this issue: Comment below
Please 🙏 only claim if you want to start working on it within a day.
Once claimed we add you as contributor to this repository.
👌 Accept our invitation to this repository. Once accepted, assign yourself to this repository
👓 Please review our Code of Conduct
In a nutshell: be patient and actively kind
🔄 replace the up for grabs label with in progress.
📝 Edit hoodiehq/hoodie-admin-client’s LICENSE file and replace its content with the content of hoodiehq/hoodie’s LICENSE file.
💾 Commit your changes with the message chore(LICENSE): use standard Apache V2.0 text
🔀 Start a Pull Request. Set the title to LICENSE: use standard Apache V2.0 text and set description to `closes #49. There are two ways how you can start a pull request:
1. If you are familiar with the terminal or would like to learn it, here is a great tutorial on how to send a pull request using the terminal.
2. You can edit files directly in your browser
🏁 Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

🤔❓ Questions

Ping us in the Hoodie Chat or on Twitter

hoodie.account.isSignedIn() returns true in “signout" event handler

This is a starter issue.

🤔 What you will need to know

JavaScript, Node.js. Although this is code that runs in the browser, it looks like Node.js code and can be tested with node only.

🐞 The Bug

hoodie.account.on('signout', function () {
  alert(hoodie.account.isSignedIn()) // true, should be false
})
hoodie.account.signOut()

You can run the code on https://tracker.hood.ie/ – create an account, then open the console, paste it in and run it.

🎯 The goal

hoodie.account.isSignedIn() should return false in the 'signout' event handler.

📋 Step by Step

claim this issue: @dsims00
mentor: @gr2m
Setup the hoodie repository locally and make sure that all tests pass
Un-skip the test: We prepared a test, follow the instructions here
Start a Pull Request. Mention closes hoodiehq/camp#9 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Implement the fix :) Make sure that tests pass again
Commit with `fix: isSignedIn() returns false in signout event handler
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

npm start -- setup

This is a starter issue.

🤔 What you will need to know

JavaScript, Node.js. Knowledge about npm would be helpful but are not required.

❓ The Motivation

We try to integrate very tightly with npm and its eco system. Instead of creating our own CLI tool, we want to use npm directly. At this point we only use the npm start script to start the Hoodie Server, in future we might want to have all kind of commands like npm start setup, npm start console, etc.

🎯 The goal

When running npm start setup, the Hoodie Server should not get started. Instead the following things should happen:

Create a README.md unless it already exists. Put in dummy content for now
Set the "start" script in package.json to "hoodie" (see setup instructions)

📋 Step by Step

claim this issue (comment below or assign yourself if you can)
Setup the hoodie repository locally and make sure that all tests pass
Implement the feature. hoodie executes the binary which is hoodie/bin/start.js as defined here. Instead of calling the cli function, check if the setup argument was passed and if yes, do the setup as described :) A first step (and commit) could be a console.log('setup'), to get a pull request going.
Commit with feat: hoodie setup
Don’t worry about wording or amount of commits. We will clean up everything before we merge :)
Start a Pull Request. Mention closes hoodiehq/camp#2 in the description.
If this is your first, welcome 🎉 😄 Here is a great tutorial on how to send a pull request
Done 👍 Replace the in progress label with ready. Ask in comments for a review :)

Ping us in the Hoodie Chat or on Twitter if you have any questions :)

hoodiehq / camp Goto Github PK

camp's People

Contributors

Stargazers

Watchers

Forkers

camp's Issues

❓ The Motivation

🎯 The goal

📋 Step by Step

🆕🐥☝ First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

🤔 What you will need to know

❓ The Motivation

🎯 The goal

📋 Step by Step

🤔❓ Questions

Your First Pull Request?

🤔 What you will need to know

🐞 The Issue

🎯 The goal

📋 Step by Step

Your First Pull Request?

🤔 What you will need to know

🐞 The Issue

🆕🐥☝ First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

🤔 What you will need to know

❓ The Motivation

🎯 The goal

📋 Step by Step

🤔❓ Questions

Your First Pull Request?

🤔 What you will need to know

❓ The Motivation

🎯 The goal

📋 Step by Step

🆕🐥☝ First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

🤔 What you will need to know

❓ The Motivation

🎯 The goal

📋 Step by Step

🤔❓ Questions

🆕🐥☝ First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

🤔 What you will need to know

❓ The Motivation

🎯 The goal

📋 Step by Step

🤔❓ Questions

🆕🐥☝ First Timers Only

🎃💻👕 Hacktoberfest: Trick or Treat!

🤔 What you will need to know

❓ The Motivation

🎯 The goal

📋 Step by Step

🤔❓ Questions

🤔 What you will need to know

About unixstickers and their donation system

🎯 The goal

💭 Some thoughts / brainstorming

📋 Step by Step

🤔❓ Questions

Your First Pull Request?

🤔 What you will need to know

🐞 The Issue

🎯 The goal

📋 Step by Step

🤔 What you will need to know

❓ The Motivation

🎯 The goal

📋 Step by Step

🤔❓ Questions

🎃🙀👕🎓😻 Hacktoberfest: Trick or Treat!

🤔 What you will need to know

❓ The Motivation

📋 Step by Step

🤔 What you will need to know

🐞 The Bug