Re: [dba-dev] Re: And now what?
Hi Guys, Priority wise IMO Really need to hammer the issues right now looking for hidden gems. The group has usually managed to keep our open issue count below 100, normally well below. Right now we are closer to 120 - It would help if we could just find a way to tackle that list and get things moved into or out of work planning. Assigning issues to developers: Now that means Ocke, but that just isn't gonna fly. Some way is needed to pull out which issues needing developer talent, other then Ocke, in order to get them addressed. Keep in mind that the current list of desired features: http://wiki.services.openoffice.org/wiki/Base/Features/Pool Someone needs to really look at that list and see what can be implemented as extension - rumor is that Google SOC will be accepting OO.o again, if so then a simple specification for a few of these features would go a long way in raising our chances of getting some help that way. Anyway - just a few thoughts of the top of my head...(mostly) Drew - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] Re: And now what?
Drew Jensen wrote: Hi Guys, Priority wise IMO Really need to hammer the issues right now looking for hidden gems. The group has usually managed to keep our open issue count below 100, normally well below. Right now we are closer to 120 - It would help if we could just find a way to tackle that list and get things moved into or out of work planning. Assigning issues to developers: Now that means Ocke, but that just isn't gonna fly. Some way is needed to pull out which issues needing developer talent, other then Ocke, in order to get them addressed. Keep in mind that the current list of desired features: http://wiki.services.openoffice.org/wiki/Base/Features/Pool Someone needs to really look at that list and see what can be implemented as extension - rumor is that Google SOC will be accepting OO.o again, if so then a simple specification for a few of these features would go a long way in raising our chances of getting some help that way. Anyway - just a few thoughts of the top of my head...(mostly) good ideas .. i had similar thoughts :) so let us start with a 'new year cleaning up db unconfirmed issues' next week .. further info will follow next monday (please keep the next week free for that action) .. also it is a good opportunity for newbies to join in Drew bye chris - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] Re: And now what?
Anyway - just a few thoughts of the top of my head...(mostly) good ideas .. i had similar thoughts :) *laughing*...hey I said mostly Drew ps - yeah I stole them - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] Re: And now what?
Drew Jensen wrote: Anyway - just a few thoughts of the top of my head...(mostly) good ideas .. i had similar thoughts :) *laughing*...hey I said mostly Drew ps - yeah I stole them bad boy .. as punishment you can host the newbies ;) - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
[dba-dev] Re: And now what?
Drew Jensen wrote: Hi, Ok - so 50% of the developer team is now gone. Anyone want to take a crack at where that leaves us? Come on now - everyone has had a day to think about it. Drew Drop embedded HSQLDB and make the rest working for experienced database developers (macros forms) and for the ordinary mail merger (reliable filters, connections and sort orders). My 2 Cents, Andreas S. - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] Re: And now what?
Andreas , Your proposal is maybe a bit to drastic, but OO can, indeed, been a ideal frontend for any DB, included a Oracle Base :-), I hope they reed this dispared crys and gives us some exctra developer power. Fernand Drew Jensen wrote: Hi, Ok - so 50% of the developer team is now gone. Anyone want to take a crack at where that leaves us? Come on now - everyone has had a day to think about it. Drew Drop embedded HSQLDB and make the rest working for experienced database developers (macros forms) and for the ordinary mail merger (reliable filters, connections and sort orders). My 2 Cents, Andreas S. - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
[dba-dev] Re: And now what?
Fernand Vanrie wrote: Andreas , Your proposal is maybe a bit to drastic, but OO can, indeed, been a ideal frontend for any DB, included a Oracle Base :-), I hope they reed this dispared crys and gives us some exctra developer power. Yes, reduce Base to a better frontend. Drop that embedded caricature of a database backend. It is slow, unsafe (too many reports about data loss), insecure (no permissions) because behaves like an extension. It installs itself before you can use it and it gets repackaged when you close the document. May be it was the most efficient way to accomplish what the crowd shouted for (back in 2005) and certainly it was a nice toy for educational purposes but now let it rest in peace. If all the other pieces would work more consistently (simpler rather than easier!) it could be a big improvement with less software to maintain. Just leave the job to create a relational database up to the professionals and power users with their own tools for the respective database backend. There is no need for a table designer or relation editor in a mere frontend tool. - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
Re: [dba-dev] Re: And now what?
On 3/2/2010 8:45 PM, Andreas Saeger wrote: Fernand Vanrie wrote: Andreas , Your proposal is maybe a bit to drastic, but OO can, indeed, been a ideal frontend for any DB, included a Oracle Base :-), I hope they reed this dispared crys and gives us some exctra developer power. Yes, reduce Base to a better frontend. That was Base is already. Drop that embedded caricature of a database backend. It's not a caricature. If it was one, then use MiniSQL or the like instead. It is slow, unsafe (too many reports about data loss), insecure (no permissions) because behaves like an extension. It installs itself before you can use it and it gets repackaged when you close the document. May be it was the most efficient way to accomplish what the crowd shouted for (back in 2005) and certainly it was a nice toy for educational purposes but now let it rest in peace. For single-user installations it is more than enough. Besides it has been improving over time. If all the other pieces would work more consistently (simpler rather than easier!) it could be a big improvement with less software to maintain. Just leave the job to create a relational database up to the professionals and power users with their own tools for the respective database backend. There is no need for a table designer or relation editor in a mere frontend tool. False. As a matter of fact I know of sites which used MS Access for exactly those purposes (and not using the MSA's JetEngine). Even if there is some frustration, keep it in proportion (and let those gazillion single-users still have their database with Base). In addition, it may be possible that developers from the community step up/in? ---rony - To unsubscribe, e-mail: dev-unsubscr...@dba.openoffice.org For additional commands, e-mail: dev-h...@dba.openoffice.org
