Our Purpose

[stevenwadejr]

Bringing together and building a community of local area developers to solve problems and provide assistance through the use of software where needed.

[BigBlueHat]

Great start, @stevenwadejr Let's get some stuff in here about "open": collaboration, source, etc.

I want it to be abundantly clear that this is collaborative, meritocratic, collaborative, etc. ;)

@OpenUpstate/greenville got any thoughts?

[allella]

I was out of town for the discussion. Can someone summarize the thoughts and direction discussed so far?

[BigBlueHat]

@allella most of it centers around focusing on building "open collaboration" (via open source, etc) in Upstate, SC. There are some ideas--which need writing up (in the Wiki?)--that would help all the various, fabulous groups now in existence collaborate on making the upstate more awesomer. 😸

@allella did that sum it up? 😄 Let's turn this thread into iterating @stevenwadejr's proposed summary.

[stevenwadejr]

I had a great discussion with @wryenmeek last week about OpenUpstate. The idea came up that there are so many great groups in this area but not many groups or members know about other groups. We threw around the idea of openupstate.org becoming an "umbrella" home in name and location only for area groups. It'd be a localized meetup.com. Each group could have a "sub site" with event integration, calendars, and any information they may want.

The benefit that Wryen and I saw from this "umbrella" was to centralize and make a home for these groups. To allow for these groups to become "neighbors". The site could have a shared centralized calendar which we saw as an asset since so many groups overlap and trying to find time between events and regularly scheduled meetings is a pain. With a shared home and especially a shared event calendar, groups obviously benefit, but members and individuals benefit from "group discovery".

In my opinion, this would benefit all groups under this "umbrella" of OpenUpstate. It's that whole "a rising tide lifts all boats" mentality.

[BigBlueHat]

👍 to all the things!

[allella]

Yes, lately there seem to be a lot of new groups and momentum at OpenWorks, Iron Yard and Greenville as a whole. The lines definitely blur a bit between some and OpenUpstate falls into that blur, though I feel the topics of recent events have stood on their own.

Regarding an umbrella for events, OpenWorks has a public calendar on our to-do list. OW will have a need for reserving event spaces for both open and private use, so that could break the mold.

Though we'd like to see what can be done with Meetup.com. It looks like TIY has a Meetup account too.

Here's a list of groups/events which have met at OpenWorks for a feel of who's utilizing the OW space and the overlap in purpose we're seeing without even factoring in other communities who meet at various locations.

Beer and Napkins
OpenUpstate
Code for Greenville
10-4 Good City
OpenUp
DesignThinkers
PHP Upstate (UpstatePHP)
Technically a Beer
Open Data Day
NEXT High School
RESTFest

[stevenwadejr]

@allella I was thinking the umbrella of OpenUpstate.org would reproduce some of the functionality and community of meetup.com but localized. It could tie in with OpenWorks and other venues. I think the point and benefit would be collaboration, community, and centralization.

Also @allella, it's UpstatePHP ;)

[wryenmeek]

The problem for the tech community and (other communities) is: who is doing
what when where and why?

Everyone is using a ton of different means to tell people about events.
Email, meetup, eventbeight, Facebook, Twitter and the list goes on.

There is a TON of stuff going on (go look at greenville forwards'
collection of event calentldars).

Finding contextually relevant events and the groups and places that host
them is hard with so much noise and so many different places to look.

There are a couple of approaches:

1. Cetralize collection and distribution. One webplace to collect and
   distribute information. This directly competes with facebook events and
   meetup. Im not a fan of reinventing the wheel.
2. Scrape or syndicate the data then make it accessable via an API (say
   ckan?) Webplace agnostic. Use rss, ical and email to automate submission.
   Have a simple signup for organizers to add their group details and tell the
   app where to listen for event notifications. Then use the api to build a
   search site to stream line finding relevant info.

@allella https://github.com/allella I was thinking the umbrella of
OpenUpstate.org would reproduce some of the functionality and community of
meetup.com but localized. It could tie in with OpenWorks and other venues.
I think the point and benefit would be collaboration, community, and
centralization.

Also @allella https://github.com/allella, it's UpstatePHP ;)

—
Reply to this email directly or view it on GitHub
#1 (comment).

[BigBlueHat]

@wryenmeek 👍 2️⃣ sounds best.

There's this thing called "The Web." It uses hypertext to give anyone the opportunity to re-organize anything. 😉

Nothing has to end up in OpenUpstate.org, though. The hope is that it becomes a valuable place to look for stuff to collaborate on...and collaborate! 😺

"Centralize" can be a confusing word...so to be clear, the intent is more to aggregate, collect, curate rather than to own, manage, or oversee.

