Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Suggested steps to get ideas moving toward a project #99

Merged
merged 3 commits into from
May 23, 2017
Merged

Suggested steps to get ideas moving toward a project #99

Changes from 2 commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f69aa1b
added some extra steps folks can take
werdnanoslen Apr 19, 2017
0272328
added values link
werdnanoslen Apr 20, 2017
6d69cfc
rephrased step re:issues, updated link
werdnanoslen May 21, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
45 changes: 42 additions & 3 deletions ISSUE_TEMPLATE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,19 +1,58 @@
<!--- Keep everything below and click 'Submit new issue' --->

### What problem are we trying to solve?

Answer here.


### Who will benefit (directly and indirectly) from this project?

Answer here.

### Links to any research/data available/articles

### Where can we find any research/data available/articles?

Links here.

### What are the next steps (validation, research, coding, design)?

### What help is needed at this time?

Answer here.

### What help is needed at this time?

### What are the next steps (validation, research, coding, design)?

Answer here.

----
<!--- You can skip the following for now, but come back to it later! --->

### Project management

#### Checklist for NEW ideas :baby:
Hey, you're official! You're now part of the growing civic hacking community in Austin. Here's a few things to get started (a couple you've probably already done).

- [x] Create this idea issue
- [x] Flesh out the who, where, and what questions above
- [ ] Start the conversation about this new idea on [Slack](https://openaustin-slackin.herokuapp.com/)!
- [ ] Respond with at least one update on this issue within the next month

#### Checklist for ACTIVE projects :fire:
Let's get this project started! When this idea starts taking off, the Projects Core Team will start helping this project's lead(s) out with project management and connecting you to resources you may need. To get there, please complete and check off the following:

- [ ] Complete [Open Leadership 101](https://mozilla.teachable.com/p/open-leadership-101)
- [ ] Create a [GitHub repository](https://github.com/new) and Slack channel for work.
- [ ] Create a [README file](https://mozilla.github.io/open-leadership-training-series/articles/opening-your-project/write-a-great-project-readme/) in your project repository. This file should help newcomers understand what your project is, why it's important, and kinds of help you're looking for.
- [ ] Turn on your [Issue Tracker](https://mozilla.github.io/global-sprint/project-lead/templates/#4-create-issues) and create issues to describe each task that you need help with and how a contributor can get started on that task.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't understand this step and the link didn't provide any clarity. Could we just say the todo is to create some Github Issues or adopt a tool like Trello to manage tickets? I think this could go even more in-depth about creating labels and fleshing out issues so it is easy for ppl to jump in and contribute

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You mean all four steps? The Open Leadership 101 is a way to ensure that folks who want to take an idea to a project know some fundamentals of open project management and know of this source as a guide for reference later. The README is the closest thing to a front page for non-GIthub savvy users to using a Github repo, so it's extremely important, as is the issue tracker for providing an open area for collaboration that is also more permanent and trackable than Slack. Trello could also go here, but I don't want to make folks think they need so many different tools to get a project started.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I didn't understand line 46. "Turn on your [Issue Tracker]" And the link didn't make sense with it. I think it would be more clear if you explained that they should either create Issues in a Github repo or Trello. All I was suggesting is for the Issue Tracker line to provide more details and direction.


#### Checklist for FEATURED Projects :tada:
To have your project FEATURED on [Open-Austin.org](https://open-austin.org/), complete the following documentation. In past projects, well-documented featured projects have more contributions than other projects.

* [ ] In your README, link to the [Open Austin Community Participation Guidelines](https://docs.google.com/document/d/1OujyBccPpepUXSY5_nP3alzvd81WlCKSeSf_-sU5K-U/edit?usp=sharing) or write your own code of conduct.
* [ ] [Create file: LICENSE](http://choosealicense.com/) to give your project an open license, allowing for sharing and remixing.
* [ ] [Create file: CONTRIBUTING.md](https://github.com/acabunoc/mozsprint-repo-template/blob/master/CONTRIBUTING.md) so others know [how they can contribute](https://mozilla.github.io/open-leadership-training-series/articles/building-communities-of-contributors/write-contributor-guidelines/).

Once all of the above is complete,
- [ ] [Create an issue](https://github.com/open-austin/open-austin.github.io/issues/new) on the open-austin.github.io repo with the title `Add [this project] to projects page. An Open Austin leader will review this issue and post your project :balloon:

If you get stuck at any point, feel free to reach out to the leadership team on Slack by adding @leadership to your message. We're here to help you make real changes to our city.