Well, good communications has been and continues to be a problem. I think a certain amount of the problem is that the vast majority of the developers can just talk to one another, so there's no record of the discussion or notification of changes taking place somewhere those of us who aren't at IDA can look at.
This isn't how it works. We seldom see each other except for occasional dinners, movies and other non-computer related activities. The discussions are often computer, programming and Pike-related, but on a conceptual level.
The pike newsletter was a nice idea, but there was only one issue of it.
I though so too (obviously, since I tried to start the newsletter). I just made one as an example and then tried to get an author/editor. If anyone would like to make a new try I think we would all appreciate it.
I have to admit, it would be nice if a changelog were updated _as_ features got added, rather than an afterthought. It's always easier to prune entries than to go back afterwward looking for things that changed.
It is not always appearent what is an important change and what the implications of a change really is. Remember that the change that started this discussion really was very minor in terms of changed code and was more of a bug fix than a feature change.
/ Martin Nilsson (provokatör)
Previous text:
2004-03-29 19:41: Subject: Re: ADD_FUNCTION() macro on pike 7.5 ?
I realize this might be the wrong forum for this, but what problems does it create?
Yes we can... But AFAIK "official" system was optional some day ago. So giving it as mandatory will give us (= Caudium) more problems than it solve.
Well, good communications has been and continues to be a problem. I think a certain amount of the problem is that the vast majority of the developers can just talk to one another, so there's no record of the discussion or notification of changes taking place somewhere those of us who aren't at IDA can look at.
So, until someone at IDA volunteers to take notes, or one of us decides to move to sweden, it's going to continue to be a problem.
I agree, but low level change should not be kept secret... And I still think that changing low level thing on Pike C modules every day will make some developper more and more lazy about Pike...
I don't think that "being public" is the problem. I mean, it's not like there isn't a fine web interface to the changes that do get made. The problem is that no one is "interpreting" the changes and letting the non-core developers know about it. The pike newsletter was a nice idea, but there was only one issue of it.
I am a bit surprised that so much changes inside current pike (that'll maybe be future stable pike ?) are not public ?
I have to admit, it would be nice if a changelog were updated _as_ features got added, rather than an afterthought. It's always easier to prune entries than to go back afterwward looking for things that changed.
How about it? I think that would be a good policy to have: if you add or change functionality, you should have a description of the change or addition in the CHANGELOG. No exceptions.
Where is a changelog about that ? Nothing ?
As always, documentation is a problem. I'm slowly progressing with the tutorial, but that doesn't address the other problems such as c module development. I don't know that complaining more about the problem will do any good, as the people who have the knowledge to write the docs are so busy (understandably) with other things. My solution was to learn how to write modules and then document the process. I've not gotten very far with that yet, though.
Bill
/ Brevbäraren