Dear all,

I would very much like to see Storm progress a lot more quickly, and this is something that I unfortunately cannot spare enough time to at the moment.

Therefore, I ask if anybody would like to co-maintain with me.

If you are interested, please contact me off-list so that we can chat briefly about what you'd want for Storm and how we can work together. Ideally you'd also have been involved previously on the issues list helping others out, and had CVS experience.

Thanks.

Comments

Magnity’s picture

Magnity commented

After an offline discussion, it has been decided to add juliangb (http://drupal.org/user/719472) to be a co-maintainer.

Part of the agreement is though that we will still continue to advertise for other co-maintainers to aid progress. Please get in touch if you'd be interested.

avpaderno’s picture

avpaderno
he/him
Primary language Italian
Location Brescia, 🇮🇹 🇪🇺
commented

I approved juliangb's application, and granted him access to this project repository.

carsten müller’s picture

carsten müller commented

Hi Magnity,

for info. I am developing an add on module for storm named "storm_contrib". In fact it is a package of modules which are offering new features for storm. It was quite too much to offer all this stuff as patches, so i decided to start a new module. We want to use storm in our organization and we need some more features, which i have to implement now.
The module is still in very early development, but in April i want to publish the dev version on drupal.org. Here a list of the features to avoid that we are implementing the same features and wasting time:

- calculation of end dates for projects, tasks and tickets depending on entered durations
- considering weekends in calculations
- considering national holidays in calculations
- considering holidays of persons
- hourly cost rate in storm persons
- calculation of costs depending on timetrackings
- budgets (duration and costs) for projects
- balance for each project displaying the budget, estimated costs calculated by entered durations and costs, the real costs calculated by timetrackings and expenses and the relations of all costs, - same for durations
- considering utilisations of persons when assigning tickets or tasks
- overviews of timetrackings for persons including daily and monthly statistic
- maybe more ...

I'm looking forward to publish the module to push storm a little bit more. Then you can see that I'm working with storm. If you are still looking for a co maintainer you can probably add me. Maybe i can add some of th features directly in storm. Right at the beginning i want to keep the both modules separate because of bugs and issues. So people who are already using storm will do not get any problems. Also not everybody needs all the new features.

carsten müller’s picture

carsten müller commented

add on:

- conversion of currencies in calculation of costs if currencies of tickets, tasks and projects are mixed

juliangb’s picture

juliangb commented

Hi Carsten,

I know that it can be additional work to make patches and get them in through the issues queue, but please could I encourage you do so if there are bits of your functionality that would be helpful to the majority of Storm users? Naturally there may be bits which fit better as an add-on module.

Also, I will be very happy to add you as a co-maintainer in due course, but please do have some involvement on the issues list first!

Thanks,
Julian

carsten müller’s picture

carsten müller commented

Hi juliangb,

thanks for your reply. Sure, there will be functionality that will fit into storm. But by now they are not tested. My plan is to make the module(s) ready for publishing and for testing. We are going to start test in our company in April. I will also pubish everything in the middle or maybe end of April, so the community can start testing and can create issues. First i want to keep the new functionality separate from the storm core, because if there are bugs (sure they will be, i am just a developer, no machine), they can be handled separate and they will not affect the storm modules. The issue queue of storm is long enough and when i have got some time i want to help reducing it. When the bugs have been reduced and the system is running stable we can think about moving functionality to the storm core. So you do not have to care about the new functions and so your are able to focus on the current issue queue. The second aspect is that storm is already in use and by adding new functionality step by step it will be easier for uns and for the community using storm in their daily work.

The next week and on easter i am on vacation (which is really needed) but after that i am going to start helping on storm.

Greetings
Carsten

juliangb’s picture

juliangb commented

OK, sounds good.

juliangb’s picture

juliangb commented

Pending CVS access, I would like to add tchurch as a co-maintainer.

juliangb’s picture

juliangb commented
Status: Active » Closed (fixed)

I'm closing this issue because with tchurch as a co-maintainer, Storm is not dependent now on just me to commit things.

Closing this issue does not mean that new co-maintainers are not welcome, just that the need is not as urgent.

I would welcome anyone who has an interest in improving Storm and has been active in the issues queue to contact me about joining. Also, note that CVS access is not required to submit or review patches!