[drupal-devel] Hello and SoC Proposal
Hi folks, I'm Fabiano Sant'Ana, working in a WebDAV Interface for Drupal in SoC, may be you already know me from #Drupal@freenode.net (my nick is wundo). You can read my proposal here: http://wundo.net/soc/ Please comment and suggest changes. Thank you, Fabiano Sant'Ana.
On Sun, 3 Jul 2005, Fabiano Sant'Ana wrote:
I'm Fabiano Sant'Ana, working in a WebDAV Interface for Drupal in SoC, may be you already know me from #Drupal@freenode.net (my nick is wundo). You can read my proposal here: http://wundo.net/soc/ Please comment and suggest changes.
I have to admit that my knowledge of webdav is rather limited. To me it is mainly http on steroids. In your proposal you describe that you want to use webdav as a backup-tool for Drupal for both the files and the database. While I am quite sure that this would work for the files (if they are in a webdav enabled directory), I am surprised that it would work for the database. I don't think that webdav has a way to access the database. Please let me know if I am wrong. I see the same problem for usage of webDAV as a remote content creation tool. We already have various blogging methods for this. The main use I see for webdav is for massuploading verious forms of non-text data that will be imported into Drupal through the execution of the cron hook. It is probably also usefull to allow module upload through webdav and the node_import module. This module accept a csv file as input and currently relies on http post upload. I can imagine that webDAV could be used to upload larger csv files more efficiently. Adding node export in a similar way would allow for easier sharing of content. Just a couple of thoughts. Cheers, Gerhard
Hi Fabiano, I think the problem with your proposal is that you don't really say what the WebDAV API is, what functions it will have. It is possible that what you have in mind will satisfy Gerhard's concerns (his thoughts on how we might use this were exactly what mine were). Please describe the actual interface (method signatures) in more detail. cheers, Robert PS. Please post to PlanetSoC.com as well. Gerhard Killesreiter wrote:
On Sun, 3 Jul 2005, Fabiano Sant'Ana wrote:
I'm Fabiano Sant'Ana, working in a WebDAV Interface for Drupal in SoC, may be you already know me from #Drupal@freenode.net (my nick is wundo). You can read my proposal here: http://wundo.net/soc/ Please comment and suggest changes.
I have to admit that my knowledge of webdav is rather limited. To me it is mainly http on steroids.
In your proposal you describe that you want to use webdav as a backup-tool for Drupal for both the files and the database.
While I am quite sure that this would work for the files (if they are in a webdav enabled directory), I am surprised that it would work for the database. I don't think that webdav has a way to access the database. Please let me know if I am wrong.
I see the same problem for usage of webDAV as a remote content creation tool. We already have various blogging methods for this.
The main use I see for webdav is for massuploading verious forms of non-text data that will be imported into Drupal through the execution of the cron hook.
It is probably also usefull to allow module upload through webdav and the node_import module. This module accept a csv file as input and currently relies on http post upload. I can imagine that webDAV could be used to upload larger csv files more efficiently. Adding node export in a similar way would allow for easier sharing of content.
Just a couple of thoughts.
Cheers, Gerhard
Hi Fabiano -- Congratulations on being selected for SoC -- welcome aboard. On 3-Jul-05, at 6:50 AM, Fabiano Sant'Ana wrote:
I'm Fabiano Sant'Ana, working in a WebDAV Interface for Drupal in SoC, may be you already know me from #Drupal@freenode.net (my nick is wundo). You can read my proposal here: http://wundo.net/soc/ Please comment and suggest changes.
Looks good. I have some suggestions/questions about the webdav_upload.module. Currently, files are attached to individual nodes. So, it would seem that the WebDAV view has to mirror this somehow. Would this appear as a "node" folder, filled with folders that have numbers that correlate to node IDs? Or a folder called upload (for the name of the module). This should be part of the work of designing the API. It might be easier to work with the filestore2 module, because one node == one file. Yes, I know it doesn't use the file API, but it's the closest thing to document management that Drupal has. Other Drupal developers: there has been lots of discussion about file issues lately. It sucks that the only way to "re-use" binary files within Drupal is to link to them. Should we re-examine this for 4.7? Maybe the Google Sitemap student can do some file API work? Lastly: it would be good to have all proposals on Drupal.org, linking to the student's site/blog/whatever if they have one. Fabian -- I copy/pasted your proposal here -- http://drupal.org/node/26292 -- you can edit to fix formatting if you like. P.S. Robert -- http://www.planetsoc.com/ -- *nice* work!!! However, the link straight there from the Contributor Links is a little confusing. Maybe have it link locally to the handbook, and link out to Planet SoC from there? I'm also going to ask the docs team to make a badge for SoC to rotate on the front page. -- Boris Mann http://www.bmannconsulting.com
Other Drupal developers: there has been lots of discussion about file issues lately. It sucks that the only way to "re-use" binary files within Drupal is to link to them. Should we re-examine this for 4.7? Maybe the Google Sitemap student can do some file API work?
Very fine suggestion.
P.S. Robert -- http://www.planetsoc.com/ -- *nice* work!!! However, the link straight there from the Contributor Links is a little confusing.
Which link are you talking about? Maybe have it link locally to the handbook, and link out to
Planet SoC from there?
Didn't follow that either, though might be related to my previous question. I'm also going to ask the docs team to make a
badge for SoC to rotate on the front page.
Super idea. Give these guys some spotlight. Robert
On 3-Jul-05, at 12:43 PM, Robert Douglass wrote:
P.S. Robert -- http://www.planetsoc.com/ -- *nice* work!!! However, the link straight there from the Contributor Links is a little confusing.
Which link are you talking about?
On Drupal.org, if you have the "Contributor links" block enabled, the very bottom link is "Summer of Code", and links directly to www.planetsoc.com -- it should link to http://drupal.org/ googlesummerofcode2005 instead. -- Boris Mann http://www.bmannconsulting.com
P.S. Robert -- http://www.planetsoc.com/ -- *nice* work!!! However, the link straight there from the Contributor Links is a little confusing.
Which link are you talking about?
I added a link to the 'contributors block' which one can enable from his personal settings. Planetsoc.com is nice (it still has some rough edges) but keeping the SoC information in the Drupal handbook current is important too. I can change that link based on suggestions, or I can remove it completely and link to the pages in the handbook once they are up to date. -- Dries Buytaert :: http://www.buytaert.net/
On 3-Jul-05, at 1:59 PM, Dries Buytaert wrote:
P.S. Robert -- http://www.planetsoc.com/ -- *nice* work!!! However, the link straight there from the Contributor Links is a little confusing.
Which link are you talking about?
I added a link to the 'contributors block' which one can enable from his personal settings. Planetsoc.com is nice (it still has some rough edges) but keeping the SoC information in the Drupal handbook current is important too. I can change that link based on suggestions, or I can remove it completely and link to the pages in the handbook once they are up to date.
I updated this slightly, and yes, please point to the local http:// drupal.org/googlesummerofcode2005 page -- more info can be added/ edited there. And yes, this is likely a "docs" or infrastructure discussion, too. -- Boris Mann http://www.bmannconsulting.com
On 03 Jul 2005, at 23:14, Boris Mann wrote:
I updated the contributors block. -- Dries Buytaert :: http://www.buytaert.net/
participants (5)
-
Boris Mann -
Dries Buytaert -
Fabiano Sant'Ana -
Gerhard Killesreiter -
Robert Douglass