#337 Estimating team resources: how many hours per week can you consistently spend on NeuroFedora?
Closed: Fixed 4 years ago by ankursinha. Opened 4 years ago by ankursinha.

I think it's time we got some idea of the man power we currently have in the team.

So, how many hours per week can you consistently spend on NeuroFedora tasks? (This is time specifically for NeuroFedora. So time for other Fedora tasks should not be included)

The idea is that we approximate the total man-power we have, and use that to decide what tasks to do next. It's just to get an idea, we know that our free time varies greatly depending on work/life and so on. (Note: It is perfectly fine to say 0 if you are too busy at the moment already!)

Important read: Bex's post on deciding how much work one can take on:
https://www.winglemeyer.org/ramblings/2019/01/07/cookie-cleanup.html#


  • 4/5 hours a week

However, I will start a post-doc in the next month or so and this may change depending on my responsibilities at work.

Sorry, but specifically to NeuroFedora, my hours are neraly zero... :-(

Sorry, but specifically to NeuroFedora, my hours are neraly zero... :-(

That's perfectly OK. I already see how busy you are with QA/Mindshare and all of that!

I have more or less 16 hours per week for the whole project...

3-5 hours per week for me.

However, there are some weeks where it becomes difficult for me to participate (this week).

Important read: Bex's post on deciding how much work one can take on:
https://www.winglemeyer.org/ramblings/2019/01/07/cookie-cleanup.html#

Interesting post

0 to 1 hour at this time.

I have more or less 16 hours per week for the whole project...

Ah, is that for all your Fedora work? Should we say 1-2 of this could be used on NeuroFedora tasks?

I have more or less 16 hours per week for the whole project...

Ah, is that for all your Fedora work? Should we say 1-2 of this could be used on NeuroFedora tasks?

I will say 2 hours as a good approximation :)

So, in total, we have about 12-16 hours a week.

Please keep doing your bits: packaging/testing/compose checking and so on, but let's keep in mind our resource constraints before making new plans.

Thanks all, closing this now!

Metadata Update from @ankursinha:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Login to comment on this ticket.

Metadata