Forum OpenACS Development: Re: Some ideas about package structure ... comments?

Collapse
Posted by Joel Aufrecht on
Two points:

1) Since the special feature about /resources is that it's not permission-checked, could the name reflect that?  What about /public-resources or /public?

2) Can we make this the first TIP?  (Or OIP?)  One quick-and-dirty way to support the OIP process technologically might be a new forum.  Anybody can post, first post in a thread must be a full, formal OIP proposal; then the thread has a week or two (or whatever is in the OIP plan - we should link that in the forum title) to accumulate yes and no votes from the Core Team.  I'm sure this process has many drawbacks compared to a new custom package or a special version of Bugs, but are any of those drawbacks fatal?  If not, I hope we do this or something similar to get momentum in a formal OIP process.