Splitting the work

[Omer Katz]

nose2 has been (almost) inactive for some time and I'd like to change that. We really need to start working on 0.5.0.
Would you guys mind conducting a bi-weekly stand-up meeting in order to move this project forward?

Best Regards,
Omer Katz.

[jason pellerin]

I'd love to see more active work and more progress, but my available time for work on nose/nose2 has dwindled almost to nothing, so I can barely keep up with pull requests as they come in (and sometimes, I can't even do that). I could see having a bi-weekly checkin by email and/or this list, but I can't commit to being available for a standup meeting in synchronous time. :(

--
You received this message because you are subscribed to the Google Groups "nose-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nose-dev+u...@googlegroups.com.
To post to this group, send email to nose...@googlegroups.com.
Visit this group at http://groups.google.com/group/nose-dev.
For more options, visit https://groups.google.com/groups/opt_out.

[Malthe Borch]

Maybe a triage stage could help with the workflow. I submitted a fairly trivial patch four months ago, but it was never looked at:

   https://github.com/nose-devs/nose/pull/727

At least putting on a label such as "trivial" or "easy" would help determine which pull requests / issues were ready for review without requiring too much work.

\malthe

[jason pellerin]

Malthe, 

First of all, I apologize for not reviewing your patch. I know how aggravating it is to submit a pull request and then... nothing.

A triage stage is a good idea, and we should do that. But ultimately the problem is me -- I no longer have any time for OSS work. I can't use day-job hours for it anymore, and my free time for OSS has dwindled from an hour a week or so to pretty much nothing.

So I think, sadly for me, what really needs to happen is for new leadership to take over nose and nose2. I still want to contribute as much as I can, but that really isn't very much at all now.

I've put forth this call a few times before as my time to work on nose/2 was reduced, but I'll do it again now.

Thanks and apologies again,

JP

[John Szakmeister]

On Tue, Jan 7, 2014 at 10:12 AM, jason pellerin <jpel...@gmail.com> wrote:
> Malthe,
>
> First of all, I apologize for not reviewing your patch. I know how
> aggravating it is to submit a pull request and then... nothing.
>
> A triage stage is a good idea, and we should do that. But ultimately the
> problem is me -- I no longer have any time for OSS work. I can't use day-job
> hours for it anymore, and my free time for OSS has dwindled from an hour a
> week or so to pretty much nothing.

FWIW, having a triage step is good when there are several people who
will step up to review patches and provide good feedback. I think
it's less useful when there isn't a team to do that... it's just more
work to do with no clear gain.

> So I think, sadly for me, what really needs to happen is for new leadership
> to take over nose and nose2. I still want to contribute as much as I can,
> but that really isn't very much at all now.
>
> I've put forth this call a few times before as my time to work on nose/2 was
> reduced, but I'll do it again now.

Jason, I can take over nose but I think you probably need to do a
couple of things on your end. I think the biggest one might be to add
me as a maintainer to nose on PyPI so that I can publish new releases.
I don't know if there's anything that needs to be done on the
ReadTheDocs end of things either. I've avoided stepping up more
because it's really your project and I didn't want to be making
judgement calls on the behalf of nose without your input. But if
you're stepping down, I can probably fill that gap. I say "probably"
because I'm assuming that nose should enter a maintenance phase. If
everyone thinks it needs more features and much more loving, then I'm
not the guy (my days are quite busy too with a family and after-school
activities).

One thing that I believe really needs to be done is to decide what is
the ultimate fate of nose vs. nose2. Personally, I think nose should
go into bug fix mode, and we should probably be pushing nose2 as the
tool people should be using. I think there is some value in fixing
some brokeness in nose, especially for those who cannot make that
transition right now. I'm not excited about adding a bunch of new
features to nose because it's architecture is showing it's age, and I
think nose2 is in a better spot. Either way, I do think we should
probably be more public about the intentions for nose and nose2.

Assuming that nose will be entering maintenance mode, I can certainly
take that burden off of your shoulders. At the moment, I think
someone else will have to step forward for nose2.

> Thanks and apologies again,

No need to apologize! Life happens. :-) And that's the great thing
about open source--someone else can pick up the ball and run with it.
:-)

-John