🆒 ❓

[stevenwadejr]

@wryenmeek & @BigBlueHat I guess that means I still need to build a website for UpstatePHP. Dang :)

[wryenmeek]

Correct me if I am wrong but your looking for OpenUpstate to be more of a
hub for the opensource community right?

Its more than just events

Its repos, opportunities to help, requests for help, facilitating
communication, whos who, community knowledge

I leave anything out?
On Jun 17, 2014 11:29 AM, "BigBlueHat" [email protected] wrote:

@wryenmeek https://github.com/wryenmeek [image: 👍][image: 2️⃣]
sounds best.

There's this thing called "The Web." It uses hypertext to give anyone the
opportunity to re-organize anything. [image: 😉]

Nothing has to end up in OpenUpstate.org, though. The hope is that it
becomes a valuable place to look for stuff to collaborate on...and
collaborate! [image: 😺]

"Centralize" can be a confusing word...so to be clear, the intent is more
to aggregate, collect, curate rather than to own, manage, or oversee.

[image: 🆒][image: ❓]

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[wryenmeek]

Dont jump off the boat yet. Were still brain storming no?
On Jun 17, 2014 11:32 AM, "Steven Wade" [email protected] wrote:

@wryenmeek https://github.com/wryenmeek & @BigBlueHat
https://github.com/BigBlueHat I guess that means I still need to build
a website for UpstatePHP. Dang :)

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[wryenmeek]

I kid you not this is the first thing in my inbox when I got home:
https://groups.google.com/a/codeforamerica.org/forum/#!topic/brigade/ELtMHm23eis

we arn't the only ones interested in this solution space.

On Tue, Jun 17, 2014 at 5:16 PM, Wryen Meek [email protected] wrote:

Dont jump off the boat yet. Were still brain storming no?
On Jun 17, 2014 11:32 AM, "Steven Wade" [email protected] wrote:

@wryenmeek https://github.com/wryenmeek & @BigBlueHat
https://github.com/BigBlueHat I guess that means I still need to build
a website for UpstatePHP. Dang :)

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

Wryen Meek
678.701.5005
http://www.linkedin.com/in/wryenmeek/ https://www.google.com/+WryenMeek

[GlenKPeterson]

I started a page:
https://github.com/GlenKPeterson/GreenvilleScTechMeetings/wiki/Greenville-SC-Tech-Meetings

If I know you and you lead a local group, just ask and I'll give you write access. Ditto those who I give write access should feel free to give others write access under the same conditions.

[stevenwadejr]

@GlenKPeterson can you/I add UpstatePHP to the list? We meet on the 3rd Thursday of each month

[GlenKPeterson]

I had to guess at the link to use, but it's done. I may have changed the URL by accident. I haven't used GitHub for this a lot. Once the information is all gathered, we can figure out where it belongs, etc.
https://github.com/GlenKPeterson/GreenvilleScTechMeetings/wiki

[allella]

A group of folks at Code for Greenville talked about user stories/ideas/wants out of an event aggregator and API for upstate tech events.

We left off that we'd setup a Git repo under https://github.com/codeforgreenville and use the issue tracker there to discuss. I think Wyren needs to setup that repo before we can continue the conversation.

In addition to Wryen's proposition on this thread, there was talk about OpenUpstate potentially being the stakeholder for such an API. That is, if OpenUpstate's purpose aligns with that sort of role.

We also have at least a handful of Howard Dean https://www.youtube.com/watch?v=D5FzCeV0ZFc

[allella]

I know folks are looking at OpenUpstate as a potential no-agenda aggregater
of tech communities.

An open events API that scrapes and auto-imports tech events from wherever
the groups are already posting them was the focus of a Code for Greenville
group.

We've started a list of tech-related organizations.
hackgvl/OpenData#1

Hopefully the folks on this thread can help flesh that out. Besides the
events API, this would seem to be a good basis for OpenUpstate to evaluate
the full scope of groups in the area its purpose is considered.

On Wed, Jun 18, 2014 at 9:42 AM, Glen K. Peterson [email protected]
wrote:

I had to guess at the link to use, but it's done. I may have changed the
URL by accident. I haven't used GitHub for this a lot. Once the information
is all gathered, we can figure out where it belongs, etc.
https://github.com/GlenKPeterson/GreenvilleScTechMeetings/wiki

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

[stevenwadejr]

@allella I started a new thread based on your idea of an events API. I would like to see it be more than just events, but also pull information about groups, and through a GUI, maybe have information about venues for anyone looking for a place to have a meeting.

The idea is based on the example API I used for my talk here

[BigBlueHat]

@wryenmeek you summed it up well when you said:

