Re: Full screen calendar add-in??
As Steve notes, modules collaboratively developed and released is urgent and important to the A5 community, beyond the short-term goals of having any particular module (calendar or otherwise) available right now.
Alpha provides a great development environment, which is what they are best able to do for us. The developers in this forum can certainly take it forward from there.
The benefits of a collaborative volunteer effort would be:
1. (obviously,) certain modules would be available that are not currently available
2. One or more modules could be tailored for new users reference as an example of best coding practices. This fulfills a training role.
3. Seeing successful modules will encourage others to volunteer - success begets success
4. Maintaining a support system (file management and version control) would ensure that modules are maintained, described and available.
5. Less reinvention of the wheel of course
6. In other development communities, people who coordinate the volunteer efforts for a module are often professional developers who benefit from the industry and customer exposure that coordinating a well-known module provides. There's nothing like a well-known and admired project as evidence of one's ability to deliver good solutions.
I would really like to see a first effort at making such a collaborative volunteer effort work for A5. I would also like to be part of such an effort, although I recognize I don't have the A5-specific expertise to justify a leadership position.
As Steve's closing question implies, maybe similarly minded people need only raise their hand and see what response that produces. Among those people, some internal discussion should allow for the ball to get rolling from there.
As Steve notes, modules collaboratively developed and released is urgent and important to the A5 community, beyond the short-term goals of having any particular module (calendar or otherwise) available right now.
Alpha provides a great development environment, which is what they are best able to do for us. The developers in this forum can certainly take it forward from there.
The benefits of a collaborative volunteer effort would be:
1. (obviously,) certain modules would be available that are not currently available
2. One or more modules could be tailored for new users reference as an example of best coding practices. This fulfills a training role.
3. Seeing successful modules will encourage others to volunteer - success begets success
4. Maintaining a support system (file management and version control) would ensure that modules are maintained, described and available.
5. Less reinvention of the wheel of course
6. In other development communities, people who coordinate the volunteer efforts for a module are often professional developers who benefit from the industry and customer exposure that coordinating a well-known module provides. There's nothing like a well-known and admired project as evidence of one's ability to deliver good solutions.
I would really like to see a first effort at making such a collaborative volunteer effort work for A5. I would also like to be part of such an effort, although I recognize I don't have the A5-specific expertise to justify a leadership position.
As Steve's closing question implies, maybe similarly minded people need only raise their hand and see what response that produces. Among those people, some internal discussion should allow for the ball to get rolling from there.
Comment