Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Repo info
Activity
  • Aug 23 14:51
    gep13 labeled #695
  • Aug 23 14:51
    gep13 milestoned #695
  • Aug 23 14:51
    gep13 assigned #695
  • Aug 23 14:51
    gep13 opened #695
  • Aug 22 13:22
    Sukender opened #694
  • Aug 21 06:41
    gep13 closed #693
  • Aug 21 06:41
    gep13 commented #693
  • Aug 21 06:40
    gep13 milestoned #693
  • Aug 21 06:40
    gep13 labeled #693
  • Aug 21 06:40

    gep13 on develop

    (GH-693) Clarify usage requirem… (compare)

  • Aug 21 06:39

    gep13 on develop

    (maint) Remove mention of ZenHu… (compare)

  • Aug 21 04:00
    Lemmingh opened #693
  • Aug 09 14:39
    cybercatgurrl commented #617
  • Aug 01 08:39
    pascalberger commented #692
  • Aug 01 07:56
    gep13 commented #692
  • Aug 01 07:34

    mwallner on develop

    (build) Disable documentation o… (compare)

  • Aug 01 07:34
    mwallner closed #692
  • Aug 01 07:33

    mwallner on develop

    (doc) Fix typo (#691) (compare)

  • Aug 01 07:33
    mwallner closed #691
  • Jul 31 05:46
    AdmiringWorm commented #637
Richard Simpson
@RichiCoder1
Cool. They apparently even have irc support
Gary Ewan Park
@gep13
ooo, I like that
Richard Simpson
@RichiCoder1
This is very slick :D
Gary Ewan Park
@gep13
agreed
never really used IRC before if I am honest
@RichiCoder1 trying out mentions - i can edit messages as well!
Richard Simpson
@RichiCoder1
Very cool
And that's fine. For me, it just happened to be where a lot of dev conversations happened.
Gary Ewan Park
@gep13
i would be happy to work in here, rather than in Jabbr, I like the fact that it is all integrated
Richard Simpson
@RichiCoder1
Agreed! I'd be happy to set up camp here.
Gary Ewan Park
@gep13
cool :+1:
Richard Simpson
@RichiCoder1
While I have you here, what do you think of our progress and where we are in regards to hitting the 0.12 milestone?
Gary Ewan Park
@gep13
I think we are doing fine. I don't want to get into a mind set of things "must" be done by this date, otherwise there will be trouble. This is OSS, and things get done, when they get done. As long as we have issues/features for everything that we want to do before the next release, we can get a feel for when it will be ready
Richard Simpson
@RichiCoder1
At this point, I'm thinking about stopping on features and just focusing on bugs, so we can get at least an initial release out. Then do a round of feedback and focus on improving and refining the experience with v0.13
Gary Ewan Park
@gep13
That sounds like a good idea to me.
I will do the testing on #114 and #113
for #40 I was just going to add the dependency in the nuspec, and see if that covers it for now
Richard Simpson
@RichiCoder1
Did you get any head way on #120? I'm going to be setting up some additional test machines to try and catch any other works-on-my-machine bugs.
Gary Ewan Park
@gep13
there is more that we could do here, but I am hesitant to do too much, as this is somethign that really needs to be fixed in Chocolatey itself
Richard Simpson
@RichiCoder1
Agreed.
Gary Ewan Park
@gep13
I haven't had a chance to repo #120 on a machine that has VS2013 installed, so can't do any actual debugging on it. hoping to do that tomorrow
what about #82 can we had to unit tests to teh code base?
Richard Simpson
@RichiCoder1
Ahh, that's a good point. I just need to figure out the best way to introduce them xD. Setting up tests in general has never been a strong suit of my, so I'm not sure what direction to take with them.
Gary Ewan Park
@gep13
ahhh, me either. I was hoping that you were going to be an elite Unit Testing kind of a guy :-)
We might want to talk to @ferventcoder and @mwrock to see if they can provide some guidance about the best way of going about it, before jumping in
Richard Simpson
@RichiCoder1
Nope, none of that here.
Agreed.
Gary Ewan Park
@gep13
it would be great if we could get at least rudimentary Unit Testing in place before the 0.12.0 release, that way we can move forward knowing that we aren't breaking stuff
let me send an email to the team, and see if they can offer some guidance
Richard Simpson
@RichiCoder1
Sounds good! I'm going to hop off and grab lunch. Let me know if I need to hop on anything.
Gary Ewan Park
@gep13
cool, sounds good. I am just finishing up work, and then I am out this evening, but I will try to get the email out before I go, and we can see where that takes us
have a good lunch!
Richard Simpson
@RichiCoder1
@gep13 Do we want to eliminate all the old Chocolatey Explorer code that's in the WPF_refresh branch? Just realized I never asked.
Ryan Rauh
@rauhryan
Did yall get the HuBoard integration working?
Richard Simpson
@RichiCoder1
Supposedly. I don't know what that entails though
Ryan Rauh
@rauhryan
If you drag a card in HuBoard, it should post a message to the chat room
Richard Simpson
@RichiCoder1
Just dragged an issue, but nothing happened
I guess that's a no.
Ryan Rauh
@rauhryan
thats so strange
Maybe you unchecked all of the events in gitter
Deleting both of the integrations and add them back
Gitter had a deployment issue and I kind of jumped the gun announcing it on twitter
could you please retry :)
Ryan Rauh
@rauhryan
Im super excited to see it work for someone
Richard Simpson
@RichiCoder1
There we go, that seems to have done it. Wish gitter would allow you to reconfigure the hooks rather then having to tear them down and recreate them
Ryan Rauh
@rauhryan
You should add an issue in their github repo
I'll :+1:
Richard Simpson
@RichiCoder1
I think that's right.