Correct me if I am wrong but your looking for OpenUpstate to be more of a hub for the opensource community right?

Its more than just events Its repos, opportunities to help, requests for help, facilitating communication, whos who, community knowledge

I leave anything out?

The overarching theme (to me at least) is collaboration. OpenUpstate (as an org/group/thing) should exist to facilitate and foster that. Right now, that mostly looks like connecting people and pot stirring. 😄 The practical implementation details remain to be defined.

I'm gonna close this one in favor of new threads defining those. ;)

Thanks, all!

[stevenwadejr]

@BigBlueHat can we re-open this? I'd like to get your opinions on what you'd like to see from OpenUpstate and I'd love to keep this thread open to help define that.

[BigBlueHat]

Fine by me. 😄 Maybe we don't close discussions?

[stevenwadejr]

@BigBlueHat and @wryenmeek:

I would love for you both as the "leaders" of your respective groups (OpenUpstate and Code for Greenville) to define the scope and goals for each group.

There is some obvious confusion among the members of each group and we're getting even more theoretical overlap right now than we originally thought.

Based on conversations with you both, I would see the group goals as so:

• Code for Greenville - Projects, ideas, opportunities related to facilitating and improving local government and making Greenville data more accessible.
• OpenUpstate - Facilitate growth, awareness, and support local groups. Participate in projects that build the community.

With these goals, in my opinion, ideas that come up in Code for Greenville that either don't fit within the "scope" of it's intent, or which are outside of the available resources to the group, that's where someone like OpenUpstate is a partner and can work with folks from other groups.

OpenUpstate can also act as a facilitator supporter of community projects through guidance and collaboration.

I love the idea that both groups were founded on, but we need some more direction and definition from the founders. This will help the two function side by side and work together to use each other's strengths without fragmenting the community further.

[BigBlueHat]

Thanks for holding our feet to the fire @stevenwadejr! Seriously. 👍

OpenUpstate

Mission

Foster a collaborative developer community through the creation and curation of locally-source content, code, and other creations.

Vision

Create a cross-meet-up, non-language/tech/company specific organization to encourage the growth, health, and general well-being of the Upstate South Carolina tech communities.

@stevenwadejr that an OK start? 😁

[stevenwadejr]

@BigBlueHat That sounds great!

I'd like to get @wryenmeek to chime in on his side soon if we can.

Once we have both sides defined, we can set clear "boundaries". And by boundaries, I just mean a clear definition of each's roles individually and together. This will help us know where each group should concentrate, and where there can/should be overlap.

[stevenwadejr]

Based on @wryenmeek's comments here, @BigBlueHat, what do you see as the overlap, and do you think OpenUpstate can work along side Code for Greenville? If so, in what capacity and in what type of scenarios?

I'd love to see both @BigBlueHat and @wryenmeek's opinions on how OpenUpstate can Code for Greenville can/should work together.

[wryenmeek]

based on @BigBlueHat's description it sounds like CfG is encompassed by
OpenUpstate's Mission & Vision. Just about anything CfG does will further
the OpenUpstate Mission & Vision as will most anything any of the other
groups in the area will do.

On Mon, Jun 30, 2014 at 8:32 PM, Steven Wade [email protected]
wrote:

Based on @wryenmeek https://github.com/wryenmeek's comments here
#3 (comment),
@BigBlueHat https://github.com/BigBlueHat, what do you see as the
overlap, and do you think OpenUpstate can work along side Code for
Greenville? If so, in what capacity and in what type of scenarios?

I'd love to see both @BigBlueHat https://github.com/BigBlueHat and
@wryenmeek https://github.com/wryenmeek's opinions on how OpenUpstate
can Code for Greenville can/should work together.

—
Reply to this email directly or view it on GitHub
#1 (comment)
.

Wryen Meek
678.701.5005
http://www.linkedin.com/in/wryenmeek/ https://www.google.com/+WryenMeek

[BigBlueHat]

@wryenmeek yep! The objective is to encourage all this stuff to keep going, succeed, and make Greenville yet-more-awesome!!1! 😸 AND do all that collaboratively. 😉

It seems that Code for Greenville has interest, objectives, and drive to make this event thing happen. Certainly, OpenUpstate will promote it, point to it, get more people involved. When the time comes for CfG to focus more narrowly on civic issues and this events data project needs a "wider" home (so it doesn't get perceived as "merely" civic-focused), then perhaps we move it under OpenUpstate's Org on GitHub.

The same people should be involved regardless (i.e., the one's interested enough to show up 😺).

What's needed on the OpenUpstate side atm is things to point to that are being built, in the open, in the Upstate. This is a great one to start with! @wryenmeek keep up the greatness. 😄