Our next move

Hi Ryan,

Can we get started here?

Maybe a look at the project plan. I still need to get a few things done.

What do you think?

Btw who has access here?

Agreed, I am really anxious to get working on database abstraction so we can adopt any type of database backend, and provide a few more facilities for creating easy-to-use components not targeted at programmers (e.g. formbuilders with automatic persistence and validation against custom database tables, custom user/group/role profiles, etc.).

Though those won’t be 1.0 goals, I want to make sure we balance our long-term goals, and our short-term tasks, just so we’re moving in the right direction in all aspects of the project. We really need to utilize Flyspray for this as much as possible so we can track each others progress and be able to make quick design/development decisions. I also need to upgrade Flyspray to latest version so we can get RSS feeds from Flyspray.

What do you guys think about moving relatively quickly with merging snippets/chunks and users to free up and optimize tables along with the bug fixes and putting a password reminder in the admin login (and loosing that last reference to Etomite on the login page!)?

I’d say some basic optimization, maybe some lingo changes (as discussed elsewhere), the requisite bugfixes, and some minor menu/navigation cleanup in the manager would make a great .9.1 release. Maybe even some minor graphics updates and stylesheet tweaks in the manger as well.

Regarding the naming conventions, I really would like to revisit that soon and focus on concepts that are really non-developer oriented but that still fit for devloper lingo. In other words, I’d like to be able to understand it immeidately without having to ask for an explanation! (and merging whereever possible, of course)

What goes on behind the scenes may be another thing entirely though.

Here a copy of the proposed BlueWater plan.

PS. I’m not in a rush to get any of these changes inside x9.1. these features might not make it out until x9.2 or x9.5

It all sounds good to me. I think 9.1 really needs to be bugfixes and some simple naming and look fixes as mentioned. I’d like to see 9.1 happen soon, so I don’t want to get bogged down with any big projects.

I think we need to put some attention toward the support site also. I think getting the repository and a demo up would go a long way toward improving the site and getting us some more users.

I agree on the support site too. That’s really my major priority since I’ve already made three bugfix commits towards .9.1.

Another thing to note is that the bluewater manager will certainly be more event driven thus making it 90% more modular. This means that you’ll be able to override/extend some core functions.

for example:

OnInitBackup -starts the backup screen.
OnAuditLog -logs the manager audit.
OnWebAuditLog -logs the web page info.

These will enable you to add custom menus:
OnMenuPreRender
OnMenuRender
OnMenuRenderItem

Plugins will also have execution priority.

Excellent stuff Raymond.

Ok,

Now it’s time to roll on. I would like for everyone to have a look at the project plan and then choose the tasks that you think you’ll be able to handle and then post your duration and start date.

This way I can then adjust the project plan according. If you see the need for additional tasks then please let me know

Does the project plan need to be updated to reference our recent merging discussion?