You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: how-to-work-with-us/consulting/readme.md
+5-5
Original file line number
Diff line number
Diff line change
@@ -18,18 +18,18 @@ But it's hard for us to help every member individually and there are many member
18
18
19
19
- Want to use the tools we have built (particularly Largo) but may require some help setting them up or customizing them to suit their needs
20
20
- In some cases may require additional custom development to add functionality that we have not yet built
21
-
- Would be willing to pay (provided our rates are competitive) for our services and even pay us to host their sites in the same way we host sites for members.
21
+
- Would be willing to pay (provided [our rates](consulting-rates.md) are competitive) for our services and even pay us to host their sites in the same way we host sites for members.
22
22
23
23
Until now we’ve been referring people to outside contractors and freelancers, but as we continue to grow our technology team we have the capability to take on <em>some</em> of this work ourselves.
24
24
25
-
For INN members, we will subsidize the cost of these services to keep them very affordable (see the rates section below for details). We will also, from time to time, take on work from non-members (at regular market rates).
25
+
For INN members, we will subsidize the cost of these services to keep them very affordable (see [our rates](consulting-rates.md) for details). We will also, from time to time, take on work from non-members (at regular market rates).
26
26
27
27
**Some examples of the services we offer include:**
28
28
29
29
- Content migration, design customization and custom development for members using our Largo platform beyond what we're able to do for "free" as a benefit of INN membership
30
-
- Assistance with editorial design and development for news apps, data projects or special series
30
+
- Assistance with editorial design and development for news apps, data projects or special projects
31
31
- Ongoing or project-based support, training and assistance with story production
32
-
-Design and development of microsites or other special projects
32
+
-Assistance with general technology strategy, recruiting and hiring, and building and managing technology resources at your organization.
33
33
34
34
**Taking on this additional paid work will allow us to:**
35
35
@@ -42,4 +42,4 @@ We hope that this new program will be a win-win for members and for INN and that
42
42
43
43
If you're interested in working with us, we'd love to discuss your needs and how we can help. [Get in touch with us here](mailto:[email protected]) to learn more.
44
44
45
-
We've also assembled an FAQ to provide more detail on the program.
45
+
We've also assembled a list of [frequently asked questions](consulting-faq.md) to provide more detail on the program.
Copy file name to clipboardexpand all lines: how-to-work-with-us/contributing.md
+12-11
Original file line number
Diff line number
Diff line change
@@ -1,18 +1,19 @@
1
1
# Code of conduct and how to contribute
2
2
3
-
Since the INN nerds team works primarily with open source projects in public spaces, we think it's important to identify some community guidelines for how we like to work, what we expect from the people we work with, and how to contribute to our projects.
3
+
Since the INN nerds team works primarily with open source projects in public spaces, we think it's important to identify some community guidelines for how we like to work, what we expect from the people we work with and how to contribute to our projects.
4
4
5
-
## Code of conduct
5
+
###Code of conduct
6
6
7
7
1. Be welcoming, friendly, patient, kind, courteous and respectful.
8
8
2. Use your best judgment — if you're not sure about something, ask.
9
-
3. When you mess up, own up to your mistake and apologize (except in instances where apologizing would do more harm).
10
-
4. If you repeatedly violate this code of conduct, you will no longer be welcome to contribute to our projects.
9
+
3. We welcome contributions from people of any skill level and are committed to helping you build your skills wherever and however we can. Never be afraid to ask questions (even if you feel like they're too basic to bother us; you're not). [We're all impostors](http://geekfeminism.wikia.com/wiki/Impostor_syndrome).
10
+
4. When you mess up, own up to your mistake and apologize (except in instances where apologizing would do more harm).
11
+
5. If you repeatedly violate this code of conduct, you will no longer be welcome to contribute to our projects.
11
12
12
13
13
14
### What this means (our social rules)
14
15
15
-
##### Give constructive criticism
16
+
**Give constructive criticism**
16
17
17
18
Be friendly and offer well-reasoned opinions of someone's work or ideas, whether your critique is positive or negative.
18
19
@@ -23,7 +24,7 @@ Dismissing an idea out of hand is unacceptable. An explanation and support for y
23
24
Set personal conflicts aside when giving critique. Focus on the merits of the idea or work, not the person presenting them.
24
25
25
26
26
-
##### Create a safe space for learning
27
+
**Create a safe space for learning**
27
28
28
29
Everyone should feel comfortable saying, "I don't know." Everyone should feel comfortable asking questions and requesting help.
29
30
@@ -35,7 +36,7 @@ The [Hacker School User's Manual](https://www.hackerschool.com/manual) does a gr
Remember that this is a public space. Act accordingly.
41
42
@@ -46,14 +47,14 @@ Harassment and exclusionary behavior include offensive verbal comments related t
46
47
<sup>*</sup>From the [Conference Code of Conduct](http://confcodeofconduct.com/)
47
48
48
49
49
-
##How to contribute code
50
+
###How to contribute code
50
51
51
52
- Send us pull requests for bug fixes and small suggestions.
52
53
- For feature requests, create an issue to start a discussion. We'll decide together whether or not the requested feature gets built. Be sure and explain clearly why your feature request is essential.
53
-
- For detailed information about our preferred code structure and styles, refer to our [code style guide](https://github.com/INN/docs/tree/master/style-guides/code).
54
+
- For detailed information about our preferred code structure and styles, refer to our [code style guide](/style-guides/code).
54
55
55
56
56
-
##Other resources
57
+
###Other resources
57
58
58
59
This document is based on similar documents created by other organizations. Inspiration for this guide came from the following:
59
60
@@ -63,4 +64,4 @@ This document is based on similar documents created by other organizations. Insp
63
64
-[Conference Code of Conduct](http://confcodeofconduct.com/)
64
65
-[Hacker School User's Manual](https://www.hackerschool.com/manual#sub-sec-social-rules)
65
66
66
-
If you have questions about the code of conduct or how to contribute, feel free to contact us: [email protected].
67
+
If you have questions about the code of conduct or how to contribute, feel free to contact us: [[email protected]](mailto:[email protected]).
Copy file name to clipboardexpand all lines: how-to-work-with-us/intake-procedure.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,8 @@
1
1
# How to Work With Us
2
2
3
-
We love making things and we love helping our members and clients publish great journalism. We want to make it easy for you to approach us with ideas and projects, and we want you to know what to expect when working with us.
3
+
We love making things and helping our members and clients perform acts of great journalism. We want to make it easy for you to approach us with ideas and projects, and we want you to know what to expect when working with us.
4
4
5
-
**When you approach us with a project**, we'll talk about the idea as a team and review the requirements and expectations. We strongly recommend you familiarize yourself with [our process](https://github.com/INN/docs/blob/master/how-we-work/process.md) so you know what to expect.
5
+
**When you approach us with a project**, we'll talk about the idea as a team and review the requirements and expectations. We strongly recommend you familiarize yourself with [our process](/how-we-work/process.md) so you know what to expect.
6
6
7
7
**To get in touch** with the team, send an email to [[email protected]](mailto:[email protected]). Include a brief project description, what you hope to accomplish, and any timeline considerations we should know about.
8
8
@@ -14,7 +14,7 @@ We love making things and we love helping our members and clients publish great
14
14
15
15
**Maintenance:** As part of our contract, we'll work with you to identify any ongoing maintenance needs for a project, and if necessary create a plan to archive or retire projects that have a shorter shelf life. We won't ever leave you with a mess to clean up.
16
16
17
-
**Approach us with problems or questions, not solutions.** To do our best work, we prefer to start with the question or problem we're trying to solve, and build a feature or product from there. Often times the first or most obvious solution isn't the best one and we want to make sure you succeed. Here are a few examples of what that can look like:
17
+
**Approach us with problems or questions, not solutions.** To do our best work, we prefer to start with the question or problem we're trying to solve, and work with you to build a feature or product from there. Often times the first or most obvious solution may not be the best one and we want to be a partner with you in crafting the best solution because we are invested in your success. Here are a few examples of what that can look like:
18
18
19
19
20
20
Better :thumbsup: | Worse :thumbsdown: |
@@ -25,7 +25,7 @@ We want to tell this important story in a big way that sets it apart | Build us
25
25
We want readers to know what our current top stories are | Can you add a carousel to the homepage? ([Ahem.](http://shouldiuseacarousel.com/)) |
Copy file name to clipboardexpand all lines: how-to-work-with-us/member-services.md
+3-9
Original file line number
Diff line number
Diff line change
@@ -6,17 +6,15 @@ We help our members become more sustainable by listening carefully to their need
6
6
7
7
**This means that we will:**
8
8
9
-
-**Identify common needs** that a number of members share. (We are often unable to provide one-on-one assistance for free and instead offer paid consulting services to members at a highly reduced rate.)
10
-
-**Build platforms and tools to address these needs** but recognize that each member is different and the tools we build need to be customizable to suit these needs. For example, with Largo, we save members time and money by eliminating 90 percent of the effort typically involved in building a WordPress news website because the needs of sites are very similar, thus freeing you up to spend your time and money on the last 10 percent that is unique to your organization (mostly look and feel).
9
+
-**Identify common needs** that a number of members share. (We are often unable to provide one-on-one assistance for free and instead offer [paid consulting services](/how-to-work-with-us/consulting) to members at a highly reduced rate.)
10
+
-**Build platforms and tools to address these needs** but recognize that each member is different and the tools we build need to be customizable to suit these needs. For example, with [Largo](http://largoproject.org), we save members time and money by aiming to eliminate 90 percent of the effort typically involved in building a WordPress news website because the needs of sites are very similar, thus freeing you up to spend your time and money on the last 10 percent that is unique to your organization (mostly look and feel, in our experience).
11
11
-**Invest in documentation, group training and resources** to help members use and get the most out of the tools we build.
12
12
-**Negotiate on our members' behalf** to get free or reduced pricing for common third-party software and services.
13
13
14
14
Information on how to become a member, membership standards, dues, etc., [can be found on the INN website](http://investigativenewsnetwork.org/members/become-a-member/).
15
15
16
-
17
16
### As part of their INN membership our members receive:
18
17
19
-
20
18
**For members using [Largo](http://largoproject.org) (our WordPress framework/platform):**
21
19
22
20
-**Up to 32 hours of complimentary assistance** with setup and configuration if they use our shared hosting.
@@ -25,28 +23,24 @@ Information on how to become a member, membership standards, dues, etc., [can be
25
23
-**Free access to fonts** from [Adobe's Typekit library](https://typekit.com/).
26
24
-**Site licenses** for a number of premium WordPress plugins.
27
25
28
-
29
26
**For members participating in collaborative investigations and data projects:**
30
27
31
28
-**News applications and interactive features** to support collaborative investigations, localizable and flexible enough to work on a variety of member websites regardless of CMS.
32
29
-**Help with integrating these apps/features** into your stories and websites.
33
30
-**Promotion of member stories** through our website, newsletters and social media.
34
31
35
-
36
32
**For members who want to use the tools we build:**
37
33
38
34
-**Easy to understand documentation** to help members get up and running with any tools we build and open source.
39
35
-**Individual assistance**. We always recommend reading the documentation first (and helping us improve it if we miss something!), but if you get stuck we're happy to provide assistance and answer any questions you might have.
40
36
-**We love feedback** and wherever possible we will prioritize feature requests from members.
41
37
42
-
43
38
**For all members:**
44
39
45
-
-**Discounted rates on paid consulting** — currently $50/hr for members, reduced from our regular rate of $150/hr.
40
+
-**[Discounted rates](/how-to-work-with-us/consulting/consulting-rates.md) on paid consulting** — currently $50/hr for members, reduced from our regular rate of $150/hr.
46
41
-**Open office hours** the first Thursday of the month from 3-5 p.m. CT. Members can sign up for a 30 minute (or more if you clear it with us in advance) block to meet with our entire team and get feedback on any tech related issues you might be facing (new project ideas, critique of works in progress, general tech/strategy/design questions). Since we're a remote team, these will be Google hangouts and can be either public (anyone can join or watch) or private (if you want to keep the conversation just between us).
47
42
-**General tech help**. Please consider signing up for our open office hours and/or paid consulting services, but when time and resources allow we're happy to answer general tech questions as they come up and help in any way we can.
48
43
49
-
50
44
**For developers at member organizations:**
51
45
52
46
-**Support for open source projects**. As a team we're committed to supporting members' open source projects. If you need help with something feel free to reach out to us.
Copy file name to clipboardexpand all lines: how-we-work/process.md
+2-3
Original file line number
Diff line number
Diff line change
@@ -1,5 +1,4 @@
1
-
##Our Process
2
-
1
+
#Our Process
3
2
4
3
This is a general framework for how our team approaches our work. Depending on the scope of the project, we may use an abbreviated version or add more checkpoints and iterations.
5
4
@@ -52,7 +51,7 @@ This is a general framework for how our team approaches our work. Depending on t
52
51
53
52
54
53
55
-
####Jargon, defined
54
+
###Jargon, defined
56
55
**Stakeholders:** The people who are meaningfully involved in a project and have influence/decision-making power.
57
56
58
57
**User:** Anybody who is going to end up using the feature or product. These are often your readers, but don't forget about internal users (editors, reporters, business staff, etc.).
-**[Google Hangouts](https://plus.google.com/hangouts):** For [meetings](meetings.md) and daily scrum
11
11
12
+
We maintain [a list of tools and services](http://nerds.investigativenewsnetwork.org/discounts/) (including many of the above) that offer discounts to nonprofits on our team blog.
* Element IDs and class names should always be ``lowercase-with-dashes``.
4
4
* Put modals and JST templates in their own files. If using our fork of the NPR app template these belong in the `templates` and `jst` directories, respectively. When this isn't feasible, put modals in the page footer first, followed by inline javascript templates.
0 commit comments