[OSCTC-planning] Infrastructure changes

Wed Dec 17 16:12:34 UTC 2014

Carol,

I like that approach!  I've thought along those lines myself.  It seems
like we have three major audiences:

- individuals who want to get involved in open source
- project maintainers or project members who want to involve their projects
by finding new contributors, becoming more welcoming, participating in
events
- open source community builders who want help running events, using our
tools, etc.

Any given tool, product, or program can help all three.  A community
builder might be the first person to organize an OSCTC even but project
maintainers should know the program exists so they can participate in
events.  Same for individuals.

What about a design that starts by asking whether you want to: (I dislike
the phrasing for all of these but it gets to my point)

- Learn More About Open Source / Get Involved In Open Source
- Make Your Project More Welcoming
- Build A Community / Run an Event

Which lead to further pages that link to individual
programs/tools/resources?  With perhaps the biggest projects - IRC channel,
opportunity finder, OSCTC, also linked on the main page but more
discretely, like in the top navbar.

- Shauna

On Wed, Dec 17, 2014 at 10:58 AM, Carol Willing <
willingc at willingconsulting.com> wrote:
>
>  Hi Shauna and all,
>
> I'm not sure how to put this in words but I would love to see the
> infrastructure flow from the major missions of OpenHatch. Stepping back, I
> see two very valuable brands (OpenHatch and OSCTC) which could each stand
> on their own but are more valuable together.
>
> There has been huge growth over the past year and a half. Thanks to many,
> many people. What follows is more or less what I tell people when they ask
> what OpenHatch and/or OSCTC does:
>
>
> Outreach and education
> Open Source Comes to Campus <---> Open Source Comes to You (or your
> community)
>
> Welcoming, productive communities
>     Wealth of documentation
>     Welcome Bot
>     Profiles of projects/open source communities
>
> You
>     Missions - building skills
>     Finding a project
>     Getting help
>
>
> It would be really cool to highlight these major missions on the home page
> and make information and access from each of these valuable missions more
> accessible and easier to find/use/contribute.
>
> Carol
>
>
>
>
> On 17/12/2014 04:56, Heidi Ellis wrote:
>
>  Hmmm, isn’t that what the homepage of openhatch.org is currently?  When
> I go there, I see:
>
>
>
>
>
> As for the mission, we frequently send students to openhatch.org without
> mentioning OSCTC.  OpenHatch is a great place to give newbies ideas of how
> to get started. That seems to me to be the main mission of OpenHatch.
>  OpenHatch lets students see what others are doing and what can be done
> which is very helpful.  So making that transparent on the site seems to me
> to be a real help to the community. OSCTC is one effort that also supports
> getting started.  I also send students to hang out on the IRC channel.
>
>
>
> Heidi
>
>
>
>
>
>
>
> *From:* OSCTC-planning [mailto:osctc-planning-bounces at lists.openhatch.org
> <osctc-planning-bounces at lists.openhatch.org>] *On Behalf Of *Alex Bayley
> *Sent:* Tuesday, December 16, 2014 5:56 PM
> *To:* Planning for Open Source Comes to Campus
> *Subject:* Re: [OSCTC-planning] Infrastructure changes
>
>
>
> OK, so it seems to me like you could make the homepage of openhatch.org
> be mostly an OSCTC landing page, with links to the other stuff as
> subsidiary pages.
>
> A.
>
> On 17/12/2014 9:52 am, Shauna Gordon-McKeon wrote:
>
>  There's the IRC channel, the training missions, the opportunity finder,
> and occasional non-OSCTC in person events like sprints.  There are a couple
> of projects that I've done as well that are used by OSCTC but not
> exclusively, such as the In-Person Event Handbook (
> http://opensource-events.com/), WelcomeBot (
> https://github.com/shaunagm/WelcomeBot) and Merge Stories (
> http://mergestories.com/).  OSCTC is the highest priority OpenHatch
> project but the others are still quite valuable.
>
>
>
> On Tue, Dec 16, 2014 at 5:45 PM, Alex Bayley <skud at growstuff.org> wrote:
>
> Actually, can I just ask... what does OpenHatch do that *isn't* OSCTC?
> And what is its relative priority/importance, relative to OSCTC?
>
> A.
>
>
>
> On 17/12/2014 9:44 am, Shauna Gordon-McKeon wrote:
>
>
>
>
>
> On Tue, Dec 16, 2014 at 4:09 PM, Alex Bayley <skud at growstuff.org> wrote:
>
> Surely newcomers would mostly land on openhatch.org?
>
>
>
> That's probably true.  Currently openhatch.org points towards
> campus.openhatch.org, which is actually a pretty bad place for it to
> link, information-wise, in that it's aimed entirely at organizers (not
> attendees, maintainers, or non-organizer volunteers) and is possibly the
> spot, of all those listed, that has the most restricted access.
>
>
>
> Sheila, can you elaborate on "Have a friendly landing page that is
> generated from readme?"
>
>
>
>
>
>
>
>
> A.
>
>
>
> On 17/12/2014 8:07 am, sheila miguez wrote:
>
>
>
>
>
> On Tue, Dec 16, 2014 at 1:19 PM, Shauna Gordon-McKeon <shaunagm at gmail.com>
> wrote:
>
> Hi all,
>
>
>
> I'm hoping to make a bunch of infrastructure changes over the next week or
> two. Asheesh and I started brainstorming on an etherpad here:
>
> https://etherpad.mozilla.org/openhatch-infrastructure
>
> [...]
>
>
>
>  With regard to A: perhaps the place to start is with a canonical place
> that everything points to (and that points to everything else) that
> newcomers can be pointed to.  Have folks seen this done before/do you have
> intuitions about the best place to put this?  In the Github readme, perhaps?
>
>
>
> Have a friendly landing page that is generated from readme?
>
>    - For people who find you via github, they won't have to dig around to
>    figure out the url to the content, it will be in the readme.
>    - For people who do not know about github, they will have easy access
>    to the content (and can find the repo from it).
>    - The brand is not github.
>
>
>
>
>
>
>
>
>
>
> --
>
> shekay at pobox.com
>
>
>
>   _______________________________________________
>
> OSCTC-planning mailing list
>
> OSCTC-planning at lists.openhatch.org
>
> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
>
>  --
>
> Alex "Skud" Bayley
>
> skud at growstuff.org
>
> http://growstuff.org/
>
>
> _______________________________________________
> OSCTC-planning mailing list
> OSCTC-planning at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
>
>  _______________________________________________
>
> OSCTC-planning mailing list
>
> OSCTC-planning at lists.openhatch.org
>
> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
>
>  --
>
> Alex "Skud" Bayley
>
> skud at growstuff.org
>
> http://growstuff.org/
>
>
> _______________________________________________
> OSCTC-planning mailing list
> OSCTC-planning at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
>
>
>  _______________________________________________
>
> OSCTC-planning mailing list
>
> OSCTC-planning at lists.openhatch.org
>
> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
>
>  --
>
> Alex "Skud" Bayley
>
> skud at growstuff.org
>
> http://growstuff.org/
>
>
>
> _______________________________________________
> OSCTC-planning mailing listOSCTC-planning at lists.openhatch.orghttp://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
>
> --
>  *Carol Willing*
> Developer | Willing Consulting
> +1 760 456 9366 | https://willingconsulting.com
>
> _______________________________________________
> OSCTC-planning mailing list
> OSCTC-planning at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/osctc-planning
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/osctc-planning/attachments/20141217/10ae99d5/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 18134 bytes
Desc: not available
URL: <http://lists.openhatch.org/pipermail/osctc-planning/attachments/20141217/10ae99d5/attachment-0001.jpe>