[jason pellerin]

On Tue, Jan 7, 2014 at 10:24 AM, John Szakmeister <jo...@szakmeister.net> wrote:

On Tue, Jan 7, 2014 at 10:12 AM, jason pellerin <jpel...@gmail.com> wrote:
> Malthe,
>
> First of all, I apologize for not reviewing your patch. I know how
> aggravating it is to submit a pull request and then... nothing.
>
> A triage stage is a good idea, and we should do that. But ultimately the
> problem is me -- I no longer have any time for OSS work. I can't use day-job
> hours for it anymore, and my free time for OSS has dwindled from an hour a
> week or so to pretty much nothing.

FWIW, having a triage step is good when there are several people who
will step up to review patches and provide good feedback.  I think
it's less useful when there isn't a team to do that... it's just more
work to do with no clear gain.

> So I think, sadly for me, what really needs to happen is for new leadership
> to take over nose and nose2. I still want to contribute as much as I can,
> but that really isn't very much at all now.
>
> I've put forth this call a few times before as my time to work on nose/2 was
> reduced, but I'll do it again now.

Jason, I can take over nose but I think you probably need to do a
couple of things on your end.  

Awesome! I'll see what I can do on pypi and rtd.

One thing that I believe really needs to be done is to decide what is
the ultimate fate of nose vs. nose2.  Personally, I think nose should
go into bug fix mode, and we should probably be pushing nose2 as the
tool people should be using. I think there is some value in fixing

some brokeness in nose, especially for those who cannot make that
transition right now.  I'm not excited about adding a bunch of new
features to nose because it's architecture is showing it's age, and I
think nose2 is in a better spot.  Either way, I do think we should
probably be more public about the intentions for nose and nose2.

I agree with all of this. And I think nose2 is mature enough now that most projects will be able to switch without too much trouble. I'm not sure about how to announce that sort of thing, though. Any suggestions?

Assuming that nose will be entering maintenance mode, I can certainly
take that burden off of your shoulders. 

Thank you, that is very, very much appreciated.

JP 

[John Szakmeister]

On Tue, Jan 7, 2014 at 10:31 AM, jason pellerin <jpel...@gmail.com> wrote:
> On Tue, Jan 7, 2014 at 10:24 AM, John Szakmeister <jo...@szakmeister.net>
> wrote:

[snip]

>> Jason, I can take over nose but I think you probably need to do a
>> couple of things on your end.
>
> Awesome! I'll see what I can do on pypi and rtd.

Great!

>> One thing that I believe really needs to be done is to decide what is
>> the ultimate fate of nose vs. nose2. Personally, I think nose should
>> go into bug fix mode, and we should probably be pushing nose2 as the
>> tool people should be using. I think there is some value in fixing
>>
>> some brokeness in nose, especially for those who cannot make that
>> transition right now. I'm not excited about adding a bunch of new
>> features to nose because it's architecture is showing it's age, and I
>> think nose2 is in a better spot. Either way, I do think we should
>> probably be more public about the intentions for nose and nose2.
>>
> I agree with all of this. And I think nose2 is mature enough now that most
> projects will be able to switch without too much trouble. I'm not sure about
> how to announce that sort of thing, though. Any suggestions?

That was my feeling as well.

I think the best way to announce it might be with the next patch
release for nose1. I'm not sure how to word it just yet, but
something to the effect that nose is entering maintenance mode and
everyone is encouraged to migrate to nose2. We should probably point
to the compatibility guide in that announcement
(https://nose2.readthedocs.org/en/latest/differences.html) and leave
it at that.

>> Assuming that nose will be entering maintenance mode, I can certainly
>> take that burden off of your shoulders.
>
> Thank you, that is very, very much appreciated.

You're welcome!

-John

[Justin Foo]

Any update on the handover? I'm keen to see features like colorized output and pretty tracebacks brought into nose2.

Justin

[John Szakmeister]

On Sun, Jan 19, 2014 at 12:02 PM, Justin Foo <jcjf...@gmail.com> wrote:
> Any update on the handover? I'm keen to see features like colorized output
> and pretty tracebacks brought into nose2.

Justin, I only took responsibility for nose1. Someone else will have
to step up for nose2.

-John