Suggested steps to get ideas moving toward a project #99
Conversation
the participation guidelines bit will link to the forthcoming values documentation
ISSUE_TEMPLATE.md
Outdated
| - [ ] 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. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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.
|
Oh I gotcha, yeah I think issues are turned on by default when creating a
repo, so that step can be removed and replaced with what you said. Perhaps
just the end starting with "Create issues to describe..." and put that link
on the 'create issues' text. I'll commit that in a bit...
|
|
Oh, it also seems they changed their site and a lot of content seems to
have been moved. I'll find a more appropriate link.
|
| - [ ] 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. | ||
| - [ ] [Create issues](https://mozilla.github.io/open-leadership-training-series/articles/get-your-project-online/project-set-up-for-collaboration-with-github/#assignment--add-your-first-issue) to describe each task that you plan to do or need help with and how a contributor can get started on that task. You might start and stop a lot, so consider issues as your to-do list. |
There was a problem hiding this comment.
@mateoclarke how about this?
Now that we have a good set of idea and projects policies in place, I figured it'd be useful to help folks understand what it takes to take an idea and make it a project. I've borrowed heavily from Mozilla's OLTS that I talked about at our last civic tech night, so that's why a lot of links here are also to Mozilla. These are all optional steps, of course, but it's a way to help people find resources and ways of working on their idea. Especially if they're new to working in the open.