Next Steps

[Cromian]

@hackshackers/action-group-website Hey everyone so looks like no one has commented on the RFI. If no other suggestions or changes should be made, perhaps we let Samantha add it to the next newsletter and send it out?

[samanthasunne]

The next newsletter is gonna go out tomorrow morning, so if everyone's ok with it, I'll go ahead and advertise the RFI in it. Of course you guys can keep adding and modifying even after we've sent it to the whole group.

[Cromian]

Should we create two separate documents. One for us to work off the other just a read only version?

[phillipadsmith]

Probably sensible, yes.

One “published” version, and one that can continue to be edited and refined.

On Mar 3, 2016, at 12:42 PM, Misha Vinokur notifications@github.com wrote:

Should we create two separate documents. One for us to work off the other just a read only version?

— Reply to this email directly or view it on GitHub https://github.com/hackshackers/action-group-website/issues/12#issuecomment-191880252.

[samanthasunne]

Okay - in the newsletter, should I link to the google doc we already have?

On Thu, Mar 3, 2016 at 12:41 PM, Phillip Smith notifications@github.com wrote:

Probably sensible, yes.

One “published” version, and one that can continue to be edited and refined.

On Mar 3, 2016, at 12:42 PM, Misha Vinokur notifications@github.com wrote:

Should we create two separate documents. One for us to work off the other just a read only version?

— Reply to this email directly or view it on GitHub < https://github.com/hackshackers/action-group-website/issues/12#issuecomment-191880252 .

— Reply to this email directly or view it on GitHub https://github.com/hackshackers/action-group-website/issues/12#issuecomment-191906823 .

[Cromian]

Here is the public version we can use in the newsletter - https://docs.google.com/document/d/1P4YfJrcTo9rA1UbcLDXI2QpdcndfquqNDFAFO0c51M0/edit?usp=sharing also any ideas on how people will submit the RFI?

[Cromian]

Moving thread to GitHub:

Newsletter text: - https://docs.google.com/document/d/1aZc2PQ4c6ItK_1hqD_VclSjPmm6knR0gMpAkE9V1mis/edit

As for people on the call we should definitely ask for help even from the rest of the @hackshackers/action-group-website but b/c of larger timelines and goals especially for future funding perhaps we let @burtherman makes the decision if no one from the team can meet up? As we are the most transparent action group I do not think people will raise any objections to our approach.

Attached email thread: Email Log.pdf

[samanthasunne]

Got it! We can also promote the RFP on Twitter.

[phillipadsmith]

:+1:

[samanthasunne]

Gonna start now. How does this look for a tweet?

We're seeking proposals for a remodel of the #HacksHackers website: https://docs.google.com/document/d/1P4YfJrcTo9rA1UbcLDXI2QpdcndfquqNDFAFO0c51M0/edit Get in touch by April 11: info@hackshackers.com

[Cromian]

@phillipadsmith @burtherman @samanthasunne @hackshackers/action-group-website Hey guys is anyone else getting errors when sending stuff to info@hackshackers.com?

[phillipadsmith]

Ug. Guessing none of us checked it. I'll see if I can fix before the call.

Sent from a phone. Please excuse the brevity and typos.

On Apr 5, 2016, at 6:15 AM, Misha Vinokur notifications@github.com wrote:

@phillipadsmith @burtherman @hackshackers/action-group-website Hey guys is anyone else getting errors when sending stuff to info@hackshackers.com?

— You are receiving this because you were mentioned. Reply to this email directly or view it on GitHub

[samanthasunne]

So are we sticking with info@hackshackers.com? I'm gonna send out another tweet this week.

[samanthasunne]

Can someone add the contact info (info@hackshackers.com) and deadline (April 11) to the text of the RFI itself?

[Cromian]

@samanthasunne done!

[samanthasunne]

Thanks Misha!