[drupal-devel] drupal-devel
Hello, I would like to propose a developer.drupal.org, or with any other name. this can be split into: developer.drupal.org/docs developer.drupal.org/blogs developer.drupal.org/cvs where CVS are the CVSlogs blogs are developer blogs and docs is drupaldocs So, drupaldocs is clear, it is nice at drupaldocs.org but IMO it should be a clearer part of the drupal family. Integration and eating dogfood are the keywords. Blogs are a more complex thing. I believe we willnever get all developers to blog there. about half of them have their own "sacred' home where they already blog. So a combination of blog.module and an advanced aggregrator/node_aggregator will server for this part. The CVS logs are nice on drupal.org but IMO are more developer -specific. And this they really belong in the developer subsite. So far the talks. My personal priority lies with themes.drupal.org to get that up and running. So I will not put any more effort in this. I already offered to host a drupaldevelblogs.org (or so) and I will do so, if we decide to leave (for the time being) the developers sites scattered. Leaving it scattered has its advantages too! But that is all I will *do*. Code needs to be written, maintainers must volunteer, ideas must be made reality, and discussion is needed. go ahead :) Bèr Regards, Bèr -- [ Bèr Kessels | Drupal services www.webschuur.com ]
So far the talks. My personal priority lies with themes.drupal.org to get that up and running. So I will not put any more effort in this. I already offered to host a drupaldevelblogs.org (or so) and I will do so, if we decide to leave (for the time being) the developers sites scattered. Leaving it scattered has its advantages too! But that is all I will *do*. Code needs to be written, maintainers must volunteer, ideas must be made reality, and discussion is needed.
It seems to be a much better idea to me to do a Drupal Planet so that developer blogs will get aggregated. So far the Drupal Talk feed does something similar but not in the sense of the other "Planet" sites out there. It does find more (which is not always a "problem"), but it does find less in some cases, not picking up on different Drupal developer blogs. Goba
I like the idea of Drupal hosted developer blogs. Anyone with a CVS account gets one and can use it or not. If we're really lucky, we'll get Hani Suleiman[1] to convert to Drupal and start making fun of us instead of JBoss. [1] http://www.jroller.com/page/fate/ Gabor Hojtsy wrote:
So far the talks. My personal priority lies with themes.drupal.org to get that up and running. So I will not put any more effort in this. I already offered to host a drupaldevelblogs.org (or so) and I will do so, if we decide to leave (for the time being) the developers sites scattered. Leaving it scattered has its advantages too! But that is all I will *do*. Code needs to be written, maintainers must volunteer, ideas must be made reality, and discussion is needed.
It seems to be a much better idea to me to do a Drupal Planet so that developer blogs will get aggregated. So far the Drupal Talk feed does something similar but not in the sense of the other "Planet" sites out there. It does find more (which is not always a "problem"), but it does find less in some cases, not picking up on different Drupal developer blogs.
Goba
On 14-Jul-05, at 2:24 PM, Robert Douglass wrote:
I like the idea of Drupal hosted developer blogs. Anyone with a CVS account gets one and can use it or not. If we're really lucky, we'll get Hani Suleiman[1] to convert to Drupal and start making fun of us instead of JBoss.
This came up before (but I'm too lazy to go find the archived mailing list thread). Why do "developers" only get blogs? e.g. documentation team, marketing team, etc. etc. If you want a blog, set one up external to Drupal.org, and we'll create a Developer Blogs category in the aggregator. Best is if you have a "Drupal" category, and we just syndicate that. If you apply Richard Eriksson's aggregator patch [1], you'll even get an outgoing feed of that category bundle. [1] http://drupal.org/node/9167
Gabor Hojtsy wrote:
So far the talks. My personal priority lies with themes.drupal.org to get that up and running. So I will not put any more effort in this. I already offered to host a drupaldevelblogs.org (or so) and I will do so, if we decide to leave (for the time being) the developers sites scattered. Leaving it scattered has its advantages too! But that is all I will *do*. Code needs to be written, maintainers must volunteer, ideas must be made reality, and discussion is needed.
It seems to be a much better idea to me to do a Drupal Planet so that developer blogs will get aggregated. So far the Drupal Talk feed does something similar but not in the sense of the other "Planet" sites out there. It does find more (which is not always a "problem"), but it does find less in some cases, not picking up on different Drupal developer blogs. Goba
-- Boris Mann http://www.bmannconsulting.com
Boris Mann wrote:
Why do "developers" only get blogs?
Arbitrary injustice ;-)
If you want a blog, set one up external to Drupal.org, and we'll create a Developer Blogs category in the aggregator. Best is if you have a "Drupal" category, and we just syndicate that. If you apply Richard Eriksson's aggregator patch [1], you'll even get an outgoing feed of that category bundle.
Feeds aren't nearly as good as the real thing. I think having the content on-site (searchable, full text, comments, taxonomy) has advantages. Bryght uses blogs very effectively even though you all have personal blogs on external sites as well; think the same on Drupal. Robert
On 14-Jul-05, at 3:31 PM, Robert Douglass wrote:
If you want a blog, set one up external to Drupal.org, and we'll create a Developer Blogs category in the aggregator. Best is if you have a "Drupal" category, and we just syndicate that. If you apply Richard Eriksson's aggregator patch [1], you'll even get an outgoing feed of that category bundle. [1] http://drupal.org/node/9167
Feeds aren't nearly as good as the real thing. I think having the content on-site (searchable, full text, comments, taxonomy) has advantages. Bryght uses blogs very effectively even though you all have personal blogs on external sites as well; think the same on Drupal.
This whole discussion is also out-of-scope for the development list...let's take to Docs if you want to continue discussing. OK, then I want to see it done right: * anyone that wants a blog on Drupal.org applies for it (developer, documentation, marketing, etc.), and has their role upgraded to one that allows having their own blog * apply a free-tagging vocabulary to blogs * enable the "recent blogs" block Some devil's advocate questions: * a "real" blog allows for images. This also means giving all blog contributors image upload access (ideally with terms set to "none" so they don't show up in the galleries...). * if there are a *lot* of blogs, there needs to be a way to "bubble up" the popular posts (by hits/by comments/by rating) * there will need to be a stated and displayed policy that the posts are the opinions of posters only, not the Drupal community as a whole * one link in a Drupal blog will have huge weight in terms of search ranking, so there is a lot of incentive to game the system Did I mention enabling stories, putting them in a moderation queue, and having more article style content? Yes, I did, a couple of times, since this allows anyone to contribute, will lead to higher quality content, and allows for moderation before posting. -- Boris Mann http://www.bmannconsulting.com
On Thu, Jul 14, 2005 at 10:02:18PM +0200, B?r Kessels wrote:
So, drupaldocs is clear, it is nice at drupaldocs.org but IMO it should be a clearer part of the drupal family. Integration and eating dogfood are the keywords.
+1
Blogs are a more complex thing. I believe we willnever get all developers to blog there. about half of them have their own "sacred' home where they already blog. So a combination of blog.module and an advanced aggregrator/node_aggregator will server for this part.
I'll readily put my Drupal blogs on a central site (assuming it is stable and looks nice) since I don't want to mix up personal webblogging with techy stuff which some of my friends wouldn't want to see. However, if I were starting a Drupal blog I'd like full control of the Drupal install as a testing/demoing environment. Which of course wouldn't work if we had multiple developers on the same Drupal install. And there is the whole I'm not a blogger and don't have a blog [yet] thing. Didn't someone, not in the "core drupal community," set up an aggregator awhile ago?
The CVS logs are nice on drupal.org but IMO are more developer -specific. And this they really belong in the developer subsite.
If we were separating sites (I'm not sure if I am in favor of this or not) I would think projects would have to be moved too (with download and support requests left on the main site). SOme forums would be moved. I think the best thing to do at this point might be to start a central developer blog, on drupal.org or not, and see how developers use it and let moving things happen as it becomes clear they are needed rather than building out all the infastructure up front.
So far the talks. My personal priority lies with themes.drupal.org to get that up and running. So I will not put any more effort in this. I already offered to host a drupaldevelblogs.org (or so) and I will do so, if we decide to leave (for the time being) the developers sites scattered. Leaving it scattered has its advantages too!
In my brief exploration of that trendy webapp framework, Ruby on Rails (RoR), I saw that almost everything is decentralized. The main website for them is basically a central place linking out to many other places, especially weblogs. Something I will be thinking about as well is potential usability problems with blogs, as seen recently on this list. And I hate the term 'blog' and variations of it. -Neil
On 7/15/05, neil@civicspacelabs.org <neil@civicspacelabs.org> wrote:
On Thu, Jul 14, 2005 at 10:02:18PM +0200, B?r Kessels wrote:
So, drupaldocs is clear, it is nice at drupaldocs.org but IMO it should be a clearer part of the drupal family. Integration and eating dogfood are the keywords.
+1
Blogs are a more complex thing. I believe we willnever get all developers to blog there. about half of them have their own "sacred' home where they already blog. So a combination of blog.module and an advanced aggregrator/node_aggregator will server for this part.
We can have a planet.drupal.org. Maybe we can provide blog hosting to people without homes; and aggregate them along with the others with already existing blogs. I would prefer if the drupal-based companies take care of this; it would benefit their publicity, and keep away hosting hassles from drupal.org. blogs.bryght.com / blogs.civicspace.org / blogs.anybody? I'm only unsure about the inclusion policy: what is the eligibility criteria for getting added to planet.drupal?
I'll readily put my Drupal blogs on a central site (assuming it is stable and looks nice) since I don't want to mix up personal webblogging with techy stuff which some of my friends wouldn't want to see.
I'd rather use tags / categories; like i do. That way even my feed to planet.drupal can be a drupal-posts-only feed.
So far the talks. My personal priority lies with themes.drupal.org to get that up and running. So I will not put any more effort in this. I already offered to host a drupaldevelblogs.org (or so) and I will do so, if we decide to leave (for the time being) the developers sites scattered. Leaving it scattered has its advantages too!
+1. Decentralized == robust. -Arnab http://arnab.org
participants (6)
-
Arnab Nandi -
Boris Mann -
Bèr Kessels -
Gabor Hojtsy -
neil＠civicspacelabs.org -
Robert Douglass