Request for comments / discussion - The Storm development process

Events happening in the community are now at Drupal community events on www.drupal.org.
juliangb's picture

Hi all,

I'd like some feedback please on how we can improve Storm development.

As a background to this request, the time I have free to work on Storm has reduced (including time for non-coding maintainer tasks), and I know that others who have previously put a lot of time into Storm are time pressed too. Also, I think it is worth noting the effects of this, in my opinion Storm as a package is falling behind and because of that, usage is beginning to stagnate or drop.

I have some thoughts on why this is and what needs to be done, and will post these in due course, but I'd really like to have a brainstorm from members of the Drupal community.

What am I looking for in the comments?
- Thoughts on the process that is used in the Storm issues queue
- Thoughts on the ease of being involved with that process
- Thoughts on the long term way that Storm is moving in terms of the software package
- Potential solutions to the problems, not just a list of problems

What am I not looking for?
- Specific bug reports / coding tasks / feature requests - lets try to keep a broad perspective
- Non-constructive comments - as with any discussion - it will really help us make progress to keep on topic

Any questions, please ask and I'll try to clarify in the comments.

Thanks...

Comments

Hi Julian, sorry, i want to

carsten müller's picture

Hi Julian,

sorry, i want to work more on storm, but at the moment time is rare. I'm looking forward that things are getting better, so we get more time to work on storm.

This is a good initiative from you. At the moment i do not have any ideas of how to improve working on storm. There is a long list of issues...

Here some very rough ideas:

  • sprint camps, where all developers are working on issues and improvements, maybe at a weekend day or more
  • maybe one evening in the week which is reserved for working on storm. It is not neccessary that all maintainers work at the same evening.
  • a master maintainer who assigns the issues to the developers. so it is clear who works on which ticket

A first step could be that we are priorizing the issues. the import ones like bugfixes should be solved first. After that we can solve the feature requests.
I think the main problem is missing time ...

We are more than interested

mitke's picture

We are more than interested that Storm continues.
Unfortunately, I have no time at all to develop, but we are working with a developer to extent Drupal functionality to our needs.
We are now attending the issue of assigning multiple persons to project/task/ticket.

I don't have ideas on how to resolve the lack of time, but we are paying and willing to pay for developments/issues that are relevant to our use of Storm. Maybe you can go through the issues and divide them into 2 groups:
1. Issues that will be developed on free time (like bugs, small issues, etc.)
2. Issues which requires funding (larger developments, etc...) - for these issues developers can publish price offers and sponsors can sponsor the development.

Thanks to both of you for

juliangb's picture

Thanks to both of you for your thoughts. I'm hoping that there will be others with thoughts too.

I also think it would be worth adding - which direction should we be focusing on for Storm? Is there a much needed feature? Does it need to be more stable? Does it need to integrate better with other modules? Is the Drupal 7 port more important than any improvement to the current version?

Also, a couple of questions - I'm guessing those subscribed to this group have something invested in Storm. Do you tend to be using it for yourself? Making sites for others? Do you manage one or more installations?

Looking forward to the D7 release

leemako's picture

Hello all, im not a coder at all and unfortunately cannot offer those sorts of services but I cant say that as a Drupal user this project is very exciting. I have been checking in regularly to see what progress has been made on the D7 version and intend to use the module both for my own business and for clients.

Maybe its worth sending putting a vote on the project page for what people most want the team to concentrate on. My vote goes for D7 release obviously. Good luck guys and thanks for your efforts so far, excellent job!

Agreed on D7. It seems there

aendra's picture

Agreed on D7. It seems there are a bunch of people with very little time developing this project right now; feel free to correct me if I'm wrong. For the project to not stagnate, I think the D7 branch is critical in building community buy-in for the project and getting more developers with more time working on it. Once I have more time to work on personal projects, I'd be really interested in helping with the D7 version's development.

Personally, I'd like to apologize for not having done the documentation I talked about a while back -- I'm in the process of moving continents and haven't had a ton of time. I hope to contribute something within the next few months on that front.

--
ændrew rininsland
news, photos, data, code.
aendrew.com :: @aendrew