Hi everybody!
I'm the maintainer of video.module .
We have realeased a good 4.6 video.module then the past weeks worked
hard for the new 4.7 version (MAIN).
Now we have a patch for a bug in the 4.6 branch but I'm not able to
submit it to the 4.6 branch
I tried it but not luky with cvs... I'm getting:
cvs commit: sticky tag `DRUPAL-4-6' for file `video.module' is not a branch
Does someone could explain how can I do it?
Thanks
Fabio
Hi!
grep "function theme_" *module|wc -l
55
grep -B1 "function theme_" *module|grep \*/|wc -l
17
If my greps are correct, then there are 38 theme functions in core now
which are undocumented.
Regards
NK
Subject: Re: [development] Encouraging Collaboration
>>> IMHO Drupal is going through some growing pains - Dries pointed this
>>> out
>>> in Amsterdam when he talked about the phenominal growth of the
>>> community. There is a lot of work to be done.
>>
>>
>> Correct. Bear in mind that there always have been growing pains, and
>> that there always will be growing pains. It's perfectly normal.
>> What matters is how we counter the growing pains.
>
>agreed. However as the speed of growth accelerates it will place new
>strains on the community - IMHO.
Not really. It's the same strain it's been for the two years I've been playing. This cycle has repeated several times during that time period as more people joined. Each active participant we get brings subtle and dramatic changes to the project. Sometimes the change is in doing the invisible stuff that paves the way for the dramatic visible later. Few see the groundwork, just the result. We probably need to do better writeups on the scale and scope of the work involved when any more new features get added/introduced to Drupal.org. People who are not involved miss a sense of understanding at the work involved by all the contributors.
It seems if you can last about six months, then you tend to begin to understand the scale and scope of what is going on. :)
>> To answer your questions:
>>
>> 1. Download page: we are working on improving the download page.
> great is there a discussion about this somewhere?
I thought it was in the archives, I easily could be wrong, I know it's in writing somewhere.
>> 3. Who is this product for? Drupal is for users who want to setup a
>> website _and_ for developers who need a platform.
>
>That's reasonable - but pretty ambitious. There aren't many products
>out there that are developers tools as well as non-web developers
>tools. As a matter of fact I can't think of any off hand at all. This
>doesn't mean that Drupal can't do it - it just means that it is new
>territory (the fun kind).
How is this different that what we have now? I am not a developer. Two years ago I needed to setup a website and never left. This was with no knowledge of php or MySQL and I was able with minimal assistence using the documentaiton in the forums and the install.txt to do so on an IIS server. I undertstand MySQL a bit better now, php marginally (enough to play with phpTemplate but that's it).
Where we are making lots of progress every release is in making it even easier for the non developer. There is documentation in the various snippets sections of the handbook that is improving bit by bit every month.
>> 4. How do things get done around here? Either you do it yourself, or
>> you work on it with others.
>>
>> So we are working on the growing pains -- even though you might not
>> have noticed.
>
>no I actually have noticed - and everyone is doing a great job. I did
>not mean to be negative nor critical - sorry if it came off that way.
You didn't to me, but the really weird thing is, that is absolutly is the way things get done here.
The way you find this out is to be involved as you are now. Track developement, say hi in #drupal sometimes.
Submit patches, documentation, answer forums questions, etc.
So you've noticed. What have you noticed? I'm curious. Perhaps it's something that can be mentioned in the newsletter because we've all forgotten or missed it because we were involved.
Don't forget, have fun too.
-sepeck
What if we set up a parallel contributions repository using a different
SCM which we would optionally put our modules in? If a few of the large
contrib projects moved we could get a good idea of how well it works
without risking productivity on core.
This of course would be horribly technically complex since the cvs
module and release scripts would have to deal with two systems in parallel.
--
Neil Drumm
http://delocalizedham.com/
Hello,
http://drupal.org/node/36352
Currently search is broken in HEAD. The bug is know, two possibile fixes
are known and simple. But which one to choose is a bit political issue
;)
Anyway, this bug blocks at least 1 other patch, so maybe some people can
take a look at the url? I probably won't like the decision, but any
decision is better then no decision at all.
--
Piotrek
irc: #debian.pl
Mors Drosophilis melanogastribus!
Hi,
With all this talk about different scm's. I have been using darcs
(darcs.net) and I use it for a number of projects.
Basically darcs is a distributed similar to bzr or git. I find that it
works well, and has a number of features that I like, such as patch
picking (means you can select which patches you take) and when you are
recording a change set you can pick what changes are going to be
included into the patch.
Using tailor I have gone one step further and I have set up a darcs
drupal repository which people can download from. To get the cvs version
of drupal you can execute the following command.
darcs get --partial http://repos.heydon.com.au/drupal
this will get the latest version of the drupal repository.
I have set it up so this repository will be synced with the drupal cvs
repository every 6 hours.
To update you local repository you just do the following in the drupal
directory
darcs pull -a
and it will download all the new patches that have been applied.
When you have made changes to your copy of drupal you can then do a
darcs whatsnew
and it will show you all the changes, and to record these use the
following
darcs record
and you can then choose which changes will be included in the patch.
I also have the web frontend going which can be gotten to at the
following.
http://repos.heydon.com.au/darcsweb/darcsweb.cgi?r=drupal;a=summary
which is a little ugly at the moment as tailor doesn't really look that
nice. There is also some problem ATM with the web frontend, but I think
this is because of the version of python or something that dreamhost has
done to python.
Let me know what you think.
Gordon.
On 11/16/05, Richard Archer <drupal.org(a)juggernaut.com.au> wrote:
> If I wanted to check out all the contributions, how much
> disk space and bandwidth would I be looking at?
>
Here's my mirrors:
$ du -sh drupal-cvs/*
52M drupal-cvs/contrib-4.6
119M drupal-cvs/contributions
2.2M drupal-cvs/drupal
2.0M drupal-cvs/drupal-4.6
--
e
one inch frame: http://eafarris.al.umces.edu/
I really like the approaches implemented in drupal.js.
But I've been wondering--would we do better to use the now widely supported,
and excellently designed, Prototype library (http://prototype.conio.net/ --
see documentation e.g. at
http://www.sergiopereira.com/articles/prototype.js.html) instead?
The advantages would be that we'd be using a well supported open source
library, rather than our own (nice, but not used elsewhere) solution. Doing
so would allow Drupal developers to use the ever-expanding range of
Prototype-based libraries, including:
moofx http://moofx.mad4milk.net/
behaviour http://bennolan.com/behaviour/
scriptaculous http://script.aculo.us
We'd still need some custom drupal methods, but we could reduce them to a
minimum.
We could also draw on other open source CMS etc. softwares using Prototype,
e.g, Ruby on Rails.
Doing so would require some refactoring of our existing javascript
(autoexpand, etc.), but really not so much. And we'd be able to take
advantage of some great features and methods in Prototype and its related
libraries.
Prototype and its relatives are "MIT style" licensed, presumably GPL
compatible,
http://www.gnu.org/philosophy/license-list.html#GPLCompatibleLicenses.
Thoughts?
Hello,
I ma not sure if I stumbled on a critical bug or if I am just reading teh
wrong docs. Or if I am just being stupid.
I use this: cache_set('gallery_'. $node->nid, $gallery, CACHE_TEMPORARY);
To define a cache chnuk for every $gallery object ($gallery is an array with
all $image node objects preloaded)
But, when I do so everything breaks enomously. I get a fatal error (something
with unlocked tables)
Any help would be appreciated. And I really hope this is not something broken
in core, because we could easily do without new bugs every day. :)
--------------------------------------
Warning: sprintf(): Too few arguments
in /var/www/staging/includes/database.inc on line 158
Fatal error: Query was empty query:
in /var/www/staging/includes/database.mysql.inc on line 99
Fatal error: Table 'sessions' was not locked with LOCK TABLES query: UPDATE
sessions SET uid = 2, cache = 0, hostname = '81.11.226.132', session =
'messages|a:0:{}watchdog_overview_filter|s:3:\"all\";', timestamp =
1132238132 WHERE sid = '06ade4989cd77ea1fec28bcb8ac426c6'
in /var/www/staging/includes/database.mysql.inc on line 99
Warning: Unknown(): A session is active. You cannot change the session
module's ini settings at this time. in Unknown on line 0
--------------------------------------------
Bèr
--
[ Bèr Kessels | Drupal services www.webschuur.com ]