On 8 December 2015 at 21:45, David Evans <[email protected]> wrote: > Are there specific topics that should be addressed to you and others to admin > or should we just use the admin address > for everything?
> In particular, are there issues that can only be handled by the other admins > or do you have pretty much full access to > the various components (buildbots, web server/trac, svn repo, etc)? Apropos this what would you think about hosting the trac setup on the repository along with the www/ tree? This way patches to Trac could be submitted as well. On a broader view I think that if possible we should store the complete sourcecode of the website, trac and/or other components, in the repo. The running Trac is likely to have its codebase saved in a VCS anyway and having it in the public repo would allow patches submission, think of plugins or custom patches to them. I don't know how macosforge is managed, is there any obstacle (say security concern or so) in sharing the currently running code? > These features have been broken for quite some time and are useful to the > developer community. I know you have a lot > on your plate right now but it would be nice if their priority could be > escalated. Well, on the fun side Ryan still took time to properly format my wiki syntax in the ticket so I'd say it's not too bad. ;-) -- Andrea _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
