[Maria-docs] Random Query Generator docs might disappear soon
Hi! Reading this: https://blogs.oracle.com/MySQL/entry/eol_of_mysql_forge We have documentation there that we refer to from the KB for example, http://forge.mysql.com/wiki/RandomQueryGenerator I think we need to move the documentation for the tool to our KB There is currently no license for the content on the mysql forge... -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/
On Mon, 16 Jul 2012 01:16:52 +0800 Colin Charles <colin@montyprogram.com> wrote: Colin> Hi! Colin> Colin> Reading this: Colin> https://blogs.oracle.com/MySQL/entry/eol_of_mysql_forge Colin> Colin> We have documentation there that we refer to from the KB for Colin> example, http://forge.mysql.com/wiki/RandomQueryGenerator Colin> Colin> I think we need to move the documentation for the tool to our KB Colin> Colin> There is currently no license for the content on the mysql Colin> forge... Even if the Forge was not going away, having our own set of documentation for the RQG scripts would be a good idea. I'll add this to my task list with an August 1st deadline. Elena: Beyond what is mentioned on this page: http://kb.askmonty.org/en/rqg-extensions-for-mariadb-features/ , have you or Philip made modifications to the RQG scripts which would require changes to the documentation as it exists on MySQL Forge? Thanks. -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://gplus.to/mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com
Hi Daniel, On 16.07.2012 17:11, Daniel Bartholomew wrote:
Elena: Beyond what is mentioned on this page: http://kb.askmonty.org/en/rqg-extensions-for-mariadb-features/ , have you or Philip made modifications to the RQG scripts which would require changes to the documentation as it exists on MySQL Forge?
Yes, there is quite a lot of stuff in RQG developed by Philip or somebody else which was not documented on Forge last time I checked. I've made a few more modifications too, in addition to those described in the KB (only documented those which were more or less final). So if we have our version of documentation, it would be good to have access so I could keep adding to it when I encounter undocumented chunks; or I could send you my findings and you would publish them, whichever you prefer. But the problem with my modifications is that they currently live in my work tree, I'm still not sure what is the right way to handle it. I see that Oracle guys do merges into the main RQG tree (not Philip), so I guess they kind of "own" it, and I don't know whether I should merge my changes, especially MariaDB-specific parts, into the same tree, or request them to decide whether they want them, or to keep a separate MariaDB tree. So far I've just been merging the main tree into mine, to avoid diversion, but not the other way round. Any opinions would be appreciated. Regards, /E
Thanks.
On Mon, 16 Jul 2012 17:27:04 +0400 Elena Stepanova <elenst@montyprogram.com> wrote: Elena> Hi Daniel, Elena> Elena> On 16.07.2012 17:11, Daniel Bartholomew wrote: Elena> > Elena> > Elena: Beyond what is mentioned on this page: Elena> > http://kb.askmonty.org/en/rqg-extensions-for-mariadb-features/ , Elena> > have you or Philip made modifications to the RQG scripts which Elena> > would require changes to the documentation as it exists on Elena> > MySQL Forge? Elena> Elena> Yes, there is quite a lot of stuff in RQG developed by Philip or Elena> somebody else which was not documented on Forge last time I Elena> checked. I've made a few more modifications too, in addition to Elena> those described in the KB (only documented those which were more Elena> or less final). So if we have our version of documentation, it Elena> would be good to have access so I could keep adding to it when I Elena> encounter undocumented chunks; or I could send you my findings Elena> and you would publish them, whichever you prefer. My plan is to create a Random Query Generator category and to put the docs for the RQG under there. The URI will be: http://kb.askmonty.org/en/random-query-generator The above doesn't exist right now, but when it does, and the initial documentation is in place, you will be able to update the docs whenever you make changes to the various RQG scripts. Elena> But the problem with my modifications is that they currently Elena> live in my work tree, I'm still not sure what is the right way Elena> to handle it. I see that Oracle guys do merges into the main RQG Elena> tree (not Philip), so I guess they kind of "own" it, and I don't Elena> know whether I should merge my changes, especially Elena> MariaDB-specific parts, into the same tree, or request them to Elena> decide whether they want them, or to keep a separate MariaDB Elena> tree. So far I've just been merging the main tree into mine, to Elena> avoid diversion, but not the other way round. Elena> Elena> Any opinions would be appreciated. If the Oracle people are willing to merge in your changes and additions (including the MariaDB-specific parts) then it would be simpler to just use their tree, but if they're unwilling and/or slow to merge in your changes then we should probably have our own tree and merge in their changes periodically. What about adding the RQG to the mariadb-tools project? Or is it a big/separate enough project that it needs its own launchpad project and tree? Thanks. -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://gplus.to/mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com
On 7/16/2012 6:08 PM, Daniel Bartholomew wrote:
<cut>
My plan is to create a Random Query Generator category and to put the docs for the RQG under there. The URI will be:
http://kb.askmonty.org/en/random-query-generator
The above doesn't exist right now, but when it does, and the initial documentation is in place, you will be able to update the docs whenever you make changes to the various RQG scripts.
Elena> But the problem with my modifications is that they currently Elena> live in my work tree, I'm still not sure what is the right way Elena> to handle it. I see that Oracle guys do merges into the main RQG Elena> tree (not Philip), so I guess they kind of "own" it, and I don't Elena> know whether I should merge my changes, especially Elena> MariaDB-specific parts, into the same tree, or request them to Elena> decide whether they want them, or to keep a separate MariaDB Elena> tree. So far I've just been merging the main tree into mine, to Elena> avoid diversion, but not the other way round. Elena> Elena> Any opinions would be appreciated.
If the Oracle people are willing to merge in your changes and additions (including the MariaDB-specific parts) then it would be simpler to just use their tree, but if they're unwilling and/or slow to merge in your changes then we should probably have our own tree and merge in their changes periodically.
I'll try to find out.
What about adding the RQG to the mariadb-tools project? Or is it a big/separate enough project that it needs its own launchpad project and tree?
randgen is about 20 Mb / 500 files as of now, so I'd say it's pretty big comparing to mariadb-tools. I don't know whether it would be good or bad to have it there, I know some people prefer to have everything in the same project, even in maria, to minimize the number of pulls/branches, while others want the amount of pulled data to be as small as possible, and get additional stuff only when they need it. I'm equally fine with either. /E
Thanks.
Hi! On 16 Jul 2012, at 22:08, Daniel Bartholomew wrote:
Elena> But the problem with my modifications is that they currently Elena> live in my work tree, I'm still not sure what is the right way Elena> to handle it. I see that Oracle guys do merges into the main RQG Elena> tree (not Philip), so I guess they kind of "own" it, and I don't Elena> know whether I should merge my changes, especially Elena> MariaDB-specific parts, into the same tree, or request them to Elena> decide whether they want them, or to keep a separate MariaDB Elena> tree. So far I've just been merging the main tree into mine, to Elena> avoid diversion, but not the other way round. Elena> Elena> Any opinions would be appreciated.
If the Oracle people are willing to merge in your changes and additions (including the MariaDB-specific parts) then it would be simpler to just use their tree, but if they're unwilling and/or slow to merge in your changes then we should probably have our own tree and merge in their changes periodically.
I'm all for working on things as one. So if Oracle is willing to merge, or whoever is currently maintaing it merges, it will be awesome. If they are not interested in upstream development, maybe we should become upstream? I don't know if you have such cycles, but it can be done -- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/
On 7/16/2012 9:09 PM, Colin Charles wrote:
Hi!
On 16 Jul 2012, at 22:08, Daniel Bartholomew wrote:
Elena> But the problem with my modifications is that they currently Elena> live in my work tree, I'm still not sure what is the right way Elena> to handle it. I see that Oracle guys do merges into the main RQG Elena> tree (not Philip), so I guess they kind of "own" it, and I don't Elena> know whether I should merge my changes, especially Elena> MariaDB-specific parts, into the same tree, or request them to Elena> decide whether they want them, or to keep a separate MariaDB Elena> tree. So far I've just been merging the main tree into mine, to Elena> avoid diversion, but not the other way round. Elena> Elena> Any opinions would be appreciated.
If the Oracle people are willing to merge in your changes and additions (including the MariaDB-specific parts) then it would be simpler to just use their tree, but if they're unwilling and/or slow to merge in your changes then we should probably have our own tree and merge in their changes periodically.
I'm all for working on things as one. So if Oracle is willing to merge, or whoever is currently maintaing it merges, it will be awesome. If they are not interested in upstream development, maybe we should become upstream? I don't know if you have such cycles, but it can be done
Oh no, they are doing some development, that's for sure, as they merge their internal tree into the main tree every now and then. I'll find out about merging our changes. Regards, /E
-- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/
Hi Daniel, Colin, Just got an update on the topic in the randgen mailing list: https://lists.launchpad.net/randgen/msg00195.html. In short, RQG documentation will be moved to Github. /E On 7/16/2012 9:12 PM, Elena Stepanova wrote:
On 7/16/2012 9:09 PM, Colin Charles wrote:
Hi!
On 16 Jul 2012, at 22:08, Daniel Bartholomew wrote:
Elena> But the problem with my modifications is that they currently Elena> live in my work tree, I'm still not sure what is the right way Elena> to handle it. I see that Oracle guys do merges into the main RQG Elena> tree (not Philip), so I guess they kind of "own" it, and I don't Elena> know whether I should merge my changes, especially Elena> MariaDB-specific parts, into the same tree, or request them to Elena> decide whether they want them, or to keep a separate MariaDB Elena> tree. So far I've just been merging the main tree into mine, to Elena> avoid diversion, but not the other way round. Elena> Elena> Any opinions would be appreciated.
If the Oracle people are willing to merge in your changes and additions (including the MariaDB-specific parts) then it would be simpler to just use their tree, but if they're unwilling and/or slow to merge in your changes then we should probably have our own tree and merge in their changes periodically.
I'm all for working on things as one. So if Oracle is willing to merge, or whoever is currently maintaing it merges, it will be awesome. If they are not interested in upstream development, maybe we should become upstream? I don't know if you have such cycles, but it can be done
Oh no, they are doing some development, that's for sure, as they merge their internal tree into the main tree every now and then. I'll find out about merging our changes.
Regards, /E
-- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/
_______________________________________________ Mailing list: https://launchpad.net/~maria-docs Post to : maria-docs@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-docs More help : https://help.launchpad.net/ListHelp
https://lists.launchpad.net/randgen/msg00196.html: The RQG documentation has been moved to GitHub https://github.com/RQG/RQG-Documentation/wiki On 7/17/2012 1:33 PM, Elena Stepanova wrote:
Hi Daniel, Colin,
Just got an update on the topic in the randgen mailing list: https://lists.launchpad.net/randgen/msg00195.html. In short, RQG documentation will be moved to Github.
/E
On 7/16/2012 9:12 PM, Elena Stepanova wrote:
On 7/16/2012 9:09 PM, Colin Charles wrote:
Hi!
On 16 Jul 2012, at 22:08, Daniel Bartholomew wrote:
Elena> But the problem with my modifications is that they currently Elena> live in my work tree, I'm still not sure what is the right way Elena> to handle it. I see that Oracle guys do merges into the main RQG Elena> tree (not Philip), so I guess they kind of "own" it, and I don't Elena> know whether I should merge my changes, especially Elena> MariaDB-specific parts, into the same tree, or request them to Elena> decide whether they want them, or to keep a separate MariaDB Elena> tree. So far I've just been merging the main tree into mine, to Elena> avoid diversion, but not the other way round. Elena> Elena> Any opinions would be appreciated.
If the Oracle people are willing to merge in your changes and additions (including the MariaDB-specific parts) then it would be simpler to just use their tree, but if they're unwilling and/or slow to merge in your changes then we should probably have our own tree and merge in their changes periodically.
I'm all for working on things as one. So if Oracle is willing to merge, or whoever is currently maintaing it merges, it will be awesome. If they are not interested in upstream development, maybe we should become upstream? I don't know if you have such cycles, but it can be done
Oh no, they are doing some development, that's for sure, as they merge their internal tree into the main tree every now and then. I'll find out about merging our changes.
Regards, /E
-- Colin Charles, http://bytebot.net/blog/ | twitter: @bytebot | skype: colincharles MariaDB: Community developed. Feature enhanced. Backward compatible. Download it at: http://www.mariadb.org/ Open MariaDB/MySQL documentation at the Knowledgebase: http://kb.askmonty.org/
_______________________________________________ Mailing list: https://launchpad.net/~maria-docs Post to : maria-docs@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-docs More help : https://help.launchpad.net/ListHelp
_______________________________________________ Mailing list: https://launchpad.net/~maria-docs Post to : maria-docs@lists.launchpad.net Unsubscribe : https://launchpad.net/~maria-docs More help : https://help.launchpad.net/ListHelp
On Tue, 17 Jul 2012 14:51:44 +0400 Elena Stepanova <elenst@montyprogram.com> wrote: Elena> Elena> https://lists.launchpad.net/randgen/msg00196.html: The RQG Elena> documentation has been moved to GitHub Elena> Elena> https://github.com/RQG/RQG-Documentation/wiki Ok, thanks. That does change things a bit, at least as far as creating our own set of docs in the KB. For now, I'll update our links to the old RQG docs to point to the new location. Elena: Do you still want a RQG section in the KB for documenting your MariaDB-specific changes? Thanks. -- Daniel Bartholomew Google+ - http://gplus.to/dbart Twitter - http://twitter.com/daniel_bart MariaDB: An Enhanced Drop-in Replacement for MySQL Website - http://mariadb.org Twitter - http://twitter.com/mariadb Google+ - http://gplus.to/mariadb Facebook - http://fb.com/MariaDB.dbms Knowledgebase - http://kb.askmonty.org Monty Program - http://montyprogram.com
On 7/17/2012 4:19 PM, Daniel Bartholomew wrote:
On Tue, 17 Jul 2012 14:51:44 +0400 Elena Stepanova <elenst@montyprogram.com> wrote:
Elena> Elena> https://lists.launchpad.net/randgen/msg00196.html: The RQG Elena> documentation has been moved to GitHub Elena> Elena> https://github.com/RQG/RQG-Documentation/wiki
Ok, thanks. That does change things a bit, at least as far as creating our own set of docs in the KB. For now, I'll update our links to the old RQG docs to point to the new location.
Elena: Do you still want a RQG section in the KB for documenting your MariaDB-specific changes?
I would prefer to keep it, yes (somewhere under Quality, as it is now -- please feel free to change the name if you know a better one). Even if I agree with Oracle/Philip that the code goes into the main tree, I think it's good to have MariaDB-specific features documented somewhere along with other MariaDB documentation. Thanks, /E
Thanks.
participants (3)
-
Colin Charles -
Daniel Bartholomew -
Elena Stepanova