[3560] in BarnOwl Developers
Re: Updating the list of projects on the website
daemon@ATHENA.MIT.EDU (Alex Dehnert)
Tue Aug 20 02:42:46 2013
Date: Tue, 20 Aug 2013 02:42:27 -0400 (EDT)
From: Alex Dehnert <adehnert@MIT.EDU>
Reply-To: sipb-vice-chair@MIT.EDU
To: debathena@mit.edu, barnowl@mit.edu, xvm@mit.edu, etherpad@mit.edu,
sipb-afsreq@mit.edu, sipb-www@mit.edu, asksipb@mit.edu, wakeup@mit.edu,
mailman-acl@mit.edu, bazki@mit.edu, usenet@mit.edu, rtfm@mit.edu,
feed@mit.edu
cc: sipb-vice-chair@mit.edu
In-Reply-To: <512F2434.7020500@mit.edu>
If you're in the "To:" line of this email, you're listed on
https://sipb.mit.edu/projects/, but didn't fill out the survey I sent to
get an updated projects list:
https://docs.google.com/forms/d/1zumk13yzo1kzKLPPZ8B7441_EbJH4KAp7f-a6hfMTVM/viewform
I've been derpy, but with frosh about to show up I'm finally planning to
actually finish updating the projects page with more detailed information,
and would appreciate folks filling out the survey so I can use it.
If you're involved in a project that's not on the list above, I'd love to
list you on the Projects page too! Please fill out the form. So far, I
have:
Scripts
SQL
Library Access to Music Project
MITeX
Gutenbach
Dormbase
Linerva
IAP
Mirrors
Thanks,
Alex
On Thu, 28 Feb 2013, Alex Dehnert wrote:
> Pretty sure we have more than three active projects...
>
> 1. Please have somebody fill out
> https://docs.google.com/forms/d/1zumk13yzo1kzKLPPZ8B7441_EbJH4KAp7f-a6hfMTVM/viewform
> for each project
>
> 2. If you're willing and interested in mentoring prospectives who are
> trying to get involved, please let me know.
>
> Thanks,
> Alex
>
> On 02/25/2013 12:48 AM, Alex Dehnert wrote:
>> Hi folks,
>> I'm trying to update http://sipb.mit.edu/projects/ to be easier for
>> prospectives to use to find interesting projects. To do that, I'd
>> appreciate it if each project could fill out
>> https://docs.google.com/forms/d/1zumk13yzo1kzKLPPZ8B7441_EbJH4KAp7f-a6hfMTVM/viewform
>> so I know what to put for your bugtracker, whether you're actively
>> recruiting[*], etc.. The more complete your answers the better, but I'd
>> rather you left things blank or emailed me your responses than didn't
>> put in anything (and if you don't do anything, I'll probably assume your
>> project is dead).
>>
>> You can see which projects have responded already at
>> https://docs.google.com/forms/d/1zumk13yzo1kzKLPPZ8B7441_EbJH4KAp7f-a6hfMTVM/viewanalytics.
>>
>> Also, if you're willing and interested in helping prospectives get
>> involved in SIPB projects (in general, or just for your projects) please
>> let me know, including which projects you want to help with.
>>
>> Thanks,
>> Alex
>> (Incoming SIPB Vice-Chair)
>>
>> [*] I have a question "Activity level" on the form. As guidelines on
>> what the options mean:
>>
>> Actively recruiting vs. active:
>> * Would you like prospectives pointed your way when they say "Hi! What
>> can I work on?"
>> * If a prospective comes up to you and says "Hi! Underwater basket
>> weaving sounds awesome! What can I do to help with the underwater
>> basket-weaving project?", can you easily point them at something to do
>> and supply reasonable amounts of mentoring?
>>
>> If "yes" to both, I'd probably consider you actively recruiting. If
>> "no" to both, then probably not.
>>
>> Active vs. inactive vs. moribund:
>>
>> If somebody's made commits or taken updates or something on your project
>> in the last three months, you're active.
>>
>> For inactive vs. moribund:
>> Do you have people who will give advice, do code review, or have ideas
>> for where the project should go? If so, you're just inactive; if not,
>> you're moribund.
>>
>>
>> -------- Original Message --------
>> Subject: Using the website for recruiting?
>> Date: Wed, 13 Feb 2013 15:02:42 -0500 (EST)
>> From: Alex Dehnert <adehnert@MIT.EDU>
>> To: sipb-outreach@mit.edu
>> CC: sipb-www@mit.edu
>>
>> The SIPB website seems like it should be a good tool for recruiting, and
>> in particular for helping prospectives find things to get involved in.
>>
>> [...]
>>
>> For the Projects page, it seems like there are a couple of key things we
>> want to get across (for recruiting, at least):
>> * What projects exist?
>> * What are good ways to get started? Obvious components of this are
>> where to find the code and bugtracker (and if applicable, any
>> easy/starter/hackathon tickets). Another plausible component is "Who
>> should I talk to?", though I worry about that getting outdated if we put
>> people, or feeling impersonal (and thus not useful) if we don't.
>> * Are projects interested in new people? (Scripts can absolutely use
>> more labor, and I think we at least pretend that we'll spend time
>> helping interested people get involved. I think Linerva, SIPB AFS,
>> sipb-noc, and some other projects are mostly not enthusiastically
>> recruiting.
>>
>> It seems like it's hard for somebody to easily get that information off
>> the Projects page. (Most of it is there, but it's not really skimmable.)
>> My hypothesis is that converting that page to a table might be helpful.
>> Does that make sense? Do people have preferred alternatives/
>>
>> [...]
>>
>
>
