Forum OpenACS Development: Re: social networking functionality for acs-subsite? TIP?

Collapse
Posted by Don Baccus on
The TIP rules, as I understand them, don't have this requirement[1].

OK, fine, we relaxed that requirement (it was discussed in the beginning).

Great, you get to start a TIP.

It doesn't mean you get to hack core without TIP'ing.

I don't think I'm special. I really didn't think this social networking thing was worth distracting the OCT from other work. It seems like a very small, incrementally positive thing. Nothing more. As an afterthought, based on your reaction, I'm wondering if there is some kind of MIT/facebooky vs. MIT.alt feud thing motivating this dialog.

Oh, good grief, Torben, stuff a sock in the conspiracy theory orifice.

You've been told you need to TIP before adding functionality to core.

This is not new.

I'm fairly confident, yet remain open-minded and do not assume to understand all core-developer issues

This statement alone justifies our policy that changes of this sort require a TIP.

Create or show me the package, and I'll move it there.

That's not how it works, Torben.

Remove your commits. We'll discuss afterwards if you choose to TIP.

Collapse
Posted by Don Baccus on
As an afterthought, based on your reaction, I'm wondering if there is some kind of MIT/facebooky vs. MIT.alt feud thing motivating this dialog.

1. TIP'ing is our process, well established, and no secret.

2. You have a personal habit of breaking stuff in core and others have had to spend time fixing it in the past ... while this doesn't mean we'll be more strict in our requiring you to TIP than we are on ourselves, it does mean that your thinking that we'll be *more* lax than we are on ourselves or others just ain't going to happen.

Hi Don,

you wrote: "You have a personal habit of breaking stuff in core and others have had to spend time fixing it in the past ..."

I supposed it could be viewed that way. I have mistakenly broken core functionality from inadvertently breaking package.info XML standards so the core couldn't read it --twice.

Yet, to my defense, I've also taken initiative to help fix things that were inadvertently broken by code improvements from others, digging in where I had little understanding. The outcomes were positive, even if my own net contribution was only in helping others to see the problem and motivating them to fix it.

I will TIP all core changes, including the one in dispute. Sorry for the confusion on removing the code.. I'm working on it..