Re: [Webteam] [SFC-Core] Call in 10
2012-05-01 07:37:33 GMT
Two things, apologies for the length but I'd **really** appreciate some feedback (and cc'ing discuss on this):
1. Workflow (Process, Knowledge-sharing, Etc)
At the FCsummit, we observed some patterns of behavior for SFC. Chapters sometimes have a thriving group of folks, and even a whole network in the case of NYC's FC Coalition. Others seem to be just an individual or maybe a few folks, friends possibly roped in to working on events or initiatives. Given the growth of SFC internationally, and the current processes and interactions taking place as we speak, it seems that SFC, as an organization, acts like a network of resources, groups, and individuals. Folks share projects, ask questions, get advice, give feedback, and all work on awesome things in the Free/Libre Cultural space. From an organizational standpoint, the incoming board needs to do some hard thinking and work to update the purpose, mission, and direction of the org in the FC movement. Functionally, we already see that this is a network of valuable resources sharing knowledge amongst themselves and with new folks. Email is the primary conduit by which this sharing takes place. But there are other options and opportunities out there. We all see how valuable they could be!
The draft I'm presenting (attached) should be somewhat consistent with SFC's current behavior patterns, but in order for it (or something like it) to be effective, we need to get folks in this community on the same page and commit to putting in a bit of time and investment to make it valuable for ourselves and for new people joining the FC movement. If we build a knowledge base, we need to be sure those who could contribute are able to (they have access) and that information can be organized, and categorized for intuitive and sufficient discovery (e.g. browse and search). There are various other constraints, but to me, the most critical change needs to be social--this community needs to adopt a process for working together because that's what it does--SFC is all about sharing! ;)
The workflow - Work is done by chapters, individuals, the board, and external contributors. This work can be published anywhere (maybe your chapter has it's own wiki or blog, awesome!), or it could be unpublished at this time. At some point, either this work should be posted, in some way, on the SFC wiki (or at least linked to your chapter's blog for example). There are two routes. One is to start some email threads with relevant folks, communicate, and perhaps feedback into the work for some time, but eventually post to the wiki. The other is to post straight to the wiki, which can then feedback into further work.
(Question: Does it seem intuitive that information posted on the wiki can be related to SFC the organization, individual chapters, or Free Culture itself? Anyone have thoughts about this?)
Okay, on this note, what email address should I use to set up the github account?
freeculture is taken, studentsforfreeculture is available, and libreculture is available.
I think using webteam <at> freeculture.org is a security risk since anyone can sign up for it and we only really need the account to sign up and create a few repos. Do we have any admin/info accounts for the freeculture.org domain?
Repos to create:
FreeCulture.org Support - This may be a convenient place to openly manage and document work on the site as it exists, then retire it once we move over to the new site, but it's not totally necessary. Thought it might be useful for consolidation purposes.
As long as we use git and publish the source code, the details on host don't concern me too much.
Github is nice though!
Sent from my iPhone
On Apr 28, 2012, at 8:26 PM, Asheesh Laroia <freeculture <at> asheesh.org> wrote:
> On Sat, 28 Apr 2012, Alec Story wrote:
>> I know when we discussed this in the past we favored gitorious because it's
>> open. Anyone feel strongly about this?
> I used to be a big Gitorious partisan, but my main project (OpenHatch) just switched to Github for the following reasons:
> * Better bandwidth
> * More installed user base
> * "Web hooks" that let you get pinged when the repo changes
> Full conversation here:
> * http://lists.openhatch.org/pipermail/devel/2011-November/002521.html
> * http://lists.openhatch.org/pipermail/devel/2012-February/002658.html
> Do note that this makes me sad in some ways.
> -- Asheesh.
> Webteam mailing list
> Webteam <at> freeculture.org
Webteam mailing list
Webteam <at> freeculture.org
_______________________________________________ Discuss mailing list Discuss <at> freeculture.org http://lists.freeculture.org/mailman/listinfo/discuss FAQ: http://wiki.freeculture.org/Fc-discuss