If you have a proposal for a project or product first find a Group Admin
Unless you can just launch something on your own. Then, just do it!
Figure out relevant Groups to contact. Login (or register), then click the Groups tab and open the view of the Group tags, to help you find a group. Once you have found a group, you want to contact a Group Admin. After you have clicked on one Group, then you will be able to see Group Admins and Moderators (if they exist) as shown here.
Speak to the Group Admins about how to create a “Doc” within their group. (We are in the process of developing more efficient workflows). To contact a Group Admin, click on their Avatar (logo/ photo). Then you can send them a private or public message.
Some guidelines for what to submit to a Group Admin
courtesy of @clenchner
- Explain in clear language what the problem is you are trying to solve. Consider sentences like ‘if you are a supporter wanting to accomplish X, this service/website/app offers the following process for meeting that demand: a, then b, then c. In other words, explain the behavior of your idea, not only ultimate goals like ‘more coordination’ or ‘outreach’ or event ‘communication between people’.
- Define the target audience in behavioral ways. Like: tech savvy activists who have time to give but aren’t physically present at an occupation. Or: 2nd and 3rd tier supporters unlikely to become active but who seek accurate information to share on their own networks.’
- Define the outcome as something that can be measured for success. ‘We think it will help 100 people a day locate volunteer opportunities, provided we reach traffic of 1000 people a day.’ Or ‘This idea will increase the Google ranking of movement friendly sites, to help drown out opposing or MSM sites, so that ‘friendly’ sites comprise 50% or more of the first 20 links.’
- Say something about whether this is an essential, urgent priority or a nice thing to have once we’re done with what IS urgent. ‘Video aggregation portals that facilitate conversation won’t impact operations on the ground. But It’s a great add on service to a site that is already up and running.’ Don’t make us decide on our own how important this is relative to other things. If you don’t know – then first learn what we’re doing. And don’t bullshit us with crap like ‘there is an urgent need to change Twitter hashtags!’
- If your service/website/app is not constructed using open source technology that can be replicated by others, then say so up front, and make the case that the value it provides justifies the efforts of a community that prioritizes open source technology. If you intend to keep your branding on something, explain precisely what that looks like, how it compares to similar branded services. Branding is not evil, we just need to understand.
- If you are asking others to review something new, make the case for why we should give it any attention; this requires that you NOT assume anyone shares your excitement that a great new X does Y. Put the perceived needs of actual working groups at the fore, instead of your own desires for rapid adoption.
- Ask yourself: do you need working group of OWS approval for this? OccupyTogether.org, occupywallst.org never asked for permission, they just did it. Maybe that’s better? If our attention/adoption is essential, say so; if you are engaging in marketing and outreach so that more folks will hear about and use your new thingy, say so upfront. It’s fine! We are techies who get excited about our own shit as well. Just be clear about it.
- If some kind of decision or assistance is necessary, please phrase it as an explicit request. “To make this work, IWG developers must come to a decision to use my idea, and work with me on implementation. Please let me know your plan for getting this on the agenda, and the name of an individual who will be my connection to your work.”
- Members of the FLO/Solutions WG, or the Internet Working Group: let’s figure out how to name individuals as ‘the’ connection to new people and new ideas. If there was a list of active members, and a few coordinators, it would be possible to assign things sensibly. It might work, as a start, to assign every new person or idea to one of the four teams: backbone, web development, digital strategy, and that other one.