Talk:Developers Space

From wiki.gpii
Jump to: navigation, search

I moved the part the parts about web components to the components page to not give too much bias towards them (we would have needed to describe all other parts here as well to be inclusive) --Till (talk) 13:39, 16 March 2014 (EDT)

I removed the following parts Colin wrote up very nicely for the time being as I think they are nice hypotheses (I agree with them intuitively), but that we need establish in a participatory way, the talk section seems more fit to me--Till (talk) 10:40, 15 March 2014 (EDT)

Distributed, Decentralized and Wherever the Action Is

If you build it, developers won't come. There are already a wide variety of successful and active forums, repositories, and social networks for supporting both open source and traditional software development. Sites such as Github provide a socially interconnected platform for managing source code, reviewing contributions, filing bugs, and documenting projects. Stack Overflow is a highly successfully forum for asking technical questions and receiving crowd-ranked responses. The Mozilla Developer Network provides reliable, cross-browser documentation about the web platform. In each case, these sites give developers a means to establish social credibility, build a portfolio of their work, and gain meritocratic influence in a community.

Our goal is to establish the Developer Space not as its own separate forum that is independent of these sites, but as a resource that is harmonized and interconnected with places where developers do their work every day. Creating communities from scratch is a vast and costly effort. Since the accessibility community is so small, the Developer Space can't afford to position itself as a single, monolithic clearinghouse for inclusion-related tools and knowledge. Instead, it needs to serve as a means to connect and sustain a network (or federation) of contributors across a variety of open source projects and communities, without undermining the support and identity of these communities and yet addressing the fragmentation of knowledge that is systemic with the accessibility field. Components contributed to the Developer Space will never need to be located in a particular source code management system or site. Wherever possible the Developer Space effort will actually link to and actually contribute back to these successful forums rather than establishing a separate system, community, or place to go. The key "value add" for the Developer Space is our expertise and diversity, particularly our ability to help developers quickly find advice and tools—wherever they are located—that will help them build more accessible and personalizable applications.