Where should it be documented? I set up Confluence exactly like the other JIRA installations using the same directory structures, startup scripts, tomcat setup, and logging policies. If it is a matter of not enough volunteers to administrate it, let me know and I'll get a few other people. I'm willing to write whatever docs or build whatever team size infrastructure feels necessary to ensure Confluence is well-supported.
Don On 11/9/06, Roy T. Fielding <[EMAIL PROTECTED]> wrote:
On Nov 9, 2006, at 10:52 AM, Don Brown wrote: > What exactly makes something a part of the "official" ASF > infrastructure? I thought it was that a member of Infrastructure had > volunteered to maintain it, and if that's the case, Confluence is > indeed a part of the "official" ASF infrastructure since I, as a > member of ASF and Infrastructure, have volunteered to maintain it. When infrastructure votes to maintain it for as long as the projects wish to use it, then it is infrastructure. Right now, Confluence is just an experiment and we made that abundantly clear. The first two people who promised to maintain it disappeared immediately after setup. One new person is not sufficient to maintain anything, even though the effort is appreciated. To be maintainable, it must be possible for the entire team to maintain the working instance. That means documenting what to do when it breaks, preferably somewhere that is accessible when it happens to be broken (like under the infrastructure subversion). ....Roy --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
