roadmap

Although actual implementation details are still forming around the pieces we are trying to implement for the Drupal 6 core i18n feature set (which will get shipped with Drupal 6 hopefully), we should define some goals which we aim for, so we see the target. Unless we work in the same direction, there will be no useable consistent i18n solution in Drupal core for people to build their sites on. So what is possible to accomplish in the Drupal 6 timeframe, and what will only be possible to implement in contrib modules?

Here's what I would like to be accomplished over the next month:

1. Fix all bugs currently in the issue queue and implement all feature requests.
2. Better display/theming of configuration options in the poll display (e.g. duration, starting date, eligibility, etc.).
3. Views integration.
4. Default options per content-type.
5. jQuery magic for ranking votes.
6. Email capability for electoral list - option to send to all who are eligible, those who have voted, or those who haven't voted.
7. Actual releases for 5.0 and 4.7 branches.

It's also time for some progress evaluation from last month, when I had the following priorities for my work on Advanced Poll:

I am willing to dedicate some real time and purpose to such a project. We will need a bit more organization form the top down though. I'm joining a couple of the mailing lists towards that end and i would really like to get the ball rolling on this. I use drupal privately and professionally and both would benefit immensely from this project. While I would love for such a project to be self sustaining (wiki or otherwise) i think it will require some early heavy seeding to get things going. Perhaps integrating "development time frame" as a field into project_issue module would also provide some structure to help make the "feature improvements" process more organic.

I had provided little updates over the last few weeks due to several reasons (including my laziness) so I apologize for that. I created a roadmap before but I found that roadmap is hard to update so I create this one. From now on, I will provide weekly reports on this groups and update this post to reflect changes. The table below may not show all that have been done or will be worked on but I hope it'll provide a clearer overview of the works. I have a feeling that this amount is a bit too much. However, I think it's feasible if things goes smoothly. If things goes wrong, I may cry for help here anyway :)

The task that most concern me now is the XML-RPC interface. We need a clear, intuitive but powerful interface that covers most of actions we can perform with Drupal. For now, the way that I implement that interface is by the need of the XUL part. But if it goes this way, the interface will be almost useless to others. I created a post about the XML-RPC interface here and hoping that I'll receive a lot of valuable advices and ideas.

About the works that have been done, I have created some base facilities for Drupal Manager. The most important part is the form renderer. The remote form render is able to render a Drupal form or just a part of it and collecting data, you may see how it works in the demo (Preferences pane). However, the form render is quite limited now. It don't spport some form elements like buttons and file upload. About the home screen, the node manager interface has been reviewed. It's more useful now and support tabs. The code has been rearranged an clean up a lot.

I also created a demo site at http://www.sandb0x.net/demo/demo.html . If you feel curious, please take a look at it.

Hello everybody,
I'm Hung who have been accepted to work on the project "Multi-site admistration through rich XUL client".
I'll start working on this project since today (1/6).

1) In-depth analysing and completing the remote configuration API. I'll post the information of the API here :

2) Analysing the nodes administration tasks, stabilize the Nodes Manager add new features

3) Implement the tabbed interface

4) Implement the config editor

5) Implement specific modules