search

Appsterdam / open

Appsterdam is an open community-driven organization. This public repository contains all the knowledge used in the creation and running of Appsterdam.
41 stars 14 forks source link

Appsterdam A Lab Hours - 2 #51

Closed tross6 closed 11 years ago

tross6 commented 11 years ago

It looks like the original issue thread was closed. I don't know how to reopen it, so starting a new one.

Thanks, Valentina for the reminder on your availability. It can get confusing coordinating this.

Here's the schedule so far then:

Mon 16th: @tross6 Tue 17th: ??? Wed 18th: @tross6 morning / @PlayfulPandas afternoon Thu 19th: @casperkoomen (tentative) / @PlayfulPandas afternoon Fri 20th: ???

tross6 commented 11 years ago

@timodewinter Around 5pm would be great if possible.

@PlayfulPandas, you're still coming at 14.30 today? I will need your key to close up b/c Timo will have mine after the pickup.

timodewinter commented 11 years ago

Perfect, I'll make sure someone will pick it up.

PlayfulPandas commented 11 years ago

hey guys, I am here

tross6 commented 11 years ago

I will be back in 45 minutes or so. If Timo's person comes before I get back, could you give them your key?

tross6 commented 11 years ago

Anyone available for Tuesday (tomorrow) and Friday this week?

tross6 commented 11 years ago

Anyone available for even a half-day tomorrow? Preferably afternoon?

ron- commented 11 years ago

I can do tomorrow 1-6, that helpful?

tross6 commented 11 years ago

Yes, Ron, that's great. Thanks!

timodewinter commented 11 years ago

Hey guys, I'm not available this week, but from next week onwards I will be able to do Friday all day.

Also, I still have a set of keys from Friday, who shall I pass them on to? I can also drop 'm off tomorrow morning.

On ma, sep. 16, 2013 at 7:45 PM, tross6 notifications@github.com="mailto:notifications@github.com"> wrote:

Yes, Ron, that's great. Thanks! — Reply to this email directly or view it on GitHub.

tross6 commented 11 years ago

Timo, you can give them to me tomorrow morning. Or, I will be there all day Wednesday, so that works, too. I will have two keys then, but I can then give it to Casper who has Thursday.

timodewinter commented 11 years ago

Ill drop by wednesday morning, is a little easier for me, I might be there before you, will leave 'm on the table then ;-)

On ma, sep. 16, 2013 at 8:11 PM, tross6 notifications@github.com="mailto:notifications@github.com"> wrote:

Timo, you can give them to me tomorrow morning. Or, I will be there all day Wednesday, so that works, too. I will have two keys then, but I can then give it to Casper who has Thursday. — Reply to this email directly or view it on GitHub.

ron- commented 11 years ago

Might be closer to 1:30. Hope that isn't a problem!

tross6 commented 11 years ago

Sounds good, Timo,

I made edits to the Freeworkspace.md file yesterday or so. But now for some reason I'm not able to. Any advice?

tross6 commented 11 years ago

Okay, no problem Ron!

tross6 commented 11 years ago

Casper @casperkoomen is now doing Thursday (with Valentina as backup PM) and Friday this week. We'll get him on Github so he can participate in the convo directly.

PlayfulPandas commented 11 years ago

Hi Tara, tomorrow wed 18 if I come at 1330 is still ok? I have to go somewhere earlier and I fear I might be late for 1300

PlayfulPandas commented 11 years ago

13, maybe late

tross6 commented 11 years ago

Sorry I didn't respond yesterday, Valentina.

That's no problem at all. Just come when you can, and no worries.

timodewinter commented 11 years ago

@tross6 I was unable to drop by this morning due to a class I had to attend. I can either drop it off around 6, or drop it off at Casper's if he lives close to the centrum.

On Sep 17, 2013, at 12:22 PM, tross6 notifications@github.com wrote:

Sounds good, Timo,

I made edits to the Freeworkspace.md file yesterday or so. But now for some reason I'm not able to. Any advice?

— Reply to this email directly or view it on GitHub.

tross6 commented 11 years ago

Hi Timo--Around 6 today would be great. Thank you!

tross6 commented 11 years ago

Just wanted to note that we don't have an official Appsterdam attendant after 1:30 today, due to illnesses. Francisca stepped in to open (thanks, Francisca!), but she has to leave at 1:30.

I've been there four days this week, and need to stay in Haarlem today so I can't do it.

If anyone can come for the afternoon to be there for Appsterdam, that would be great. If not, our friend Anton who has his own key (not an official Appsterdamer) will lock up for us in any case.

ribeto commented 11 years ago

I'm here so I can get the key from Francisca and close up today.  I was planning to be here on Monday as well so I can open up Monday morning too. Let me know

On September 20, 2013 at 11:17:52 AM, tross6 (notifications@github.com) wrote:

Just wanted to note that we don't have an official Appsterdam attendant after 1:30 today, due to illnesses. Francisca stepped in to open (thanks, Francisca!), but she has to leave at 1:30.

I've been there four days this week, and need to stay in Haarlem today so I can't do it.

If anyone can come for the afternoon to be there for Appsterdam, that would be great. If not, our friend Anton who has his own key (not an official Appsterdamer) will lock up for us in any case.

— Reply to this email directly or view it on GitHub.

tross6 commented 11 years ago

Great, Hristo! Thanks!

I will also be there on Monday, but if you can open, I will come a bit later in the morning.

ribeto commented 11 years ago

I think Francisca left. So I'd have to get a key from someone in order to open on Monday.

tross6 commented 11 years ago

Okay, the github communication method isn't working perfectly yet. :-)

I'll open on Monday, then. I'll be there between 9:45-10:00.

spllr commented 11 years ago

Hi @tross6 etc all.

Here are some tips on how to yield an issue tracker in the most effective way.

Rule 1: Can it be closed?

Try to make sure issues can be closed.

So opening an issue for opening on monday is very valid.

Rule 2: Can it be assigned?

Issues are most effective if they can be assigned to someone responsible.

So when rule one is applied, you should be able to open an issue for open space on Monday and assign it to whoever is expected to do this.

This also makes it easier to swap responsible people, notify them, give them the option to un-assign themselves and keep track of tasks which have no responsible person.

Rule 3: Reference issues

The issue tracker allows you to reference issues. So it's good to have one master ticket like this one for the week. And then create sub tickets which reference the main ticket. Referencing is as easy as typing a # and then the issue number. When using the web interface, it will autocomplete for you.

Rule 4: Use github user names

When using the @tross6 convention, people will be notified via email. And next to that, it's pretty much the same argument why you should use @username conventions on twitter.

Hope this helps :-)

tross6 commented 11 years ago

Thanks for the tips, @spllr!

judykitteh commented 11 years ago

As per @tross6's suggestion, a new thread for key coordination will be opened each week. Closing this issues. See #53.

@spllr's GitHub tips has been added to this new document in Help.